Execution Profile

garnet-labs/ghaw-garnet-reference

Recorded at the kernel by Garnetfor commit 9e507f0 (merge ref)

CI/test

run 42900627127

Execution chains

4 destinations · 5 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker[2814 · Runner.Worker]
        • bash
          • node[3329 · node]
            • dash
              • node[3342 · node]step: <unknown>
                • storage.googleapis.com142.251.33.219:443 (https) · tcp
                • localhost127.0.0.100:53 (dns) · udp(dns resolver)
            • registry.npmjs.org104.16.5.34:443 (https) · tcp
            • localhost127.0.0.100:53 (dns) · udp(dns resolver)
        • localhost127.0.0.100:53 (dns) · udp(dns resolver)
    • systemd-resolved[2488 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.14
      • python3.14[1470 · python3.14]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/ghaw-garnet-reference
WorkflowCI
Jobtest
Run ID42900627127
Profile UUID01a1c743-1c7e-70bb-ab80-f4955b01d1f6
Commit SHA9e507f05a93dcb4cf89a81d1e9f829094e6d1311(merge ref)
Refrefs/pull/26/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