view tests/test-bad-pull.t @ 41066:0358cca1dccf

exthelper: reintroduce the ability to register revsets

I think this is what Yuya and Boris agreed on.[1]  This happens *after* the
extsetup phase now (and after the _aftercallback notifications).  But this is
trivial, mergeable between exthelper instances, and doesn't need to have the
extension name supplied when registering.

The test needed updating so that extsetup() takes a `ui` argument, as exthelper
isn't trying to be backward compatible with 1.3.1.

[1] https://www.mercurial-scm.org/pipermail/mercurial-devel/2018-December/125888.html

#require serve

  $ hg clone http://localhost:$HGPORT/ copy
  abort: * (glob)
  [255]

  $ test -d copy
  [1]

  $ "$PYTHON" "$TESTDIR/dumbhttp.py" -p $HGPORT --pid dumb.pid
  $ cat dumb.pid >> $DAEMON_PIDS
  $ hg clone http://localhost:$HGPORT/foo copy2
  abort: HTTP Error 404: * (glob)
  [255]
  $ killdaemons.py