These are chat archives for etorreborre/specs2

10th
Oct 2017
hodga
@hodga
Oct 10 2017 09:32
I finally found out what was wrong. The errors seems to appear randomly, but it happened when i did this: there was after(timeout).no(mock)
which i think is wrong anyway
hodga
@hodga
Oct 10 2017 09:56
However, the tests did not fail in 3.9, and the error messages told me nothing of where the error occured, which has been a problem before for me before. I suspect Mockito is to blame, but if you have any idea on how to get more precise error messages I could try to help.
Eric Torreborre
@etorreborre
Oct 10 2017 09:58
Do you have a test project I could use to investigate the issue? Are you saying that you get org.mockito.exceptions.misusing.UnfinishedVerificationException intermittently?
hodga
@hodga
Oct 10 2017 09:59
No, it happens at the same place every time as long as i dont modify the tests, but it happens in tests that are in no way connected to where the error is, at least from what i can tell from the output and project structure.
I have created a project where i recreated, i can push it to my github
Eric Torreborre
@etorreborre
Oct 10 2017 10:00
can you try to run your spec sequentially?
hodga
@hodga
Oct 10 2017 10:06
you mean like this? parallelExecution in Test := false
Eric Torreborre
@etorreborre
Oct 10 2017 10:07
this can be tried to but I was thinking of testOnly *MySpec -- sequential
hodga
@hodga
Oct 10 2017 10:07
ah, ok, but the error do not occur whan i run single tests, only when i run many
Just now i tried to strip my reproducing project down and the test disappeared
Eric Torreborre
@etorreborre
Oct 10 2017 10:08
I am wondering if this could be due to sbt classloading which is not deterministic and caused issues in the past
hodga
@hodga
Oct 10 2017 10:12
I dont know, it seems pretty deterministic, there could be some issues with caching?
I also updated from sbt 0.13.15 to sbt 1.0.1 and the errors was the same, though the time the errors happened changed
i pushed a project that reproduces the problem here
Eric Torreborre
@etorreborre
Oct 10 2017 10:14
Thanks I will try to have a look at it later today
hodga
@hodga
Oct 10 2017 10:15
Great :) I added the error in the test do stuff 8 on line 231 in TestClassATest
Eric Torreborre
@etorreborre
Oct 10 2017 10:16
ok
hodga
@hodga
Oct 10 2017 10:16
and the error happens for me in TestClassATest4 on line 28
Eric Torreborre
@etorreborre
Oct 10 2017 17:00
For me the error is on hod.TestClassesTest2, line 11. I will try to fix that tomorrow
Thanks for this project that's really helpful :-)