Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Status and outlook for SR1 RC3 -- are we in trouble? -- no longer
> The slf4j.jcl bundle is not there, but I suppose that Markus has fixed the pb differently.

I do see following message in log ... probably related to how Markus fixed it ... are "cycles" very bad? I guess it is only an "info" message so I'd assume not.

!ENTRY org.eclipse.osgi 2 0 2010-09-10 00:21:01.483
!MESSAGE Info: cycle(s) found while stopping bundles: [[ch.qos.logback.classic,org.slf4j.api,ch.qos.logback.slf4j,ch.qos.logback.core]].

(this was while testing the _javascript_ IDE from 9/9)





From:        Pascal Rapicault <pascal@xxxxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        09/10/2010 12:01 AM
Subject:        Re: [cross-project-issues-dev] Status and outlook for SR1 RC3        --        are we in trouble? -- no longer
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx



On a JEE package, I have tested the following and was successful.
- Downloaded SR0
- Updated to SR1 (I did in a strange because I could not find a repo with the EPP metadata for the SR1 package)
- Make the resulting install  readonly (after cleaning up the configuration/org.eclipse.osgi)
- Run
- Install findbugs from MarketPlace
- Restarted and looked for the plugins in the plugins list

The slf4j.jcl bundle is not there, but I suppose that Markus has fixed the pb differently. In any event the configuration looked consistent, all the bundles in the bundle.info were in the plugins folder.

I'm rather confident that we are good. The only thing we need to do now is confirm for each package, that every bundle listed in the bundles.info is indeed found in the plugins folder.

PaScaL

On 2010-09-09, at 11:34 PM, David M Williams wrote:

> Yes, the "nightlies" at
> http://www.eclipse.org/epp/download.php
> for 9/9 should have that fix

Well, maybe not.
I don't see it in the _javascript_ package.
I see
org.slf4j.api_1.5.11.v20100519-1910.jar
but should (also) see
org.slf4j.jcl_1.5.11.v20100419-1106.jar

Right?

I guess we'll have to wait for Markus to tell us.





From:        David M Williams/Raleigh/IBM@IBMUS
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        09/09/2010 07:54 PM
Subject:        Re: [cross-project-issues-dev] Status and outlook for SR1 RC3 --        are we in trouble? -- no longer
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx



Yes, the "nightlies" at
http://www.eclipse.org/epp/download.php
for 9/9 should have that fix .... as far as I understand ... haven't looked myself.

On other news, I've had to disable linuxtools again while bug 324419 continues to be investigated. (I personally don't think it's linuxtools "fault", btw ... but, not sure anyone knows yet why p2 (or the b3 builder) isn't "finding" what it needs.).

So, I've disabled so we can get a clean build with mylyn and actf in it ... once we do (approx 11 pm eastern) I'll promote that, and we'll have new RC3 (candidate) packages in the morning.






From:        Pascal Rapicault <pascal@xxxxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        09/09/2010 07:45 PM
Subject:        Re: [cross-project-issues-dev] Status and outlook for SR1 RC3 --        are we in trouble? -- no longer
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx



Do we have EPP packages based on those builds?
Would those packages include the changes discussed earlier wrt the inclusion of slf4j bundles.

On 2010-09-09, at 11:16 AM, David M Williams wrote:

Thanks Kim (and John) .... that seemed to do the trick and we actually got a green build on the first try! Hopefully that's give others (especially all the +3 teams) to finish up on time today.

I did promote the successful build to
http://download.eclipse.org/releases/maintenance/
so some preliminary packages could be created by end of today and some early repo testing done, for those teams that want/need to do that.

- - - - - -
> Plus, there's been no comment in bug 324419
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=324419
> which was blocking LinuxTools from contributing last week.

There has at least been some comments in this bug now ... there's not an obvious solution yet, but we'll see if we can come up with something to get LinuxTools back on the train.

- - - - - -
@Beth
> When is the aggregation of the repo likely to run?

Already happened ... at least the rep creation, if that's what you meant. Others will be kicked off within 15 minutes of someone committing a change to the b3aggrcon file.
(If I am missing the point of your question, feel free to ask again).


Thanks everyone .. maybe there's hope after all :)





From:        Kim Moir <Kim_Moir@xxxxxxxxxx>
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        09/09/2010 09:22 AM
Subject:        Re: [cross-project-issues-dev] Status and outlook for SR1 RC3 -- are we        in trouble yet?
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx




I've cleaned up our repo.  David, if you could try another build that would be great.  The content in our aggregator files has not changed.

Kim
John Arthorne/Ottawa/IBM@IBMCA
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

09/09/2010 08:56 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject
Re: [cross-project-issues-dev] Status and outlook for SR1 RC3 -- are we        in trouble yet?









The Eclipse and Equinox features are consistent from my parsing of the metadata for the last few builds. However there is an older version of "org.eclipse.equinox.server.p2" being picked up by the aggregation that doesn't match what is in the latest platform build. I think we should be discarding our old builds that are still hanging around in our repository because somebody is picking them up. I'll chat with Kim about it.
David M Williams <david_williams@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

09/09/2010 12:19 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
To
cross-project-issues-dev@xxxxxxxxxxx
cc
Subject
[cross-project-issues-dev] Status and outlook for SR1 RC3 -- are we        in trouble yet?









Yes, I think we are in trouble. We haven't had a good build in two days. I'll admit Monday was a holiday for a lot of people .... but ... it's now Thursday ... +3 day!

I didn't pay much attention to the failures at first, expecting them to be fixed soon, but I think they may have all been similar to the latest one, see summary notice attached below or full console log at
https://build.eclipse.org/hudson/view/Repository%20Aggregation/job/helios.runAggregator/345/console

It appears  that Eclipse platform and Equinox have some inconsistencies? (In a brief note from Kim, she thought it might be related to features losing their distinctive version qualifier suffix (bug 208143 https://bugs.eclipse.org/bugs/show_bug.cgi?id=208143) and she was hoping "the next build" would fix that. Apparently not?

What scares me is once Eclipse/Equinox is fixed, I'm sure there will be several more issues, as there often is with Jetty and RAP having exact dependency versions ... hopefully they can react quickly, if that's still the case.

Plus, there's been no comment in bug 324419
https://bugs.eclipse.org/bugs/show_bug.cgi?id=324419
which was blocking LinuxTools from contributing last week.

By all rights, if we are on day +3 and the day +0 contributions have not built yet, the whole schedule slips out 2 or 3 days.

I am hoping we can avoid that. Perhaps if we all get out of "holiday mode" and focus on the simultaneous release builds on Thursday we can recover? Let's assess schedule changes at the end of Thursday (or early Friday).

Thank you .... and good luck!





----- Forwarded by David M Williams/Raleigh/IBM on 09/08/2010 11:39 PM -----

From:        David M Williams/Raleigh/IBM@IBMUS
To:        Kim Moir <kmoir@xxxxxxxxxx>
Cc:        David M Williams/Raleigh/IBM@IBMUS
Date:        09/08/2010 04:51 PM
Subject:        [HeliosAggregation] Failed for build 2010-09-08_16-46-02



The following errors occured when building Helios:

Software being installed: all.contributed.content.feature.group 1.0.0

Only one of the following can be installed at once: [org.eclipse.equinox.p2.artifact.repository 1.1.1.R36x_v20100901, org.eclipse.equinox.p2.artifact.repository 1.1.1.R36x_v20100823, org.eclipse.equinox.p2.artifact.repository 1.1.0.v20100513]

Cannot satisfy dependency: all.contributed.content.feature.group 1.0.0 depends on: org.eclipse.equinox.sdk.feature.group 3.6.1.r361_v20100903-7H7R07v8rtOZyYbv1I6aZgou5z07

Cannot satisfy dependency: all.contributed.content.feature.group 1.0.0 depends on: org.eclipse.sdk.ide 3.6.1.M20100908-0800

Cannot satisfy dependency: org.eclipse.equinox.p2.user.ui.feature.group 2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr depends on: org.eclipse.equinox.p2.artifact.repository [1.1.1.R36x_v20100901]

Cannot satisfy dependency: org.eclipse.equinox.sdk.feature.group 3.6.1.r361_v20100903-7H7R07v8rtOZyYbv1I6aZgou5z07 depends on: org.eclipse.equinox.serverside.sdk.feature.group [3.6.0.v20100421-7u7NFVgFN5JdPKPhDHd_6Yqc54uw]

Cannot satisfy dependency: org.eclipse.equinox.server.p2.feature.group 1.0.0.v20100503-7x7IFGOFQ74dz0POCNUBj98N depends on: org.eclipse.equinox.p2.artifact.repository [1.1.1.R36x_v20100823]

Cannot satisfy dependency: org.eclipse.equinox.serverside.sdk.feature.group 3.6.0.v20100421-7u7NFVgFN5JdPKPhDHd_6Yqc54uw depends on: org.eclipse.equinox.server.p2.feature.group [1.0.0.v20100503-7x7IFGOFQ74dz0POCNUBj98N]

Cannot satisfy dependency: org.eclipse.sdk.ide 3.6.1.M20100908-0800 depends on: org.eclipse.equinox.p2.user.ui.feature.group [2.0.1.r361_v20100903-897HFZFFZRuSD2LMtVxyz0Vr]

Check the log file for more information: https://build.eclipse.org/hudson/view/Repository%20Aggregation/job/helios.runAggregator/345/console
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Back to the top