Option --scan-revisions did not work so well
My working area was
icarusbuild01.fnal.gov:/icarus/app/users/petrillo/LArSoft/develop/c2_prof, with content in
develop [icarus_data] develop [icaruscode] develop [icarusutil] develop [larana] develop [larcore] feature/gp_moreGeometryFeatures [larcorealg] develop [larcoreobj] develop [lardataalg] feature/gp_refreshLArVoxelReadout [larsim]
The output of
trigger --build-delay 0 --scan-revisions was:
using revision:icarus_data@914e5c6 icaruscode@ icarusutil@ larana@ larcore@ larcorealg@ larcoreobj@ lardataalg@ larsim@1e4cef21 Triggering CI build
and the resulting failure can be contemplated in the LArCI dashboard : http://dbweb5.fnal.gov:8080/LarCI/app/build_detail/phase_details?build_id=lar_ci/5339&platform=Linux%203.10.0-957.5.1.el7.x86_64&phase=checkout&buildtype=slf7%20e17:prof.
I am using a
current version of
#2 Updated by Vito Di Benedetto 4 months ago
- % Done changed from 0 to 90
Gianluca, thanks to report this issue.
It has been fixed into generic_ci develop branch.
Next CI release candidate is planned for the end of June. At that time there will be a test UPS package available through CVMFS.
If you think it will be useful to have this fix available earlier, I'll be happy to make a new UPS package in coming days.