Execution Profile

garnet-org/action

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

CI/build-and-verify

run 388503956222026-10-16 04:24 UTC

Execution chains

6 destinations · 6 processes

systemd
- hosted-compute-
  - Runner.Listener
    - Runner.Worker
      - bash
        node[2626 · node]step: Install dependencies
        registry.npmjs.org104.16.0.34:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
      - node[2592 · node]
        api.github.com140.82.112.5:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
  - sudo
    - sudo[2081 · sudo]
      - 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-resolve[560 · systemd-resolve]
  - 168.63.129.16:53 (dns) · udp
- python3
  - python3[1418 · python3]
    - 168.63.129.16:32526, 80 (http) · tcp
- systemd-network[721 · systemd-network]
  - ip6-allroutersff02::2:0 (reserved) · icmpv6

Run details

Repositorygarnet-org/action

WorkflowCI

Jobbuild-and-verify

Run ID38850395622

Profile UUID01a142f4-68bc-7d33-bd3b-39c1e496c1c4

Commit SHA1b4ec7aa4270b3e6eafa059cb8f0f4666252b648(merge ref)

Refrefs/pull/181/merge

Timestamp2026-10-16 04:24:35 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.