[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
The behavior of "make check"
From: |
Dan Eble |
Subject: |
The behavior of "make check" |
Date: |
Thu, 10 Oct 2019 12:43:45 -0400 |
Begin forwarded message:
>
> Subject: [testlilyissues:issues] Re: #5564 Fix conversion warnings in beaming
> code
> Date: October 10, 2019 at 12:08:48 EDT
> I'm sorry to contribute to your frustration. I can see what the process is,
> but my question (which I direct to LilyPond developers in general) is whether
> it is justified that make check run to completion using an out-of-date
> lilypond rather than either rebuilding it first or raising some kind of
> alarm. Must we continue to put up with it?
>
> The purpose of make is to follow dependencies and do exactly what needs to be
> done. The difference in behavior between these cases seems contrary to that:
>
> make && make check
> make check
—
Dan
- The behavior of "make check",
Dan Eble <=