You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Observed this error in the same place again but for the _User collection.
Failed: cannot perform operation: a background operation is currently running for collection parse._User
Can confirm this is occurring on postgres so far as I've observed. I haven't seen this on mongodb yet. It's looking possible that this race is strictly related to our implementation in that db.
montymxb
changed the title
Possible Racing Test
Possible Racing Test (postgres)
Oct 31, 2017
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Issue Description
Observed a possibly racing test case, which seems to intermittently result in a failure. The test is
can handle connect command
inParseLiveQueryTest.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 vianpm 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
Database
Logs/Trace
The text was updated successfully, but these errors were encountered: