-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
Platform: HP, OS: Linux
A Maven 2 Job fails with tests:
Tests run: 6, Failures: 1, Errors: 0, Skipped: 0
But reports the job as a success, not unstable.
Hudson 1.3.17 was OK, I am seeing this issue with Hudson 1.319. I am unable to
test or revert back to Hudson 1.317 or 1.318 as I get the following Hudson
Exception for all jobs:
A timer trigger started this job
Building on master
FATAL: hudson.model.AbstractProject.getWorkspace()Lhudson/FilePath;
java.lang.AbstractMethodError:
hudson.model.AbstractProject.getWorkspace()Lhudson/FilePath;
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:264)
at hudson.model.Run.run(Run.java:949)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:301)
at hudson.model.ResourceController.execute(ResourceController.java:93)
at hudson.model.Executor.run(Executor.java:116)
Thanks.
- duplicates
-
JENKINS-4177 Failing tests do not make a build unstable
- Closed