On 31/05/2017 13:21, Stefan Schmidt wrote:
Hello.
On 05/29/2017 12:41 PM, Stefan Schmidt wrote:
Hello.
Once again I had problems with the E server being over capacity and
returning 503 when accessing phab.
I often heard claims that the load of Jenkins jobs trigger the bug we
see here. To actually see if the load due to Jenkins jobs is related
to this I now disabled all build triggers on Jenkins. That means no
Jenkins jobs are going to run until I enable these again. be more
careful with your commits.
Right now the last builds are being performed and after that we should
have no new ones.
I will go an re-enable them again if we either see the same server
instabilities without Jenkins running (which proves in my book hat
Jenkins is not the culprit) or in something like 2 or 3 weeks even if
we have no server problems. In the later case we will have to see what
to do.
And phab 503 again. Without any Jenkins jobs running at all. The last
one have been running two days ago.
Beber, you still think Jenkins is to blame?
I will leave it disabled for a few more days to see how that goes.
Yes, this is still my main believe as of today due to qemu layer. We
won't be able to take any conclusion before I've been able to reboot the
physical host after Jenkins build were disabled, this will be done by
tomorrow.
Thanks for disabling the job, that will definitely help to understand
what to blame.
I may be wrong of course, but at least we'll know.
Cheers,
Bertrand
--
Bertrand
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
