Execution Profile

garnet-labs/roast

Recorded at the kernel by Garnetfor commit 19b0b97 (merge ref)

Dependency install/dependency-install

run 34307195084

Execution chains

11 destinations · 6 processes
  • systemd
    • hosted-compute-agent[2004 · hosted-compute-agent]
      • Runner.ListenerRunner.Worker
        • bash
          • bundle[2627 · bundle]step: Install gems
            • index.rubygems.org151.101.1.227:443 (https) · tcpalso recorded: rubygems.org
            • localhost127.0.0.53:53 (dns) · udp(dns resolver)
      • sudo
        • provjobd2148124310[2023 · provjobd2148124310]
          • 140.82.112.24:443 (https) · tcp
      • 140.82.112.23:443 (https) · tcp
      • 140.82.112.24:443 (https) · tcp
      • 140.82.113.23:443 (https) · tcp
      • localhost127.0.0.53:53 (dns) · udp(dns resolver)
    • python3.12
      • python3.12[1323 · python3.12]
        • 168.63.129.16:32526, 80 (http) · tcp
        • 169.254.169.254:80 (http) · tcp(cloud metadata)
    • systemd-resolved[564 · systemd-resolved]
      • 168.63.129.16:53 (dns) · udp
    • systemd-networkd[720 · systemd-networkd]
      • ip6-allroutersff02::2:0 (reserved) · icmpv6
Run details
Repositorygarnet-labs/roast
WorkflowDependency install
Jobdependency-install
Run ID34307195084
Profile UUID01a08436-865e-768e-a078-1fdf13a2a8f9
Commit SHA19b0b97052b8b06372ee4655e51646c3a9ab78cf(merge ref)
Refrefs/pull/2/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