On Thu, 21 Feb 2019 at 20:03, Milosz Wasilewski < milosz.wasilewski@linaro.org> wrote:
Hi Axel,
The workerlosterror should usually be temporary. We're also getting them from time to time. In our case worker runs out of memory and crashes. After it's restarted it tries the same task again. So if your worker always crashes on the same task (which might be the case) it will cause symptoms as you describe. In this case it's best yo upgrade as 0.62 contains memory consumption fixes.
Hi Milosz,
thank you for your response. We upgraded to 0.62 and now it seems to work so I guess it was related to memory leaks too.
Regards, Axel
P.s. sorry for top posting. I'm replying from my mobile.
Milosz
On Wed, Feb 20, 2019, 17:06 Axel Lebourhis <axel.lebourhis@linaro.org wrote:
Well, I upgraded to 0.62.1 and now it's working fine.
Sorry for bothering.
Regards, Axel
On Wed, 20 Feb 2019 at 16:05, Axel Lebourhis axel.lebourhis@linaro.org wrote:
Hi all,
After looking to squad-worker's log, I can see it reports "WorkerLostError". On the web ui, the last build on project summary page is not updated with last test results, but these results are visible if we click on
this
build. Moreover, the build is still on "unfinished" state while there is no
test
running, and it gives no reason about why the build is considered unfinished.
Is it possible the build is not updated because of the worker facing errors ?
You can see the worker's log in attachment.
Best regards, Axel
Squad-dev mailing list Squad-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/squad-dev