I also stumbled over (something like) this for "Tests" as well as for "Changes" tab (using the Firefox browser normally – although not sure if that has any relevance though):

• And it seems to be related to opening the latest/newest Blue Ocean pipeline execution in a new browser tab from the pipeline's activity view (that lists all pipeline executions)

Typical occurrence example:

• A pipeline execution was triggered by SVN post commit hook, but in "Changes" tab Blue Ocean claims "there are no changes", e.g.:
• But obiously there must have been changes (cf. SVN post commit hook)
• => I then press <ESC> to go to the pipeline's activity view (that is listing all pipeline executions) and re-enter the same pipeline execution (still in the same browser tab!), then it shows the changes, e.g.:

I updated to Blue Ocean (1.7.2) and the issue doesn't occur anymore. I'm not sure if 1.6 or 1.7.x fixed it.

I just re-tested based on my aforementioned reproducer comment (https://issues.jenkins-ci.org/browse/JENKINS-51111?focusedCommentId=343321&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-343321) and the problem is still there for me in Blue Ocean 1.7.2! (Please mind that Jenkins core and plugin updates from last 3 weeks are yet missing, thus still using Jenkins 2.136; not sure if this is relevant at all.)

woolzer Can you try this as well? (I hope the steps to reproduce are understandable)

I claim JENKINS-55497 solved this issue

(I hope nobody minds my/this "Resolve")

I don't believe my change would have fixed this issue. It sounds like a similar bug though (retrieving and caching the run summary for the last run of a project leads to false cache hit when retrieving the full details for the same run). This code snippet looks suspicious:

https://github.com/jenkinsci/blueocean-plugin/blob/3f049df3d253727d021e95ee53a4d1be228bf8cf/blueocean-rest-impl/src/main/java/io/jenkins/blueocean/service/embedded/rest/AbstractPipelineImpl.java#L106

halkeye could you take a look / comment on this?

stuartrowe I'm confused by your comment. Sounds like you suspect its not fixed, but reinholdfuereder says it is actually fixed for them?

I agree, the null looks suspicious, but the PR it was merged in with (https://github.com/jenkinsci/blueocean-plugin/commit/1e05a5cf487cdb85112cbbb61d6ebf1f9cb889b4) says it was done for performance issues.

I think a longer term better fix is making the tests page pull the data it needs if its not available, but i'm way less familiar with the actual frontend code here.

I'm just saying that if it is fixed, it's not due to my PR. I looped you in in case there were any other recent BO changes that came to mind. I don't have jobs that produce xUnit style output so I haven't noticed this issue and can't confirm a fix.

Okay cool, I agree, i don't think its related to your change, but its a complicated system so who knows.

I'm leaving this as resolved! 

stuartrowe and halkeye: Sorry for the confusion. I am really extremely pretty sure that the problem I described in https://issues.jenkins-ci.org/browse/JENKINS-51111?focusedCommentId=343321&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-343321 (with rather straightforward reproducer steps) works now as expected (for "changes" AND for "tests") – and I think that was really the same problem as this issue's original description.

However, I could also imagine that stuartrowe is perfectly right about that he only fixed the "changes" now in the course of JENKINS-55497, and "tests" was already fixed some time ago...