Closed aandvalenzuela closed 1 year ago
Sorry, my bad: forgot to sync environment file. I have updated CMSSW_13_0_X branch, please let me know if it builds now.
Thank you @iarspider!
@smuzaffar, we also need to put a fresh tag of cmssw
in the recipe, but this is for fetching cmssw
.
thanks I will try that
for me CMSSW_13_0_X still fails. please update https://codimd.web.cern.ch/s/QL8ZVMHHQ# with a working set of instructions
[a]
lib/spack/spack/installer.py:1491 ==> [2022-12-20-17:26:00.200465] No build task for hdf5-1.10.6-mswrprp3owoubyaas2uawv6sczih743o to skip since pkg-config-0.29.2-ikpf4vg2i52fy5jwyikreiwvtn75zcpi failed
lib/spack/spack/installer.py:1799 ==> [2022-12-20-17:26:00.200708] Error: Failed to install pkg-config due to NoSuchBucket: An error occurred (NoSuchBucket) when calling the GetObject operation: The spe
cified bucket does not exist
lib/spack/spack/environment/environment.py:1501 ==> [2022-12-20-17:26:05.867744] Skip view update, this environment does not maintain a view
lib/spack/spack/main.py:1010 ==> [2022-12-20-17:26:05.868002] InstallError: Terminating after first install failure: An error occurred (NoSuchBucket) when calling the GetObject operation: The specified bucket does not exist
lib/spack/spack/error.py:54 ==> [2022-12-20-17:26:05.868273] Error: Terminating after first install failure: An error occurred (NoSuchBucket) when calling the GetObject operation: The specified bucket does not exist
Traceback (most recent call last):
File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/installer.py", line 1757, in install
note that I used CMSSW_13_0_X branch of iarspider/cms-spack-repo
for me CMSSW_13_0_X still fails. please update https://codimd.web.cern.ch/s/QL8ZVMHHQ# with a working set of instructions
Hi Shahzad,
yesterday there were some problems with CERN IT infrastructure, could also affect S3. The error you see (NoSuchBucket
) usually occurs when S3_ENDPOINT_URL
is not set. It is set here, so it should be set when using singBuild.sh
(which is a wrapper to run build.sh
inside singularity container)
Hi all,
Just to confirm, I have built all the packages except cmssw
(that is building now) with branch CMSSW_13_0_X
. In any case, do we expect cmssw to fail @iarspider?
Hi all,
Just to confirm, I have built all the packages except
cmssw
(that is building now) with branchCMSSW_13_0_X
. In any case, do we expect cmssw to fail @iarspider?
If it starts building (i.e. Spack can fetch it), it should build fine.
For me, it fails in building cmssw
with:
Traceback (most recent call last):
File "/build/avalenzu/workspace/spack/stage/spack-stage-cmssw-CMSSW_13_0_X_2022-12-20-1100-2eapzj3txrtbs2inrrdlv4adv3a2bnx2/CMSSW_13_0_X_2022-12-20-1100/src/CondFormats/Serialization/python/condformats_serialization_generate.py", line 31, in <module>
import clang.cindex
ModuleNotFoundError: No module named 'clang'
gmake: *** [tmp/el8_amd64_gcc11/src/CondFormats/HIObjects/src/CondFormatsHIObjects/a/Serialization.cc] Error 1
I am using:
version("CMSSW_13_0_X_2022-12-20-1100", tag="CMSSW_13_0_X_2022-12-20-1100")
Any hint on how clang should be imported here?
@iarspider , how can I build without using binary caches?
@iarspider , how can I build without using binary caches?
@smuzaffar spack install --no-cache
For me, it fails in building
cmssw
with:Traceback (most recent call last): File "/build/avalenzu/workspace/spack/stage/spack-stage-cmssw-CMSSW_13_0_X_2022-12-20-1100-2eapzj3txrtbs2inrrdlv4adv3a2bnx2/CMSSW_13_0_X_2022-12-20-1100/src/CondFormats/Serialization/python/condformats_serialization_generate.py", line 31, in <module> import clang.cindex ModuleNotFoundError: No module named 'clang' gmake: *** [tmp/el8_amd64_gcc11/src/CondFormats/HIObjects/src/CondFormatsHIObjects/a/Serialization.cc] Error 1
I am using:
version("CMSSW_13_0_X_2022-12-20-1100", tag="CMSSW_13_0_X_2022-12-20-1100")
Any hint on how clang should be imported here?
@aandvalenzuela Could you please test with this commit?
This change will rebuild llvm and it's dependents, so will take some time to get to CMSSW. There is probably a faster way to test it, maybe by creating a dummy cmssw-like SCRAM-based package that can just import clang
- @smuzaffar can probably help with that.
@smuzaffar spack install --no-cache
will disable binary cache, but will still try to download sources from S3. If you don't want to use sources from S3, you need to do spack mirror --scope=site rm cms-s3
. There shouldn't be any buildcache for CMSSW_13_0_X at the moment - if @aandvalenzuela didn't upload something.
ok thanks @iarspider , I am tetsing --no-cache
now.
llvm python dir should be in PYHONPATH so that import clang
works. looks like https://github.com/iarspider/cms-spack-repo/commit/b15508ade1ddb3823962e3cd6deb6e9523032ba0 should do it
I confirm I have not uploaded anything for CMSSW_13_0_X
by the way, llvm in cmsdist adds %{i}/lib64/python%{cms_python3_major_minor_version}/site-packages
( https://github.com/cms-sw/cmsdist/blob/IB/CMSSW_13_0_X/master/llvm.spec#L3 ) , @iarspider are you sure the change https://github.com/iarspider/cms-spack-repo/commit/b15508ade1ddb3823962e3cd6deb6e9523032ba0 is correct?
@smuzaffar I think just PYTHONPATH
is actually not needed now - only PYTHON3PATH
(since scram
resets PYTHONPATH
). But now that you ask - it may need one more fix (equivalent of this - creating .egg file), but I'm not 100% sure this is necessary (as eggs are outdated and aren't used anymore). I am running a local build now without creating egg
, let's see how it goes. Is there a simple way to test import clang
without building too many packages (i.e. a full set of CMSSW dependencies) .
@iarspider https://github.com/iarspider/cms-spack-repo/commit/b15508ade1ddb3823962e3cd6deb6e9523032ba0 fails with the same ModuleNotFoundError
error.
@aandvalenzuela can you try manually creating PKG-INFO
as done here, and then retry?
@iarspider Should it be a post-install method as in https://github.com/iarspider/cms-spack-repo/blob/CMSSW_12_6_X/repos/cms/packages/llvm/package.py#L205-L217?
@iarspider Should it be a post-install method as in https://github.com/iarspider/cms-spack-repo/blob/CMSSW_12_6_X/repos/cms/packages/llvm/package.py#L205-L217?
Just create that file by hand. It it works - yes, it should go into post-install method. Also, check that llvm python bindings are installed under lib64/python...
, not under lib
- I think there were problems with that.
@iarspider , CMSSW_13_0_X env failed again with error
lib/spack/spack/installer.py:1930 ==> [2022-12-22-05:45:40.420398] rust: Building rust-1.57.0-ozbws4kin7hjtcyw5ssnyjk2a25clvdw [Package]
lib/spack/spack/installer.py:2042 ==> [2022-12-22-05:45:40.436947] rust: Executing phase: 'configure'
lib/spack/spack/installer.py:2042 ==> [2022-12-22-05:46:04.445861] rust: Executing phase: 'build'
lib/spack/spack/installer.py:2042 ==> [2022-12-22-06:02:53.619948] rust: Executing phase: 'install'
lib/spack/spack/error.py:54 ==> [2022-12-22-06:09:26.668421] Error: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 546551: ordinal not in range(128)
/data/cmsbld/pgo/spk/spack/lib/spack/spack/build_environment.py:1086, in _setup_pkg_and_run:
1083 tb_string = traceback.format_exc()
1084
1085 # build up some context from the offending package so we can
>> 1086 # show that, too.
1087 package_context = get_package_context(tb)
1088
1089 logfile = None
See build log for details:
/data/cmsbld/pgo/spk/spack/stage/spack-stage-rust-1.57.0-ozbws4kin7hjtcyw5ssnyjk2a25clvdw/spack-build-out.txt
Traceback (most recent call last):
File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/build_environment.py", line 1070, in _setup_pkg_and_run
return_value = function(pkg, kwargs)
File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/installer.py", line 2088, in build_process
return installer.run()
File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/installer.py", line 1950, in run
self._real_install()
File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/installer.py", line 2064, in _real_install
combine_phase_logs(pkg.phase_log_files, pkg.log_path)
File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/installer.py", line 469, in combine_phase_logs
log_file.write(phase_log.read())
File "/usr/lib64/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 546551: ordinal not in range(128)
and rust build logs contains
lib/spack/spack/installer.py:2042 ==> [2022-12-22-05:45:40.436947] rust: Executing phase: 'configure'
lib/spack/spack/util/executable.py:198 ==> [2022-12-22-05:45:40.460840] './spack_bootstrap_stage/rust-1.57.0-x86_64-unknown-linux-gnu/install.sh' '--prefix=/data/cmsbld/pgo/spk/spack/stage/spack-stage-rust-1.57.0-ozbws4kin7hjtcyw5ssnyjk2a25clvdw/spack-src/spack_bootstrap'
install: creating uninstall script at /data/cmsbld/pgo/spk/spack/stage/spack-stage-rust-1.57.0-ozbws4kin7hjtcyw5ssnyjk2a25clvdw/spack-src/spack_bootstrap/lib/rustlib/uninstall.sh
install: installing component 'rustc'
install: installing component 'rust-std-x86_64-unknown-linux-gnu'
install: installing component 'rust-docs'
install: installing component 'rust-demangler-preview'
install: installing component 'cargo'
install: installing component 'rustfmt-preview'
install: installing component 'rls-preview'
install: installing component 'llvm-tools-preview'
install: installing component 'clippy-preview'
install: installing component 'rust-analysis-x86_64-unknown-linux-gnu'
install: WARNING: failed to run ldconfig. this may happen when not installing as root. run with --verbose to see the error
rust installed.
@iarspider Should it be a post-install method as in https://github.com/iarspider/cms-spack-repo/blob/CMSSW_12_6_X/repos/cms/packages/llvm/package.py#L205-L217?
Just create that file by hand. It it works - yes, it should go into post-install method. Also, check that llvm python bindings are installed under
lib64/python...
, not underlib
- I think there were problems with that.
In this case it fails with the same error
Looks like a quick fix didn't work. I will look into it later today, probably need to apply more changes to LLVM recipe.
@iarspider , CMSSW_13_0_X env failed again with error
lib/spack/spack/installer.py:1930 ==> [2022-12-22-05:45:40.420398] rust: Building rust-1.57.0-ozbws4kin7hjtcyw5ssnyjk2a25clvdw [Package] lib/spack/spack/installer.py:2042 ==> [2022-12-22-05:45:40.436947] rust: Executing phase: 'configure' lib/spack/spack/installer.py:2042 ==> [2022-12-22-05:46:04.445861] rust: Executing phase: 'build' lib/spack/spack/installer.py:2042 ==> [2022-12-22-06:02:53.619948] rust: Executing phase: 'install' lib/spack/spack/error.py:54 ==> [2022-12-22-06:09:26.668421] Error: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 546551: ordinal not in range(128) /data/cmsbld/pgo/spk/spack/lib/spack/spack/build_environment.py:1086, in _setup_pkg_and_run: 1083 tb_string = traceback.format_exc() 1084 1085 # build up some context from the offending package so we can >> 1086 # show that, too. 1087 package_context = get_package_context(tb) 1088 1089 logfile = None See build log for details: /data/cmsbld/pgo/spk/spack/stage/spack-stage-rust-1.57.0-ozbws4kin7hjtcyw5ssnyjk2a25clvdw/spack-build-out.txt Traceback (most recent call last): File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/build_environment.py", line 1070, in _setup_pkg_and_run return_value = function(pkg, kwargs) File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/installer.py", line 2088, in build_process return installer.run() File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/installer.py", line 1950, in run self._real_install() File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/installer.py", line 2064, in _real_install combine_phase_logs(pkg.phase_log_files, pkg.log_path) File "/data/cmsbld/pgo/spk/spack/lib/spack/spack/installer.py", line 469, in combine_phase_logs log_file.write(phase_log.read()) File "/usr/lib64/python3.6/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 546551: ordinal not in range(128)
Haven't seen this one a long time. Will investigate, thanks!
Hello @iarspider!
Looks like a quick fix didn't work. I will look into it later today, probably need to apply more changes to LLVM recipe.
Any update on this fix?
@aandvalenzuela working on it
Just for the records, cmssw
built yesterday with the latest commit acaac7b717123c0546bd609eda79b4378010a8cb. I am starting a fresh new build from scratch so that we can confirm and get the proper build times.
@smuzaffar regarding rust
failure: I can't reproduce it. While I have seen these in the past, I think they are mostly
"solved" by setting correct locale (C
, instead of UTF8
), something that SCRAM (I think) also does.
yes @iarspider , @aandvalenzuela and myself figured it out last week :-) unsetting [a] fixed the rust install issue. But still I can not build cmssw with spack compiler wrappers
unset LC_ALL
unset LC_CTYPE
I will now close this issue, since llvm
now builds fine. We can open another for building CMSSW with compiler wrappers.
Hello,
For me and @smuzaffar,
CMSSW_13_0_X
branch fails in building forel8_amd64_gcc11
. I open this issue for the records so that we can track the changes required for building.Build instructions:
Clone
cms-spack-repo
andcms-bot
repositories in workspace:Set the required env variables:
Run
bash -ex $WORKSPACE/cms-spack-repo/bootstrap.sh
script.Check compiler definition at
$WORKSPACE/spack/etc/spack/linux/compilers.yaml
.Start the build by running
$WORKSPACE/cms-spack-repo/scripts/singBuild.sh
script.Environment modifications: We have performed the following updates to the environment since it was failing in building:
xpmem
. We updated to version2.6.6-20220308
since it is the version in the recipe.clhep
since the variant was not correct. We changed the version in the environment file toclhep@2.4.5.1+cms
.xrootd
since the version in the environment file is not defined in the recipe. We added the checksum in the recipe:Build error in llvm: This new failure is in
llvm
. Error message:Spack build log at
cmsdev22
, path/build/avalenzu/workspace/llvm-error
.@iarspider could you confirm that the build instructions are correct? Are we missing anything so that it builds for you but not for us?
cleanup-cms-repo
is failing with the samexpmem
andclhep
errors for the time being, but it has not buildxrootd
orllvm
yet.Sorry for the inconvenience, Andrea.