Execution Profile

garnet-labs/action

Recorded at the kernel by Garnetfor commit 9156eb9 (merge ref)

Garnet Fork PR Single Job Test/single

run 39486520301

Execution chains

3 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • curl[2656 · curl]
          • example.org172.66.157.237:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[535 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1440 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/action
WorkflowGarnet Fork PR Single Job Test
Jobsingle
Run ID39486520301
Profile UUID01a15adb-d3dc-741b-ae87-36ea9fe0b7aa
Commit SHA9156eb971a375d3c6602410f28fed0929188d325(merge ref)
Refrefs/pull/5/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