Execution Profile

garnet-labs/ghaw-garnet-reference

Recorded at the kernel by Garnetfor commit 32616e1 (merge ref)

CI/test

run 41724401762

Execution chains

6 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2423 · node]
            • dash
              • node[2436 · node]
                • storage.googleapis.com142.250.114.207:443 (https) · tcp
                • localhost127.0.0.53:53 (dns) · udp(dns resolver)
            • registry.npmjs.org104.16.9.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1979508239[1879 · provjobd1979508239]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-gccus02-02.githubapp140.82.114.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • python3.12
      • python3.12[1229 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[498 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/ghaw-garnet-reference
WorkflowCI
Jobtest
Run ID41724401762
Profile UUID01a1a35e-dafc-77da-9438-781a3c2f2a4b
Commit SHA32616e10fb4f862ac01b1da2e2d13a62f3873f3d(merge ref)
Refrefs/pull/8/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