[PWGLF] added separate fn for signal loss correction using mt scaling #26745
Triggered via pull request
April 17, 2026 05:57
nasirmehdimalik
synchronize
#15823
Status
Failure
Total duration
19s
Artifacts
–
Annotations
10 errors, 1 warning, and 2 notices
|
[pdg/explicit-code]:
PWGLF/TableProducer/Resonances/resonanceInitializer.cxx#L264
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
[pdg/explicit-code]:
PWGLF/TableProducer/Resonances/resonanceInitializer.cxx#L263
Avoid hard-coded PDG codes. Use named values from PDG_t or o2::constants::physics::Pdg instead.
|
|
[name/o2-column]:
PWGLF/DataModel/LFResonanceTables.h#L217
Use UpperCamelCase for names of O2 columns and matching lowerCamelCase names for their getters.
|
|
[name/o2-column]:
PWGLF/DataModel/LFResonanceTables.h#L177
Use UpperCamelCase for names of O2 columns and matching lowerCamelCase names for their getters.
|
|
[name/o2-column]:
PWGLF/DataModel/LFResonanceTables.h#L82
Use UpperCamelCase for names of O2 columns and matching lowerCamelCase names for their getters.
|
|
[magic-number]:
PWGLF/DataModel/LFResonanceTables.h#L457
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[magic-number]:
PWGLF/DataModel/LFResonanceTables.h#L452
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[magic-number]:
PWGLF/DataModel/LFResonanceTables.h#L390
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[magic-number]:
PWGLF/DataModel/LFResonanceTables.h#L380
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
[magic-number]:
PWGLF/DataModel/LFResonanceTables.h#L374
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
|
|
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.
|