[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Fw: Failures in the Hudson Juno run.aggregator job?

Next update:
Mylyn's fixed (moved/copied) their repo.
Next problem that showed up was a Jubula ripple effect due to EclipseLink repo being disabled (ignore that, I went back and disabled EclipseLink feature only, instead of whole repo so Jubula can "find" what it needs for now).

Next was an ACTF problem. I saw that early ... so, will need to investigate, but its a leaf component so I think we can temporarily disable unless we hear something from the team soon ... say in the next 3 minutes?

Thanks,




From:        David M Williams/Raleigh/IBM@IBMUS
To:        Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        06/13/2012 11:57 AM
Subject:        [cross-project-issues-dev] Fw: Failures in the Hudson Juno        run.aggregator job?
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx




Update ... Eric said to temporarily disable EclipseLink, and he'll try to rebuild to avoid this dependency ... we'll see who shows up next.

[FYI, it is helpful, if you get a not about your project failing, to keep us all informed, here on cross-project list. I know many are waiting for a "green build"].



----- Forwarded by David M Williams/Raleigh/IBM on 06/13/2012 11:48 AM -----


From:        
David M Williams/Raleigh/IBM
To:        
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        
06/13/2012 11:45 AM
Subject:        
Re: [cross-project-issues-dev] Failures in the Hudson Juno        run.aggregator job?




Nope, just me (just kidding). The current "visible" problem is with EclipseLink but ... just so everyone else knows what we (don't) know ... we've exchanged some notes and something "mysterious" is going on. Current theory is that "mylyn's" whole repo is missing ... waiting to hear from them ... here's the exchange so far ... if anyone has recently removed
ejb_3.1.0 from their repo, can you let us know?


> > David,
> >
> > I'm curious why this is happening now. This same build has been
> > submitted since last Thursday or Friday, and is only failing today.
> >
> > After review it looks legitimate and we are investigating what we
> > should do about it, but the issue looks like it had been masked, and
> > I'm wondering if the masking is permanently removed, or if this
> > failure will in essence be temporary.
> >
> > The problem is that we aren't building our repo with the ejb_3.1.0
> > dependency (we don't put it in plugins and the features don't depend
> > upon it - but a jar would depend upon the classes. The jar in
> > question is a special case though as it would only be used in a
> > container where the classes already exist - so actually shipping the
> > jar would be superfluous).
> >
> > -Eric


> Eric,
> Hmm, not sure ... it could be you (or, aggregator) was "picking it
> up" from someone's else repo and they have changed their repo.
>
> And, I think Mylyn's repo is currently "not present at all". Does
> this sound like the kind of think that Mylyn might have in their repo?
> David





From:        
Jeff Johnston <jjohnstn@xxxxxxxxxx>
To:        
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>,
Date:        
06/13/2012 11:34 AM
Subject:        
[cross-project-issues-dev] Failures in the Hudson Juno        run.aggregator job?
Sent by:        
cross-project-issues-dev-bounces@xxxxxxxxxxx




I noticed that the Juno run.aggregator job is failing on Hudson after a
bunch of RC4 changes.  Is someone assigned to each of the issues (other
than David)?

-- Jeff J.
_______________________________________________
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