search

eclipse-gemoc / gemoc-studio

gemoc-studio
Eclipse Public License 1.0
25 stars 22 forks source link

Builds are failing because of some unresolved ajdt dependency #304

Closed ebousse closed 1 year ago

ebousse commented 1 year ago

Bug description

Currently building a studio from the master branch leads to:

[ERROR] Failed to resolve target definition file:/home/jenkins/agent/workspace/gemoc-studio-integration_master/gemoc-studio/gemoc_studio/releng/org.eclipse.gemoc.gemoc_studio.targetplatform/gemoc_studio.target: Could not find "org.eclipse.ajdt.feature.group/2.2.4.202304111527" in the repositories of the current location -> [Help 1]

See for instance this build attempt.

How to reproduce

Steps to reproduce the behavior:

  1. Start a pipeline for the master branch on the CI server

Additional context

I tried working on the gemoc_studio.tpd file to solve the problem, but when trying to generate the gemoc_studio.target file it fails because of the timesquare repository − which is what is pointed out in https://github.com/eclipse/gemoc-studio/issues/295.

dvojtise commented 1 year ago

note: that the gitlab.inria is currently (from 13:00 to 14:00 today) in maintenance to timesquare artefact aren't available too

dvojtise commented 1 year ago

I also have this ongoing branch https://ci.eclipse.org/gemoc/job/gemoc-studio-integration/job/bump-melange/ that contains some element going to solve related issues but for now some tests (apparently Melange based ) still seem not satisfying.

ebousse commented 1 year ago

Great, looks nice, do you know when you plan to merge this branch?

Are the failing tests really that bad?

dvojtise commented 1 year ago

Actually, I'm strongly considering merging it ASAP

I finally prefer to see those flacky tests rather than waiting too much.

I hope, it should be easier to fix them from the latest build rather than from a dev environment.

I also strongly consider do another Eclipse bump because in the latest build, eclipse is very slow to start (long wait even before seeing relevant log on the console. on my preliminary test, a debug break seems to point bundle dependency resolution process but I wasn't able to say which bundle is "faulty")

ebousse commented 1 year ago

Sounds good, looking forward to having master in good shape!

I also noticed the slowdown, it's quite painful… if eclipse 2023-09 solves this, then it's definitely a good idea :+1:

dvojtise commented 1 year ago

5 tests fixed without changing anything that sounds related to the failing test (one remaining through) I merge ...