Execution Profile

garnet-org/action

Recorded at the kernel by Garnetfor commit 668c8ac (merge ref)

CI/build-and-verify

run 31537762260

Execution chains

5 destinations · 6 processes
  • systemd
    • hosted-compute-agent[1975 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2486 · node]step: Install dependencies
              • registry.npmjs.org104.16.0.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2454 · node]
            • api.github.com140.82.114.5:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3925660716[1992 · provjobd3925660716]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • systemd-resolved[520 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1417 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Run ID31537762260
Profile UUID019ff2b7-80bd-7dc1-a529-c335406c3ec6
Commit SHA668c8acd7b7340328e7dd4bf176bacae9d98a192(merge ref)
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.

Read the docs