On 17/12/14 11:31 , "Dominig ar Foll (Intel OTC)" <[email protected]> wrote:
>Hello; > >with the addition of new profile joined to the change of some low level >packages, we have created a dead lock within Tizen public OBS. >At the time of writing that email 1200 packages are waiting for building >and critical projects such as the IVI release M14.4 or Tizen-Yocto are >stalled. > >More details and progress can be fond here : > ttps://bugs.tizen.org/jira/browse/TINF-751 > >In order to help the system to regain a stable and working state, quite >a few submissions will have to be delayed or cancelled. > >I would also propose that general submission to Tizen which is the >default are removed and that default goes only on Common, submission for >real profiles should be done on a specific request. >Note that submission of a specific profile is already possible. > >Advises, hints and alternatives from the infra team for solving that >issue are more than welcome. We already adjusted several parameters on build nodes that would improve build time for big packages (e.g. most known offender, crosswalk build got down from 6000+ seconds to ~2500sec). + build-compare tool seems to be not properly updated during gcc 4.8->4.9 upgrade. we observing dozens of builds that might be avoided. People in my team are looking to fix that as well, hopefully today. However, there certain things that should be done in parallel by some developers and especially by release engineers of profiles. - for profiles (including and most importantly for Common), changes must be accepted/declined in timely manner. there are some submissions that are not taken care of for more than 5 days. Having Common releases not on regular basis (not daily) means that delta between content developers submits and content actually in profiles codelines is growing exponentially. - while processing queue, REs must pay attention to size of each changes, group(!) and accept changes that has smaller impact on rebuild times, that would significantly decrease “waiting” time after change is accepted in main project. It doesn’t make sense to accept some low level toolchain packages first if you have dozens of application submissions in the queue, as accepting toolchain changes would trigger worlds rebuilds for everything and will block acceptance of everything else. - one of the most important things: no broken builds should be in profiles. Failed to build package is one of the first priority candidates to be selected for build if any meta information in repository changes. so, system can spend times on trying to build something that is broken and that is not unblocking packages further in the chain. In Common at the moment there are 5 build failures (at least 2 package changes seems to be accepted without any testing). - crosswalk split in two packages seems to be not working anymore. it was supposed to have crosswalk package to build long time, and crosswalk-bin to be built in fraction amount of time. Currently it doesn’t look like that, and both variants taking almost same amount of time, so I suspect that some recent changes in crosswalk being guilty for that. > >Regards > >-- >Dominig ar Foll >Senior Software Architect >Open Source Technology Centre >Intel SSG > >_______________________________________________ >Dev mailing list >[email protected] >https://lists.tizen.org/listinfo/dev > -- Best regards, Alexander Kanevskiy. --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
