Execution Profile

garnet-org/action

Recorded at the kernel by Garnetfor commit eee3a96 (merge ref)

CI/build-and-verify

run 40734002915

Execution chains

5 destinations · 7 processes
  • systemd
    • hosted-compute-[2088 · hosted-compute-]
      • Runner.Listener
        • Runner.Worker[2904 · Runner.Worker]
          • bash
            • node[3366 · node]
              • registry.npmjs.org104.16.1.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[3333 · node]
            • api.github.com140.82.113.5:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • sudo[2109 · sudo]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • glb-2a3c35-public-internal.githubapp.com140.82.114.24:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-02.githubapp
      • glb-2a3c35-public-internal.githubapp.com140.82.114.24:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-02.githubapp
    • systemd-resolve[543 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • python3
      • python3[1902 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Profile UUID01a18383-892c-7840-813b-055b76738c6b
Refrefs/pull/197/merge
Timestamp

The record is egress-centric; processes without recorded egress do not appear.

Put the record on your pull requests

Garnet records what your code actually did when it ran — one step in your GitHub Actions workflow.