| Since the move to the CBI build, I have not paid attention to the shared install tests since they initially had issues running in this environment. That said I just ran the tests locally and there are some issues with the tests themselves - the verifier bundle, a bundle being used to sniff the shared run needs to be modified.
Given the late time of the day, I'm going to refrain from doing any change and I will look at it during the week end. If you are going to re-build, I can disable the tests.
Pascal On 2013-03-14, at 5:32 PM, Ian Bull wrote: Hi everyone,
I was looking at the recent test failures in p2, and fixed a few. Here is a summary.
testNickname (2 failures)
This was a problem with test ordering. With JUnit 4 order matters, and we had other tests that were changing the nickname of a repository. I fixed this by clearing the Nickname in these other tests.
testGZFileAreNotUnzipped (1 failure)
We were running a test that was using the symbolic name of an ECF bundle in the test. This bundle's name has changed (it had the segment httpclient which was changed to httpclient4). I've updated the test and it now passes locally.
SharedConfigurationTests (2 failure)
I haven't looked at these. Pascal has been doing some things with Shared Installs, and I hope he can investigate this.
AbstractSharedInstallTest (2 failure)
I haven't looked at these. Pascal has been doing some things with Shared Installs, and I hope he can investigate this.
In summary, the first 3 test failures have been fixed, although they were only problems with the tests themselves. The last 4 are still there. Since the shared install support is something that is currently under development, and Pascal seems to have a good grip on this, I'm not calling to call a Stop Ship for M6. Pascal, if you feel otherwise, please let us know.
Cheers, Ian
-- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
|
