Skip to content
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

Intermittent error in LoadBalancerTest.java #269

Closed
agarman opened this issue Mar 2, 2017 · 2 comments
Closed

Intermittent error in LoadBalancerTest.java #269

agarman opened this issue Mar 2, 2017 · 2 comments
Labels
area/test lifecycle/stale type/bug The PR fixed a bug or issue reported a bug type/flaky-tests

Comments

@agarman
Copy link

agarman commented Mar 2, 2017

Expected behavior

mvn test completes successfully in 10-15 minutes.

Actual behavior

Tests run: 526, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 881.775 sec <<< FAILURE! - in TestSuite
testLoadReportsWrittenOnZK(com.yahoo.pulsar.broker.loadbalance.LoadBalancerTest)  Time elapsed: 0.027 sec  <<< FAILURE!
java.lang.AssertionError: expected [true] but found [false]
	at com.yahoo.pulsar.broker.loadbalance.LoadBalancerTest.testLoadReportsWrittenOnZK(LoadBalancerTest.java:202)

testResumptionAfterBacklogRelaxed(com.yahoo.pulsar.broker.service.ReplicatorTest)  Time elapsed: 49.376 sec  <<< FAILURE!
com.yahoo.pulsar.client.api.PulsarClientException$TimeoutException: Could not send message to broker within given timeout


Results :

Failed tests: 
  LoadBalancerTest.testLoadReportsWrittenOnZK:202 expected [true] but found [false]
  ReplicatorTest.testResumptionAfterBacklogRelaxed » Timeout Could not send mess...

Steps to reproduce

Intermittent test failure.

System configuration

Pulsar version: 17630b9

@merlimat merlimat added this to the 1.17 milestone Mar 2, 2017
@agarman
Copy link
Author

agarman commented Mar 13, 2017

Tests run: 540, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 863.584 sec <<< FAILURE! - in TestSuite
testLoadReportsWrittenOnZK(com.yahoo.pulsar.broker.loadbalance.LoadBalancerTest) Time elapsed: 0.012 sec <<< FAILURE!
java.lang.AssertionError: expected [true] but found [false]
at com.yahoo.pulsar.broker.loadbalance.LoadBalancerTest.testLoadReportsWrittenOnZK(LoadBalancerTest.java:202)

Pulsar version: f0fbb4d

@merlimat merlimat modified the milestones: 1.17, 1.18 Mar 31, 2017
@merlimat merlimat modified the milestones: 1.18, 1.19 Jun 15, 2017
sijie added a commit to sijie/pulsar that referenced this issue Mar 4, 2018
…apache#269)

Example:

```
(CONNECTING) />
(CONNECTED) /> ls pulsar/functions/test
test-namespace
(CONNECTED) /> ls pulsar/functions/test/test-namespace
function11
function12
function13
(CONNECTED) /> ls pulsar/functions/test/test-namespace/function11
8e4dcc81-3b00-4bf9-a489-1823b5514788-pulsar-functions-api-examples.jar
(CONNECTED) /> ls pulsar/functions/test/test-namespace/function12
0ee8e267-74cb-4178-99ea-6c723298223c-pulsar-functions-api-examples.jar
(CONNECTED) /> ls pulsar/functions/test/test-namespace/function13
8f1dea11-0070-434b-ba97-a42b44d8063c-pulsar-functions-api-examples.jar
(CONNECTED) />
```
@sijie sijie added type/bug The PR fixed a bug or issue reported a bug triage/week-34 labels Aug 22, 2018
@sijie sijie removed this from the 2.2.0-incubating milestone Sep 12, 2018
hrsakai pushed a commit to hrsakai/pulsar that referenced this issue Dec 10, 2020
Currently, the Pulsar Go Client is only tested against Go version 1.12. The motivation for this change is to help bring confidence that the Go client is compatible with multiple versions of Go, all being tested with each PR.

I've modified the two GitHub Action workflows that are a part of this repo with a [matrix](https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix) such that we test against multiple versions of Go.

- [X] Make sure that the change passes the CI checks.
hangc0276 pushed a commit to hangc0276/pulsar that referenced this issue May 26, 2021
@mattisonchao
Copy link
Member

I think this flaky test is Has been fixed.
@lhotari

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test lifecycle/stale type/bug The PR fixed a bug or issue reported a bug type/flaky-tests
Projects
None yet
Development

No branches or pull requests

8 participants