Execution Profile

garnet-labs/action

Recorded at the kernel by Garnetfor commit 251c0ff (merge ref)

Garnet Fork PR Multiple Jobs Test/marker_net

run 39489419910

Execution chains

3 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.ListenerRunner.Worker
      • bash
        • curl[2669 · curl]step: Request example.net marker
          • example.net104.20.21.8:443 (https) · tcp
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • python3.12
      • python3.12[1510 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[514 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/action
WorkflowGarnet Fork PR Multiple Jobs Test
Jobmarker_net
Run ID39489419910
Profile UUID01a15aee-7902-75d1-8265-2b7118790c10
Commit SHA251c0ffc92cc825611ae51b06364a9488153e0b1(merge ref)
Refrefs/pull/7/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