Re: Stagnant regression test output

[Dan Eble]

On Feb 16, 2018, at 07:49, Dan Eble  wrote:
> 
> At this point, I don’t have any reason to believe that there is a problem 
> affecting other people; however, I don’t have evidence to the contrary 
> either.  It’s going to take me some time to get to the bottom of it.  My 
> hypothesis is that there’s yet another undiscovered problem with my using a 
> separate, read-only source directory, but I want to warn everyone to pay 
> attention as you test, just in case it’s not limited to my environment.

I haven’t been able to reproduce this problem all week; however, I have noticed 
make complaining about clock skew now and then, so I am content to assume that 
that had something to do with the original problem and I just didn’t notice it 
at the time.

VirtualBox appears not to cope with time very well after the host sleeps and 
wakes up.
—
Dan


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Stagnant regression test output

[Phil Holmes]

- Original Message - 
From: "David Kastrup" <d...@gnu.org>

To: "Han-Wen Nienhuys" <hanw...@gmail.com>
Cc: "LilyPond Development Team" <lilypond-devel@gnu.org>
Sent: Saturday, February 24, 2018 9:31 AM
Subject: Re: Stagnant regression test output



Han-Wen Nienhuys <hanw...@gmail.com> writes:


There used to be a test that created a random layout (which should
always trigger), just to make sure that the regression test comparison
itself was working. Has this disappeared?


No.

--
David Kastrup


See http://lilypond.org/test/v2.19.81-1/compare-v2.19.80-1/index.html

test-output-distance.ly

--
Phil Holmes

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Stagnant regression test output

[David Kastrup]

Han-Wen Nienhuys  writes:

> There used to be a test that created a random layout (which should
> always trigger), just to make sure that the regression test comparison
> itself was working. Has this disappeared?

No.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Stagnant regression test output

[Han-Wen Nienhuys]

There used to be a test that created a random layout (which should
always trigger), just to make sure that the regression test comparison
itself was working. Has this disappeared?

On Fri, Feb 16, 2018 at 1:49 PM, Dan Eble  wrote:
> Last night, I noticed that the log output for my local regression tests did 
> not hold the updated output I expected after test-clean, check.  It still 
> held old output that did not match what my rebuilt lilypond binary produced 
> in a manual run on the test input.  I ended up deleting my whole build 
> directory and starting over.
>
> At this point, I don’t have any reason to believe that there is a problem 
> affecting other people; however, I don’t have evidence to the contrary 
> either.  It’s going to take me some time to get to the bottom of it.  My 
> hypothesis is that there’s yet another undiscovered problem with my using a 
> separate, read-only source directory, but I want to warn everyone to pay 
> attention as you test, just in case it’s not limited to my environment.
>
> Regards,
> —
> Dan
>
>
> ___
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel



-- 
Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Stagnant regression test output

[Dan Eble]

Last night, I noticed that the log output for my local regression tests did not 
hold the updated output I expected after test-clean, check.  It still held old 
output that did not match what my rebuilt lilypond binary produced in a manual 
run on the test input.  I ended up deleting my whole build directory and 
starting over.

At this point, I don’t have any reason to believe that there is a problem 
affecting other people; however, I don’t have evidence to the contrary either.  
It’s going to take me some time to get to the bottom of it.  My hypothesis is 
that there’s yet another undiscovered problem with my using a separate, 
read-only source directory, but I want to warn everyone to pay attention as you 
test, just in case it’s not limited to my environment.

Regards,
— 
Dan


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel