Closed AndrewEdmonds11 closed 4 months ago
Hi @AndrewEdmonds11, You have proposed changes to files in these packages:
which require these tests: build.
@Mu2e/fnalbuild-users, @Mu2e/write have access to CI actions on main.
:hourglass: The following tests have been triggered for 51bf7956c272c05c609caf53e573e3994380ba00: build (Build queue has 1 jobs)
:umbrella: The build tests failed for 51bf7956c272c05c609caf53e573e3994380ba00.
Test | Result | Details |
---|---|---|
test with | :white_check_mark: | Command did not list any other PRs to include |
merge | :white_check_mark: | Merged 51bf7956c272c05c609caf53e573e3994380ba00 at 127c7871bd0725b30a2e85064c18568b49b425e1 |
build (prof) | :white_check_mark: | Log file. Build time: 04 min 11 sec |
ceSimReco | :x: | Log file. Return Code 9. |
g4test_03MT | :white_check_mark: | Log file. |
transportOnly | :white_check_mark: | Log file. |
POT | :white_check_mark: | Log file. |
g4study | :white_check_mark: | Log file. |
cosmicSimReco | :x: | Log file. Return Code 1. |
cosmicOffSpill | :x: | Log file. Return Code 9. |
ceSteps | :x: | Log file. Return Code 9. |
ceDigi | :x: | Log file. Return Code 9. |
muDauSteps | :white_check_mark: | Log file. |
ceMix | :x: | Log file. Return Code 9. |
rootOverlaps | :white_check_mark: | Log file. |
g4surfaceCheck | :white_check_mark: | Log file. |
FIXME, TODO | :white_check_mark: | TODO (0) FIXME (0) in 0 files |
clang-tidy | :white_check_mark: | 0 errors 0 warnings |
N.B. These results were obtained from a build of this Pull Request at 51bf7956c272c05c609caf53e573e3994380ba00 after being merged into the base branch at 127c7871bd0725b30a2e85064c18568b49b425e1.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever
on the job page.
This PR goes with Mu2e/Offline#1306. At the moment, I have done the following (there are some questions):
noCompression
compression at the end of the primary stageAnd some things I haven't done:
On this latter point, the SurfaceSteps are smaller in size than the StepPointMCs so there may be some space to add SurfaceSteps for pileup processes. From
product_sizes_dumper
output of a 5-event dts file: