Re: Repetitive "shell submit results failed" errors when running testbot manually
Colin Finck <[email protected]> Wed, 1 Aug 2018 19:09:57 +0200
| Newsgroups | gmane.os.reactos.kernel |
|---|---|
| Message-ID | <[email protected]> |
I have checked the web server and the new "performance" configuration made it consume more RAM than available. This caused some website unavailabilities lately (500/502 error codes), which were also the cause for the failing submissions. I have now reduced the maximum number of simultaneous requests served and restarted the affected components. Everything should be back to normal and hopefully work more reliable in the future. Cheers, Colin Am 01.08.2018 um 18:28 schrieb Hermès BÉLUSCA - MAÏTO: > Hello! > > I repeatedly get an error "shell submit results failed" while trying to > run testbot on a PR patch, see for example > https://build.reactos.org/builders/Test%20KVM/builds/20818 > and as a result I cannot obtain the results under reactos.org/testman . > > Can someone investigate what is going on? > > Regards, > Hermes > > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://www.reactos.org/mailman/listinfo/ros-dev > _______________________________________________ Ros-dev mailing list [email protected] http://www.reactos.org/mailman/listinfo/ros-dev
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJbYelnAAoJEBunTnBFa6GpYzIP/1TWyvP1ZtYnFKv92+JQje1v dBL7tjAV/AIHySNewAskCN7Ws+oqKYBq1/oVMaIBEbDEypf24CTDuUFIvFI2qfjH cbBdIODzSd0rK9ORsjex0dJ1rXQPyI1PZCx1ZFy+2FZ9hrQme4RJygPs4AqD9laQ WX1hEEsBUedEXVtdlojRld2FUPvptQ8+3vivuokFSHNuaVoKXzMQLn7zqDyxh2om FppSwjgLj/csrqBa5S1pw9OUVwPvgec+qpyahmSUJKLQzd8wELFB+DpSvHwERGly FPo1hiRqgMdzvu6V2nvrhdv7z6bWOhLPgEOP2lNyfRw93NY1PaNhOJgCXdQcMjQ8 zhQzXb1+vW/54Dy1M4ZjzNyuYDQSK3Zmb030dO1m8aLubbff3y1IhhkzcZr+zmAj tfv1m48wIxrXywLWZa0iNgoDisNUdmdLYTDxZcqtytlIhkh1Vv6W4asJ2NFpsutM HIOi3wUXDsPkivMT2qVSoeCmXiqxOIBwOisd8GT52sA0PfY8bGIRHA+boQkhN5I1 pbF0Oih7CJb2I4uBuwC6LxCjxpPs0bz9IH1TiKjnDWmoDYameAO2wPI+252VEE33 VGZ7wp0gzqqkVG+XmN3e8UcWO+A/2QC69zvu9VgGKRrC5RMkIrKgFoIlOrML0CNC cZ7Q7IuBH82fsWwgIRO9 =lWAY -----END PGP SIGNATURE-----