Last modified: 2014-02-20 13:18:07 UTC
jenkins not responding (at least for operations/apache-config) see recheck @ https://gerrit.wikimedia.org/r/101220 (12-27 18:27) didn't respond to that nor to the newer patchsets
The job operations-apache-config-lint execute PHP code and is thus in the 'test' pipeline. That one only execute jobs for trusted users and does not let you use the 'recheck' keyboard. One has to either forge anew patchset or hit +2 to get the tests to run.
(In reply to comment #1) > The job operations-apache-config-lint execute PHP code and is thus in the > 'test' pipeline. That one only execute jobs for trusted users and does not > let > you use the 'recheck' keyboard. That seems unreasonable. Is there any php run besides the one redirects.conf generator? that script should probably change <1x/month. You can just assume it's safe if the script is unchanged from the version in the current HEAD. Also, jenkins has gotten stuck before and will probably get stuck again; how is one supposed to find out why the bot's not running? (i.e. differentiate between the possible reasons: high load/big queue, jenkins completely borked, i'm not trusted) > One has to either forge anew patchset or hit +2 to get the tests to run. One==One in the set of trusted? Apparently editing the commit msg via web UI is sufficient? (which you did and then the bot spoke/voted)
Will be fixed whenever we get rid of the check/test pipelines which would be the case when we run tests in isolated environments. See bug 45499
