Execution Profile

garnet-labs/reward-hacking-gym

Recorded at the kernel by Garnetfor commit 40961a5

Garnet Reward-Hacking-Gym CI/eval-harness

run 30684847850

Execution chains

5 destinations · 5 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Workerbash
        • pip
          • dualstack.python.map.fastly.net151.101.0.223:443 (https) · tcpalso recorded: files.pythonhosted.org
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd724786478
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • hosted-compute-
      • Runner.Listener
        • Runner.Worker
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • systemd-network
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/reward-hacking-gym
WorkflowGarnet Reward-Hacking-Gym CI
Jobeval-harness
Run ID30684847850
Profile UUID019fbbae-4f66-7e33-bf54-f94cddfb3a74
Commit SHA40961a59a574f4dbff0c93598a55a7fb36ca9ac5
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