Repository navigation
[Common,PWGJE] Adding embedding for jets - #18088
Conversation
|
O2 linter results: ❌ 0 errors, |
|
Need this PR AliceO2Group/AliceO2#15836 to be committed to O2 first |
da8007d to
4bda01b
Compare
|
Error while checking build/O2Physics/o2 for 4bda01b at 2026-10-06 16:07: Full log here. |
4bda01b to
094027e
Compare
|
Error while checking build/O2Physics/code-check for 4bda01b at 2026-10-06 16:25: Full log here. |
|
Error while checking build/O2Physics/staging for 4bda01b at 2026-10-06 16:51: Full log here. |
|
Error while checking build/O2Physics/code-check for 094027e at 2026-10-07 12:29: Full log here. |
|
Error while checking build/O2Physics/staging for 094027e at 2026-10-06 18:47: Full log here. |
|
Error while checking build/O2Physics/o2 for 094027e at 2026-10-06 18:47: Full log here. |
094027e to
db161c6
Compare
db161c6 to
657a059
Compare
|
Error while checking build/O2Physics/code-check for db161c6 at 2026-10-07 13:18: Full log here. |
|
Error while checking build/O2Physics/code-check for 657a059 at 2026-10-07 16:50: Full log here. |
|
@nzardosh Please fix the errors before merging to avoid merging regressions. |
|
will fix in a separate pr :) |
|
Commenting on one of the specific errors, I might have more comments on the others. @vkucera I think the include checker should probably remain as as a warning, not as an error. It's difficult to enforce, and sometimes it is not producing particularly ergonomic results. For example: Common/DataModel/Multiplicity.h:220:16: error: no header providing "o2::aod::is_origin_hash" is directly included [misc-include-cleaner,-warnings-as-errors]should probably be fixed at the level of the framework, not at the level of the user code. Moreover, clearly people see it more as a nuisance and the cleanup is not worth the discussion. We need to find a better strategy. How about simply having automatic PRs, like we do for the clang-format? Then people decide to merge them or not at their liking. |
|
Hi @ktf
Not a good idea. Correct includes are a necessary prerequisite to guarantee compilation of each file without which Clang-Tidy cannot perform a proper code analysis. Plus the unnecessary includes hurt the recompilation time.
Why? It takes a single command to fix almost all of the cases if we keep it green in the upstream.
OK, let's fix the framework then.
This I did not quite understand.
I wish it was possible but from my experience it is not always the case. I can elaborate in details.
This cannot be left to people's liking if they want reliable and meaningful CI. |
How about we do it automatically before running clang-tidy? |
This PR adds the ability to do embedding to the jet framework