Allow silencing predict tile stdout #874
Closed
Conversation
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
|
Thanks for jumping in. The test above yields the same error as mine, but I can't find any reason it doesn't show locally. Same pytorch-lightning version. |
|
What's weird is that the individual test passed locally in my fork. Let me try a couple more things... |
|
So if we just run the test that was failing it passes. So the most likely scenario is that there is some sort of state persisting in the tests that is causing the issue and for some reason it's happening on GitHub but not locally on Ubuntu 22.04 (for me) |
|
Yah , I got the same here. |
|
Still failing here with Ubuntu 22.04, so that won't help us replicate locally |
|
Can close in favor of #878 |
|
I think this can be closed. |
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.
See Lightning-AI/pytorch-lightning#13358
I'm not sure what's going on with the test in #854 but I took the original commit, rebased it against main, cleanup up a style issue, and tests seem to be passing on my fork.