Skip to content

Please consider the following formatting changes to #12910 #17623

Please consider the following formatting changes to #12910

Please consider the following formatting changes to #12910 #17623

Triggered via pull request September 23, 2025 10:19
@alibuildalibuild
opened #13095
Status Failure
Total duration 14s
Artifacts

o2-linter.yml

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

Annotations

10 errors and 2 notices
[name/configurable]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L46
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/workflow-file]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L1
Name of a workflow file must match the name of the main struct in it (without the PWG prefix). (Class implementation files should be in "Core" directories.)
[name/struct]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L41
Use UpperCamelCase for names of structs.
[name/constexpr-constant]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L134
Use UpperCamelCase for names of constexpr constants. Names of special constants may be prefixed with "k".
[name/constexpr-constant]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L56
Use UpperCamelCase for names of constexpr constants. Names of special constants may be prefixed with "k".
[name/function-variable]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L133
Use lowerCamelCase for names of functions and variables.
[doc/file]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L1
Provide mandatory file documentation.
[doc/file]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L11
Documentation for \author is missing, incorrect or misplaced.
[doc/file]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L11
Documentation for \brief is missing, incorrect or misplaced.
[doc/file]: Common/TableProducer/ft0CorrectedMcOverride.cxx#L11
Documentation for \file is missing, incorrect or misplaced.
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.