[issue1977] Multirepo push should fail if subrepo push fails

[Marcus Lindblom]

New submission from Marcus Lindblom <macke at yar.nu>:

If my .hgsub contains a http-path, that requires ssl to push, then the "big"
push skips that subrepo and pushes the master repo.

I'd expect the push to fail (requiring a --force or something), so that I
can push the sub-repo first, in order to have a consistent state.

The current behaviour is a bit frustrating because: 
 * The 'ssl required' is not easy to spot amongst the output (see below)
 * My CI system starts building & testing the change, and its checkout fails
since the sub-repo commits haven't been pushed (but .hgsubstate has)

This is how it looks:

>hg push
pushing to ssh://sever/tpd-build
pushing subrepo TheFancyLib
searching for changes
ssl required                   <-- argh!
pushing subrepo BuildSystem
searching for changes
no changes found
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: rev 61ab8c9fc57625de0847c89171cc6ba888117627 sent
> ...

----------
messages: 11416
nosy: marcusl
priority: bug
status: unread
title: Multirepo push should fail if subrepo push fails

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue1977>
____________________________________________________