On Thu, Dec 17, 2020 at 12:01:25PM +0100, Alexander Bluhm wrote:
> On Wed, Dec 16, 2020 at 04:42:59PM +0100, Alexander Bluhm wrote:
> > When debugging tests, it is useful to see the target name and which
> > output belongs to it.
>
> A small addition:
>
> Run setup_once targets in a sepearate blo
On Wed, Dec 16, 2020 at 04:42:59PM +0100, Alexander Bluhm wrote:
> When debugging tests, it is useful to see the target name and which
> output belongs to it.
A small addition:
Run setup_once targets in a sepearate block with headline before
all other targets.
ok?
bluhm
Index: share/mk/bsd.reg
On Wed, Dec 16, 2020 at 05:01:18PM +0100, Theo Buehler wrote:
> On Wed, Dec 16, 2020 at 04:42:59PM +0100, Alexander Bluhm wrote:
> > When debugging tests, it is useful to see the target name and which
> > output belongs to it. A lot of my tests have echo lines, but I
> > think this is better done
On Wed, Dec 16, 2020 at 04:42:59PM +0100, Alexander Bluhm wrote:
> When debugging tests, it is useful to see the target name and which
> output belongs to it. A lot of my tests have echo lines, but I
> think this is better done in the framework. Then all tests behave
> simmilar. I would remove t
Hi,
When debugging tests, it is useful to see the target name and which
output belongs to it. A lot of my tests have echo lines, but I
think this is better done in the framework. Then all tests behave
simmilar. I would remove the echos from the Makefiles afterwards.
ok?
bluhm
Index: share/mk
