Do you still have a note of the javaspace tests that failed? If not,
I'll run the category and see what happens.
It is interesting to note that both the test failures I've tackled
recently turned out to be showing up problems in the code under test,
not just the tests. It shows the importance of letting the tests speak
to us by running them and analyzing failures.
Patricia
On 10/20/2010 1:44 PM, Jonathan Costers wrote:
Great job Patricia!
My vote would go to the "javaspace" test category.
Last time I ran that one (250 or so tests IIRC) I got 16 failures.
If we can get these cleared up, I believe we have a solid test base in place
to start validating some new developments and experiments.
Looks like we are really getting some momentum here, I like it a lot.
Thanks to all for your hard work.
Jonathan
2010/10/20 Patricia Shanahan<[email protected]>
On 10/19/2010 4:08 PM, Patricia Shanahan wrote:
I propose modifying TxnManagerImpl to make it match the interface
declaration, and allow an abort to be retried. This may break other
tests, if they are assuming the behavior that TxnManagerImpl implemented.
I'm doing a full QA test, including txnmanager. Although the test is still
running, all of the txnmanager tests, including GetStateTest, have passed.
Those tests are the most likely to notice the change.
If the rest of the QA test is clean when it finishes, I'll check in the fix
and we can add txnmanager to the default category list.
Any votes on my next bug hunt? For example, are there bug reports in Jira
that really need to be fixed before the next release?
Patricia
