diff tests/test-bundle-r.t @ 51280:c17cf2d51ff4 stable

bundle: do not detect --base argument that match nothing as lack of argument

With the previous version of the code, if --base did not match anything, it will
be handled as if no --base was provided and will fallback to using discovery
with the default path. This has two issues :
- The resulting bundle won't match what the user requested,
- if not default path is configured, it will crash.

We now properly distinct between the two cases and if the --base query does not
find any changeset, we will assume that everything under --rev needs to be sent.

--- a/tests/test-bundle-r.t	Wed Dec 27 18:42:13 2023 +0100
+++ b/tests/test-bundle-r.t	Wed Dec 27 18:02:26 2023 +0100
@@ -141,14 +141,9 @@
   ignoring --base because --all was specified
   9 changesets found
   $ hg -R test bundle --base 3-3 -r tip test-base-match-nothing-with-dest.hg --config paths.default=$TESTTMP/test-3
-  searching for changes (known-bad-output !)
-  1 changesets found (known-bad-output !)
-  5 changesets found (missing-correct-output !)
+  5 changesets found
   $ hg -R test bundle --base 3-3 -r tip test-base-match-nothing-no-dest.hg
-  config error: default repository not configured! (known-bad-output !)
-  (see 'hg help config.paths') (known-bad-output !)
-  5 changesets found (missing-correct-output !)
-  [30]
+  5 changesets found
   $ hg -R test bundle --base 3 -r tip test-bundle-should-fail.hg
   1 changesets found