-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
None
-
Jenkins 2.214
Warnings-NG 7.3
Java 1.8.0_222
We are using Warnings-NG to collect warnings for cppcheck, clang and msbuild.
Sometimes there are new warnings reported for a build, but when trying to check them using the warnings detail view, the warnings are simply not loading.
This has occured with both MacOS and Windows and Firefox, Chrome or Safari.
However it did not occur at the same time, so we encountered situations where the warnings would not load using Safari on MacOS but did load with Firefox on Windows.
Sometimes a restart of jenkins helped, sometimes it didn't. In general the problem just dissapeared after some while, it happens very unregularly.
I read that this warnings-details view is loaded using ajax, so i checked the browser developer console for messages, but i could not find anything that seemed to be related to the problem.
Are there some other ways of identifying or debugging the problem when it occurs? If so, i am happy to collect more information on the problem!
- is duplicated by
-
-
- Resolved
-
[JENKINS-60810] Detail view sometimes not loading
Thanks for adding the details. Maybe it makes sense to retry after such a failure.
Stephan Vallant
added a comment - If that would have helped, i wouldn't even bothered to create a issue here.
The problem occurs at random times on both macos and win, on all browsers, for random projects and random builds, which makes it really hard to pin down.
But once it has occured, it usually stays around for that particular build. Looking at other Issue details usually still works, only the currently failing one keeps failing.
We require "no new warnings" as quality gate for pull requests, so looking at newly introduced warnings is quite important in the process- up until now our workaround was to ask a collegue to open the page.
Could it be a nginx configuration problem?
Stephan Vallant
added a comment - If that would have helped, i wouldn't even bothered to create a issue here.
The problem occurs at random times on both macos and win, on all browsers, for random projects and random builds, which makes it really hard to pin down.
But once it has occured, it usually stays around for that particular build. Looking at other Issue details usually still works, only the currently failing one keeps failing.
We require "no new warnings" as quality gate for pull requests, so looking at newly introduced warnings is quite important in the process- up until now our workaround was to ask a collegue to open the page.
Could it be a nginx configuration problem? I really have no idea. Ajax in Jenkins is something that is totally hidden in the API so I have no clue where to start.
Stephan Vallant
added a comment - I just checked, nothing shows up in the jenkins server logs either... any other idea where information could be hidden?
Stephan Vallant
added a comment - I just checked, nothing shows up in the jenkins server logs either... any other idea where information could be hidden? Stephan Vallant
added a comment - This issue occurs on our team on a regular basis now, again across browsers and operating systems... Also across jenkins + plugin versions.
Are we really the only ones experiencing this?
Stephan Vallant
added a comment - This issue occurs on our team on a regular basis now, again across browsers and operating systems... Also across jenkins + plugin versions.
Are we really the only ones experiencing this? Even with the newest version of the plugin we still experience this problem...
However maybe i've found a lead, i've noticed some errors popping up in the console (see screenshots error1 - error5).
Is this something you can maybe work with?
Stephan Vallant
added a comment - - edited Even with the newest version of the plugin we still experience this problem...
However maybe i've found a lead, i've noticed some errors popping up in the console (see screenshots error1 - error5).
Is this something you can maybe work with? 
So i further investigated this issue and tracked down the failing request.
When i am looking at the issues of a particular build (so e.g. the msbuild warnings), there is a table with DOM-id "issues".
The page then makes a request to
<jenkins-url>/$stapler/bound/<random-string>/getTableModel.
It seems like while this works most of the time, sometimes the request runs into a timeout and the connection is ended with a 500 internal server error.
I've seen in the github codebase that the there is a corresponding method in the IssuesDetail.java class, however i do not understand the code enough to point to any place the error could lay.
I attached a small log captured via firefox of an instance where the issues were not loading. Looking at the network timing it seems like the connection just ran into a timeout.