-
Notifications
You must be signed in to change notification settings - Fork 192
Revert "Boost - update to 1.75.0" #6698
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
Conversation
A new Pull Request was created by @smuzaffar (Malik Shahzad Muzaffar) for branch IB/CMSSW_11_3_X/master. @cmsbuild, @smuzaffar, @mrodozov can you please review it and eventually sign? Thanks. |
This must be FileInPath
https://github.com/cms-sw/cmssw/blob/master/FWCore/ParameterSet/src/FileInPath.cc#L96
Perhaps? Looking at it
… On Mar 4, 2021, at 8:04 AM, Malik Shahzad Muzaffar ***@***.***> wrote:
Reverts #6655
need more testing on aarch64 where it is failing all relvals with errors like
----- Begin Fatal Exception 04-Mar-2021 02:04:40 CET-----------------------
An exception of category 'ConfigFileReadError' occurred while
[0] Processing the python configuration file named MinBias_8TeV_pythia8_TuneCUETP8M1_cff_GEN_SIM.py
Exception Message:
unknown python problem occurred.
RuntimeError: boost::filesystem::status: Function not implemented: "/build/cmsbld/jenkins_c/workspace/ib-run-relvals/CMSSW_11_3_X_2021-03-03-2300/poison/SimTracker/SiStripDigitizer/data/APVShapePeak_default.txt"
At:
/cvmfs/cms-ib.cern.ch/nweek-02670/slc7_aarch64_gcc9/cms/cmssw-patch/CMSSW_11_3_X_2021-03-03-2300/python/FWCore/ParameterSet/Types.py(835): insertInto
/cvmfs/cms-ib.cern.ch/nweek-02670/slc7_aarch64_gcc9/cms/cmssw-patch/CMSSW_11_3_X_2021-03-03-2300/python/FWCore/ParameterSet/Mixins.py(377): insertContentsInto
/cvmfs/cms-ib.cern.ch/nweek-02670/slc7_aarch64_gcc9/cms/cmssw-patch/CMSSW_11_3_X_2021-03-03-2300/python/FWCore/ParameterSet/Types.py(920): insertContentsInto
/cvmfs/cms-ib.cern.ch/nweek-02670/slc7_aarch64_gcc9/cms/cmssw-patch/CMSSW_11_3_X_2021-03-03-2300/python/FWCore/ParameterSet/Types.py(913): insertInto
/cvmfs/cms-ib.cern.ch/nweek-02670/slc7_aarch64_gcc9/cms/cmssw-patch/CMSSW_11_3_X_2021-03-03-2300/python/FWCore/ParameterSet/Mixins.py(377): insertContentsInto
/cvmfs/cms-ib.cern.ch/nweek-02670/slc7_aarch64_gcc9/cms/cmssw-patch/CMSSW_11_3_X_2021-03-03-2300/python/FWCore/ParameterSet/Types.py(920): insertContentsInto
/cvmfs/cms-ib.cern.ch/nweek-02670/slc7_aarch64_gcc9/cms/cmssw-patch/CMSSW_11_3_X_2021-03-03-2300/python/FWCore/ParameterSet/Types.py(913): insertInto
/cvmfs/cms-ib.cern.ch/nweek-02670/slc7_aarch64_gcc9/cms/cmssw-patch/CMSSW_11_3_X_2021-03-03-2300/python/FWCore/ParameterSet/Config.py(1092): _insertInto
/cvmfs/cms-ib.cern.ch/nweek-02670/slc7_aarch64_gcc9/cms/cmssw-patch/CMSSW_11_3_X_2021-03-03-2300/python/FWCore/ParameterSet/Config.py(1306): fillProcessDesc
<string>(2): <module>
----- End Fatal Exception -------------------------------------------------
You can view, comment on, or merge this pull request online at:
#6698
Commit Summary
• Revert "Boost - update to 1.75.0"
File Changes
• M boost.spec (4)
Patch Links:
• https://github.com/cms-sw/cmsdist/pull/6698.patch
• https://github.com/cms-sw/cmsdist/pull/6698.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Yes it is FileInPath but at https://github.com/cms-sw/cmssw/blob/master/FWCore/ParameterSet/src/FileInPath.cc#L89 . Looks like now |
Yes - do we have the boost build logs? Eg, was the platform found correctly?
… On Mar 4, 2021, at 9:59 AM, Malik Shahzad Muzaffar ***@***.***> wrote:
Yes it is FileInPath but at https://github.com/cms-sw/cmssw/blob/master/FWCore/ParameterSet/src/FileInPath.cc#L89 . Looks like now bf::exists(p) throws exception if file does not exist but this is only happening for aarch64 . for amd64 and ppc64le, it is not throwing exception
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
If you want the commit history
https://github.com/boostorg/filesystem/blob/develop/src/operations.cpp
… On Mar 4, 2021, at 10:01 AM, Malik Shahzad Muzaffar ***@***.***> wrote:
boost code in question is
https://github.com/cms-externals/boost/blob/cms/v1.75.0/libs/filesystem/src/operations.cpp#L2571
https://github.com/cms-externals/boost/blob/cms/v1.72.0/libs/filesystem/src/operations.cpp#L1693
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
- has statx : no
- has statx syscall : yes
Are we hitting this?
boostorg/filesystem#172
… On Mar 4, 2021, at 10:06 AM, Malik Shahzad Muzaffar ***@***.***> wrote:
boost build log for aarch64 is https://cmssdt.cern.ch/SDT/jenkins-artifacts/build-any-ib/CMSSW_11_3_X_2021-03-02-1100/slc7_aarch64_gcc9/106005/external/boost/1.75.0-692eebc1b36f0139611ad4f3eddf0ca8/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I am not 100% sure. A simple test[a] on aarch64 with boost 1.75 also fails even if I set -DBOOST_FILESYSTEM_HAS_STATX_SYSCALL [a]
|
let me try to build on the 2nd aarch64 node , may be boost was built on the other node |
yup looks like issue is with boost built on one system and running it on other. |
I think we can replace boost::filesystem in this package with std::filesystem. I may have a PR soon to try (of course std::filesystem may not have the same issue)
… On Mar 4, 2021, at 10:51 AM, Malik Shahzad Muzaffar ***@***.***> wrote:
yum looks like issue is with boost built on one system and running it on other.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
thanks @davidlange6 , #6699 is not testing boost 1.75 and cms-sw/cmssw#33066 |
Reverts #6655
need more testing on aarch64 where it is failing all relvals with errors like