gpsd-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gpsd | Pipeline #200139571 has failed for master | 71f2b070


From: Bernd Zeimetz
Subject: Re: gpsd | Pipeline #200139571 has failed for master | 71f2b070
Date: Wed, 14 Oct 2020 20:25:54 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.1


On 10/10/20 12:10 AM, James Browning wrote:

> Specifically no. I would guess that the hardware for the runner is
> underpowered, misutilized, and/or overloaded. Given that GCP and
> presumably as a result GitLab runners now support FreeBSD it might be
> time to move the runner to the cloud. The result would probably be more
> complicated but brisker running. That portion is out of my range. I
> think bzed set it up.

The question is: why is it so slow now?

Looking at the logs this is the case since:

https://gitlab.com/gpsd/gpsd/-/commit/889bd055ea513249f468730579d6eeaef4c51ec9

We have roughly 55399 lines in the regression tests (+- comments, wc -l
fails on binary crap, ....), so:

55399*0.05/60
46.16583333333333333333

Regression tests sleep for 46 minutes...

That is 27 Minutes more than before that change.

Nothing that is fixable with CPU power or whatever else.
Just by fixing the crap that needs WRITE_PAD at all.



Bernd

-- 
 Bernd Zeimetz                            Debian GNU/Linux Developer
 http://bzed.de                                http://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F



reply via email to

[Prev in Thread] Current Thread [Next in Thread]