Execution Profile

garnet-org/action

Recorded at the kernel by Garnetfor commit 0c70f96 (merge ref)

CI/build-and-verify

run 40060718931

Execution chains

6 destinations · 7 processes
  • systemd
    • hosted-compute-agent[1971 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2589 · node]step: Install dependencies
              • registry.npmjs.org104.16.0.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2556 · node]
            • api.github.com140.82.114.6:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • sudo[2043 · sudo]
          • 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-01.githubapp
      • glb-p4a577-public-internal.githubapp.com20.75.202.224:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-eus-01.githubapp
    • systemd[519 · 717 · systemd]
      • systemd[1736 · systemd]
        • 168.63.129.16:32526, 80 (http) · tcp
      • 168.63.129.16:53 (dns) · udp
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Profile UUID01a16c13-6625-76a2-954a-6e277929fe41
Refrefs/pull/192/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.