Execution Profile

aleesikander/express

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

ci/test

run 32045911518

Execution chains

5 destinations · 6 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker[1963 · Runner.Worker]
        • bash
          • node[2517 · node]step: Install dependencies
            • dash
              • node
                • node
                  • dash
                    • node
                      • node[2598 · node]step: Run tests
                        • example.com104.20.23.154:443 (https) · tcp
                        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
            • registry.npmjs.org104.16.1.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[445 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1570 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-networkd[644 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositoryaleesikander/express
Workflowci
Jobtest
Run ID32045911518
Profile UUID01a01092-b125-7b0b-ae38-25b7fc7c1902
Commit SHAe4cff854f9197e3369e969d5e9603f0c9147619e(merge ref)
Refrefs/pull/18/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