Bugzilla – Full Text Bug Listing
| Summary: | [Tooling] TargetSwitcher_Test fails | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Rüdiger Herrmann <ruediger.herrmann> |
| Component: | Demo | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | beyhan.veliev |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Rüdiger Herrmann
(In reply to comment #0) > All test cases from the TargetSwitcher_Test fail. I tried to run them aginst a > 3.6.1 target as well as 3.7M6 - same result. > Note: I am using a launch config with manually selected plug-ins as I had > problems with junit4 when running with all plug-ins from workspace and target. > The launch config is valid according to the the 'Validate Plug-ins' button. > What's wrong? > Hi Rüdiger, are you using the launch configuration available with the tests? The launch configuration for 3.6.1 available with the test should work for 3.6 and 3.7. You just need to select the right SWT fragment. P2 provides its APIs as OSGi services and I suppose that the org.eclipse.equinox.ds is not selected in your launch configuration that is why the NullPointerExceptin happens. Thanks for the tip, Equinox DS was missing. Now the testSwitchTagret test succeeds but all remaining test cases from TargetSwitcher_Test still fail. Any idea? org.eclipse.core.runtime.CoreException: Problems occurred while resolving the target contents at org.eclipse.rap.ui.internal.intro.target.TargetSwitcher.downloadTarget(TargetSwitcher.java:167) at org.eclipse.rap.ui.internal.intro.target.TargetSwitcher.install(TargetSwitcher.java:97) at org.eclipse.rap.ui.internal.intro.target.TargetSwitcher_Test.testInstallTargetAvailable(TargetSwitcher_Test.java:95) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at junit.framework.TestCase.runTest(TestCase.java:164) [ ... ] Contains: An error occurred while collecting items to be installed Contains: session context was:(profile=TARGET_DEFINITION:local:1300814044994.target, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Contains: java.lang.NullPointerException at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:582) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:565) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:637) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:249) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:224) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:180) at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:116) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:621) at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifacts(SimpleArtifactRepository.java:692) at org.eclipse.equinox.internal.p2.engine.DownloadManager.fetch(DownloadManager.java:110) at org.eclipse.equinox.internal.p2.engine.DownloadManager.start(DownloadManager.java:99) at org.eclipse.equinox.internal.p2.engine.phases.Collect.completePhase(Collect.java:76) at org.eclipse.equinox.internal.p2.engine.Phase.postPerform(Phase.java:216) [ ... ] (In reply to comment #2) > Thanks for the tip, Equinox DS was missing. Now the testSwitchTagret test > succeeds but all remaining test cases from TargetSwitcher_Test still fail. > Any idea? The bundle o.e.e.p2.transport.ecf is missing which provides the Trasport/Download mechanism of P2. Also make sure that o.e.ecf. o.e.ecf.filetransfer and o.e.ecf.provider.filetransfer are selected. I just verified that "RAP Tooling Tests 3.6" launch configuration available in CVS doesn't select all bundles. Just the required. Does this launch configuration not work for you? It uses junit 3. Since the "RAP Tooling Tests 3.6" launch config didn't work out of the box I must have ruined it completely while trying to bring it to work. Replacing with HEAD and adding the right SWT fragment brought it back to work. Thanks for your assistance! Though there is one other thing I noticed: some of the tests write "[Fatal Error] :1:1: Premature end of file." to System.err. Can we do anything about this or is it is written by p2? (In reply to comment #4) > > Though there is one other thing I noticed: some of the tests write "[Fatal > Error] :1:1: Premature end of file." to System.err. Can we do anything about > this or is it is written by p2? It is written by p2 but I don't get these error messages when I run the tests on Windows. I'm creating on the fly p2 repositories for the tests and jarring artifacts using an ant script. I suppose that the jars created by the script are corrupted on Linux and that is why p2 logs such an error message. But I don't know exactly where the problem is. If you have an idea let me know. (In reply to comment #5) > (In reply to comment #4) > > > > Though there is one other thing I noticed: some of the tests write "[Fatal > > Error] :1:1: Premature end of file." to System.err. Can we do anything about > > this or is it is written by p2? > It is written by p2 but I don't get these error messages when I run the tests on > Windows. I'm creating on the fly p2 repositories for the tests and jarring > artifacts using an ant script. I suppose that the jars created by the script are > corrupted on Linux and that is why p2 logs such an error message. But I don't > know exactly where the problem is. If you have an idea let me know. I do run the tests on Windows (Vista 32), too. I opened bug 340737 to track this issue, |