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
[10.3.X] updated utm to tag 0.7.1 #4338
Conversation
as requested here #4334
please test |
The tests are being triggered in jenkins. |
A new Pull Request was created by @smuzaffar (Malik Shahzad Muzaffar) for branch IB/CMSSW_10_3_X/gcc700. @cmsbuild, @smuzaffar, @gudrutis, @mrodozov can you please review it and eventually sign? Thanks. |
-1 Tested at: 69415ac
I found an error when building: + export BOOST_BASE=/build/cmsbld/jenkins/workspace/ib-any-integration/testBuildDir/slc6_amd64_gcc700/external/boost/1.63.0-gnimlf + BOOST_BASE=/build/cmsbld/jenkins/workspace/ib-any-integration/testBuildDir/slc6_amd64_gcc700/external/boost/1.63.0-gnimlf + make -j 8 -f Makefile.standalone all make: Makefile.standalone: No such file or directory make: *** No rule to make target 'Makefile.standalone'. Stop. error: Bad exit status from /build/cmsbld/jenkins/workspace/ib-any-integration/testBuildDir/tmp/rpm-tmp.LoyETX (%build) RPM build errors: Bad exit status from /build/cmsbld/jenkins/workspace/ib-any-integration/testBuildDir/tmp/rpm-tmp.LoyETX (%build) You can see the results of the tests here: |
please test |
The tests are being triggered in jenkins. |
Pull request #4338 was updated. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
thanks @smuzaffar Asking because of two HeavyIon PR I want to make. The second of the two PRs depends on the first and on this external UTM at the same time. So having the UTM in the IB would help. Thanks. |
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_10_3_X/gcc700 IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
as requested here #4334