[issue3382] bisect -U leaves no breadcrumb to indicate which rev is to be tested

[Bryan O'Sullivan]

New submission from Bryan O'Sullivan <bos at serpentine.com>:

This is the other part of issue3381.


I'm trying to bisect a bug in a very big tree, where checking out a working 
dir takes a while.

So I noticed the -U option to bisect, and thought I'd give it a try. I 
started in a normal hg repo.

  hg bisect -g 3333 -U
  hg bisect -b 4444 -U

In this world, the working dir's parents (deliberately) do not match the 
revision that bisect wants us to look at, but the revision to be tested is 
only printed to stdout, and is not stored persistently anywhere.

I thought that a revset might tell me:

  hg log -r 'bisect(untested)'

But this just tells me about all untested revs, not the current one.  Since I 
want to use the revision inside a command to be run by hg bisect -c, I'm 
stuck: the working dir doesn't reflect the rev being bisected, and since the 
command is being run by hg, it has no way to find out what that rev is.

----------
messages: 19664
nosy: bos
priority: bug
status: unread
title: bisect -U leaves no breadcrumb to indicate which rev is to be tested

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