-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor
-
Component/s: pipeline-stage-view-plugin
-
None
-
Environment:Jenkins plugin BOM build started Apr 24, 2026, 8:03:27 AM Denver time
https://ci.jenkins.io/job/Tools/job/bom/job/master/6182/
An automated test shows an error in the rendered date logic of the Pipeline stage view plugin during the one hour period after midnight. When the job was run after midnight but before 1:00 AM, the rendered time is displayed as "24:57" instead of "00:57".
The test failure caused a second run of the plugin BOM release build on 24 April 2026, but otherwise it seems like it is a minor bug.
The failing test reports:
Error details:
Rendered time '24:57' should match expected time 00:57 for timezone Australia/Sydney (user a)
Stack trace:
java.lang.AssertionError: Rendered time '24:57' should match expected time 00:57 for timezone Australia/Sydney (user a) at org.junit.Assert.fail(Assert.java:89) at org.junit.Assert.assertTrue(Assert.java:42) at com.cloudbees.workflow.ui.view.WorkflowStageViewActionTest.testTimezoneRespectedInStageStartTime(WorkflowStageViewActionTest.java:174)
Standard output:
=== Starting testTimezoneRespectedInStageStartTime(com.cloudbees.workflow.ui.view.WorkflowStageViewActionTest) Pipeline script for testTimezoneRespectedInStageStartTime(): node { stage ('Build'); sh ('echo Building'); }
Standard error:
0.133 [id=29] INFO o.jvnet.hudson.test.WarExploder#explode: Picking up existing exploded jenkins.war at /home/jenkins/agent/workspace/Tools_bom_master/target/pct-work/pipeline-stage-view-plugin/ui/target/jenkins-for-test 0.508 [id=29] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer2: Running on http://localhost:40589/jenkins/ 0.850 [id=29] INFO jenkins.model.Jenkins#<init>: Starting version 2.561 0.942 [id=44] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 1.422 [id=45] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 1.435 [id=47] INFO j.b.api.BouncyCastlePlugin#start: /home/jenkins/agent/workspace/Tools_bom_master/target/pct-work/pipeline-stage-view-plugin/ui/target/tmp/j h9806664543406497566/plugins/bouncycastle-api/WEB-INF/optional-lib not found; for non RealJenkinsRule this is fine and can be ignored. 2.549 [id=43] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 2.559 [id=44] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins 2.560 [id=44] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions 4.665 [id=47] INFO jenkins.InitReactorRunner$1#onAttained: System config loaded 4.665 [id=42] INFO jenkins.InitReactorRunner$1#onAttained: System config adapted 4.666 [id=42] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 4.667 [id=42] INFO jenkins.InitReactorRunner$1#onAttained: Configuration for all jobs updated 4.799 [id=49] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 5.462 [id=29] WARNING o.o.s.devtools.CdpVersionFinder#findNearestMatch: Unable to find CDP implementation matching 112 5.464 [id=29] WARNING o.o.s.chromium.ChromiumDriver#lambda$new$4: Unable to find version of CDP to use for 112.0.5615.49. You may need to include a dependency on a specific version of the CDP using something similar to `org.seleniumhq.selenium:selenium-devtools-v86:4.28.1` where the version ("v86") matches the version of the chromium-based browser you're using and the version number of the artifact is the same as Selenium's. 11.040 [id=29] INFO hudson.lifecycle.Lifecycle#onStatusUpdate: Stopping Jenkins 11.055 [id=29] INFO hudson.lifecycle.Lifecycle#onStatusUpdate: Jenkins stopped 11.125 [id=29] INFO o.j.h.t.TemporaryDirectoryAllocator#dispose: deleting /home/jenkins/agent/workspace/Tools_bom_master/target/pct-work/pipeline-stage-view-plugin/ui/target/tmp/j h9806664543406497566
The test failure screenshot:
