Closed pinkenburg closed 1 week ago
Report for commit 32bed5ff86d032d759b1059b6825a7ab0dba121f:
gcc-12.1.0
/ clang
is SUCCESS, :bar_chart:clang report (full)/(new), build loggcc-12.1.0
/ new
is SUCCESS, :bar_chart:Compiler report (full)/(new), build log
gcc-12.1.0
, build new
: run the default sPHENIX macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: run the default CaloProduction/Fun4All_Year1.C macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: run the default CaloProduction/Fun4All_Year2.C macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: run the default StreamingProduction/Fun4All_Stream_Combiner.C macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: run the default TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C macro: build is SUCCESS, output, trends :bar_chart: gcc-12.1.0
, build new
: Valgrind test of CaloProduction/Fun4All_Year1.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart: gcc-12.1.0
, build new
: Valgrind test of CaloProduction/Fun4All_Year2.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart: gcc-12.1.0
, build new
: Valgrind test of StreamingProduction/Fun4All_Stream_Combiner.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart: gcc-12.1.0
, build new
: Valgrind test of TrackingProduction/Fun4All_TrkrHitSet_Unpacker.C: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart: gcc-12.1.0
, build new
: run the overlap check for sPHENIX macro: build is SUCCESS, output gcc-12.1.0
, build new
: Valgrind test: build is SUCCESS, :bar_chart:valgrind report, trends :bar_chart:gcc-12.1.0
/ scan
is SUCCESS, :bar_chart:scan-build report (full)/(new), build logclang-tidy
is SUCCESS, :bar_chart:clang-tidy
report (full)/(new)cpp-check
is SUCCESS, :bar_chart:cppcheck
report (full)/(new)_Automatically generated by sPHENIX Jenkins continuous integration_
Types of changes
What kind of change does this PR introduce? (Bug fix, feature, ...)
This PR moves caloTreeGen from QA to packages. It's the more logical place and there was a typo in the package list, so this was never build. Let's see if jenkins likes it
TODOs (if applicable)
Links to other PRs in macros and calibration repositories (if applicable)