Execution Profile

garnet-org/action

Recorded at the kernel by Garnetfor commit 6abe4bf (merge ref)

CI/build-and-verify

run 320562697202026-08-17 18:43 UTC

Execution chains

5 destinations · 5 processes

systemd
- hosted-compute-agent
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2403 · node]step: Install dependencies
        registry.npmjs.org104.16.11.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2371 · node]
        api.github.com140.82.112.5:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd3541973371[1901 · provjobd3541973371]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - hosted-compute-watchdog-prod-iad-01.githubapp140.82.114.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
- systemd-resolved[504 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1572 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-org/action

WorkflowCI

Jobbuild-and-verify

Run ID32056269720

Profile UUID01a01109-3cb9-758c-ba54-fe0a509e9d1c

Commit SHA6abe4bf0aa313242b1e2b2c2d4348fd8ac250d2c(merge ref)

Refrefs/pull/134/merge

Timestamp2026-08-17 18:43:29 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.