Hi,
I checked a little with the inspector, and AFAICT the values were
correctly added to the API parameters, so the likely error location is on
the other side, on the server side, in the plugin.
I probably won't be able to change the script for some hours, since the
file needs to be reloaded, which means restarting the buildbot.
On Wed, 13 Jan 2021 12:33:02 +0100, Pierre Tardy <tar...@gmail.com> wrote:
I am not sure why this wouldn't work. I vaguely recall there was an issue
there, but can't figure it out staring at the code.
As this is quite ancient, I am not sure the JS part will even build
anymore
:-/
You can change the default values at that line in the python
https://github.com/tardyp/buildbot_profiler/blob/master/buildbot_profiler/api.py#L193
I think you will be able to force them by editing this file inside your
virtualenv..
Regards
Pierre
Le mer. 13 janv. 2021 à 11:46, Yngve N. Pettersen <yn...@vivaldi.com> a
écrit :
> I insist on the buildbot profiler. What I was saying before is that
you
> need to hit the record button before the problem appears, and put a
large
> enough record time to be sure to catch a spike.
> Then, you will be able to zoom to the cpu spike and catch the issue
> precisely.
>
> If the spike is in the order of minutes like you said, you can
configure
> it
> like this and get enough samples to get enough evidence to where the
code
> is actually spending time:
>
> ProfilerService(frequency=500, gatherperiod=60 * 60, mode='virtual',
> basepath=None, wantBuilds=100
I tried configuring this with the settings dropdown in the WebGUI
plugin,
but AFAICT it is not working, it only gathers info for 30 seconds.
I guess I must be holding it incorrectly.
> This will record for one hour, and mitigate the memory used if you
worry
> about it.
--
Sincerely,
Yngve N. Pettersen
Vivaldi Technologies AS
--
Sincerely,
Yngve N. Pettersen
Vivaldi Technologies AS
_______________________________________________
users mailing list
users@buildbot.net
https://lists.buildbot.net/mailman/listinfo/users
