Ed, Axel,
During weekend, when I saw a free slot at hudson-slave1 I run our
build over there. If you look at the console https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.1-nightly/231/console),
you may check that the ecore (and uml) plugin tests are executed.
However the job gets stuck as same as other jobs which try to
execute over there. That's the reason why the hudson-slave1 server
is always busy.
Concerning your question, Axel, I think that what was changed is
trying to build on hudson-slave2. Why do our plugin test cases run
on one server, but they dont' on the other one ? ... It doesn't look
an easy question to solve...
So, I think we should do the following
- Wait until hudson-server1 works well (I'll open a bugzilla during
today), to check that the build success on hudson-slave1.
- Then, I'll try a build on hudson-server2 to check if it fails
again. If so, I'll open a bugzilla (and mail dev-cross-project) to
see if it's infrastructure problem...
P.S: Meanwhile, if you want to disable the plugin tests to have a
clean build, just let me know it.
Best Regards,
Adolfo.
El 12/02/2011 9:16, Axel Uhl escribió:
A good starting point for analysis may be to figure
out what changed between the last successful build and the first
build that broke for an unresolved junit bundle. Did anything
change in *our* config, or may something have changed in the
repository from which we *obtain* the bundles our stuff depends
on?
Best,
-- AXel
On 2/12/2011 6:47 AM, Ed Willink wrote:
Hi Axel
On 11/02/2011 23:21, Axel Uhl wrote:
The Junit4 version ranges didn't help.
No surprise. Here's again the
build error message:
A pity; it was a possible guess.
Unfortunately when the build fails, guessing is too often the
solution.
This suggests that the problem is
somehow related to the Ecore
(Plugin) launch config. There, a plugin dependency needs to be
resolved. Unfortunately, I can't tell how the build is trying
to
resolve plugin dependencies provided by a JUnit plugin test
launch
config. Adolfo?
Indeed any ideas Adolfo? We should probably drop the JUnit
plugin tests
until they work.
Regards
Ed
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev
|