Execution Profile

garnet-labs/ghaw-garnet-reference

Recorded at the kernel by Garnetfor commit 5cbcb66 (merge ref)

CI/test

run 42173569203

Execution chains

5 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2644 · node]step: <unknown>
            • dash
              • node[2689 · node]
                • storage.googleapis.com172.253.63.207:443 (https) · tcp
                • localhost127.0.0.53:53 (dns) · udp(dns resolver)
            • registry.npmjs.org104.16.4.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd3780133858[2109 · provjobd3780133858]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-02.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • python3.12
      • python3.12[1395 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[519 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/ghaw-garnet-reference
WorkflowCI
Jobtest
Run ID42173569203
Profile UUID01a1af82-95b9-7a9d-bb73-45fe4dd8b462
Commit SHA5cbcb66ecc953caf40e45ef74528873acead491f(merge ref)
Refrefs/pull/22/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