Execution Profile

garnet-org/action

Recorded at the kernel by Garnetfor commit 682c02e (merge ref)

CI/build-and-verify

run 31838253234

Execution chains

7 destinations · 7 processes
  • systemd
    • hosted-compute-agent[1880 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker[1988 · Runner.Worker]
          • bash
            • node[2426 · node]step: Install dependencies
              • registry.npmjs.org104.16.2.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2393 · node]
            • api.github.com140.82.116.6:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd778426385[1895 · provjobd778426385]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • glb-2a3c35-public-internal.githubapp.com140.82.112.23:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-01.githubapp
      • 140.82.112.24:443 (https) · tcp
    • systemd-resolved[559 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1212 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Profile UUID01a001f9-36f6-7f3b-8e12-e6cd8b25297e
Refrefs/pull/130/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.