Execution Profile

garnet-org/action

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

CI/build-and-verify

run 44387472286

Execution chains

7 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2234 · Runner.Worker]
          • bash
            • node[2789 · node]step: Install dependencies
              • registry.npmjs.org104.16.9.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2749 · node]
            • github.com140.82.114.3:443 (https) · tcp
            • api.github.com140.82.114.6:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.111.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • sudo[2186 · 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[224 · systemd]
      • systemd[1454 · systemd]
        • 168.63.129.16:32526, 80 (http) · tcp
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Profile UUID01a1f045-8d5e-7285-85b4-cf597675eb6e
Refrefs/pull/203/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.