Project

General

Profile

Bug #22423

Option --scan-revisions did not work so well

Added by Gianluca Petrillo about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
04/19/2019
Due date:
% Done:

0%

Estimated time:
Duration:

Description

My working area was icarusbuild01.fnal.gov:/icarus/app/users/petrillo/LArSoft/develop/c2_prof, with content in srcs:

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 lar_ci, v3_6_0.

Also available in: Atom PDF