Hi Laurent,
Not really.... I definitely made my jobs get stuck to slave1
server... My general feelings are that things work better in slave1,
but I didn't get any useful reason or conclusion.
When I tried to run my jobs in other servers some weeks ago in
master, the builds worked again... who knows ... I can't really help
here, sorry.
Looking at your error log, it looks like the same/similar one I had
... As said, let's see if you and Dennis obtain a better diagnosis
of the issue.
Cheers,
Adolfo.
El 19/08/2011 8:23, Laurent Goubet escribió:
Hi folks,
Resurrecting this old thread ... I am now experiencing this same
issue (which is new to me, but Adolfo had this as soon as
february).
When I run my build on master, it inevitably fails in
Required plug-in 'org.eclipse.jdt.junit4.runtime' could not be found.
However, if I restrict the build so that it runs on hudson-slave1,
this error goes away. For any one interested, compare this log
(failure, run on master) https://hudson.eclipse.org/hudson/view/Modeling/job/m2t-acceleo-master/15/console
to this one (success, no change at all (same code as the failure),
but run on hudson-slave1)
https://hudson.eclipse.org/hudson/view/Modeling/job/m2t-acceleo-master/16/console.
Adolfo, did you find any workaround other than restricting the
build server?
Regards,
Laurent
On 04/03/2011 18:29, Adolfo Sánchez-Barbudo Herrera wrote:
David,
The option comes from the following "-DX.display="${DISPLAY}" argument in
the buckminster command:
junit --DX.display="${DISPLAY} -launch
"org.eclipse.ocl.ecore.tests/launches/org.eclipse.ocl.ecore.tests\
\(Plugin).launch" --flatXML --output
"${WORKSPACE}/MDT-OCL.test.results/org.eclipse.ocl.ecore.plugin.tests.xml"
I also removed said argument to see what happened. The results
are the same regardless the used display: the build only success
on hudson-slave1.
This is a wish rather than a real need: It could be desirable
having more servers (slots) on which run my builds :). On the
other hand It would be good to know if I'm the only one who have
problems with this. Is there any way to know if there are more
jobs tightened to hudson-server1 ?
Regards,
Adolfo.
El 04/03/2011 17:12, David M Williams escribió:
oops, I don't use
:11 after all (I do, but on another, local test build
machine of mine, so I panicked ... I use ":9" on
build.eclipse.org) ... but, guess the question is still
valid. Do we need to coordinate these? I think technically
we do ... but, hate to add to "processes" unless a concrete
need ... so, maybe if it ever does cause a problems? (And,
forget that BuildServerPorts page ... now that I've re-read
it, it is so old I do not even understand it :)
From: David M
Williams/Raleigh/IBM@IBMUS
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 03/04/2011 12:03 PM
Subject:
Re:
[cross-project-issues-dev] Build fails/success depending on
the server in which it's run.
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
>INFO: junit
'-DX.display=:11' ...
Display :11!?
I use Display :11 too. I can not imagine that this issue
causes this particular problem with differences between
build machines that you are primarily asking about ... but,
do we need to start "coordinating" these displays used? I
suppose maybe they could be "shared" between processes, but
suspect that would usually lead to unexpected results?
Perhaps we should start a wiki page? With who's using which
one, so conflicts can be avoided? Perhaps expand this one: http://wiki.eclipse.org/BuildServerPorts
Advice welcome,
From: Adolfo
Sánchez-Barbudo Herrera <adolfosbh@xxxxxxxxxxxxxxxx>
To: Cross
project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 03/04/2011
11:48 AM
Subject: Re:
[cross-project-issues-dev] Build fails/success depending on
the server in which it's run.
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Denis,
The error was included in the original mail/post. I'll paste
you again:
INFO: junit '-DX.display=:11' '--launch'
'org.eclipse.ocl.ecore.tests/launches/org.eclipse.ocl.ecore.tests
(Plugin).launch' '--flatXML' '--output'
'/opt/users/hudsonbuild/workspace/buckminster-mdt-ocl-core-3.1-nightly/MDT-OCL.test.results/org.eclipse.ocl.ecore.plugin.tests.xml'
Required plug-in 'org.eclipse.jdt.junit4.runtime' could not
be found.
Terminating xvnc.
Archiving artifacts
The error could arise for any kind of problem in the
configuration along the complex build process. I've not
really investigated or tried to fix the error when running
on master/fastlane, since the build has been properly
working on hudson-slave1 since time ago. IMO, It looks like
that some plugin is required in the target platform managed
by buckminster when running our JUnits. What is perplexing
is that the same build/configuration works in one server,
but it doesn't work in other servers.
I don't really want to make you spend time on this if you
don't have any clue, I'm happy while having my build working
on hudson-slave1. It would be great running the build in
other servers, though. So, if anybody else have a clue or
has experienced and fixed this strange issue, please let us
know it.
Best Regards,
Adolfo.
El 04/03/2011 16:21, Denis Roy escribió:
You would have to help me understand what exactly is causing
the failure, because the logfiles seem to be an endless spew
of characters that make no sense to me :)
In principle, all of the Linux Hudson machines are
configured identically, except for their IP address and
name.
Denis
On 03/04/2011 09:46 AM, Adolfo Sánchez-Barbudo Herrera
wrote:
Denis,
Now that the servers activity is calmed down. I've decided
to experiment with this issue again. The result of our build
[1] has been the same (excepting that we don't have
hudson-slave2 server :) as you have recently announced ):
- hudson-slave1: build succeed
- master: build failed
- fastlane: build failed
In principle, I don't have any problem to be tight to a
specific server, specially now that we have more slots for
hudson-server1 :D, however, I'm curious to know why this may
be happening. Is anybody else experiencing this issue ?
[1] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.1-nightly/
Cheers,
Adolfo.
El 15/02/2011 14:16, Denis Roy escribió:
I'm not sure if this is related or not, but the Master's
disk had filled up yesterday with endless Hudson/Java stack
trace spew. I've cleared the log and restarted everything
(yesterday) and all seems well.
Denis
On 02/15/2011 06:11 AM, Adolfo Sánchez-Barbudo Herrera
wrote:
Hello Folks,
With the storage problem we have had with the servers, I've
discovered a weird issue building against different servers.
Our buckminster based build [1] used to be run using
hudson-server1. However, I've discovered that if I run my
build on a different server (hudson-slave2, fastlane and
master) the build fails when trying to execute some Plugin
Junit tests with the following error:
INFO: junit '-DX.display=:12' '--launch'
'org.eclipse.ocl.ecore.tests/launches/org.eclipse.ocl.ecore.tests
(Plugin).launch' '--flatXML' '--output'
'/opt/users/hudsonbuild/.hudson/jobs/buckminster-mdt-ocl-core-3.1-nightly/workspace//test.results/org.eclipse.ocl.ecore.plugin.tests.xml'
Required plug-in 'org.eclipse.jdt.junit4.runtime' could not
be found.
There are other tests which are executed. The difference is
that "org.eclipse.ocl.ecore.tests (Plugin).launch" is a
plugin junit tests launch configuration.
Before figuring out why this plugin is missed and who needs
it, I'd like to ask you a couple of questions:
- Why could a build success in a server and fail in another
one. Is there any kind of information available ?
- Does anybody face on this/similar issue ?
[1] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.1-nightly/
_______________________________________________
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
|