Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] cdt-verify-test-cdt-other job failing repeatedly

Hi folks,

I have pushed[1] a fix for this to master, tracked in Bug 534839[2].

I have also re-triggered all the builds that had failed for this reason. To avoid every patchset having to be rebased I have disabled gerrit checking the standalone debugger for now. I will reenable that in a few days, so if you get failures again in a few days you will need to rebase or ping me to have a look.

There are over a dozen gerrit verify jobs to be built, so it will take a few hours to catch up on everything. I will monitor how it goes, but I may not be able to resolve anything until it is morning UK time.

[1] https://git.eclipse.org/r/#/c/122896/ 
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=534839

Thanks
Jonah

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

On 17 May 2018 at 13:57, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
The Standalone Debugger needs constant updating because it is defined as its own product.

I will take care of this most recent update and review William's change as it looks like a new way to solve this kind of problem.

Jonah

~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com

On 17 May 2018 at 10:58, William Riley <william.riley@xxxxxxxxxxx> wrote:

That would make sense, a change upstream that added a dependency not already explicitly included in the standalone debugger product. Telling Tycho to include all dependencies in the debugger product repo fixes the build error (https://git.eclipse.org/r/#/c/122845/).

 

Any thoughts on this Jonah/anyone? Not completely clear if there is a requirement for us to fully track dependencies we ship which come in from other Eclipse projects. I can go through and add the exact missing dependences if there is.

 

William

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@eclipse.org] On Behalf Of Doug Schaefer
Sent: 16 May 2018 15:06


To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] cdt-verify-test-cdt-other job failing repeatedly

 

This could be coming from the Photon M7 build. There was a huge dump of changes in this final development milestone. Reminds me of the old days 😉.

 

:D

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@eclipse.org] On Behalf Of William Riley
Sent: Wednesday, May 16, 2018 3:05 AM
To: CDT General developers list. <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] cdt-verify-test-cdt-other job failing repeatedly

 

From the last failure it looks like a missing dependency in the standalone debugger product, it cannot find "org.apache.batik.constants 1.9.1".

 

I took a very quick look and couldn't see a recent change that would account for that.

 

Regards

William

 

-------- Original Message --------

Subject: [cdt-dev] cdt-verify-test-cdt-other job failing repeatedly

From: Nathan Ridge <zeratul976@xxxxxxxxxxx>

Date: 16 May 2018, 03:22

To: CDT Mailing List <cdt-dev@xxxxxxxxxxx>

Hi all,

For the past couple of days, the cdt-verify-test-cdt-other job has been failing repeatedly for all of the patches I've tried. It's a "FAILURE", i.e. not just failing tests which usually cause it to be "UNSTABLE".

I looked at the console output, but the only thing I can see that looks like an error is this, which doesn't tell me much:

19:50:51 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-director-plugin:1.1.0:materialize-products (materialize-products) on project org.eclipse.cdt.debug.application.product: Installation of product org.eclipse.cdt.debug.application.product for environment linux/gtk/x86 failed: Call to p2 director application failed with exit code 13. Program arguments were: [-metadataRepository, file:/jobs/genie.cdt/cdt-verify-test-cdt-other/workspace/debug/org.eclipse.cdt.debug.application.product/target/repository/, -artifactRepository, file:/jobs/genie.cdt/cdt-verify-test-cdt-other/workspace/debug/org.eclipse.cdt.debug.application.product/target/repository/, -installIU, org.eclipse.cdt.debug.application.product, -destination, /jobs/genie.cdt/cdt-verify-test-cdt-other/workspace/debug/org.eclipse.cdt.debug.application.product/target/products/org.eclipse.cdt.debug.application.product/linux/gtk/x86/cdt-stand-alone-debugger, -profile, DefaultProfile, -profileProperties, org.eclipse.update.
 install.features=true, -roaming, -p2.os, linux, -p2.ws, gtk, -p2.arch, x86]. -> [Help 1]
19:50:51 [ERROR]
19:50:51 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
19:50:51 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
19:50:51 [ERROR]
19:50:51 [ERROR] For more information about the errors and possible solutions, please read the following articles:
19:50:51 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
19:50:51 [ERROR]
19:50:51 [ERROR] After correcting the problems, you can resume the build with the command
19:50:51 [ERROR]   mvn <goals> -rf :org.eclipse.cdt.debug.application.product

Does anyone know what's going on here?

Thanks,
Nate
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev

 

 

Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.




Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.




Back to the top