ci: Improve nextest config - #56462
Closed
MrSubidubi wants to merge 1 commit into
Closed
Conversation
osiewicz
requested changes
May 11, 2026
osiewicz
left a comment
Member
There was a problem hiding this comment.
I recall that @SomeoneToIgnore had strong objections to immediate-final, as we've tried it before: #39643
(from private convo):
...I do not see the list of what's failed, and have to scroll for eternity for another failure.
Member
Author
|
Yeah I think that is a valid point, hadn't thought of it like that. Optimally, there would be another variant. Will close for the time being. |
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
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.
As noted in https://nexte.st/docs/configuration/reference/?h=list+wrapper#default-configuration,
immediate-finalis the recommended setting forfailure-outputfor large test suites, as is definitely the case for this repository.Furthermore, allow one flaky run for the ocasionally flaky tests that we do have. We will add some tracking for which tests are flaky at a later point.
Release Notes: