Skip to content
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

[Testing] Update ROOT and Cling to LLVM18 #209

Closed

Conversation

aandvalenzuela
Copy link

Testing ROOT llvm18 update as requested in root-project#15696 (comment)

@aandvalenzuela
Copy link
Author

please test for CMSSW_14_1_ROOT6_X

  • We moved today release cycle to 14_2_X, so the first IB for it will be available tonight

@cmsbuild
Copy link

This PR touches too many files (6364 >= 3001) and will not be processed.
Please ensure you have selected the correct target branch and consider splitting this PR into several.
The processing of this PR will resume once the number of changed files drops below the limit.

@dpiparo
Copy link

dpiparo commented Aug 27, 2024

😱

@aandvalenzuela
Copy link
Author

FYI, cms-sw/cms-bot#2323 disables the check on the number of files in non-cmssw repositories, so that we can move forward with the testing

@cmsbuild
Copy link

A new Pull Request was created by @aandvalenzuela for branch cms/master/9e38588b80.

@aandvalenzuela, @iarspider, @smuzaffar can you please review it and eventually sign? Thanks.
@ReyerBand, @argiro, @missirol, @mmusich, @rchatter, @thomreis, @wang0jin this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.
cms-bot commands are listed here

@cmsbuild
Copy link

cmsbuild commented Aug 28, 2024

cms-bot internal usage

@aandvalenzuela
Copy link
Author

please test for CMSSW_14_2_ROOT6_X

@cmsbuild
Copy link

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b2e919/41168/summary.html
COMMIT: b9b6290
CMSSW: CMSSW_14_2_ROOT6_X_2024-08-27-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/root/209/41168/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially added 14 lines to the logs
  • Reco comparison results: 1276 differences found in the comparisons
  • DQMHistoTests: Total files compared: 44
  • DQMHistoTests: Total histograms compared: 3328202
  • DQMHistoTests: Total failures: 6390
  • DQMHistoTests: Total nulls: 8
  • DQMHistoTests: Total successes: 3321784
  • DQMHistoTests: Total skipped: 20
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -0.2720000000000002 KiB( 43 files compared)
  • DQMHistoSizes: changed ( 10224.0,... ): -0.004 KiB MessageLogger/Errors
  • DQMHistoSizes: changed ( 10224.0,... ): -0.004 KiB MessageLogger/Warnings
  • DQMHistoSizes: changed ( 25.0,... ): -0.008 KiB MessageLogger/Errors
  • DQMHistoSizes: changed ( 25.0,... ): -0.008 KiB MessageLogger/Warnings
  • Checked 191 log files, 161 edm output root files, 44 DQM output files
  • TriggerResults: no differences found

@cmsbuild
Copy link

Pull request #209 was updated.

@cmsbuild
Copy link

cmsbuild commented Aug 28, 2024

cms-bot internal usage

@aandvalenzuela
Copy link
Author

please test for CMSSW_14_2_ROOT6_X

@cmsbuild
Copy link

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b2e919/41185/summary.html
COMMIT: 6456e70
CMSSW: CMSSW_14_2_ROOT6_X_2024-08-27-2300/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week0/cms-sw/root/209/41185/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • You potentially added 9 lines to the logs
  • Reco comparison results: 1268 differences found in the comparisons
  • DQMHistoTests: Total files compared: 44
  • DQMHistoTests: Total histograms compared: 3328202
  • DQMHistoTests: Total failures: 6384
  • DQMHistoTests: Total nulls: 10
  • DQMHistoTests: Total successes: 3321788
  • DQMHistoTests: Total skipped: 20
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: -0.2720000000000002 KiB( 43 files compared)
  • DQMHistoSizes: changed ( 10224.0,... ): -0.004 KiB MessageLogger/Errors
  • DQMHistoSizes: changed ( 10224.0,... ): -0.004 KiB MessageLogger/Warnings
  • DQMHistoSizes: changed ( 25.0,... ): -0.008 KiB MessageLogger/Errors
  • DQMHistoSizes: changed ( 25.0,... ): -0.008 KiB MessageLogger/Warnings
  • Checked 191 log files, 161 edm output root files, 44 DQM output files
  • TriggerResults: no differences found

@iarspider
Copy link

please test for CMSSW_14_2_ROOT6_X/el8_aarch64_gcc12

devajithvs and others added 24 commits September 10, 2024 16:07
- Include `StringExtras.h`
This is now needed due to:
llvm/llvm-project@3ff3af3
In LLVM 18 with incremental extensions enabled, the Preprocessor will
never report tok::eof, but tok::annot_repl_input_end instead.
Prevents failures such as:

```
Processing roottest/root/meta/runnamespace.C...
Error in cling::MetaProcessor: cannot read from binary input:
'runnamespace.C'
```
This is needed for macros that start with `{` after the rebase
C++20 builds were failing due to the commit:
llvm-project/commit/574ee1c02ef73b66c5957cf93888234b0471695f

with an error `imported non C++20 importable modules`
This makes them run after the <Platform> library: It provides the
__cxa_atexit function, which must not be found in the process.
LLVM now defines multiple Dylibs, and __cxa_atexit is provided in
the <Platform> library.
We started seeing an assertion failure in ~FinalizedAlloc when we
moved the generators to ProcessSymbols JITDylib:
[cling] Move generators to ProcessSymbols JITDylib

This ikely changed the destruction order that caused the assertion to
trigger.
This fixes the Cling test Driver/E.C.
This applies the upstream changes in commit
llvm/llvm-project@9992b38
to a copy of the modulemap from MacOSX14.2.sdk.
This fixes the failing python enum tests like:
- `roottest-python-cpp-cpp`
- `roottest-python-cmdLineUtils-ROOT_8197`

Also remove `R__BYTESWAP` which should not be needed anymore.

The leak was fixed with:
llvm/llvm-project#78311

This caused our tests to fail as they relied on the
previous behavior.
Upstream LLVM now unconditionally uses indirect / PC relative
personality encodings since commit
llvm/llvm-project@ca65969

This leads to references of DW.ref.__gxx_personality_v0 that cannot
be resolved with RuntimeDyld, that we are still using for the moment.
As a fix, auto-claim symbols as we are doing for PPC, see upstream commit:
llvm/llvm-project@72ea1a7
There are still failures with RuntimeDyld on AArch64 which seem to
be solved with JITLink, so make the switch now.
@cmsbuild
Copy link

Pull request #209 was updated.

@cmsbuild
Copy link

cms-bot internal usage

@smuzaffar smuzaffar closed this Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.