Execution Profile

garnet-labs/actions

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

Garnet Runtime Visibility/dep-install

run 41157871528

Execution chains

13 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker
          • bash
            • node[2420 · node]
              • registry.npmjs.org104.16.0.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2385 · node]
            • github.com140.82.114.4:443 (https) · tcp
            • api.github.com140.82.114.6:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.108.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd384100034[1870 · provjobd384100034]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-eus-01.githubapp20.75.202.224:443 (https) · tcp(github infra)also recorded: glb-p4a577-public-internal.githubapp.com
    • systemd-resolved[507 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1196 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/actions
WorkflowGarnet Runtime Visibility
Jobdep-install
Run ID41157871528
Profile UUID01a18faf-4f4d-7fb5-b136-5fba3328152e
Commit SHAdb109852bec2b4cbdeed3f1725cb0792009d103d(merge ref)
Refrefs/pull/4/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