| Re: [mdt-ocl.dev] Fwd: Build failed in Hudson: buckminster-mdt-oc l-core-3.1-nightly #228 |
|
Ed, Axel Yesterday I was having problems with hudson web UI (not very responsive). Today it looks like it works better. After disabling every non-standalone test, the build successfully completed (running on hudson-server2). Besides, the hudson-server1 doesn't look busy. I'll try to re enable the all the tests, and check if it finishes. If all works as expected, I run the build on the different servers to compare the results... Best Regards, Adolfo. El 14/02/2011 11:45, Willink, Ed escribió: Hi Adolfo We need to disable enough to at least ensure that built artefacts are copied. The most recent Update zip from the build I killed after 11 hours is corrupt, so there is no downlaodable update site. Regards Ed-----Original Message----- From: mdt-ocl.dev-bounces@xxxxxxxxxxx [mailto:mdt-ocl.dev-bounces@xxxxxxxxxxx] On Behalf Of Adolfo Sánchez-Barbudo Herrera Sent: 14 February 2011 11:07 To: mdt-ocl.dev@xxxxxxxxxxx Subject: Re: [mdt-ocl.dev] Fwd: Build failed in Hudson: buckminster-mdt-ocl-core-3.1-nightly #228 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 outwhat changedbetween the last successful build and the first build thatbroke foran 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 thebuild error message:A pity; it was a possible guess. Unfortunately when the build fails, guessing is too oftenthe 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 JUnitplugin testsuntil 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-- Open Canarias, S.L. *Adolfo Sánchez-Barbudo Herrera* adolfosbh(at)opencanarias(dot)com <mailto:adolfosbh%28at%29opencanarias%28dot%29com> C/Elías Ramos González, 4, ofc. 304 38001 SANTA CRUZ DE TENERIFE Tel.: +34 922 240231Please consider the environment before printing a hard copy of this e-mail. The information contained in this e-mail is confidential. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. If you have received this e-mail in error, please inform us immediately on +44 (0)118 986 8601 and delete it and all copies from your system. Thales Research and Technology (UK) Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 774298 Thales UK Limited. A company registered in England and Wales. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX. Registered Number: 868273 _______________________________________________ mdt-ocl.dev mailing list mdt-ocl.dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev --
|
