Execution Profile

garnet-labs/pnpm

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

DNS resolver record/record

run 33938526234

Execution chains

16 destinations · 8 processes
  • systemd
    • bashbashbashbashRunner.Listener
      • Runner.Worker
        • bash
          • pnpm[5115 · pnpm]step: Install the fixture with a cold store
            • 104.16.10.34:443 (https) · tcp
            • 8.8.4.4:53 (dns) · udp
          • sudo[4599 · sudo]step: Capture port-53 packets as ground truth
            • apt-get
              • http[4643 · 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[4635 · 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[4574 · sudo]
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • chronyd[1682 · chronyd]
      • 169.254.169.123:123 (ntp) · udp
    • sudo
      • blacksmithd[2084 · blacksmithd]
        • 192.168.127.1:1034 · tcp
    • systemd-resolved[1523 · systemd-resolved]
      • 8.8.8.8:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowDNS resolver record
Jobrecord
Run ID33938526234
Profile UUID01a06f5b-0e5c-7ebf-a7b6-c05f3255ab29
Commit SHAe385623ee6827faf96b191e12f2552e74c3cfa97(merge ref)
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.

Read the docs