Execution Profile

garnet-labs/pnpm

Recorded at the kernel by Garnetfor commit 1c40dea (merge ref)

DNS resolver record/record

run 33937913883

Execution chains

27 destinations · 9 processes
  • systemd
    • bashbashbashbashRunner.Listener
      • Runner.Worker
        • bash
          • pnpm[5122 · pnpm]step: Install the fixture with a cold store
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
          • sudo[4583 · sudo]step: Capture port-53 packets as ground truth
            • apt-get
              • http[4627 · http]step: Answer DNS from a local forwarder
                • mirrors.sonic.net157.131.224.201:80 (http) · tcpalso recorded: mirrors.sr.sonic.net
                • localhost127.0.0.53:53 (dns) · udp(dns resolver)
              • http[4619 · http]step: Answer DNS from a local forwarder
                • archive.ubuntu.com185.125.190.81:80 (http) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • node
          • sudo[4558 · sudo]
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd[4894 · systemd]
      • 1.1.1.1:53 (dns) · udp
    • chronyd[1686 · chronyd]
      • 169.254.169.123:123 (ntp) · udp
    • sudo
      • blacksmithd[2114 · blacksmithd]
        • 192.168.127.1:1064 · tcp
    • systemd-resolved[1471 · systemd-resolved]
      • 8.8.8.8:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowDNS resolver record
Jobrecord
Profile UUID01a06f50-66e5-7cef-8456-1e201b55c0f0
Refrefs/pull/39/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.