Execution Profile

garnet-labs/pnpm

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

Garnet Execution Diff/execution-diff

run 33562246388

Execution chains

8 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2685 · node]step: Run selected workload
              • registry.npmjs.org104.16.4.34:443 (https) · tcp
          • node[2713 · node]
            • glb-db52c2cf8be544.github.com140.82.114.21:443 (https) · tcpalso recorded: results-receiver.actions.githubusercontent
            • productionresultssa18.blob.core.windows20.150.88.228:443 (https) · tcpalso recorded: blob.bn9prdstrz04a.trafficmanager.net, blob.bn9prdstrz04a.store.core.windows.net
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd743486832[2053 · provjobd743486832]
          • 20.75.202.224:443 (https) · tcp
    • python3.12
      • python3.12[1294 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[586 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[768 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/pnpm
WorkflowGarnet Execution Diff
Jobexecution-diff
Profile UUID01a05eea-2de1-7644-9f12-460d82572666
Refrefs/pull/31/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.