Execution Profile

garnet-labs/litellm

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

Dependency install and test (recorded)/install-test

run 42270015323

Execution chains

4 destinations · 4 processes
  • systemd
    • hosted-compute-agent
      • Runner.ListenerRunner.Worker
        • bash
          • node[2429 · node]step: Install dependencies (lifecycle scripts execute here)
            • registry.npmjs.org104.16.6.34:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd444179924[1888 · provjobd444179924]
          • 140.82.114.23:443 (https) · tcp
    • systemd-resolved[416 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1202 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-labs/litellm
WorkflowDependency install and test (recorded)
Jobinstall-test
Run ID42270015323
Profile UUID01a1b219-95f3-71f1-9dc4-be40debac936
Commit SHAd86c621889d2beb54e3f97c024b037117e04bd3a(merge ref)
Refrefs/pull/56/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