Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 324948

Summary:	[tests] Test failures due to missing repository
Product:	[Eclipse Project] Equinox	Reporter:	DJ Houghton <dj.houghton>
Component:	p2	Assignee:	P2 Inbox <equinox.p2-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	john.arthorne, tjwatson
Version:	3.7
Target Milestone:	3.7 M3
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:
Bug Depends on:
Bug Blocks:	324960, 324961

Description DJ Houghton

2010-09-10 07:24:29 EDT

The tests in our builds (M, I, and N) have been failing this week with the following error:

!ENTRY org.eclipse.equinox.p2.artifact.repository 4 1000 2010-09-09 15:27:43.819
!MESSAGE No repository found at http://download.eclipse.org/eclipse/updates/3.6-I-builds.

!ENTRY org.eclipse.equinox.p2.core 4 0 2010-09-09 15:27:43.820
!MESSAGE Unable to load repositories.
at org.eclipse.equinox.p2.tests.full.Install36from35.install36From35(Install36from35.java:66)

This is because the 3.6 i-builds update site has been deleted. We should re-write the test to point to a new repository. (probably the Helios final repo)

Comment 1 DJ Houghton

2010-09-10 08:53:01 EDT

I talked to Kim and the 3.6 i-builds repo has been removed. It sounds like the right thing to do is change the tests to point to the real 3.6 repo.

Comment 2 DJ Houghton

2010-09-10 08:58:22 EDT

Fixed in HEAD.

Comment 3 Thomas Watson

2010-09-10 09:24:06 EDT

(In reply to comment #2)
> Fixed in HEAD.

What about future 3.6.2 builds?  Will it continue to fail?

Comment 4 DJ Houghton

2010-09-10 09:25:15 EDT

(In reply to comment #3)
> What about future 3.6.2 builds?  Will it continue to fail?
>

I released it to the 3.6.x stream as well. See bug 324960.

Comment 5 John Arthorne

2010-09-10 09:48:45 EDT

Wouldn't it be more useful at this point for the test to upgrade from 3.6 to 3.7? Of course in the 3.6.x stream it should still test 3.5->3.6.

Comment 6 DJ Houghton

2010-09-10 09:52:12 EDT

(In reply to comment #5)
> Wouldn't it be more useful at this point for the test to upgrade from 3.6 to
> 3.7? Of course in the 3.6.x stream it should still test 3.5->3.6.

Bug 324962 has been opened to address this.