On Sun, Oct 3, 2021 at 8:41 AM mi...@ubo.ro wrote:
>
> I have developed a library that depends very much on reflect package. It
> caches a specific type and return a function that encodes(does something
> with) with that kind /type of data. Think of defining database schema using
> types and
On Tue, Oct 5, 2021 at 9:23 AM Jan Mercl <0xj...@gmail.com> wrote:
>
> This is a variation on
> https://github.com/gcc-mirror/gcc/blob/2f2aeda98f3aa24034a700e7efcb6c1a9397836f/gcc/testsuite/gcc.c-torture/execute/ieee/rbug.c
>
>
>
> package main
>
> /*
>
> float s(unsigned long long k) {
>
This is a variation on
https://github.com/gcc-mirror/gcc/blob/2f2aeda98f3aa24034a700e7efcb6c1a9397836f/gcc/testsuite/gcc.c-torture/execute/ieee/rbug.c
package main
/*
float s(unsigned long long k) {
float x;
x = (float)k;
return x;
}
unsigned long long cmain() {
Hi Jerome,
Have you tried to parallelize the tests?
t.Run(tc.name, func(t *testing.T) {
t.Parallel()
// your test
})
Best Regards,
Stephane
On Tue, Oct 5, 2021 at 2:08 PM Jérôme LAFORGE
wrote:
> Hello,
> I want to know if someone has already think about to split automatically
> (by
Hello,
I want to know if someone has already think about to split automatically
(by configuration with go test -split 50) a same test table driven (more
specially when the table is huge e.g. > 300 and so it takes time to
execute) into different test runs in order to split the run on each