Execution Profile

garnet-org/action

Recorded at the kernel by Garnetfor commit 1d00a59 (merge ref)

CI/build-and-verify

run 359289857062026-09-23 22:34 UTC

Execution chains

5 destinations · 6 processes

systemd
- hosted-compute-agent
  - Runner.Listener
    - Runner.Worker[1907 · Runner.Worker]
      - bash
        node[2365 · node]step: Install dependencies
        registry.npmjs.org104.16.8.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2330 · node]
        api.github.com140.82.114.5:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd2941790638[1851 · provjobd2941790638]
      - 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
- systemd-resolved[415 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1238 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-org/action

WorkflowCI

Jobbuild-and-verify

Run ID35928985706

Profile UUID01a0d067-913a-703a-ae8f-71d02ee44282

Commit SHA1d00a59f0a22b7f732d9425181a52d3fd7bb70ad(merge ref)

Refrefs/pull/174/merge

Timestamp2026-09-23 22:34:02 UTC

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.