Execution Profile

garnet-org/action

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

CI/build-and-verify

run 32209888504

Execution chains

5 destinations · 6 processes
  • systemd
    • hosted-compute-agent
      • Runner.Listener
        • Runner.Worker[1962 · Runner.Worker]
          • bash
            • node[2391 · node]step: Install dependencies
              • registry.npmjs.org104.16.4.34:443 (https) · tcp
              • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • node[2357 · node]
            • api.github.com140.82.113.6:443 (https) · tcp
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
          • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd1891498314[1902 · provjobd1891498314]
          • 140.82.112.24:443 (https) · tcp
    • systemd-resolved[418 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • python3.12
      • python3.12[1562 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
Run details
Repositorygarnet-org/action
WorkflowCI
Jobbuild-and-verify
Run ID32209888504
Profile UUID01a017ec-4ef9-742e-9126-b91ef8f72c53
Commit SHAac459391a17b65807b5b94c9f7bab2905222fc1a(merge ref)
Refrefs/pull/135/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