Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index


On 21/11/2018 17:42, Stephan Bergmann wrote:
If nobody objects, we'd update the build baselines on master (towards LO 6.3) as follows (cf README.md):

(also discussed this in yesterday's ESC, <https://lists.freedesktop.org/archives/libreoffice/2018-November/081435.html> "minutes of ESC call ...")

* Windows: from Visual Studio 2017 to Visual Studio 2017 version 15.7

The relevant Windows Jenkins nodes (tb68-bytemark, tb72, tb73, tb77, and tb78, I assume) need to be upgraded to >= Visual Studio 2017 version 15.7. Who can do that? Cloph?

(The latest available Visual Studio 2017 is version 15.9, and I have seen successful builds with it locally. When installing a new version on the Jenkins nodes, there are pros and cons for both choosing 15.7 and 15.9. 15.7 will guarantee that Gerrit checks against the baseline, while we'll need to upgrade the nodes sooner. 15.9 will postpone the need to upgrade again in the future, but Gerrit doesn't exactly check against the baseline. I'll leave that decision at the discretion of those who'll actually do the upgrade :)

Also, <https://gerrit.libreoffice.org/#/c/63713/2/> "Require at least flex 2.6.0, which no longer emits 'register'" failing on tb73 due to "checking the flex version... configure: error: failed (C:/cygwin/bin/flex 2.5.39 found, but need at least 2.6.0)" shows that at least some of the relevant Windows Jenkins nodes have outdated Cygwin utilities. Who can update these? flex 2.5.35 and gperf 3.1 would be relevant. The Jenkins admin_lode job can't do that automatically, I think. Cloph, can you do it manually?

* macOS: from Xcode 8 to Xcode 9.3

(Nothing needs to be done for this on the Jenkins side, as reportedly all relevant macOS nodes are already on some Xcode 9.3 or later.)

* Linux GCC: from GCC 4.8.1 to GCC 7

(See the discussion in its own sub-thread at <https://lists.freedesktop.org/archives/libreoffice/2018-November/081436.html> "Re: Compiler baselines" about rolling this out on Jenkins.)

* Linux Clang: from Clang to Clang 5.0.2

The relevant Linux Jenkins nodes (tb75-lilith, tb76-maggie, and tb79-pollux) have been updated (via admin_lode and <https://gerrit.libreoffice.org/plugins/gitiles/lode/+/5cde490b4110e229615a30067ac6dc52ef368ef4%5E%21> "On Linux, upgrade to Clang 5 plus libstdc++ 7").

* Clang compiler plugins: from Clang 3.8 to Clang 5.0.2

Enforced with <https://gerrit.libreoffice.org/plugins/gitiles/core/+/f23aa1a51cb1beea4ebe3a61ba0c9b3abd844fd9%5E%21> "Bump compiler plugins Clang baseline to 5.0.2".

* flex: from 2.5.35 to 2.6.0

The relevant Linux Jenkins nodes (tb75-lilith, tb76-maggie, and tb79-pollux) and most of the relevant macOS Jenkins nodes (tb57, tb58, tb66, gb69, tb80, and tb81; tb59 and tb82 are permanently offline) have been updated (via admin_lode and <https://gerrit.libreoffice.org/plugins/gitiles/lode/+/15b642cae14dccabd40c83668b3cea23ce3ff78e%5E%21> "Install flex 2.6.4 if necessary"). The relevant Windows Jenkins nodes apparently still need updating (see above).

* gperf: from 3.0.0 to 3.1

The relevant Linux Jenkins nodes (tb75-lilith, tb76-maggie, and tb79-pollux) and most of the relevant macOS Jenkins nodes (tb57, tb58, tb66, gb69, tb80, and tb81; tb59 and tb82 are permanently offline) have been updated (via admin_ldoe and <https://gerrit.libreoffice.org/plugins/gitiles/lode/+/3ce8f59fd916a5b2e1234d57023d8ae07262a5ff%5E%21> "On Linux, use latest gperf 3.1" resp. <https://gerrit.libreoffice.org/plugins/gitiles/lode/+/e4257cfec784da981dcbf22b543d52dafbf312e3%5E%21> "Install gperf 3.1 if necessary"). The relevant Windows Jenkins nodes presumably still need updating (see above).

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.