Closed GoogleCodeExporter closed 9 years ago
my test suite still shows the passed/failed numbers.
Original comment by omegabla...@gmail.com
on 12 Nov 2010 at 1:16
can't repro in r2609.
I'm the first one to believe there might be some kind of race condition in the
test suite, and I know that you double checked, but since you've got a huge
history of having the test suite fail because of your own changes, can I ask
you to triple check?
Finding someone who runs into the exact same problem would be the best actually.
Wat are your systems specs? I have visual studio 2008 and vista.
Original comment by wagic.the.homebrew@gmail.com
on 13 Nov 2010 at 2:16
can't repro either, not sure if i was clear about that in my comment.
Original comment by omegabla...@gmail.com
on 13 Nov 2010 at 11:54
Here's how you repro it. It's tied to the last test ran.
I did the following:
1) run only "unearth3.txt" in the test suite -> no message
2) run "unearth3.txt" plus a few other tests -> message "1 of X tests failed!"
3) run "unearth3.txt" plus the same other tests with "unearth3.txt"
being the last test. -> no message.
It seems to be that if the last test run fails, no message appears.
It could be tied to just unearth3.txt, I'll have to run a few more
tests.
Original comment by techdragon.nguyen@gmail.com
on 13 Nov 2010 at 2:23
after more testing on a clean checkout (4th one), this is what I am observing
don't know if it has to deal solely with unearth tests, but they are the ones I
found that exhibit this behavior.
If the suite ends in a test with unearth, the summary screen is blank. any
other test seems to display the summary successfully.
Stepping through the code, the code to draw the summary information does get
executed. However, in the former case nothing is shown, the latter summary
information is shown
I can't figure it out beyond that. It is becoming less and less likely that
anybody will run into this particular problem since it seems I am the only
person that will run single tests. my machine takes 15+ minutes to run the
entire suite, so I run my individual tests first. Once those pass, I run the
entire suite to make sure nothing else is broken.
For this particular issue, I've not modified any base code, just what tests are
run.
Original comment by techdragon.nguyen@gmail.com
on 13 Nov 2010 at 3:13
unearth3.txt needs to be fixed, so I will most likely have to run it
individually (I don't run the entire test suite when I'm debugging a particular
case, and I hope nobody does).
I'll keep you posted.
Original comment by wagic.the.homebrew@gmail.com
on 13 Nov 2010 at 11:30
Just to clarify:
When I said I don't run the entire test suite, I of course meant "while I'm
debugging a specific issue".
We should ALL be running the entire test suite before any code submission to
the repository.
Original comment by wagic.the.homebrew@gmail.com
on 14 Nov 2010 at 1:01
Fixed in r2611
Original comment by wagic.the.homebrew@gmail.com
on 14 Nov 2010 at 1:16
Original issue reported on code.google.com by
techdragon.nguyen@gmail.com
on 12 Nov 2010 at 8:40