Faulty feedback on jenkins
See original GitHub issueIch bin mir nicht sicher ob https://github.com/ls1intum/Artemis/issues/2169 mit folgendem Fehler zu tun hat aber ich schreib es mal hier rein:
Auf Produktion läuft https://github.com/ls1intum/Artemis/issues/2169 rebased auf develop, zusammen mit anderen nicht zusammenhängenden benutzerdifinierten Änderungen. Es gibt jetzt eine Aufgabe dort benutzen wir in den Tests die Klasse BehaviorTest, um dem Studenten sinnvolles Feedback zu geben, falls eine Klasse fehlt o.ä.
In dem folgendem Beispiel hat jemand die Main Methode Groß statt klein geschrieben: Der Jenkins output ist:
Downloaded from central: https://repo.maven.apache.org/maven2/org/junit/platform/junit-platform-launcher/1.3.2/junit-platform-launcher-1.3.2.jar (95 kB at 1.6 MB/s)
2020-11-05T13:09:47+01 Downloaded from central: https://repo.maven.apache.org/maven2/org/junit/platform/junit-platform-engine/1.3.2/junit-platform-engine-1.3.2.jar (138 kB at 2.2 MB/s)
2020-11-05T13:09:47+01 [INFO]
2020-11-05T13:09:47+01 [INFO] -------------------------------------------------------
2020-11-05T13:09:47+01 [INFO] T E S T S
2020-11-05T13:09:47+01 [INFO] -------------------------------------------------------
2020-11-05T13:09:47+01 [ERROR] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/var/jenkins_home/workspace/ALPROSTRINGCON/ALPROSTRINGCON-S6FEALCA@tmp/withMavenadc4f557/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/var/jenkins_home/workspace/ALPROSTRINGCON/ALPROSTRINGCON-S6FEALCA@tmp/withMavenadc4f557"
2020-11-05T13:09:47+01 [INFO] Running MainTest
2020-11-05T13:09:47+01 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.066 s <<< FAILURE! - in MainTest
2020-11-05T13:09:47+01 [ERROR] MainTest.testOutput Time elapsed: 0.043 s <<< FAILURE!
2020-11-05T13:09:47+01 org.opentest4j.AssertionFailedError: Could not find the method 'main' with the parameters: [ String[] ] in the class Main because the method does not exist. Make sure to implement this method properly.
2020-11-05T13:09:47+01 at MainTest.testOutput(MainTest.java:31)
2020-11-05T13:09:47+01
2020-11-05T13:09:47+01 [INFO]
2020-11-05T13:09:47+01 [INFO] Results:
2020-11-05T13:09:47+01 [INFO]
2020-11-05T13:09:47+01 [ERROR] Failures:
2020-11-05T13:09:47+01 [ERROR] MainTest.testOutput:31->BehaviorTest.invokeMethod:261->BehaviorTest.getMethod:168->BehaviorTest.getMethod:189 Could not find the method 'main' with the parameters: [ String[] ] in the class Main because the method does not exist. Make sure to implement this method properly.
2020-11-05T13:09:47+01 [INFO]
2020-11-05T13:09:47+01 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
2020-11-05T13:09:47+01 [INFO]
2020-11-05T13:09:47+01 [INFO] ------------------------------------------------------------------------
2020-11-05T13:09:47+01 [INFO] BUILD FAILURE
2020-11-05T13:09:47+01 [INFO] ------------------------------------------------------------------------
2020-11-05T13:09:47+01 [INFO] Total time: 10.176 s
2020-11-05T13:09:47+01 [INFO] Finished at: 2020-11-05T12:09:47Z
2020-11-05T13:09:47+01 [INFO] ------------------------------------------------------------------------
2020-11-05T13:09:47+01 [INFO] [jenkins-event-spy] Generated /var/jenkins_home/workspace/ALPROSTRINGCON/ALPROSTRINGCON-S6FEALCA@tmp/withMavenadc4f557/maven-spy-20201105-120937-450269038662599953396.log
2020-11-05T13:09:47+01 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on project String-konkatinieren-Tests: There are test failures.
2020-11-05T13:09:47+01 [ERROR]
2020-11-05T13:09:47+01 [ERROR] Please refer to /var/jenkins_home/workspace/ALPROSTRINGCON/ALPROSTRINGCON-S6FEALCA/target/surefire-reports for the individual test results.
2020-11-05T13:09:47+01 [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
2020-11-05T13:09:47+01 [ERROR] -> [Help 1]
2020-11-05T13:09:47+01 [ERROR]
2020-11-05T13:09:47+01 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
2020-11-05T13:09:47+01 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
2020-11-05T13:09:47+01 [ERROR]
2020-11-05T13:09:47+01 [ERROR] For more information about the errors and possible solutions, please read the following articles:
2020-11-05T13:09:47+01 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
Ich würde als Feedback erwarten:
Could not find the method 'main' with the parameters: [ String[] ] in the class Main because the method does not exist. Make sure to
Statt dem Namen der Excpetion.
Selbiges gilt für alle anderen Assertions:
2020-11-05T13:03:48+01 [ERROR] Picked up JAVA_TOOL_OPTIONS: -Dmaven.ext.class.path="/var/jenkins_home/workspace/ALPROSTRINGCON/ALPROSTRINGCON-DATHEN@tmp/withMaven186a8fb5/pipeline-maven-spy.jar" -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/var/jenkins_home/workspace/ALPROSTRINGCON/ALPROSTRINGCON-DATHEN@tmp/withMaven186a8fb5"
2020-11-05T13:03:48+01 [INFO] Running MainTest
2020-11-05T13:03:48+01 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.086 s <<< FAILURE! - in MainTest
2020-11-05T13:03:48+01 [ERROR] MainTest.testOutput Time elapsed: 0.064 s <<< FAILURE!
2020-11-05T13:03:48+01 org.opentest4j.AssertionFailedError: Nachricht enthält nicht hallo ==> expected: <true> but was: <false>
2020-11-05T13:03:48+01 at MainTest.testOutput(MainTest.java:34)
2020-11-05T13:03:48+01
2020-11-05T13:03:48+01 [INFO]
2020-11-05T13:03:48+01 [INFO] Results:
2020-11-05T13:03:48+01 [INFO]
2020-11-05T13:03:48+01 [ERROR] Failures:
2020-11-05T13:03:48+01 [ERROR] MainTest.testOutput:34 Nachricht enthält nicht hallo ==> expected: <true> but was: <false>
2020-11-05T13:03:48+01 [INFO]
2020-11-05T13:03:48+01 [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
Also Feedback gibt es:
Wie könnte ich dies debuggen? Gibt es neulich Änderungen, die dies verursachen könnten.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top GitHub Comments
Updating the jenkins plugin to version 1.2.0 fixed it
Sorry for the trouble, I guess we should have communicated this better, that the new version is needed