-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
-
Jenkins: 1.551
Tap: 1.18
The "fail the build if no test results are present" option doesn't fail the job. The tap results file exists and contains a single string (not test results).
TAP Reports Processing: START Looking for TAP results report in workspace using pattern: js_unittest_results.txt Saving reports... Processing '/var/lib/jenkins/jobs/testing/builds/2014-03-18_13-04-29/tap-master-files/js_unittest_results.txt' Parsing TAP test result [/var/lib/jenkins/jobs/testing/builds/2014-03-18_13-04-29/tap-master-files/js_unittest_results.txt]. TAP Reports Processing: FINISH Finished: SUCCESS
[bmannix@glados ~]$ cat /var/lib/jenkins/jobs/testing/builds/2014-03-18_13-04-29/tap-master-files/js_unittest_results.txt
object
EXPECTED BEHAVIOR:
The build fails based on not finding any tap test results.
>EXPECTED BEHAVIOR:
>
>The build fails based on not finding any tap test results.
Righto. So I believe we need to update the documentation.
This option only fails the build if no files are found, matching your glob pattern.
If you configure your job to search for *.t files, and there are no files, and this option has been enabled, then your job will fail. If there any file, even if only several lines with comments, it won't fail the job, since it found a file matching the pattern.