summaryrefslogtreecommitdiff
path: root/libc/src/stdlib/gpu/aligned_alloc.cpp
diff options
context:
space:
mode:
authorEric <eric@efcs.ca>2025-07-02 10:04:37 -0400
committerGitHub <noreply@github.com>2025-07-02 10:04:37 -0400
commitd78036f06ea94a42b7cff62241e91ed5b2900c7a (patch)
treeab6ca6bcbe74ae1db1ffccb3bbfacd4f480e0f7a /libc/src/stdlib/gpu/aligned_alloc.cpp
parent8b3cc4d1ed06de18166d37e5fb82c68ae4e4a7a4 (diff)
Only restart failed libc++ jobs, not cancelled ones. (#146397)
Despite the error message for preempted jobs containing the words "cancelled", these are considered workflow "failures" by github. This is important, because if we fail to distinguish between "failed" and "cancelled" jobs, the restarter will fight to restart jobs a user intentionally cancelled (either by pressing the "cancel" button, or by pushing an update to a PR). This reverts commit 3ea7fc73397032e71fb20d27084f4552211bb1f6. This also reverts earlier attempts to solve this problem by matching the messages to detect manual cancellations. This change also removes ldionne's test workflow, as its hard to correctly keep in sync. This change does not attempt to address the maintainability or testability of this script, which continues to be an issue. If asked to address these issues, my plan is to write the script in python (which most people are more familar with), and turn this action into a "docker action" using a container with the python action and dependencies built into it. Let me know if that's a direction we're interested in heading.
Diffstat (limited to 'libc/src/stdlib/gpu/aligned_alloc.cpp')
0 files changed, 0 insertions, 0 deletions