Skip to content

[PWGCF] adding new analysis for multiharmonic correlations #28724

[PWGCF] adding new analysis for multiharmonic correlations

[PWGCF] adding new analysis for multiharmonic correlations #28724

Triggered via pull request May 26, 2026 20:50
@pengchonpengchon
opened #16403
Status Failure
Total duration 15s
Artifacts

o2-linter.yml

on: pull_request_target
O2 linter
13s
O2 linter
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 1 warning, and 2 notices
[name/configurable]: PWGCF/MultiparticleCorrelations/Tasks/multiharmonicCorrelations.cxx#L81
Use lowerCamelCase for names of configurables and use the same name for the struct member as for the JSON string. (Declare the type and names on the same line.)
[name/configurable]: PWGCF/MultiparticleCorrelations/Tasks/multiharmonicCorrelations.cxx#L80
Use lowerCamelCase for names of configurables and use the same name for the struct member as for the JSON string. (Declare the type and names on the same line.)
[name/configurable]: PWGCF/MultiparticleCorrelations/Tasks/multiharmonicCorrelations.cxx#L79
Use lowerCamelCase for names of configurables and use the same name for the struct member as for the JSON string. (Declare the type and names on the same line.)
[magic-number]: PWGCF/MultiparticleCorrelations/Tasks/multiharmonicCorrelations.cxx#L672
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
[magic-number]: PWGCF/MultiparticleCorrelations/Tasks/multiharmonicCorrelations.cxx#L671
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
[magic-number]: PWGCF/MultiparticleCorrelations/Tasks/multiharmonicCorrelations.cxx#L385
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
[magic-number]: PWGCF/MultiparticleCorrelations/Tasks/multiharmonicCorrelations.cxx#L383
Avoid magic numbers in expressions. Assign the value to a clearly named variable or constant.
[name/o2-workflow]: PWGCF/MultiparticleCorrelations/Tasks/CMakeLists.txt#L1
Use kebab-case for names of workflows and match the name of the workflow file.
[name/o2-workflow]: PWGCF/MultiparticleCorrelations/Tasks/CMakeLists.txt#L17
Workflow name multiparticle-correlations-ar does not match its file name multiparticle-correlations-ar.cxx. (Matches multiparticleCorrelationsAr.cxx.)
[name/o2-workflow]: PWGCF/MultiparticleCorrelations/Tasks/CMakeLists.txt#L12
Workflow name multiparticle-correlations-ab does not match its file name multiparticle-correlations-ab.cxx. (Matches multiparticleCorrelationsAb.cxx.)
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.