[yocto-autobuilder2][PATCH] schedulers.py: run performance builds only 2x a day, not 4x


Alexander Kanavin
 

The same builds are included in a-full, so they tend to get queued up
and cause delays in builds completion, as there's only a single worker
allocated to them. Let's run them less frequently to mitigate the delays.

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
schedulers.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/schedulers.py b/schedulers.py
index 2e8f3d5..ca63c9f 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -306,11 +306,11 @@ schedulers.append(sched.Nightly(name=3D'nightly-qui=
ck', branch=3D'master', propertie
schedulers.append(sched.Nightly(name=3D'nightly-full', branch=3D'master'=
, properties=3Dparent_default_props('a-full'),
builderNames=3D['a-full'], hour=3D1, minute=3D0, dayOf=
Week=3D6))
=20
-# Run the build performance tests at 3am, 9am, 3pm and 9pm
+# Run the build performance tests at 3am and 3pm
schedulers.append(sched.Nightly(name=3D'nightly-buildperf-ubuntu1604', b=
ranch=3D'master', properties=3Dparent_default_props('buildperf-ubuntu1604=
'),
- builderNames=3D['buildperf-ubuntu1604'], hour=3D[3,9,1=
5,21], minute=3D0))
+ builderNames=3D['buildperf-ubuntu1604'], hour=3D[3,15]=
, minute=3D0))
schedulers.append(sched.Nightly(name=3D'nightly-buildperf-centos7', bran=
ch=3D'master', properties=3Dparent_default_props('buildperf-centos7'),
- builderNames=3D['buildperf-centos7'], hour=3D[3,9,15,2=
1], minute=3D0))
+ builderNames=3D['buildperf-centos7'], hour=3D[3,15], m=
inute=3D0))
=20
# Run the AUH on the 15th of every month
schedulers.append(sched.Nightly(name=3D'nightly-auh', branch=3D'master',=
properties=3Dparent_default_props('auh'),
--=20
2.29.1


Richard Purdie
 

On Sun, 2020-11-08 at 10:09 +0100, Alexander Kanavin wrote:
The same builds are included in a-full, so they tend to get queued up
and cause delays in builds completion, as there's only a single worker
allocated to them. Let's run them less frequently to mitigate the delays.

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
schedulers.py | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/schedulers.py b/schedulers.py
index 2e8f3d5..ca63c9f 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -306,11 +306,11 @@ schedulers.append(sched.Nightly(name='nightly-quick', branch='master', propertie
schedulers.append(sched.Nightly(name='nightly-full', branch='master', properties=parent_default_props('a-full'),
builderNames=['a-full'], hour=1, minute=0, dayOfWeek=6))

-# Run the build performance tests at 3am, 9am, 3pm and 9pm
+# Run the build performance tests at 3am and 3pm
schedulers.append(sched.Nightly(name='nightly-buildperf-ubuntu1604', branch='master', properties=parent_default_props('buildperf-ubuntu1604'),
- builderNames=['buildperf-ubuntu1604'], hour=[3,9,15,21], minute=0))
+ builderNames=['buildperf-ubuntu1604'], hour=[3,15], minute=0))
schedulers.append(sched.Nightly(name='nightly-buildperf-centos7', branch='master', properties=parent_default_props('buildperf-centos7'),
- builderNames=['buildperf-centos7'], hour=[3,9,15,21], minute=0))
+ builderNames=['buildperf-centos7'], hour=[3,15], minute=0))
I've been wondering about this but I suspect we should drop them from
a-full instead...

Cheers,

Richard


Alexander Kanavin
 

On Sun, 8 Nov 2020 at 13:59, Richard Purdie <richard.purdie@...> wrote:

I've been wondering about this but I suspect we should drop them from
a-full instead...

Sure, I sent a patch for that.

Alex


Richard Purdie
 

On Sun, 2020-11-08 at 14:26 +0100, Alexander Kanavin wrote:
On Sun, 8 Nov 2020 at 13:59, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
I've been wondering about this but I suspect we should drop them
from
a-full instead...
Sure, I sent a patch for that.
I've been thinking about this and the reason I've not done this is
release builds. I'm wondering if we we can somehow make the trigger
release build specific.

I think is is possible to do this, I've pushed in a patch to attempt it
since I'm the one asking for the complication :)

I've tried to reconfig the controller but we'll see whether it works
out or needs a full restart (when no builds are running).

Cheers,

Richard