On Mittwoch, 20. September 2023 13:04:00 CEST Ben Cooksley wrote:
> > = FAILING UNIT TESTS =
> >
> > konsole: (2nd week)
> >
> > * https://invent.kde.org/utilities/konsole/-/pipelines/484169
> >
> > * freebsd_qt515 tests are failing
>
> Sysadmin has been asked to take a look into this one, as by all accounts
> there is no reason for this to suddenly start failing out of the blue with
> no changes in Konsole itself.
> I'm suspecting regressions within either our FreeBSD setup, or somewhere in
> Frameworks (KParts specifically) at the moment.
I'm fixing the tests for Cantor now which started to fail after I pushed a
change to master that is not related to the failing tests now. The tests are
not stable against different timings and the async. communication with the
external process needs to be handled better. So, I assume something was
changed for the freeBSD setup that affects the performance and the timings
during the test executions. Maybe newer or older hardware in use?
Likely it relates to the load on the underlying CI worker node at the time the job is being run. There is no guarantee you're the only job running at the time as Linux or Windows could be running jobs (or they both could be) and if they're both running that will definitely impair FreeBSD performance. For most unit tests they're not load/performance sensitive so this isn't an issue.
All of the mainline Linux/FreeBSD/Windows/Android jobs provided by Sysadmin run on AMD Ryzen 7 7700 machines, with NVMe storage and plenty of RAM (the host machines have either 64GB or 128GB depending on the physical node, although the FreeBSD nodes only have 16GB allocated to them) so there is certainly no hardware limitations or age issues here.
Regards,
Alexander
Cheers,
Ben