hg command failure didn't report error message

NEW
Unassigned

Status

2 years ago
5 months ago

People

(Reporter: glob, Unassigned)

Tracking

({conduit-triaged})

Details

(Whiteboard: [lando-backlog])

(Reporter)

Description

2 years ago
during a period of network connectivity issues within scl3, autoland was unable to determine the remote tip.

this was logged with the somewhat cryptic error (from bug 1341775 comment 60):
> hg error in cmd: hg identify upstream -r tip:

logs tell the same story:

> Mar 24 23:13:19 autoland python: initiating transplant from tree: gecko rev: 9d0ae775ef4fa1bcdf02612e2f8fe7260fdaeee1 to destination: ssh://hg.mozilla.org/integration/autoland, attempt 1
> Mar 24 23:13:19 autoland python: rev: 9d0ae775ef4fa1bcdf02612e2f8fe7260fdaeee1: executing: ['identify', 'upstream', '-r', 'tip']
> Mar 24 23:17:33 autoland python: transplant from tree: gecko rev: 9d0ae775ef4fa1bcdf02612e2f8fe7260fdaeee1 attempt: 1: hg error in cmd: hg identify upstream -r tip:
> Mar 24 23:17:33 autoland python: transplant failed: tree: gecko rev: 9d0ae775ef4fa1bcdf02612e2f8fe7260fdaeee1 destination: ssh://hg.mozilla.org/integration/autoland error: hg error in cmd: hg identify upstream -r tip:
> Mar 24 23:17:33 autoland python: elapsed transplant time: 0:04:14.785872

the reason for the |hg identify| failing should have been included in the output.

Updated

6 months ago
Product: MozReview → Conduit

Updated

5 months ago
Keywords: conduit-triaged
Whiteboard: [lando-backlog]
You need to log in before you can comment on or make changes to this bug.