-
Notifications
You must be signed in to change notification settings - Fork 641
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Finish [SuppressTempFileChecks] attribute functionality, #898 #1084
Draft
paulirwin
wants to merge
2
commits into
apache:master
Choose a base branch
from
paulirwin:issue/898
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is nothing resetting this back to
true
, so the first failure will cascade to the other tests. I think we were better off with this hard coded totrue
because this will leave lots of temp files on the disk for passing tests.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is indeed the point. It tracks whether there have been any failures. In Lucene,
suiteFailureMarker
is static and is flagged as failed if any tests fail.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, thanks for the clarification. I thought this was only per test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to ChatGPT, that isn't how that works. It resets the state at the beginning of every test: https://chatgpt.com/share/677af21b-bcb8-8005-ad95-b070d0c6cdaa.
But whatever the case, I am hesitant to merge this to master when a test failure could leave all of the temporary files on disk for every successful test in the assembly that runs after it. There is a specific setting for that:
tests:leavetmpdir
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really debated whether we should even be doing this anyways in the issue comments. Again, no Lucene tests even use this attribute. I'll let you take ownership of this one from here because I'm losing interest in the purity aspect of getting this working when there is no actual benefit to our code. You can feel free to use whatever of this PR might be useful in your other test framework changes and I'm just going to mark this as draft for now. I'd appreciate getting some of my other PRs reviewed ahead of this one, anyways.