-
Notifications
You must be signed in to change notification settings - Fork 189
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
review issues listed in expected to fail file #2078
Labels
Comments
This was referenced Jun 3, 2021
9 tasks
This was referenced Jun 9, 2021
Merged
9 tasks
11 tasks
9 tasks
9 tasks
Merged
11 tasks
Also see issue #2190 - the stale bot has been closing lots of issues. If an issue still has a genuine failure in an expected-failures file, then we need to re-open the issue and add the "bug" or "Type:Technical-Debt" label. That will stop the "stale" bot from closing it. |
This was referenced Jun 18, 2021
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
issues that are closed should not be in the expected to fails files. Ether the bug was not really fixed or (more likely) the test fails because of some other issue but the expected to fail file was not updated correctly
e.g. #1346 is closed but some tests are still marked with that issue in the expected to fail file
and the test Creating a new public link share of a file with password using the old public WebDAV API does not fail because of the range issue but because of lack of the "old webdav API missing for public links"
The text was updated successfully, but these errors were encountered: