Mailing List Archives

Authenticated access

 		[Computer Systems Lab]

[← Prev]  [Date]  [Next →] [← Prev]  [Thread]  [Next →]

[DynInst_API:] [dyninst/dyninst] d1670c: GitHub CI: limit where known binary tests are run

Date: Fri, 14 Nov 2025 12:53:29 -0800
From: Tim Haines <noreply@xxxxxxxxxx>
Subject: [DynInst_API:] [dyninst/dyninst] d1670c: GitHub CI: limit where known binary tests are run 
  Branch: refs/heads/thaines/limit_binary_tests_run
  Home:   https://github.com/dyninst/dyninst
  Commit: d1670cfa5accd9ffe69ff155dd70e98be866da42
      https://github.com/dyninst/dyninst/commit/d1670cfa5accd9ffe69ff155dd70e98be866da42
  Author: Tim Haines <thaines.astro@xxxxxxxxx>
  Date:   2025-11-14 (Fri, 14 Nov 2025)

  Changed paths:
    M .github/workflows/build-opts.yaml
    M .github/workflows/compiler-multibuild.yaml
    M .github/workflows/libabigail.yaml

  Log Message:
  -----------
  GitHub CI: limit where known binary tests are run

There's no need to run those tests when doing build tests. Running the unit, integration,
and regression tests is needed to validate the build is usable.



To unsubscribe from these emails, change your notification settings at https://github.com/dyninst/dyninst/settings/notifications
[← Prev in Thread] Current Thread [Next in Thread→]
  • [DynInst_API:] [dyninst/dyninst] d1670c: GitHub CI: limit where known binary tests are run, Tim Haines <=
Previous by Date:  [DynInst_API:] [dyninst/dyninst] 38dcd9: Formatting, Tim Haines
Next by Date:  [DynInst_API:] [dyninst/dyninst] 8692b3: GitHub CI: re-enable HPCtoolkit build on Fedora, Tim Haines
Previous by Thread:  [DynInst_API:] [dyninst/dyninst] d14c88: [AMDGPU] Insert prologue and epilogue in instrumen..., Ronak Chauhan
Next by Thread:  [DynInst_API:] [dyninst/dyninst] d1bc37: [AMDGPU][DataflowAPI] Add missing registers for gf..., Ronak Chauhan
Indexes:  [Date] [Thread]