On Mon, May 01, 2006 at 09:53:45PM -0500, Steve Peters wrote:
> This is always of those fun problems you can never reproduce on your own, by 
> hand, but
> is always happening.  Nearly every smoke includes the following failure.
> 
> ../lib/Module/Build/t/extend.t..........FAILED--expected 64 tests, saw 59
> 
> Running this test with both TEST and harness by hand don't answer the 
> question of
> why.  Running with verbose gives me thoughts though.
> 
> ok 59 - Do not allow default-less prompt() for unattended builds
> Is this a question?
> ok 60 - prompt() doesn't require default for interactive builds
> Say yes
> ok 61 - y_n() doesn't require default for interactive build
> Is this a question
> ok 62 - default for prompt() without a default is ''
> Is this a question [y] y
> ok 63 -   prompt() with a default
> Is this a question [y] y
> ok 64 -   y_n() with a default
> ok
> 
> My guess is that the lines are going to STDOUT and getting picked up by
> the screen scraping that's happening in TEST.  My hope is that by adding
> "#"s to the start of those prompts the tests will start passing.  It works
> when I run "make test" from a command-line, but the smokes will be the real
> test.
> 
> Steve Peters
> [EMAIL PROTECTED]
> 
> 
> Change 28045 by [EMAIL PROTECTED] on 2006/05/02 02:47:43
> 
>       Escape prompts with #'s to avoid causing tests to fail from
>       the unexpected output.
> 

Since the above change there's been no change in the results, and, for 
me at least, no change in my inability to replicate this problem.  
Interestingly enough, this error didn't occur with my Linux icc smoke.

Is anyone else able to replicate this problem at all?

Steve Peters
[EMAIL PROTECTED]

Attachment: signature.asc
Description: Digital signature

Reply via email to