| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
There are two reasons for this:
1. Apple is about to drop support for this target. Zig will keep support
but move it to a lower tier - one that does not require continuous CI
testing. Support for this target will be maintained by the enthusiasm
of contributors but will not block other bug fixes and enhancements.
2. This is our only non-self-hosted action runner. We are migrating away
from GitHub soon at which point this runner will no longer be
available.
|
|
GitHub sucks:
Sep 20 20:49:21 ganymede runsvc.sh[82817]: An error occured: Runner version v2.326.0 is deprecated and cannot receive messages.
Sep 20 20:49:21 ganymede runsvc.sh[82817]: Runner listener exited with error code 1
Sep 20 20:49:21 ganymede runsvc.sh[82817]: Runner listener exit with terminated error, stop the service, no retry needed.
|
|
This way, if the ci-riscv64-linux label was added to a PR previously, removing
it will cause the concurrency group of the workflow to cancel the runs triggered
by the label being added.
|
|
|
|
This needs to be a separate workflow so that it doesn't interfere with non-CI
labeling of pull requests.
|
|
This reverts commit 8101104db0bdc7edeb07d91ab758c8a8d0861061.
|
|
|
|
GitHub is apparently very bad at arithmetic and so will cancel jobs that pass
the 5 hours mark, even if they're nowhere near the 6 hours timeout. So add an
hour to assist GitHub in this very difficult task.
|
|
|
|
|
|
|
|
these are taking too long. let's use a different workflow for now until
these runs are not holding up the pipeline, then they can be
reintroduced on master branch
|
|
While I experiment with ways to cut down run times, run on master only.
|
|
The idea is to have 2 runners per machine, since a lot of time is spent building
stage3 and stage4, both of which are largely single-core affairs. This will make
the test steps take longer, however, so the timeouts have been bumped a bit, and
max RSS for the test step has been lowered from 64G to 32G to prevent OOM.
Finally, we now only run a single ReleaseSafe job on PRs; Debug and Release jobs
are limited to pushes.
|
|
|
|
and reduce redundant coverage in slow runs to save time
|
|
The addition of FreeBSD and NetBSD targets to the test matrix in #24013 seems to
be causing timeouts under load. We might need to exclude some of those from CI,
but start by bumping the timeout so we can get a sense of how much more time is
actually needed.
|
|
We don't seem to be getting non-deterministic hangs since 4f3b59f, and e28b402
cut the run times significantly on top of that. Runs now seem to take around 1-2
hours, so the default timeout should be plenty.
|
|
GitHub have introduced an absolutely baffling feature where users can
use Copilot to take their simple explanation of a bug, and reword it
into a multi-paragraph monologue with no interesting details and added
false information, while also potentially ignoring issue templates.
So far, GitHub has not provided a way to block this feature at the
repository or organisation level, so for now, this is the only way to
prevent users from filing LLM-generated slop.
Related: https://github.com/orgs/community/discussions/159749
|
|
These seem to be timing out under load lately.
|
|
We were really close to the timeout previously, and we recently added
hexagon-linux and loongarch64-linux to the test matrix.
|
|
We usually do a PR for the llvm branches, so triggering a run for the branch
means we do extra work for no reason.
|
|
|
|
The devkit is a pain in the ass to keep online, I'll add this back
later.
|
|
Apple has already dropped support for macOS 12.
GitHub Actions is dropping macOS 12 support now.
The Zig project is also dropping macOS 12 support now.
This commit also bumps default minimum macos version to 13.
|
|
If you want to review code then pay attention.
|
|
|
|
|
|
Apple has already dropped support for macOS 11.
GitHub Actions is dropping macOS 11 support now.
The Zig project is also dropping macOS 11 support now.
|
|
Also makes the windows CI scripts fetch the tarballs from the network if
not already on disk.
|
|
|
|
The resinator files were moved during #19174
|
|
|
|
|
|
|
|
Same as 0b8fca5a195278bb5d5fb1ea09a504c30f751415. Whne the system gets
busy, the runs take drastically longer.
|
|
When the system gets busy, the runs take drastically longer.
|
|
|
|
|
|
Updates from LLVM release/17.x to 17.0.1
|
|
|
|
Review `std.Thread` changes.
|
|
Take ownership of std.json
|
|
It's easier to get M1 hardware for testing than x86_64-macos. This
addresses the current bottleneck in our CI pipeline.
|
|
|
