Execution Profile

garnet-labs/linear

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

build/build

run 34769691397

Execution chains

13 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Workerbash
        • node
          • registry.npmjs.org104.16.0.34:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • hosted-compute-agent
        • hosted-compute-agent
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • glb-2a3c35-public-internal.githubapp.com140.82.114.24:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-01.githubapp
      • 140.82.114.23:443 (https) · tcp
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • glb-2a3c35-public-internal.githubapp.com140.82.113.24:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-01.githubapp
    • systemd
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/linear
Workflowbuild
Jobbuild
Run ID34769691397
Profile UUID01a09bae-b9de-7d64-9375-74fc5915751d
Commit SHAa35b99309588a711db5c0d44b994eb317ff59e45(merge ref)
Refrefs/pull/11/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