Execution Profile

garnet-labs/codex

Recorded at the kernel by Garnetfor commit 68029fd (merge ref)

blocking-ci/garnet

run 32343464709

Execution chains

7 destinations · 5 processes
  • systemd
    • hosted-compute-
      • Runner.ListenerRunner.Worker
        • bash
          • cargo[2659 · cargo]step: Fetch locked Rust dependencies
            • github.com140.82.114.3:443 (https) · tcp
            • dualstack.k.sni.global.fastly.net146.75.106.137:443 (https) · tcpalso recorded: fastly-static.crates.io, static.crates.io
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • sudo[2106 · sudo]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-iad-01.githubapp140.82.112.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • cargo[2659 · cargo]step: Fetch locked Rust dependencies
          • github.com140.82.114.3:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolve[499 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • python3
      • python3[1774 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/codex
Workflowblocking-ci
Jobgarnet
Profile UUID01a01e0a-cafd-7667-8067-cf3d94249615
Refrefs/pull/15/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.