WIP: Reproduce flaky OutboxProcessorIntegrationTest.java #162
Conversation
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
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports MegaLinter is graciously provided by |
magro
force-pushed
the
OutboxProcessorIntegrationTest.java
branch
from
9b4c06e to
504c405
Compare
|
See e.g. https://github.com/tomorrow-one/transactional-outbox/actions/runs/11669616978/job/32497886155?pr=162#step:6:4777 - where `IOException: [404] toxic not found` is thrown. This happens with successful and failed tests, i.e. it doesn't seem to be causing the error we're hunting.
magro
force-pushed
the
OutboxProcessorIntegrationTest.java
branch
from
acea461 to
6b81c93
Compare
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.
Try to reproduce flaky test, don't merge.
The PR is opened to trigger the build action.