Execution Profile

garnet-labs/pnpm

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

Garnet Execution Diff/execution-diff

run 35783220731

Execution chains

6 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2390 · node]step: Run selected workload
              • registry.npmjs.org104.16.10.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2413 · node]
            • glb-db52c2cf8be544.github.com140.82.114.22:443 (https) · tcpalso recorded: results-receiver.actions.githubusercontent
            • productionresultssa3.blob.core.windows.net57.150.87.97:443 (https) · tcpalso recorded: blob.bl5prdstrz24a.trafficmanager.net, blob.bl5prdstrz24a.store.core.windows.net
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2736291[1840 · provjobd2736291]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-02.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • systemd-resolved[385 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Execution Diff
Jobexecution-diff
Profile UUID01a0cae6-0627-704d-b0c2-f26c976a2cc1
Refrefs/pull/65/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.