-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Possible Racing Test (postgres) #4294
Comments
Observed this error in the same place again but for the
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. |
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: