Execution Profile

garnet-org/action

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

CI/build-and-verify

run 314549850722026-08-11 03:18 UTC

Execution chains

5 destinations · 6 processes

systemd
- hosted-compute-agent
  - Runner.Listener
    - Runner.Worker[2075 · Runner.Worker]
      - bash
        node[2524 · node]step: Install dependencies
        registry.npmjs.org104.16.10.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2492 · node]
        api.github.com140.82.116.5:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - provjobd2737580018[2019 · provjobd2737580018]
      - localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - glb-p4a577-public-internal.githubapp.com20.75.202.224:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-eus-02.githubapp
- systemd-resolved[560 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp
- python3.12
  - python3.12[1353 · python3.12]
    - 168.63.129.16:32526, 80 (http) · tcp

Run details

Repositorygarnet-org/action

WorkflowCI

Jobbuild-and-verify

Run ID31454985072

Profile UUID019feed4-70e3-7103-a93e-f006436d54b6

Commit SHAb504f5d41f444f08dd49c5788add59a56d216793(merge ref)

Refrefs/pull/125/merge

Timestamp2026-08-11 03:18:47 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.