Skip to content

Flakey bug: PubSubTests.testContainerSubscribe fails at random times [DATAREDIS-1264] #1834

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

Closed
spring-projects-issues opened this issue Dec 9, 2020 · 1 comment
Assignees
Labels
type: bug A general bug

Comments

@spring-projects-issues
Copy link

Greg Turnquist opened DATAREDIS-1264 and commented


No further details from DATAREDIS-1264

@spring-projects-issues
Copy link
Author

Greg Turnquist commented

PubSubTests.testContainerSubscriber, a parameterized test case, will randomly fail on different JDKs (11 or 15) leaving this type of history:

[2020-12-09T16:57:46.380Z] [ERROR] Failures: 
[2020-12-09T16:57:46.380Z] [ERROR] org.springframework.data.redis.listener.PubSubTests.testContainerSubscribe
[2020-12-09T16:57:46.380Z] [INFO]   Run 1: PASS
[2020-12-09T16:57:46.380Z] [INFO]   Run 2: PASS
[2020-12-09T16:57:46.380Z] [INFO]   Run 3: PASS
[2020-12-09T16:57:46.380Z] [INFO]   Run 4: PASS
[2020-12-09T16:57:46.380Z] [INFO]   Run 5: PASS
[2020-12-09T16:57:46.380Z] [INFO]   Run 6: PASS
[2020-12-09T16:57:46.380Z] [ERROR]   Run 7: PubSubTests.testContainerSubscribe:141 
[2020-12-09T16:57:46.380Z] Expecting ArrayList:
[2020-12-09T16:57:46.380Z]  <["d09d1b66-da2a-4b95-aaa4-4fdad07d4efc", "4960e385-8f94-4202-818e-029a7d0c9701"]>
[2020-12-09T16:57:46.380Z] to contain:
[2020-12-09T16:57:46.380Z]  <["4960e385-8f94-4202-818e-029a7d0c9701", "661820ed-643b-45b0-89ef-f41b90d1a6c6"]>
[2020-12-09T16:57:46.380Z] but could not find the following element(s):
[2020-12-09T16:57:46.380Z]  <["661820ed-643b-45b0-89ef-f41b90d1a6c6"]>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants