[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fix test target name in python/GNUmakefile (issue 575790044 by addre
From: |
jonas . hahnfeld |
Subject: |
Re: Fix test target name in python/GNUmakefile (issue 575790044 by address@hidden) |
Date: |
Sun, 08 Mar 2020 01:43:57 -0800 |
On 2020/03/07 23:25:50, hanwenn wrote:
> On 2020/03/07 21:36:04, hahnjo wrote:
> > Yes, but 'check' for LilyPond also does the comparison to
test-baseline. As
> > 'check' depends on 'test' I think we should put it there because the
unit
> tests
> > should run in both cases.
>
> could you send a patch to demonstrate what you mean? I ran "make
test", but I
> don't think my unittest was run
As I said, you have to fix it first. Dan noted the place in the
top-level GNUmakefile.in above.
https://codereview.appspot.com/575790044/
- Fix test target name in python/GNUmakefile (issue 575790044 by address@hidden), jonas . hahnfeld, 2020/03/07
- Re: Fix test target name in python/GNUmakefile (issue 575790044 by address@hidden), nine . fierce . ballads, 2020/03/07
- Re: Fix test target name in python/GNUmakefile (issue 575790044 by address@hidden), hanwenn, 2020/03/07
- Re: Fix test target name in python/GNUmakefile (issue 575790044 by address@hidden), jonas . hahnfeld, 2020/03/07
- Re: Fix test target name in python/GNUmakefile (issue 575790044 by address@hidden), nine . fierce . ballads, 2020/03/07
- Re: Fix test target name in python/GNUmakefile (issue 575790044 by address@hidden), hanwenn, 2020/03/07
- Re: Fix test target name in python/GNUmakefile (issue 575790044 by address@hidden),
jonas . hahnfeld <=