Execution Profile

aleesikander/express

Recorded at the kernel by Garnetfor commit 9a09d49 (merge ref)

ci/test

run 31624809194

Execution chains

6 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2047 · Runner.Worker]
          • bash
            • node[2593 · node]step: Install dependencies
              • dash
                • node[2607 · node]
                  • storage.googleapis.com104.154.125.27:443 (https) · tcp
                  • localhost127.0.0.53:53 (dns) · udp(dns resolver)
              • registry.npmjs.org104.16.5.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd739085914[1995 · provjobd739085914]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-01.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • python3.12
      • python3.12[1416 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[548 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositoryaleesikander/express
Workflowci
Jobtest
Run ID31624809194
Profile UUID019ff71d-a5b8-7379-ac51-f5087db05b93
Commit SHA9a09d49a5593809887748907c4141754975dcdea(merge ref)
Refrefs/pull/6/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