Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a job in Jenkins that it testing nunit tests for a project. The Jenkins job fails, although all the unit tests pass.
So on Jenkins it says the build fails – but test results show no failures.
I cannot seem to figure out what is causing the job to fail. Is there some sort of way to see what causes a Jenkins job to be marked as fail? i.e. a detailed log file for a job or something? Any suggestions would be much appreciated.
Have you checked the Console Output for the failed job?
That said, errors in the Console Output can be hard to find, and then harder to understand. Sometimes I need to log in/remote to the build machine and build the solution, or run the unit tests, manually to see the error in an uncluttered, non-abstracted way (i.e., in the VisualStudio IDE or the NUnit GUI).
Oh, and the Log Parser Plugin makes finding errors in Jenkins much easier.