[PWGEM] [PWGEM/PhotonMeson]Include of check for gamma gamma contamination in Dalitz decays #28417
Triggered via pull request
May 20, 2026 08:05
lgansbartl
lgansbartl
synchronize
#16306
Status
Failure
Total duration
20s
Artifacts
–
Annotations
10 errors, 1 warning, and 2 notices
|
[magic-number]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L730
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[magic-number]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L593
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[magic-number]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L283
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[magic-number]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L280
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[const-ref-in-for-loop]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L937
Use constant references for non-modified iterators in range-based for loops.
|
|
[const-ref-in-for-loop]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L931
Use constant references for non-modified iterators in range-based for loops.
|
|
[const-ref-in-for-loop]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L582
Use constant references for non-modified iterators in range-based for loops.
|
|
[pdg/explicit-code]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L809
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
[pdg/explicit-code]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L732
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
[pdg/explicit-code]:
PWGEM/PhotonMeson/Core/Pi0EtaToGammaGammaMC.h#L730
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
O2 linter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: thollander/actions-comment-pull-request@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
O2 linter
To tolerate certain issues in a directory, add a line with the test name in "o2linter_config".
|
|
O2 linter
Exceptionally, you can disable a test for a line by adding a comment with "o2-linter: disable=" followed by the name of the test and parentheses with a reason for the exception.
|