Execution Profile

garnet-labs/action

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

Garnet Fork PR Failed Jobs Test/success

run 39491783493

Execution chains

3 destinations · 4 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker[2183 · Runner.Worker]
        • bash
          • curl[2685 · curl]
            • example.com104.20.23.154:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • python3.12
      • python3.12[1523 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[570 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/action
WorkflowGarnet Fork PR Failed Jobs Test
Jobsuccess
Run ID39491783493
Profile UUID01a15afd-d5b9-70f0-a7a1-17098a9efadb
Commit SHAc21a71985231c9ce6d0dac6ff9f3a8803ee59c8e(merge ref)
Refrefs/pull/9/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