Turn off the KUnit fault test in the M14 fragment too - #58
Merged
Merged
Conversation
tamnd
added
kind/bug
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
1 participant
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.
#51 turned off CONFIG_KUNIT_FAULT_TEST in the M13 fragment only, because the 7.2.8 cells skipped the kunit_fault suite on their own. That was the wrong conclusion. The era cell for 6.18.54 on x86_64 with gcc-14.2.0, which is M14, panicked in kunit_fault on all three KUnit boots (NULL dereference, then a fatal exception because of PANIC_ON_OOPS), the same way 6.12.111 did. It's 7.2.8 that skips the suite, not the whole era.
This turns the test off in the M14 fragment too and fixes the comments and spec 07. The M14 fragment digest changes, so every M14 cell in the store is now out of date. That covers the 7.2.8 rows on x86_64 and i386 and the arm64 tinyconfig cell, and they will run again. I stopped both servers before they spent more time on the 6.18.54 row, which would have been graded against a broken reference.