Execution Profile

garnet-labs/litellm

Recorded at the kernel by Garnetfor commit 0983b57 (merge ref)

Dependency install and test (recorded)/install-test

run 42270056859

Execution chains

7 destinations · 7 processes
  • systemd
    • hosted-compute-agent[2084 · hosted-compute-agent]
      • Runner.Listener
        • Runner.Worker[2173 · Runner.Worker]
          • bash
            • node[2624 · node]
              • registry.npmjs.org104.16.6.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1494487603[2101 · provjobd1494487603]
          • 140.82.114.23:443 (https) · tcp
      • 140.82.112.24:443 (https) · tcp
    • systemd-resolved[502 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1512 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-networkd[738 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowDependency install and test (recorded)
Jobinstall-test
Run ID42270056859
Profile UUID01a1b219-e97f-72b8-bd35-7699c585692a
Commit SHA0983b5725c85eb6f19a82990535d6a4bb975d011(merge ref)
Refrefs/pull/62/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