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
This may be a symptom of the test database not being properly isolated from the "development" database. I feel like there's a chance that all groups are actually hitting the same database file on tiki, and one group's tests are now touching the database in a way that makes the tests fail. But that's just a hunch, I have no proof of that.
I've just been looking at this, too. The output is still similar to my team's first successful build. Although the test case only adds and then deletes a user "rchamer," I don't know why there is so much going on the standard output/error.
So I think it means that DataStore is not behaving well and that the test results (especially testDelete) depend on the order of test case execution, where they shouldn't.
testUpdate in the same file (Db4oDatabaseTest.java) also fails. This comes up occasionally on Jenkins, but consistently comes up with testDelete failing as well when running just that file as a JUnit test. testUpdate fails because the user that is saved in as an ID of 0, but when pulled out the ID is 1.
Recently, my group has run into this test failing intermittently:
http://tiki.cs.wpi.edu:8080/jenkins/job/dragonsparkles4/72/testReport/
I ran some manual builds of our repo and got it to fail:
http://tiki.cs.wpi.edu:8080/jenkins/job/wpi-suite-tng/121/testReport/
This may be a symptom of the test database not being properly isolated from the "development" database. I feel like there's a chance that all groups are actually hitting the same database file on tiki, and one group's tests are now touching the database in a way that makes the tests fail. But that's just a hunch, I have no proof of that.
The text was updated successfully, but these errors were encountered: