Execution Profile

garnet-labs/action

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

Garnet Fork PR Multiple Jobs Test/marker_com

run 394894199102026-10-20 20:08 UTC

Execution chains

3 destinations · 3 processes

systemd
- hosted-compute-agentRunner.Listener
  - Runner.Worker[1944 · Runner.Worker]
    - bash
      - curl[2481 · curl]step: Request example.com marker
        example.com172.66.147.243:443 (https) · tcp
        localhost127.0.0.53:53 (dns) · udp(dns resolver)
    - localhost127.0.0.53:53 (dns) · udp(dns resolver)
- systemd-resolved[457 · systemd-resolved]
  - 168.63.129.16:53 (dns) · udp

Run details

Repositorygarnet-labs/action

WorkflowGarnet Fork PR Multiple Jobs Test

Jobmarker_com

Run ID39489419910

Profile UUID01a15aee-7709-7636-915c-f835dd64dd44

Commit SHA251c0ffc92cc825611ae51b06364a9488153e0b1(merge ref)

Refrefs/pull/7/merge

Timestamp2026-10-20 20:08:47 UTC

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.