-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump CMake to 3.17 #2157
Bump CMake to 3.17 #2157
Conversation
10802dc
to
b2b930f
Compare
@ktf @MichaelLettrich : Could you check what is the problem with alidist_macOS? I have force-pushed once, and it still fails without providing an error log. |
c7e6165
to
ddf63e0
Compare
The only thing I can see is that it is failing to build CMake on macOS. I will switch on debug output for alibuild and see what is going on. |
cmake.sh
Outdated
@@ -1,14 +1,14 @@ | |||
package: CMake | |||
version: "%(tag_basename)s" | |||
tag: "v3.16.3-alice2" | |||
tag: "v3.17.0" | |||
source: https://github.com/alisw/CMake | |||
build_requires: | |||
- "GCC-Toolchain:(?!osx)" | |||
- make | |||
prefer_system: "(?!osx)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the bug is fixed in 3.17, then we can use system CMake if it is recent enough, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove the "(?!osx)"
part at prefer_system
? If 3.17
fixes the bug we should use the brew version instead of always building our own.
ok, thx, but if the CMake build fails, why is the log empty? |
Actually, I am stupid.. The PR is actually wrong. There is no 3.17 in the alisw fork, we should use the upstream. Let me fix that. But I am wondering how it worked in the linux CI? It should have failed there! |
ddf63e0
to
df5a24a
Compare
I have no Idea why the log is empty. I think it is a "design" feature of the system that only the log of the tested package (in this case O2) is published - am I right @ktf ? |
OK, but that doesn't make sense. One should see the log for the package that failed. |
Agree. I will discuss with @ktf as soon as we can. I think we need to make some improvements under the hood as empty logs keep devs in the dark... |
95abf44bd/osx_x86-64/CMake/v3.17.0-1ake:2157: + export GIT_REFERENCE=/build/mirror/cmake
2020-03-29@11:59:02:DEBUG:O2Suite:CMake:2157: + GIT_REFERENCE=/build/mirror/cmake
2020-03-29@11:59:02:DEBUG:O2Suite:CMake:2157: + [[ ! https://gitlab.kitware.com/cmake/cmake == '' ]]
2020-03-29@11:59:02:DEBUG:O2Suite:CMake:2157: + [[ h != \/ ]]
2020-03-29@11:59:02:DEBUG:O2Suite:CMake:2157: + [[ ! -d /System/Volumes/Data/build/ci_checks/alidist_checker_macos_o2_ci_0/sw/SOURCES/CMake/v3.17.0/v3.17.0 ]]2:DEBUG:O2Suite:CMake:2157: + cd /System/Volumes/Data/build/ci_checks/alidist_checker_macos_o2_ci_0/sw/SOURCES/CMake/v3.17.0/v3.17.0@11:59:02:DEBUG:O2Suite:CMake:2157: + git checkout v3.17.0
2020-03-29@11:59:02:DEBUG:O2Suite:CMake:2157: error: pathspec 'v3.17.0' did not match any file(s) known to git |
df5a24a
to
a308fb2
Compare
ok, thx, probably the log was empty because it failed fetching the tag. Just pushed a new version, should be fixed now. Tried locally in alidock and on MacOS. |
I still get the same error in the logs. Seems that alidist is not able to check out that repo for some reason |
Even with the latest commit? It works for me. Could you perhaps wipe the build area? |
First of all I stand corrected: Empty logs are a result of the error happening outside of the build process of a package, for example if git can't check out the repository as in this case. Secondly, I see that the package is checked out in the sources, i.e. |
Done, but I think it might still fail to build when the old nonexistent tag is checked out in the src dir. |
Sure the system check was just another thing that was missing. AliBuild and switching between repos is yet another story. I wonder nevertheless why it behaves differently on linux. I hope that now we at least get the same results on both platforms. |
Also the MacOS O2 CI is stuck since ~18 hours. Could you have a look? |
Yes, the macOS CI was my bad. I quit the builder to do some debuging and forgot to restart it again 😓 its back in business. |
ok, thx, will it automatically pick up the stuck PRs without force-pushing? |
no need to force-push, the build is in process. |
@Barthelemy any ideas why |
@Barthelemy @MichaelLettrich : I do not see how the MacOS failure here can be related to MacOS. I breaks in npm. I have saved the log if you need it. Force-pushing to try again. |
376870f
to
984d45c
Compare
@davidrohr The error occurs with other prs as well, see #2158 #2156 |
It might be |
@aphecetche the new macOS checkers were setup exclusively with python3. Searching the web told me that |
Unfortunately, I'm not able to reproduce it, I can successfully compile it with Nodejs from aliBuild and brew. |
This is where Even though I use
but build machines set |
We're using |
984d45c
to
724598d
Compare
@ktf @MichaelLettrich : Could you check the logs of the AliRoot/alidist CI? The log shown here is empty again. This morning, the AliRoot CI was already green, I just rebased after the python fix for the Mac CI and now it fails. |
Looks like some git glitches on ++ hostname -s
+ DATA='prcheck,checkname=build/O2/alidist/1 host="alientest06",state="looping",cihash="af88634af0a544e7ba704baf0314301a495c1a80",uptime=38281,prid="2157",prok=1 1585604795000000000'ile:[email protected]:8082/write?db=agile' --data-binary 'prcheck,checkname=build/O2/alidist/1 host="alientest06",state="looping",cihash="af88634af0a544e7ba704baf0314301a495c1a80",uptime=38281,prid="2157",prok=1 1585604795000000000' Dload Upload Total Spent Left Speed
100 173 0 0 100 173 0 1157 --:--:-- --:--:-- --:--:-- 1161
+ '[' -f config/workers-pool-size ']'
+ '[' -f config/worker-index ']'
+ '[' -f config/debug ']'
+ '[' -f config/profile ']'
+ '[' -f config/jobs ']'
+ '[' -f config/timeout ']'
+ '[' -f config/long-timeout ']'
+ '[' -f config/silent ']'
+ '[' '!' -f config/silent ']'
+ unset SILENT
+ '[' '!' -f config/debug ']'
+ unset DEBUG
+ '[' '!' -f config/profile ']'
+ unset PROFILE
+ aliBuild clean
++ find . -maxdepth 2 -name .git -exec dirname '{}' ';'
++ grep -v ali-bot
+ for d in '$(find . -maxdepth 2 -name .git -exec dirname {} \; | grep -v ali-bot)'
+ pushd ./alidist
++ git rev-parse --abbrev-ref HEAD
+ LOCAL_BRANCH=master
+ [[ master != HEAD ]]
+ git update-ref -d 'refs/remotes/origin/pr/*'
+ true
++ date -u +%s
+ [[ 8487 -gt 14400 ]]
+ timeout -s9 600 git fetch origin +master:refs/remotes/origin/master
+ git reset --hard origin/master
+ git clean -fxd
+ popd
+ for d in '$(find . -maxdepth 2 -name .git -exec dirname {} \; | grep -v ali-bot)'
+ pushd ./alibuild
++ git rev-parse --abbrev-ref HEAD
+ LOCAL_BRANCH=HEAD
+ [[ HEAD != HEAD ]]
+ popd
+ for d in '$(find . -maxdepth 2 -name .git -exec dirname {} \; | grep -v ali-bot)'
+ pushd ./O2
++ git rev-parse --abbrev-ref HEAD
+ LOCAL_BRANCH=dev
+ [[ dev != HEAD ]]
+ git update-ref -d 'refs/remotes/origin/pr/*'
error: unable to resolve reference refs/remotes/origin/pr/*: No such file or directory
+ true
++ date -u +%s
+ [[ 8488 -gt 14400 ]]
+ timeout -s9 600 git fetch origin +dev:refs/remotes/origin/dev
+ git reset --hard origin/dev
+ git clean -fxd
+ popd
+ find separate_logs/ -type f -mtime +5 -delete
+ find separate_logs/ -type d -empty -delete
+ [[ alisw/alidist != '' ]]
++ cat force-hashes
++ grep -vE '^#'
++ true
+ HASHES=
+ [[ ! -n '' ]]
++ timeout -s9 600 list-branch-pr --show-main-branch --check-name build/O2/alidist --trust-collaborators --trusted ktf,dberzano alisw/alidist@master --workers-pool-size 2 --worker-index 1 --max-wait 300
|
@ktf There seem to be some dns issues with Using cached build for CMake
Building [email protected]
rsync: getaddrinfo: repo-ci.marathon.mesos 873: Name or service not known
rsync error: error in socket IO (code 10) at clientserver.c(125) [sender=3.1.2]
ERROR: Unable to upload tarball.
+ BUILD_ERROR=1
+ [[ 1 != '' ]]
+ timeout -s9 600 report-pr-errors --default master --no-comments --logs-dest s3://alice-build-logs.s3.cern.ch --log-url https://ali-ci.cern.ch/alice-build-logs/ --pr alisw/alidist#2157@724598dadc38bffaf78f395e2f4e7bbcfd86892f -s build/O2/alidist-dataflow
Searching all logs matching: sw/BUILD/*latest*/log, sw/BUILD/*latest/log
Found:
echo 'Builing on: '`hostname` >> copy-logs/alisw/alidist/2157/724598dadc38bffaf78f395e2f4e7bbcfd86892f/build_O2_alidist-dataflow/fullLog.txt
echo 'The following files are present in the log:' >> copy-logs/alisw/alidist/2157/724598dadc38bffaf78f395e2f4e7bbcfd86892f/build_O2_alidist-dataflow/fullLog.txt
|
Ok. Thank you for checking. I will investigate what is going on. |
@ktf : Do we understand what is the new problem with the CI? Both AliRoot and O2 mac OS CIs have been green in the meantime, but not at the same time. So in principle this PR should be fine. I am sorry I am pushing, but I need it for AliceO2Group/AliceO2#3244 |
@ktf : Can we merge this? It is open since 6 days, and it is constantly blocked by randomly failing CI. |
Sorry I missed this. @MichaelLettrich what's up with the mac builds? |
This follows recent change in alidist alisw/alidist#2157
This follows recent change in alidist alisw/alidist#2157
No description provided.