Execution Profile

garnet-labs/ghaw-garnet-reference

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

CI/test

run 41715962903

Execution chains

4 destinations · 4 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • node[2687 · node]
          • dash
            • node[2700 · node]
              • storage.googleapis.com192.178.142.207:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • registry.npmjs.org104.16.5.34:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[523 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1395 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/ghaw-garnet-reference
WorkflowCI
Jobtest
Run ID41715962903
Profile UUID01a1a32c-6243-791f-bac4-3a3fc9329566
Commit SHAd4fcc0a2063903255faa4a3c715c5a22212b9b1b(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