Re: Assert IS_VALID_FORWARD_RANGE fails in merge_tests 125 [was: Hanging tests mergeinfo-test.exe 12, 15 and skel-test.exe 4 on WinXP with VS2010 release build]

On Sun, Nov 11, 2012 at 1:59 PM, Stefan Fuhrmann
<stefan.fuhrmann_at_wandisco.com> wrote:
>
>
> On Thu, Nov 8, 2012 at 6:04 PM, Julian Foad <julianfoad_at_btopenworld.com>
> wrote:
>>
>> Stefan Fuhrmann wrote:
>>
>> > But I did run across an assertion in mergeinfo.c, :line 1174
>> >
>> >> during merge_tests.py 125:
>> >>>
>> >>> SVN_ERR_ASSERT_NO_RETURN(IS_VALID_FORWARD_RANGE(first));
>> >
>> > The weird thing about the assertion is, that the tests
>> > will continue just fine afterwards and no error was
>> > reported. I suspect some compiler optimization issue
>> > or some missing initialization.
>>
>>
>> I see this too. The test is marked XFAIL.
>
>
> OK, that explains why it simply carries on afterwards.
> It has been the first test that popped up the "your app
> terminated unexpectedly" window. And that is not
> nice behavior for an automated test suite.

Yeah, that reminds me that I had the same problem, already for a long
time (I don't notice it anymore). See this thread:

http://thread.gmane.org/gmane.comp.version-control.subversion.devel/125147

It's only when you run the test suite with a release build. With a
debug build, you won't get the annoying popup. But with a release
build on Windows, it's quite annoying that you can't run it
unattended...

-- 
Johan