[Starlingx-discuss] [Build] Build report ww39 sept 23rd - sept29 2018

[Xie, Cindy]

Thanks Cesar and team root-causing this issue.

Looking into the bug 1794415<https://bugs.launchpad.net/starlingx/+bug/1794415>, we have two solutions (or workaround?) for the issue, are you continue to drive which one to adopt in the build system? Thanks.

Thx. - cindy

From: Lara, Cesar [mailto:cesar.lara at intel.com]
Sent: Tuesday, October 2, 2018 7:02 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] [Build] Build report ww39 sept 23rd - sept29 2018

This is the build report for StarlingX project  for ww39

As of  sept 21st we started to report "Build failed in stage 'build-pkgs --std'." issues in our Intel internal CI/CD infrastructure. There were multiple workarounds to issues discovered besides the initial failure like:

-       New packages being introduced as part of the CentOS 7.5 branch.

-       Issues with our local CI/CD environment.

-       Fuzzy patches.

-       "too many loops" errors.


WindRiver started to report the same errors on their build system during this week and we proceeded as a team to root cause the issues.

After several iterations and multiple fixes, the issue was root caused and solved

"The root cause of the issue has been found. It turns out that the mock environment is recycled between build packages to save time. After the CentOS 7.5 upgrade the autoconf-archive package is built and installed in the mock environment. This package contains a set of autoconf macros which conflict with the build scripts for ceph. Therefore, ceph fails with the 'too many loops' error and all the dependant packages fails as well.." [1]

After 26 failed attempted builds we got our first successful  build on September 29th

So the balance for the week:

Failed builds - 26
Successful builds - 4

[1] https://bugs.launchpad.net/bugs/1794415


Regards

Cesar Lara
Software Engineering Manager
OpenSource Technology Center

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20181002/c8a10ce0/attachment.html>