Execution Profile

garnet-labs/open-swe

Recorded at the kernel by Garnetfor commit ee5320f

Agent CI/unit-tests

run 29894917762

Execution chains

7 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker
          • Runner.Worker
            • api.github.com140.82.114.6:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.110.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • bash
            • uv
              • dualstack.python.map.fastly.net140.248.144.223:443 (https) · tcpalso recorded: files.pythonhosted.org
              • pypi.org151.101.192.223:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node
            • github.com140.82.114.3:443 (https) · tcp
            • api.github.com140.82.114.6:443 (https) · tcp
            • release-assets.githubusercontent.com185.199.110.133:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • hosted-compute-agent
        • hosted-compute-agent
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • glb-2a3c35-public-internal.githubapp.com140.82.112.24:443 (https) · tcp(github infra)also recorded: hosted-compute-watchdog-prod-iad-02.githubapp
Run details
Repositorygarnet-labs/open-swe
WorkflowAgent CI
Jobunit-tests
Profile UUID019f8860-cf5e-7a66-bdc4-49e071fe430e
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.