Main build 41252386309 (and 41247522136): linux job failed in check_skips because
agc_shader_disk_cache_large_file skipped (runner short of free disk or memory for a
>2 GiB file) with a message the guard does not allow. Not caused by #13998.
The windows pm4_replay timeout is a one-off flake (1 of 59 red builds).
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
The same source file listed under two build directories forms two units,
sorted by directory, and each unit keeps its records in input order.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
The test reads the mingwHostTests gate of build.yml and checks that it lists core/CMakeLists.txt, cmake/, 3rdparty/, .gitmodules, tools/select_tests.py and tools/configure_seed.py. Against the previous gate it fails all six.
Run 41245658018 (b9bf246ea2). linux: agc_shader_disk_cache_large_file skips
when the runner has under 3 GiB free and check_skips.py did not list that
reason. windows: guest_timed_wait_cpu aborted on a runner scheduling hiccup
(latency bound exceeded, #13710 made it serial but it is still timing-based).
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
The test takes the files progress.py reads from the module itself and checks that the report's pull request filter matches each of them, and that library sources still start it. Against the previous filter it fails on RdnaOpcode.hpp, rdna_isa.txt and nid_names.py.
GitHub returns some open pull request bodies with an escape that is not valid
JSON, for example a backslash followed by u00XX. gh itself rejects the page,
and pr_overlap.py stops with "Invalid \uXXXX escape" on the whole open-PR
list. Add a test for a page containing such a body, and one that checks
valid escapes are still decoded to the same text.
The first test fails on upstream main with that error. The second passes.
Version 1 of the run report format: a JSON Schema, eleven example reports
(one generated in the test), a test that validates each against the schema and
checks that malformed or contradictory reports are rejected, and a workflow
that runs the test with a pinned validator.
An ANSI dependency path can also be valid UTF-8: cp1252 writes U+00C3
U+00A9 as C3 A9, which UTF-8 reads as U+00E9, so the UTF-8-first decode
named a file the compiler never opened. On Windows, when both readings
decode and differ, take the ANSI one if it exists relative to the build
directory and the UTF-8 one does not; otherwise keep UTF-8.
ninja -t deps lists the paths each compiler wrote to its depfiles, in that
compiler's active code page. d85426069c decoded them as UTF-8, which is
right for WinLibs GCC 15.2.0 (UTF-8 active code page) but not for a GCC
that runs with the ANSI code page, such as a GCC 11.4 MinGW build: a header
under C:\...\ação\ is written as cp1252 bytes, the decode raises and
select_tests dump exits with a UnicodeDecodeError. Decode a dependency as
UTF-8 and, on Windows, fall back to the ANSI code page when it is not
valid UTF-8.
Dean