Execution Profile

garnet-labs/garnet-runtime-review-demo

Recorded at the kernel by Garnetfor commit 690f02e (merge ref)

build/build

run 31257440806

Execution chains

8 destinations · 6 processes
  • systemd
    • hosted-compute-agent[1822 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2326 · node]step: Install
              • registry.npmjs.org104.16.1.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2290 · node]
            • github.com140.82.113.3:443 (https) · tcp
            • api.github.com140.82.113.6:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.110.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd566397263[1837 · provjobd566397263]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • systemd-resolved[412 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1232 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/garnet-runtime-review-demo
Workflowbuild
Jobbuild
Run ID31257440806
Profile UUID019fe15c-af22-7eb5-ba73-aba306c99ae1
Commit SHA690f02ee7d366a35a4c40518520ed5655693aa75(merge ref)
Refrefs/pull/25/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