Closed
Description
Issue Description
Observed a possibly racing test case, which seems to intermittently result in a failure. The test is can handle connect command
in ParseLiveQueryTest.spec.js
.
I first saw this in one of our CI builds and am making a note of it here, not entirely sure but I believe this may have tripped during the postgres section of tests.
Steps to reproduce
Repeatedly running npm test spec/ParseLiveQueryTest.spec.js
should eventually cause this condition to trip. If it is dependent on other spec files the entire test suite may need to be run via npm test
instead.
Expected Results
Test should return a repeatable consistent result with no periodic failures.
Actual Outcome
Test intermittently fails without evident changes having been made.
Environment Setup
-
Server
- parse-server version : 2.6.4
- Operating System: Linux (trusty)
- Hardware: n/a
- Travis CI
-
Database
- Postgres version: 9.5
- Hardware: n/a
- Travis CI
Logs/Trace
✗ can handle connect command
- Failed: cannot perform operation: a background operation is currently running for collection parse._Role
Metadata
Metadata
Assignees
Labels
No labels