On 11/4/22 22:45, Han Zhou wrote:
> On Wed, Nov 2, 2022 at 7:46 AM Dumitru Ceara wrote:
>>
>> On 11/2/22 15:35, Ales Musil wrote:
>>> To prevent some jobs not running after CI scripts updates
>>> use numbers instead of the test flags. This still allows us
>>> to use parallelization, but without
On Wed, Nov 2, 2022 at 7:46 AM Dumitru Ceara wrote:
>
> On 11/2/22 15:35, Ales Musil wrote:
> > To prevent some jobs not running after CI scripts updates
> > use numbers instead of the test flags. This still allows us
> > to use parallelization, but without worrying about skipping
> > some tests
On 11/2/22 15:35, Ales Musil wrote:
> To prevent some jobs not running after CI scripts updates
> use numbers instead of the test flags. This still allows us
> to use parallelization, but without worrying about skipping
> some tests by mistake.
>
> For "test" suites use 3 parts, with 1500 tests
Bleep bloop. Greetings Ales Musil, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Line is 86 characters long (recommended limit is 79)
#46 FILE: .ci/linux-build.sh:54:
To prevent some jobs not running after CI scripts updates
use numbers instead of the test flags. This still allows us
to use parallelization, but without worrying about skipping
some tests by mistake.
For "test" suites use 3 parts, with 1500 tests in mind.
That should give as additional space for