Skip to content

PWGCF: Add two-particle azimuthal correlation analysis task #39707

PWGCF: Add two-particle azimuthal correlation analysis task

PWGCF: Add two-particle azimuthal correlation analysis task #39707

Triggered via pull request March 12, 2026 14:56
@mintu1999mintu1999
opened #15366
Status Failure
Total duration 41s
Artifacts

code-formatting.yml

on: pull_request_target
PR formatting  /  clang-format
38s
PR formatting / clang-format
PR formatting  /  copyright headers
11s
PR formatting / copyright headers
PR formatting  /  line endings
24s
PR formatting / line endings
PR formatting  /  whitespace
15s
PR formatting / whitespace
PR formatting  /  pragma-once
6s
PR formatting / pragma-once
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 5 warnings
Trailing spaces: twoParticleAzimuthalCorr.cxx#L924
Remove the trailing spaces at the end of the line.
Trailing spaces: twoParticleAzimuthalCorr.cxx#L906
Remove the trailing spaces at the end of the line.
Trailing spaces: twoParticleAzimuthalCorr.cxx#L583
Remove the trailing spaces at the end of the line.
Trailing spaces: twoParticleAzimuthalCorr.cxx#L420
Remove the trailing spaces at the end of the line.
Trailing spaces: twoParticleAzimuthalCorr.cxx#L308
Remove the trailing spaces at the end of the line.
Trailing spaces: twoParticleAzimuthalCorr.cxx#L284
Remove the trailing spaces at the end of the line.
Trailing spaces: twoParticleAzimuthalCorr.cxx#L222
Remove the trailing spaces at the end of the line.
Trailing spaces: twoParticleAzimuthalCorr.cxx#L220
Remove the trailing spaces at the end of the line.
Trailing spaces: twoParticleAzimuthalCorr.cxx#L173
Remove the trailing spaces at the end of the line.
Trailing spaces: twoParticleAzimuthalCorr.cxx#L160
Remove the trailing spaces at the end of the line.
PR formatting / clang-format
Process completed with exit code 1.
PR formatting / pragma-once
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
PR formatting / copyright headers
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
PR formatting / whitespace
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
PR formatting / line endings
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
PR formatting / clang-format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/