8443e2ab43
ci: update tarballs to 0.17.0-dev.203+073889523
2026-04-25 22:02:35 +02:00
73c51c142c
ci: update QEMU to 11.0.0
2026-04-22 16:31:08 +02:00
0b768cd9dd
zig reduce: fix compilation ( #31930 )
...
fixes #31926
Reviewed-on: https://codeberg.org/ziglang/zig/pulls/31930
Reviewed-by: Andrew Kelley <andrew@ziglang.org >
2026-04-22 02:00:41 +02:00
29532177c1
CI: add coverage for fuzzer compiling
...
From mlugg: this commit originally also added the same coverage to the
aarch64-linux-release script, but that caused the aarch64-linux-release
job to time out, so that change has been omitted for now.
2026-04-16 19:42:23 +02:00
142703ba51
ci: x86_64-linux-release requires cc
2026-03-27 04:42:05 +01:00
3de16858f7
ci: update to qemu 10.2.2
2026-03-25 00:51:40 +01:00
4acecad933
bootstrap.c: work around the gcc sra miscomp using preprocessor checks rather than CLI arg ( #31589 )
...
Closes #31577
I've also extended the "good" ranges to fit versions >14.3 and >13.4, since both of these branches have the fix merged so if they ever make a dot release it should be good.
Reviewed-on: https://codeberg.org/ziglang/zig/pulls/31589
Reviewed-by: Andrew Kelley <andrew@ziglang.org >
Co-authored-by: fardragon <michaldrozd@protonmail.ch >
Co-committed-by: fardragon <michaldrozd@protonmail.ch >
2026-03-20 04:55:51 +01:00
57114044db
Revert "ci: disable incremental tests"
...
Since we don't know what causes the various flaky test-incremental
failures we've seen, and this branch changes a bunch of incremental
stuff, let's try turning these back on... maybe they'll magically work
now!
This reverts commit 953ca759c2
2026-03-10 11:28:36 +00:00
a5219cd288
bootstrap: work around GCC bug
...
GCC bug 119085, which affects versions 13.0--15.1, is being triggered by
the C backend, resulting in a (small but critical) miscompilation in
zig2. Unfortunately, we can't really work around that bug without a
command-line flag, because the bug is sensitive to things like the order
in which `struct` types are defined.
Therefore, I have added an option to `bootstrap.c` which causes it to
pass the appropriate flag to `gcc` to disable the optimization pass in
question. This flag can likely be removed in future, once the affected
GCC versions become less common.
At least one of our x86_64-linux CI machines is using an affected GCC
version, so I also updated the relevant CI script to pass this flag when
testing no-LLVM bootstrap.
CMakeLists also has a workaround, but no user intervention is required
there: the GCC version range is automatically detected by CMakeLists.
2026-03-10 10:26:15 +00:00
2c126b8c82
ci: enable --libc-runtimes with glibc 2.43 and musl 1.2.5 on x86_64-linux
2026-03-08 18:28:05 +01:00
571543237f
ci: update to wasmtime 42.0.1
2026-03-04 21:29:48 +01:00
421c3c3cc5
ci: update qemu to 10.2.1.1
...
https://patchwork.kernel.org/project/qemu-devel/list/?series=1059138
2026-03-02 19:25:09 +01:00
0fd8dc8ea6
ci: update to qemu 10.2.1
2026-02-17 19:16:25 +01:00
6ce0dd1a81
ci: run test-libc on x86_64-linux-debug-llvm and x86_64-linux-release
2026-02-03 17:19:16 +01:00
953ca759c2
ci: disable incremental tests
...
Too much flakiness across the board: https://codeberg.org/ziglang/zig/issues?q=&type=all&sort=relevance&labels=747060&state=open&milestone=0&project=0&assignee=0&poster=0
2026-01-21 17:21:05 +01:00
435b8411b5
ci: update to qemu 10.2.0
2026-01-06 09:55:09 +01:00
4724774433
ci: apply workaround for #22213 to x86_64-linux scripts
...
This should be reverted on the next CI tarballs update.
2025-12-05 07:32:43 +01:00
78cba86928
ci: set maxrss from $ZSF_MAX_RSS if provided by the runner
...
All of our runners now define this. When running a CI script locally, this will
not be set, so we default to 0, aka "all available system memory".
2025-12-04 20:06:48 +01:00
a38220376e
Revert "ci: apply workaround for #22213 to x86_64-linux scripts"
...
This reverts commit a8f9b5dc06
2025-11-28 22:57:33 +01:00
a8f9b5dc06
ci: apply workaround for #22213 to x86_64-linux scripts
2025-11-28 22:06:46 +01:00
e639602569
ci: update to Wasmtime 38.0.3
2025-11-06 14:08:16 +01:00
389368392e
Revert "ci: stop building FreeBSD module tests on x86_64-linux"
...
This reverts commit 16c18b835e
2025-10-30 23:17:33 +01:00
e9e0526cf8
ci: switch to patched QEMU 10.1.1.1
...
https://github.com/ziglang/qemu-static/releases/tag/10.1.1.1
2025-10-18 17:11:44 +02:00
8f86ed78da
ci: final bump to all unit test timeouts
...
The last commit passed CI, so this final bump is just to allow for
deviation caused by different loads on the runner machines. With this
change, I don't expect any current unit test to ever time out, even when
CI is under extreme load.
2025-10-18 09:32:49 +01:00
f4315a0a57
ci: bump unit test timeouts
...
i am in purgatory as a punishment bestowed upon me for daring to
question the sanctity of windows' scheduler
2025-10-18 09:28:44 +01:00
50056a5b3a
compiler: rename --test-timeout-ms to --test-timeout
...
The unit can now be specified in the argument.
2025-10-18 09:28:43 +01:00
a7251e4191
ci: bump unit test timeouts
2025-10-18 09:28:43 +01:00
b43bb3a32a
ci: set unit test timeouts
2025-10-18 09:28:42 +01:00
493ad58ff7
Revert "ci: enable running libc-test on x86_64-linux-release"
...
This reverts commit fcfdf99122
2025-10-15 21:30:25 +02:00
595cd8935a
ci: update to QEMU 10.1.1
2025-10-15 01:33:52 +02:00
4edebf40d5
Merge pull request #25402 from alexrp/libc-test-ci
...
`ci`: enable running libc-test on `x86_64-linux-release`
2025-10-14 21:29:57 +02:00
781cc731ed
ci: move Git repository unshallowing to the workflow
2025-10-01 13:00:22 +02:00
acf8d5234f
ci: stop requiring an ARCH environment variable to be set
2025-10-01 13:00:22 +02:00
fcfdf99122
ci: enable running libc-test on x86_64-linux-release
2025-10-01 03:25:25 +02:00
16c18b835e
ci: stop building FreeBSD module tests on x86_64-linux
...
They're now built on the x86_64-freebsd machine.
2025-09-22 01:39:29 +02:00
8896046b11
ci: update tarballs to 0.16.0-dev.104+689461e31
2025-08-30 13:27:25 +02:00
98e9dde389
ci: update to QEMU 10.1.0
2025-08-29 10:52:32 +02:00
7c709f920b
ci: Update to QEMU 10.0.2
2025-07-09 11:06:13 +02:00
cefe65c1b8
ci: update tarballs to 0.15.0-dev.203+53270f008
...
these have assertions enabled
2025-04-04 15:28:18 -07:00
4b360a1ff0
ci: Update tarballs to 0.15.0-dev.203+53270f008.
2025-04-04 06:08:10 +02:00
1cbfdb4244
ci: Set ZIG_GLOBAL_CACHE_DIR and ZIG_LOCAL_CACHE_DIR earlier.
...
Otherwise the disk just keeps getting filled up.
Also remove some pointless cleanup commands since the actions/checkout workflow
step already cleans the repository by default.
2025-01-29 11:46:53 -08:00
28a259d4a3
ci: Switch to Wasmtime v29.0.0.
2025-01-21 18:47:08 -05:00
dde3116e50
Dwarf: implement new incremental line number update API
2025-01-05 02:20:56 +00:00
e163ae794b
ci: Update to QEMU 9.2.0-rc1 in x86_64-linux scripts.
2024-11-24 08:35:08 +01:00
70ad7dcd48
lldb: implement tuple types
2024-11-23 23:51:35 -05:00
8bfc36f091
ci: Update to QEMU 9.1.0 in x86_64-linux scripts.
2024-10-18 00:55:20 +02:00
008acd0547
Replace tidy with superhtml as HTML validator ( #21664 )
...
Also add `$HOME/local/bin` to `PATH` in linux CI
2024-10-11 21:27:30 -07:00
65f6623ba4
lldb: print field names with a leading dot
...
This more closely resembles zig struct literals.
2024-10-09 07:48:07 -04:00
38af1b7ed1
CI: update tarballs to 0.14.0-dev.1622+2ac543388
2024-09-19 18:20:22 -07:00
0d7a9c4806
CI: update tarballs
...
This time the LLVM builds have assertions enabled.
Also the zig builds support `-rtlib=none` for disabling compiler-rt.
2024-09-19 18:20:21 -07:00
Alex Rønne Petersen