TPC: rawDataQA

[tklemenz]

Add a QC task for TPC raw digits

[tklemenz]

The o2-dataflow build error seems unrelated to the PR.

[Barthelemy]

Indeed, the o2-dataflow is due to something else (we need to move to gcc10). The macOS is strange as there is nothing. Let's see.

[tklemenz]

Is gcc10 the solution? I am getting similar complaints about #include <filesystem> on my local machine when compiling the latest O2 dev but QualityControl master builds without error.

[Barthelemy]

Do you have gcc 10 ?
The probem here is that o2-dataflow uses gcc 7 and filesystem was still in experimental back then.

[tklemenz]

I am on gcc 7.5.0

[Barthelemy]

Then this is why you have this issue. If you use the defaults o2 then it will force gcc10. It is not yet hte case with o2-dataflow and it provokes this error. We are working on it: alisw/alidist#3027

[tklemenz]

This is weird, because on my local machine I do use --defaults o2.
aliBuild build QualityControl --defaults o2

gcc 7.5.0 is my system gcc. But then it seems to me that aliBuild doesn't force gcc 10.

[Barthelemy]

Are you sure that your alidist is up to date ? Because defaults-o2.sh reads:

overrides:
  GCC-Toolchain:
     version: "v10.2.0-alice2"
     tag: "v10.2.0-alice2"

[tklemenz]

Yes, this is exactly what I see in my defaults-o2.sh, too.

overrides:
  GCC-Toolchain:
     version: "v10.2.0-alice2"
     tag: "v10.2.0-alice2"

Maybe for some reason gcc 10 was skipped during building. I'll find a way, I guess. At least I know now what the origin of the problem is.

[stheckel]

Hi,
I observe the same behaviour as Thomas concerning the gcc: I have aliBuild version 1.8.0 and alidist/O2/QC (master or dev) from Friday (May 7) morning. Compiling O2 and QC with
aliBuild build QualityControl --defaults o2
gcc is not compiled, but taken from the system, and the system version is 7.5.0. At least, when loading QC (and hence O2) and typing gcc --version I get the 7.5.0.
As Thomas I am on Ubuntu 18.04.

[tklemenz]

FYI: I changed the required version of gcc in gcc-toolchain.sh and it worked.

case $REQUESTED_VERSION in
  v10*) MIN_GCC_VERSION=100200 ;;
  *) MIN_GCC_VERSION=100200 ;;          # <---------------- HERE
esac

[Barthelemy]

@ktf Is it expected that gcc 7 is picked from the system ? should we not enforce gcc 10 ?

[ktf]

@Barthelemy alibuild will pick up GCC 10.2 from the system only if such a version is requested in GCC-ToolChain (i.e. not for aliphysics).

[Barthelemy]

@ktf But I don't think that Thomas is using aliphysics. Any ways, I think that it should go to another thread. Thomas, could you open a JIRA ticket ?

[Barthelemy]

the macOS build seems spurrious., merging.

[ktf]

I mean that the reason why we still have 7.3.0 is due to AliPhysics.

[tklemenz]

Sure, I can open a ticket and yes, I do not use aliphysics.

[tklemenz]

The ticket can be found here: https://alice.its.cern.ch/jira/browse/O2-2327