diff tests/test-clonebundles.t @ 50542:7b723217d368 stable

clonebundles: filter out invalid schemes instead of failing on them

Previously, an invalid clonebundle scheme would result in a failed
clone. By specifying a list of schemes we support,
we can make sure adding a new scheme (like the one for inline clonebundles)
does not result in clones failing for older clients.

--- a/tests/test-clonebundles.t	Thu Apr 20 10:48:12 2023 +0200
+++ b/tests/test-clonebundles.t	Thu Apr 20 11:23:45 2023 +0200
@@ -62,11 +62,16 @@
 Manifest file with URL with unknown scheme skips the URL
   $ echo 'weirdscheme://does.not.exist/bundle.hg' > server/.hg/clonebundles.manifest
   $ hg clone http://localhost:$HGPORT unknown-scheme
-  applying clone bundle from weirdscheme://does.not.exist/bundle.hg (known-bad-output !)
-  error fetching bundle: unknown url type: weirdscheme (known-bad-output !)
-  abort: error applying bundle (known-bad-output !)
-  (if this error persists, consider contacting the server operator or disable clone bundles via "--config ui.clonebundles=false") (known-bad-output !)
-  [255]
+  no compatible clone bundles available on server; falling back to regular clone
+  (you may want to report this to the server operator)
+  requesting all changes
+  adding changesets
+  adding manifests
+  adding file changes
+  added 2 changesets with 2 changes to 2 files
+  new changesets 53245c60e682:aaff8d2ffbbf
+  updating to branch default
+  2 files updated, 0 files merged, 0 files removed, 0 files unresolved
 
 Server is not running aborts