Execution Profile

aleesikander/express

Recorded at the kernel by Garnetfor commit 82d3b99 (merge ref)

ci/test

run 31536615141

Execution chains

6 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2244 · Runner.Worker]
          • bash
            • node[2781 · node]step: Install dependencies
              • registry.npmjs.org104.16.4.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1435013502[2184 · provjobd1435013502]
          • 140.82.112.24:443 (https) · tcp
    • python3.12
      • python3.12[1794 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[531 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[740 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositoryaleesikander/express
Workflowci
Jobtest
Run ID31536615141
Profile UUID019ff2ab-dd90-7bae-95bd-e85243c4bdf9
Commit SHA82d3b99e9b09090b703b8d5eff9b148bd4fc0641(merge ref)
Refrefs/pull/5/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