Execution Profile

garnet-labs/codex

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

blocking-ci/garnet

run 40987638780

Execution chains

6 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker
          • Runner.Worker
            • Runner.Worker[2720 · Runner.Worker]step: Fetch locked Rust dependencies
              • github.com140.82.112.3:443 (https) · tcp
              • dualstack.k.sni.global.fastly.net151.101.162.137:443 (https) · tcpalso recorded: fastly-index.crates.io, index.crates.io
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • bash
            • cargo[2720 · cargo]step: Fetch locked Rust dependencies
              • github.com140.82.112.3:443 (https) · tcp
              • dualstack.k.sni.global.fastly.net151.101.162.137:443 (https) · tcpalso recorded: fastly-index.crates.io, index.crates.io
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • sudo[2084 · sudo]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-iad-02.githubapp140.82.112.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • systemd[732 · systemd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/codex
Workflowblocking-ci
Jobgarnet
Profile UUID01a18a7f-6a8a-7b17-8798-a990b5489000
Refrefs/pull/36/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.