(Flaky-test) Intermittent failure - possible race - BasicEndToEndTest.testLookupThrottling #6301
Closed as not planned
Description
This showed up in the Github CI logs:
[61/161] BasicEndToEndTest.testLookupThrottling (835 ms)
Note: Google Test filter = BasicEndToEndTest.testLookupThrottling
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from BasicEndToEndTest
[ RUN ] BasicEndToEndTest.testLookupThrottling
2020-02-12 01:08:53.223 INFO ConnectionPool:85 | Created connection for pulsar://localhost:6650
2020-02-12 01:08:53.235 INFO ClientConnection:335 | [127.0.0.1:43898 -> 127.0.0.1:6650] Connected to broker
2020-02-12 01:08:53.236 ERROR ClientImpl:182 | Error Checking/Getting Partition Metadata while creating producer on persistent://public/default/testLookupThrottling -- 20
2020-02-12 01:08:53.236 INFO Client:88 | Subscribing on Topic :testLookupThrottling
2020-02-12 01:08:53.236 ERROR ClientImpl:384 | Error Checking/Getting Partition Metadata while Subscribing on persistent://public/default/testLookupThrottling -- 20
2020-02-12 01:08:53.238 INFO ClientConnection:1354 | [127.0.0.1:43898 -> 127.0.0.1:6650] Connection closed
[61/161] BasicEndToEndTest.testLookupThrottling returned/aborted with exit code -11 (835 ms)
It can be seen here: https://github.com/apache/pulsar/pull/6202/checks?check_run_id=439978679
The logs are attached:
logs_16048.zip
The reason I wonder if this is a race condition is that it's similar to these other testLookupThrottling issues:
- Intermittent test failure in ProxyLookupThrottlingTest #3552
- (Flaky-test) Intermittent failure of ProxyLookupThrottlingTest - assertion failure #6300
Perhaps they have a common underlying cause.