When viewing the Run Details logs for a running build, when a user scrolls up, the system stops loading logs entirely. This obviously prevents any karaoke behavior from occurring. It appears that when the build completes, we do refresh the data and logs to reflect the completed state.
I have tested this in the following commits and the behavior seems consistent:
- Just prior to mobx karaoke PR - https://github.com/jenkinsci/blueocean-plugin/commit/7adb6826eaeb903fcd2c47e7317c38d1e25bd885
- After mobx karaoke PR - https://github.com/jenkinsci/blueocean-plugin/commit/e8c0f65d888a03385ea9f4d62c166f016755b512
- After my recent karaoke bug fix - https://github.com/jenkinsci/blueocean-plugin/commit/7987f58dcfdc309b3f89bc6c0f5cd0326adaee65
There seems to be some debate as to what the behavior should be. Thorsten Scherler indicated it's always worked this way, although James Dumay says that log loading should continue regardless, just no auto scrolling / auto stage moving.
Before I dig deeper into JENKINS-43316 and JENKINS-43317 it'd help to know whether this issue needs addressing. And if it's true that karaoke has always worked like this, this should be marked as an enhancement and probably not block 1.1 release as it may take some time to implement this from scratch. I don't know the code base well enough to estimate the effort.