Execution Profile

garnet-labs/servers

Recorded at the kernel by Garnetfor commit 64509d1 (merge ref)

Python/test

run 35425508712

Execution chains

12 destinations · 3 processes
  • systemd
    • hosted-compute-agentRunner.Listener
      • Runner.Worker
        • node[2536 · node]
          • releases.astral.sh104.26.13.77:443 (https) · tcp
          • glb-db52c2cf8be544.github.com140.82.114.21:443 (https) · tcpalso recorded: results-receiver.actions.githubusercontent
          • raw.githubusercontent.com185.199.111.133:443 (https) · tcp
          • blob.bl5prdstrz24a.store.core.windows.net57.150.27.1:443 (https) · tcpalso recorded: blob.bl5prdstrz24a.trafficmanager.net, productionresultssa3.blob.core.windows.net
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
        • bash
          • uv[2577 · uv]step: Install dependencies
            • dualstack.python.map.fastly.net151.101.0.223:443 (https) · tcpalso recorded: files.pythonhosted.org
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • python3.12
      • python3.12[1450 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/servers
WorkflowPython
Jobtest
Run ID35425508712
Profile UUID01a0b842-aa95-7080-b093-f8e53341abd0
Commit SHA64509d143c437b15c12788ab192a090d3f272b4d(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