Execution Profile

garnet-labs/E2B

Recorded at the kernel by Garnetfor commit 01ab77e (merge ref)

Dependency install and test (recorded)/install-test

run 42269938139

Execution chains

14 destinations · 6 processes
  • systemd
    • hosted-compute-[2069 · hosted-compute-]
      • Runner.Listener
        • Runner.Worker[2258 · Runner.Worker]
          • bash
            • node[2718 · node]step: Test
              • registry.npmjs.org104.16.0.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1156799[2100 · provjobd1156799]
          • 20.75.202.224:443 (https) · tcp
      • 20.75.202.224:443 (https) · tcp
    • python3
      • python3[2146 · python3]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolve[519 · systemd-resolve]
      • 168.63.129.16:53 (dns) · udp
Run details
Repositorygarnet-labs/E2B
WorkflowDependency install and test (recorded)
Jobinstall-test
Run ID42269938139
Profile UUID01a1b219-8541-7d8f-bd3e-d96553329d32
Commit SHA01ab77e84bf6e7ccbe9cd80483c9cefb826290fe(merge ref)
Refrefs/pull/46/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