Execution Profile

garnet-labs/action

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

Garnet Fork PR Duplicate Job Names Test/duplicate_org

run 39490400738

Execution chains

3 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • curl[2684 · curl]step: Request example.org marker
          • example.org104.20.26.136:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-resolved[542 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1406 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/action
WorkflowGarnet Fork PR Duplicate Job Names Test
Jobduplicate_org
Run ID39490400738
Profile UUID01a15af4-e383-7ad0-8ba3-57c999f28f15
Commit SHAcf3096b6ac83d5836f92920ffe33cbd51763acbb(merge ref)
Refrefs/pull/8/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