On Wed, Dec 28, 2022, 11:58 Vincent Lefevre wrote:
> On 2022-12-28 10:07:19 -0500, NightStrike wrote:
> > On Wed, Dec 28, 2022, 06:46 Vincent Lefevre wrote:
> > > Perhaps, but the issue with ".NOTPARALLEL" is that it applies to
> > > the full Makefile, in case one just wants to serialize some te
On 2022-12-28 10:07:19 -0500, NightStrike wrote:
> On Wed, Dec 28, 2022, 06:46 Vincent Lefevre wrote:
> > Perhaps, but the issue with ".NOTPARALLEL" is that it applies to
> > the full Makefile, in case one just wants to serialize some tests.
>
> You can give it prerequisites to overcome that.
Th
On Wed, Dec 28, 2022, 06:46 Vincent Lefevre wrote:
> On 2022-12-28 06:00:11 -0500, NightStrike wrote:
> > On Wed, Dec 28, 2022, 03:31 Christian Jullien wrote:
> > > diff --git a/Makefile b/Makefile
> > > index c220879..c718d7a 100644
> > > --- a/Makefile
> > > +++ b/Makefile
> > > @@ -447,14 +44
On 2022-12-28 06:00:11 -0500, NightStrike wrote:
> On Wed, Dec 28, 2022, 03:31 Christian Jullien wrote:
> > diff --git a/Makefile b/Makefile
> > index c220879..c718d7a 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -447,14 +447,16 @@ config.mak:
> > $(if $(wildcard $@),,@echo "Please
On Wed, Dec 28, 2022, 03:31 Christian Jullien wrote:
> If it helps, I've just tried this patch which implement what you
> suggested, and it works. Maybe maintainers will consider to add it (.. or
> not)
>
> diff --git a/Makefile b/Makefile
> index c220879..c718d7a 100644
> --- a/Makefile
> +++ b/
cc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Vincent
Lefevre
Sent: Tuesday, December 27, 2022 12:29
To: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] randomly failing tests
On 2022-12-27 08:30:52 +0100, Herman ten Brugge via Tinycc-devel wrote:
> Are you using parallel build?
Ye
On 2022-12-27 08:30:52 +0100, Herman ten Brugge via Tinycc-devel wrote:
> Are you using parallel build?
Yes, I have a shell function "make" that uses the -j option
(with the number of available cores).
> This does not work for the testsuite .
If this doesn't work for the testsuite, why not disab
On 12/7/22 16:06, Vincent Lefevre wrote:
Tests are failing randomly on Debian/x86_64:
[...]
Test: 107_stack_safe...
Test: 108_constructor...
Test: 109_float_struct_calling...
Test: 110_average...
Test: 111_conversion...
Test: 112_backtrace...
--- 108_constructor.expect 2022-12-07 15:57:51.3
On 2022-12-07 16:12:22 +0100, Vincent Lefevre wrote:
> The cause seems to be that the generated executable name is fixed
> to "a.exe" instead of depending on the test name:
>
> 113_btdll.test: T1 = \
> $(TCC) -bt $1 -shared -D DLL=1 -o a1$(DLLSUF) && \
> $(TCC) -bt $1 -shared -D DLL=2 -o a
On 2022-12-07 16:06:27 +0100, Vincent Lefevre wrote:
> Tests are failing randomly on Debian/x86_64:
>
> [...]
> Test: 107_stack_safe...
> Test: 108_constructor...
> Test: 109_float_struct_calling...
> Test: 110_average...
> Test: 111_conversion...
> Test: 112_backtrace...
> --- 108_constructor.exp
Tests are failing randomly on Debian/x86_64:
[...]
Test: 107_stack_safe...
Test: 108_constructor...
Test: 109_float_struct_calling...
Test: 110_average...
Test: 111_conversion...
Test: 112_backtrace...
--- 108_constructor.expect 2022-12-07 15:57:51.358297673 +0100
+++ 108_constructor.output
11 matches
Mail list logo
