-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Linux Ubuntu 17
Debian 9
Jenkins Core: 2.89
JDK 1.8
As far as I see JENKINS-21905 was merged recently and in some cases I'm able to get a broken test case.
Test case: hudson.tasks.ArtifactArchiverTest#archiveNotReadable
It gets a SUCCESS build execution when it's expected a build failure:
09:45:30 [INFO] Running hudson.tasks.ArtifactArchiverTest 09:45:31 === Starting archiveNotReadable(hudson.tasks.ArtifactArchiverTest) 09:45:31 0.057 [id=14] INFO o.jvnet.hudson.test.WarExploder#explode: Using jenkins.war resources from /jenkins/workspace/jenkins-builder-GVUXEVO4UDB56JVJCAIIOJABEOBWF4DGQDPTOFAZO2HE2TBCT27Q/war/target/jenkins 09:45:32 0.316 [id=14] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: Running on http://localhost:45817/jenkins/ 09:45:32 0.765 [id=21] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 09:45:32 0.818 [id=24] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 09:45:34 2.437 [id=22] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 09:45:34 2.438 [id=22] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins 09:45:34 2.442 [id=21] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions 09:45:35 3.359 [id=21] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 09:45:35 3.620 [id=20] WARNING j.s.DeprecatedAgentProtocolMonitor#initializerCheck: This Jenkins instance uses deprecated Remoting protocols: CLI-connect,CLI2-connect,JNLP-connect,JNLP2-connectIt may impact stability of the instance. If newer protocol versions are supported by all system components (agents, CLI and other clients), it is highly recommended to disable the deprecated protocols. 09:45:35 3.624 [id=26] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 09:45:37 5.660 [id=45] INFO o.j.h.test.SimpleCommandLauncher#launch: agent launched for slave0 09:45:37 6.226 [id=55] INFO hudson.model.Run#execute: test0 #1 main build action completed: SUCCESS 09:45:38 6.887 [id=14] INFO jenkins.model.Jenkins#cleanUp: Stopping Jenkins 09:45:38 6.948 [id=14] INFO jenkins.model.Jenkins#cleanUp: Jenkins stopped 09:45:38 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 7.93 s <<< FAILURE! - in hudson.tasks.ArtifactArchiverTest 09:45:38 [ERROR] archiveNotReadable(hudson.tasks.ArtifactArchiverTest) Time elapsed: 7.144 s <<< FAILURE! 09:45:38 java.lang.AssertionError: 09:45:38 unexpected build status; build log was: 09:45:38 ------ 09:45:38 Legacy code started this job. No cause information is available 09:45:38 Building remotely on slave0 (target) in workspace /jenkins/workspace/jenkins-builder-GVUXEVO4UDB56JVJCAIIOJABEOBWF4DGQDPTOFAZO2HE2TBCT27Q/test/target/jenkinsTests.tmp/jenkins3916932103566556864test/workspace/test0 09:45:38 Archiving artifacts 09:45:38 Finished: SUCCESS
You can reproduce it locally if you follow the steps explained below:
Although I have not seen that particular test failure in the ci.jenkins.io instance, but It seems to be failing when using ephemeral containers either using Mesos or EC2 in my CI ecosystem. I thought it was just something in my CI system, but I'm certainly worry about this since I can reproduce it locally when using VirtualBox under my MacOSX. That's the reason of raising this ticket.
Apparently: https://github.com/jenkinsci/jenkins/commit/efbdac0f76378105d4b2ada8d9b639b65a41cf3b#diff-8132040eed500f670dcfaa61bb58eb91R323 does not behave as expected when running in a virtualbox with docker than when running natively and locally or in other kind of infra.
Any ideas?
Please let me know if you need further details.
- links to
