Hi
slave1 seems ok but fastlane has gone uncommunicative
(https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-branch-tests/194/)
Regards
Ed Willink
On 13/06/2012 02:46, Denis Roy wrote:
I have restarted the slave agent on slave1. Let me know if this does not solve
the
Same here, all our builds fail immediately with:
Building remotely on Fastlane
hudson.util.IOException2: remote file operation failed:
/opt/users/hudsonbuild/workspace/rap-2.0-tools at
hudson.remoting.Channel@237c8a9c:Fastlane
at hudson.FilePath.act(FilePath.java:754)
at
Yes, it works again now.
Thanks!
On Wed, Jun 13, 2012 at 1:53 PM, Mike Milinkovich
mike.milinkov...@eclipse.org wrote:
I believe Denis got this restarted. Please let us know if you're still having
problems.
Mike Milinkovich
mike.milinkov...@eclipse.org
+1.613.220.3223
-Original
Hi Folks,
I have another question concerning the Market Place.
Can the added content (of a Eclipse Projects) be shared among
different committers ? Can they be transferred in somehow ?.
Otherwise, I don't find this mechanism operational... What happen if
a
David Williams wrote on 06/12/2012 05:15:26 PM:
I appreciate everyone keeping the build green and making progress
on the sim rel reports [1], though there are a few serious issues
left there.
[1] http://build.eclipse.org/juno/simrel/reporeports/
I looked through these, and at this
Hey all,
Just updated the Virgo contribution. The mentioned above reports should be
fine now.
Waiting on the new reports...
Thanks,
Bobby
On Wed, Jun 13, 2012 at 4:45 PM, John Arthorne john_artho...@ca.ibm.comwrote:
David Williams wrote on 06/12/2012 05:15:26 PM:
I appreciate everyone
For the duplicate org.eclipse.rap.* bundles, 1.5.0.20120612-1458 our
RC4 contribution, 20120605-1606 is RC3. I guess someone depending on
the rap runtime has not picked up the RC4 yet, could that be EMF?
The duplicate org.eclipse.jetty.xml bundles come from the rap tools.
For some reason, they
It looks like this dependency is coming from RT packaging, not Saphire:
That makes more sense. All Sapphire dependencies are written very broadly since
the Juno release is actually compatible back to Helios. For
org.eclipse.core.commands, our sole dependency is written like so:
required
Am 13.06.2012 um 16:13 schrieb Ralf Sternberg:
For the duplicate org.eclipse.rap.* bundles, 1.5.0.20120612-1458 our
RC4 contribution, 20120605-1606 is RC3. I guess someone depending on
the rap runtime has not picked up the RC4 yet, could that be EMF?
We include any rap bundles or features,
Konstantin Komissarchik wrote on 06/13/2012 10:14:52 AM:
Re: [cross-project-issues-dev] Status and Outlook for Juno!
It looks like this dependency is coming from RT packaging, not
Saphire:
That makes more sense. All Sapphire dependencies are written very
broadly since the Juno release
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@eclipse.org
Hello,
In the first failing build
(https://hudson.eclipse.org/hudson/job/juno.runAggregator/516/), we can see
that the only change is the MoDisco 0.10.0 RC4 delivery.
I'm not used to read the aggregator log. Does anyone understand what is the
problem ?
If MoDisco is causing the problem. We
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
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
Hi David,
I'm now working for ACTF... Our new build will be available in several
minutes, but I'm not sure it can be ready for next aggregation build.
If we can't fix the issue soon, I'll go back to our older build methods.
Best regards,
Kentarou
---
Kentarou Fukuda, Ph.D.
IBM Research -
Ok, and ... maybe you fixed it already? :)
I made my statement based on my local build, which gave (and still
gives) the error below ... but, the aggregation on build.eclipse.org seems
to be doing ok. So ... not sure if what's causing that difference.
Cannot complete the install because one
Hey folks. I'm in the process of marking the first round of release
reviews [1] as successful. If your review was scheduled to wrap up
today, consider yourself good-to-go.
I will begin updating the corresponding bugs in the next few minutes.
FYI, we don't do review calls any more. We haven't for
Thanks for the summary, John.
On 06/13/2012 09:45 AM, John Arthorne wrote:
2) 10 features with no license (in particular their license is the
string %license). 1 from Virgo, 9 from Gemini. The most common cause
of this is missing key in feature.properties file, or the
feature.properties file
Could this be a bogus hit?
Absolutely not! :)
Its just the last day is a rapidly changing one! Ironic?
Virgo noted to this list already they'd just fixed the features licenses
and indeed the latest report is clean for features:
Hi,
I think (hope) problem in ACTF was cleared. But, I noticed that
aggregation build was stopped by other problem.
Are there any changes in emf/query2?
[exec] Mirroring artifacts from
file:///home/data/httpd/download.eclipse.org/modeling/emf/query2/updates/1.0
[exec] Build failed!
Looks like the currently running aggregation build, #534, got both changes
and it passes verification for me locally, so hopefully the mirroring will
succeed and it will be finished about 5:00 and I hope to be back to my
computer about 5 to promote new build to staging.
So ... if anyone needs
Ok, ... about 6:15 PM Eastern?
The previous build failed due to emf.query2 problem (bug 381786) so I'll
disable that and there will be just about enough time to try a respin
before 6:15 ... so, heck ... take till 6:30. :)
From: Holger Staudacher hstaudac...@eclipsesource.com
To:
Hi David,
the RTP build is done and contributed to the aggregator. The repository is
tested and from my point of view everything looks fine.
Hope everything works as expected :)
Cheers Holger
On Jun 13, 2012, at 11:10 PM, David M Williams wrote:
Ok, ... about 6:15 PM Eastern?
The
Hello,
Committed a bunch of build.properties today, but still missed the last one,
so we lack one 'about.html' in generated source plugins [1].
I am sorry, the only weak excuse I have is that there was not that much of
time today to check the final reports against production repository.
What is
24 matches
Mail list logo