Repository navigation
feat: matrix Windows EH corpus across VS 2022 and VS 2026 - #3
Merged
Merged
Conversation
Hosted runners can install Visual Studio 2022 (windows-2022) and Visual Studio 2026 (windows-2025). Add that year axis to the producer, keep VS 2022 paths/keys stable, and skip VS 2010–2019 and a non-existent VS 2025 product with an explicit reason instead of a silent cell.
The producer already wrote later MSVC years under msvc/vsYYYY/. The verifier still expected the historical msvc/... path, so every VS 2026 cell failed after a successful compile and execute. Cap the Windows matrix at six concurrent jobs so the free-plan runner queue can drain.
Hosted VS 2026 built x86/x64 cells, then failed looking up Microsoft.VisualStudio.Component.VC.Tools.ARM. Keep ARM32 on VS 2022 and make the 2026 ARM cells an explicit skip.
VS 2022 cells run on windows-2022 and VS 2026 cells on windows-2025, so producer.runner_image is not a shared envelope field. Union the images and keep schema, corpus, source, and producer revision identical.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a Visual Studio year axis to the windows-eh producer.
windows-2022with historical cell keys/paths.windows-2025undercorpus/windows-eh/msvc/vs2026/....Producer unit tests:
python3 -m unittest discover -s scripts/tests -v