Skip to content

[Flaky test] ReactorBlockHoundIntegrationTest > shouldNotReportWorkerScheduledFutureTask() FAILED #3615

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.

Sign up for GitHub

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

Jump to bottom
Open
OlegDokuka opened this issue Oct 9, 2023 · 1 comment
Open

[Flaky test] ReactorBlockHoundIntegrationTest > shouldNotReportWorkerScheduledFutureTask() FAILED #3615

OlegDokuka opened this issue Oct 9, 2023 · 1 comment
Labels
type/test/flaky
Milestone
General Backlog

Comments

@OlegDokuka
Copy link
Contributor

OlegDokuka commented Oct 9, 2023 •
edited
Loading 

ReactorBlockHoundIntegrationTest > shouldNotReportWorkerScheduledFutureTask() FAILED
    java.util.concurrent.TimeoutException: shouldNotReportWorkerScheduledFutureTask() timed out after 5 seconds
        at java.util.ArrayList.forEach(ArrayList.java:1259)
        at java.util.ArrayList.forEach(ArrayList.java:1259)
@OlegDokuka OlegDokuka added the type/bug A general bug label Oct 10, 2023
@chemicL
Copy link
Member

chemicL commented Mar 19, 2024

shouldNotReportSchedulerScheduledFutureTask is also flaky.

@chemicL chemicL added this to the Backlog milestone Feb 4, 2025
@chemicL chemicL changed the title fluky test ReactorBlockHoundIntegrationTest > shouldNotReportWorkerScheduledFutureTask() FAILED [Flaky test] ReactorBlockHoundIntegrationTest > shouldNotReportWorkerScheduledFutureTask() FAILED Feb 4, 2025
@chemicL chemicL removed the type/bug A general bug label Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/test/flaky
Projects
None yet
Milestone
General Backlog
Development

No branches or pull requests
2 participants
@chemicL @OlegDokuka