-
Bug
-
Resolution: Unresolved
-
Major
-
None
Since the last update the periodic refresh has started causing the wall display to flicker, showing "loading jobs..." every 60 seconds (or whatever I set the refresh rate to be).
It used to work beautifully!
[JENKINS-23620] The periodic refresh shows "loading jobs.."
Jens-Martin Groenne
added a comment - We are seeing the same problems, occurs in all browsers. 
Arran
added a comment - My analysis of the issue is the problem started here (with the help of git bisect):
https://github.com/jenkinsci/walldisplay-plugin/commit/69e9fe2e26fd6559ea5b6b5b313dfbcf07fd0305
So 0.6.25
It appears to occur when the repaint interval is set to less than the update interval, so sometimes the plugin can be unlucky and the update & it's various API requests haven't finished by the time the repaint comes along to redraw everything.
Arran
added a comment - My analysis of the issue is the problem started here (with the help of git bisect):
https://github.com/jenkinsci/walldisplay-plugin/commit/69e9fe2e26fd6559ea5b6b5b313dfbcf07fd0305
So 0.6.25
It appears to occur when the repaint interval is set to less than the update interval, so sometimes the plugin can be unlucky and the update & it's various API requests haven't finished by the time the repaint comes along to redraw everything. 
Lars Hagström
added a comment - No, that doesnt do it for me 
For example I set the update interval to 30 and the paint interval to 60, and that still causes occasional flashes (not quite as frequent, though).
My best workaround is still commenting out the "Loading jobs..." line in walldisplay.js...
Lars Hagström
added a comment - No, that doesnt do it for me
For example I set the update interval to 30 and the paint interval to 60, and that still causes occasional flashes (not quite as frequent, though).
My best workaround is still commenting out the "Loading jobs..." line in walldisplay.js... Arran
added a comment - On a second attempt, moving from setInterval to a recursive setTimeout doesn't fully remove the issue but does help the issue a lot.
Arran
added a comment - On a second attempt, moving from setInterval to a recursive setTimeout doesn't fully remove the issue but does help the issue a lot. Lars Hagström
added a comment - If I have my update interval set to 30 and the paint interval to 60 I don't get any flashes any longer. But the walldisplay takes a very long time to get started when I load the web page. It sometimes takes as long as 30 minutes!
Lars Hagström
added a comment - If I have my update interval set to 30 and the paint interval to 60 I don't get any flashes any longer. But the walldisplay takes a very long time to get started when I load the web page. It sometimes takes as long as 30 minutes! Code changed in jenkins
User: dvelderp
Path:
src/main/webapp/walldisplay.css
src/main/webapp/walldisplay.html
src/main/webapp/walldisplay.js
http://jenkins-ci.org/commit/walldisplay-plugin/915214c9d5109c82d3782f627ba81c021c07e1c4
Log:
JENKINS-23620 Screen repaint without disturbing glitches
Code changed in jenkins
User: Pelle Pelster
Path:
src/main/webapp/walldisplay.css
src/main/webapp/walldisplay.html
src/main/webapp/walldisplay.js
http://jenkins-ci.org/commit/walldisplay-plugin/a2874733c0771ee8a661a71d5671b3a9288ca562
Log:
Merge pull request #38 from pvelder/master
JENKINS-23620 Screen repaint without disturbing glitches
Compare: https://github.com/jenkinsci/walldisplay-plugin/compare/569cdfe069ab...a2874733c077
Code changed in jenkins
User: dvelderp
Path:
src/main/webapp/walldisplay.js
http://jenkins-ci.org/commit/walldisplay-plugin/f6be12fe459d214759694c11f8f6fe13c193c2a0
Log:
JENKINS-23620 Fix job display distorted when multiple column display
Code changed in jenkins
User: Pelle Pelster
Path:
src/main/webapp/walldisplay.js
http://jenkins-ci.org/commit/walldisplay-plugin/5c3e5b143126188b3c75a1a2a5fa32fd559e38f2
Log:
Merge pull request #39 from pvelder/master
JENKINS-23620 Fix job display distorted when multiple column display
Compare: https://github.com/jenkinsci/walldisplay-plugin/compare/a2874733c077...5c3e5b143126
I was suffering from this bug, I had to go back to 0.6.21.