Execution Profile

garnet-labs/litellm

Recorded at the kernel by Garnetfor commit 2f6fa99 (merge ref)

Dependency install and test (recorded)/install-test

run 42270087667

Execution chains

5 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[2204 · Runner.Worker]
          • bash
            • node[2664 · 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
        • provjobd2441508343[2141 · provjobd2441508343]
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • hosted-compute-watchdog-prod-iad-02.githubapp140.82.113.23:443 (https) · tcp(github infra)also recorded: glb-2a3c35-public-internal.githubapp.com
    • python3.12
      • python3.12[1407 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
    • systemd-resolved[539 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[730 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/litellm
WorkflowDependency install and test (recorded)
Jobinstall-test
Run ID42270087667
Profile UUID01a1b21a-0229-714b-ae73-62474bee5903
Commit SHA2f6fa9959f43eb3fd02ef0d3cf5501628733d17b(merge ref)
Refrefs/pull/66/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