06:31 <borneoa_> karlp: yes, you can silence some of the messages from checkpatch adding one line in the commit message. It's explained in HACKING

09:40 <karlp> can we make gerrit keep credentials longer please?

09:58 <karlp> why does gerrit say that a patch is in state "my turn" on the dashboard?

09:58 <karlp> I made a comment, it's been addressed, what is it expecting me to do that makes it "my turn" ?

10:54 <PaulFertser> The "turn" isn't really important, it just keeps track of unresolved comments or some such.

10:54 <PaulFertser> karlp: what inactivity timeout do you think is reasonable?

10:55 <karlp> at least 48hours.

10:55 <karlp> as for "turn" it's highlighting yellow a bunch of things as "you need to give attention to these" and I can't wokr out how to clear it

10:56 <karlp> so just "this is the gerrrit way" then I guess.

10:56 <PaulFertser> I hope borneoa_ can explain.

10:59 <PaulFertser> Currently it's not set so should be default of 12 hours.

11:03 <Haohmaru> what happens when those 12 hours pass? punishment?

11:04 <Xogium> tbh the way it says it, it's your turn, sounds like a game

11:04 <borneoa_> Sorry, explain what? The yellow 'your turn' stuff? I have no idea and I use a custom dashboard that doesn't show it. Maybe I should go back and check it...

11:04 <Haohmaru> hahah

11:04 <Haohmaru> white horse on D5

11:05 <Xogium> :D

11:05 <PaulFertser> borneoa_: what's your opinion on web session inactivity timeout? Do you agree it makes sense to make it 48 hours instead of 12?

11:06 <Haohmaru> make it 72, so it catches the weekend ;P~

11:07 <Xogium> :p

11:10 <borneoa_> PaulFertser: regarding inactivity. I noticed that when it's running some Jenkins build the Gerrit web server becomes unresponsive. Often the web server looses connection with some service that tracks the user id and claims the session is expired and need login again. But login doesn't work for such irresponsible status. After a while when everything returns ok, login works, but just a page refresh is enough to be back with

11:10 <borneoa_> previous login.

11:11 <borneoa_> PaulFertser: I think that the VM that runs gerrit gets overloaded by jenkins

11:11 <borneoa_> PaulFertser: is it possiyto decouple them or assign low priority to Jenkins?

11:13 <karlp> I'd personally like to stay logged in until I log out, gerrit's hardly the sort of thing I'm going to be using on a kiosk somewhere, but I fine with it being "less"

11:13 <karlp> but every day is tedious, especially when gerrit's slow.

11:14 <borneoa_> PaulFertser: then, for the session timeout I'm ok to extend it even to one week or disable it completely. I don't see issues. But for me the annoying stuff is not the timeout but the fake logout caused by Gerrit server being not responsive

11:18 <borneoa_> PaulFertser: I haven't checked if it's systematic, but when I merge a series of patches, the first goes fine, the second causes timeout. I suspect the first merge causes Jenkins to queue scan-build job. After a while everything returns normal and I can go ahead with the other patches in the series with Al ost no issues.

11:23 <PaulFertser> borneoa_: I'll recheck but I thought jenkins jobs are already niced.

11:24 <PaulFertser> Probably there's an issue with parallel builds, something like both active builds get -j$(nproc) at the same time, not sure yet.

11:26 <borneoa_> PaulFertser: I need to copy the error next time I get it. I remember was some internal server not responding. Could even be due to some limit in network usage?

11:27 <PaulFertser> borneoa_: probably it's nginx not being able to contact Gerrit process when everything's slow. Making that timeout bigger makes sense too.

13:02 <borneoa_> PaulFertser: for me it's not the web credential timeout that is expired, but the Gerrit UI that is unable to verify if the credentials are still valid. Without answer from the credentials service it assumes the credentials are expired. But then you cannot enter the credentials again because every is locked. When the UI returns responsive, no need to login again as is enough to refresh the page and go ahead with the old

13:02 <borneoa_> credentials.