Thomas Monjalon writes:
> 04/06/2019 17:49, Michael Santana Francisco:
>> On 6/4/19 4:59 AM, David Marchand wrote:
>> > - the "perf" tests are taking way too long for my taste,
+1 here.
>>
>> We should still fix them. However I don't know if we should be running
>> the perf test for every job
04/06/2019 17:49, Michael Santana Francisco:
> On 6/4/19 4:59 AM, David Marchand wrote:
> > - the "perf" tests are taking way too long for my taste,
>
> We should still fix them. However I don't know if we should be running
> the perf test for every job and every patch on travis. It takes too
>
On 6/4/19 4:59 AM, David Marchand wrote:
This is a joint effort to make the unit tests ready for CI.
The first 8 patches are fixes that I had accumulated.
Then the second part of the series focuses on skipping tests when some
requirements are not fulfilled so that we can start them in a restraine
This is a joint effort to make the unit tests ready for CI.
The first 8 patches are fixes that I had accumulated.
Then the second part of the series focuses on skipping tests when some
requirements are not fulfilled so that we can start them in a restrained
environment like Travis virtual machines
4 matches
Mail list logo
