Execution Profile

garnet-labs/garnet-runtime-review-reference

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

garnet-dependency-replay/record

run 33937541982

Execution chains

4 destinations · 4 processes
  • systemd
    • hosted-compute-agentsudo
      • provjobd1853667618[1815 · provjobd1853667618]
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • hosted-compute-watchdog-prod-eus-02.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • python3.12
      • python3.12[1109 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[466 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[652 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/garnet-runtime-review-reference
Workflowgarnet-dependency-replay
Jobrecord
Run ID33937541982
Profile UUID01a06f46-f4cd-73a8-87a8-d80fa592a1f6
Commit SHAc64c913069705808c6a4288ad329337ea9e3070e(merge ref)
Refrefs/pull/31/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