On Tue, 2024-01-16 at 11:12 +, Iain Sandoe wrote:
> Tested on x86_64, i686 Darwin, x86_64 Linux,
> OK for trunk? When?
> thanks
> Iain
Thanks; looks good to me for trunk.
Given that the scope is just the jit testsuite and that you've tested
it on 3 configurations (and presumably made use of t
gentle ping,
with the increasing use of CI, it seems an idea to tackle this sooner rather
than later.
thanks
Iain
> On 16 Jan 2024, at 11:12, Iain Sandoe wrote:
>
> Tested on x86_64, i686 Darwin, x86_64 Linux,
> OK for trunk? When?
> thanks
> Iain
>
> --- 8< ---
>
> Currently when a test fail
Tested on x86_64, i686 Darwin, x86_64 Linux,
OK for trunk? When?
thanks
Iain
--- 8< ---
Currently when a test fails, we print out a lot of information,
this includes items that are not stable between invocations (e.g.
the PID for the executable). That makes automated comparisons
between test run