Execution Profile

garnet-labs/open-swe

Recorded at the kernel by Garnetfor commit f96625c

Garnet CI/garnet-monitor

run 31377139430

Execution chains

10 destinations · 3 processes
  • systemd
    • hosted-compute-agent[2086 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker
          • node[2570 · node]
            • glb-db52c2cf8be544.github.com140.82.112.22:443 (https) · tcpalso recorded: results-receiver.actions.githubusercontent
            • github.com140.82.114.4:443 (https) · tcp
            • api.github.com140.82.114.5:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.108.133:443 (https) · tcp
            • blob.blz25prdstrz09a.store.core.windows20.209.227.33:443 (https) · tcpalso recorded: blob.blz25prdstrz09a.trafficmanager.net, productionresultssa13.blob.core.windows
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • bash
            • uv[2600 · uv]step: Sync dependencies
              • dualstack.python.map.fastly.net140.248.144.223:443 (https) · tcpalso recorded: files.pythonhosted.org
              • pypi.org151.101.0.223:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • github.com140.82.114.4:443 (https) · tcp
Run details
Repositorygarnet-labs/open-swe
WorkflowGarnet CI
Jobgarnet-monitor
Profile UUID019feb1d-c978-76b4-941f-1fa0a2c7ea58
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.