Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit cb27c8d (merge ref)

Dependency install and test (recorded)/install-test

run 42262098846

Execution chains

13 destinations · 4 processes
  • systemd
    • hosted-compute-
      • Runner.ListenerRunner.Worker
        • bash
          • node[2432 · node]step: Test
            • registry.npmjs.org104.16.0.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2444337[1899 · provjobd2444337]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-gccus02-02.githubapp140.82.112.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • systemd-resolve[434 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
    • python3
      • python3[1338 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Profile UUID01a1b1e9-a71c-7622-aee6-34b67ac44093
Refrefs/pull/29/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.