Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] repository done for SR1 RC3 - and I really mean it this time :)

Jeff has (apparently) successfully worked around this issue described in bug 324419.
That is, we got a successful aggregation build with linuxtools re-enabled.
So, I think worth re-promoting another RC3 repo to /releases/maintenance and I have just done so.
[Let me know if this has consequences I did not anticipate so I'll know to use more care in future].

One complication is this also includes some late changes to
dltk, and
emft-eef

I suspect the committers and clients of those projects would find that a good thing ... but, might (technically speaking) invalidate testing anyone else has already done this morning on the repo. (Technically it would, but in practice, doubt it'd break anything ... since they made it through an aggregation build).

So, please continue, or re-test the RC3 repo at  /releases/maintenance
But looks like linuxtools will be able to finally get an RC3 package to test with one last chance to correct errors next week in RC4.
(Yay! ... we've never "lost" anyone from the train ... so far)  

Speaking of next week ... the schedule remains the same ... even with the final, official RC3 EPP packages delayed until Monday.
Hopefully everyone is basically done, and just a few tweaks to come in next week.

Mon Sep 13                 Helios SR1 RC4 +0
Tue Sep 14                 Helios SR1 RC4 +1
Wed Sep 15                 Helios SR1 RC4 +2
Thu Sep 16                 Helios SR1 RC4 +3 [Helios repo aggregation builds tagged and turned off. After this point, respins will take an act of the Planning Council]
Fri Sep 17                 Indigo M2 +0 [no rest for the weary]
                        Helios SR1 RC4 EPP+


Thu Sep 23                 Helios SR1 promote and mirror
Fri Sep 24                 Helios SR1 GA


Thanks everyone ... as always, please feel free to ask questions or post issues here to this list and keep us all informed of complications.






From:        David M Williams/Raleigh/IBM@IBMUS
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        09/09/2010 11:57 PM
Subject:        Re: [cross-project-issues-dev] repository done for SR1 RC3
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx




Unfortunately Jeff Johnston's changes did not work around the underlying problems after all. So I temporarily removed it (again).
I hope the teams involved [ see note 1] can continue to diagnose/work on the problem on Friday ...


https://bugs.eclipse.org/bugs/show_bug.cgi?id=324419

... but, trains can't wait ? :(


Let's say we are done for the repository for SR1 RC3 ... the packages are building now, should be ready by morning (Eastern time) and ready for signoff ... well ... not to mention the complication of the slf4j bundles which might require a respin ... unless I misunderstood what that fix should be ... which would not be the first time I misunderstood what was planned :)


If there's any quick breakthroughs for bug 324419, I'd be happy to work into the weekend to get linux tools back in the groove, but suspect we should plan on delivering what we have as RC3 so that not everyone has to work through the weekend.


Thanks everyone,



[note 1] The teams involved are, in decreasing order of priority or urgency are
a) b3 aggregator (are update sites, partial IUs, being handled correctly?)
b) p2 team (do we need some p2 fix that's in 3.6.1, but not 3.6.0?
c) GEF team, can you provide a true p2 repo?
d) the linux tools team (to react to any of the above teams comments :)







From:        
Jeff Johnston <jjohnstn@xxxxxxxxxx>
To:        
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        
09/09/2010 06:05 PM
Subject:        
Re: [cross-project-issues-dev] Status and outlook for SR1 RC3
Sent by:        
cross-project-issues-dev-bounces@xxxxxxxxxxx




Hi David,

I completed the rebuild and updated the b3aggrcon file.  I assume I don't have to add "enabled=true" in the file, but if that is necessary, please feel free to do so.

I hope this solves the problem.

-- Jeff J.

On 09/09/2010 05:39 PM, David M Williams wrote:

Thanks for letting us know.

I know there's still some work going on to address bug 324419 (to get LinusTools back in)

https://bugs.eclipse.org/bugs/show_bug.cgi?id=324419

So, I'll keep an eye on things and make sure, one way or another, we get at least one more good "build" this evening ... if not two.

Thanks,






From:        
Steffen Pingel <steffen.pingel@xxxxxxxxxxx>
To:        
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:        
09/09/2010 04:10 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




We are running a bit late but would like to contribute another Mylyn build for RC3 later today to fix an important bug. I am expecting to kick off the build soon so the contribution should be ready by ~3.30 PM PDT if all goes well.

Steffen


On Thu, Sep 9, 2010 at 8:16 AM, David M Williams <
david_williams@xxxxxxxxxx> 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




--
Steffen Pingel
Committer,
http://eclipse.org/mylyn
Senior Developer,
http://tasktop.com_______________________________________________
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