Execution Profile

garnet-org/action

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

CI/build-and-verify

run 37828369312

Execution chains

5 destinations · 7 processes
  • systemd
    • hosted-compute-agent[1881 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker[1954 · Runner.Worker]
          • bash
            • node[2403 · node]step: Install dependencies
              • registry.npmjs.org104.16.8.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2371 · node]
            • api.github.com140.82.114.5:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2264084766[1900 · provjobd2264084766]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • python3.12
      • python3.12[1233 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[405 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Profile UUID01a11ce2-04d4-7f4d-9987-24de1ad34d77
Refrefs/pull/181/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.