Tests Failed While Feeling Fabulous

[info] at org.scalatest.tools.Framework$.scala(??) [info] at sbt.ForkMain$Run$.call(ForkMain.java:296) [info] at sbt.ForkMain$Run$.call(ForkMain.java:286) [info] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [info] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:1145) [info] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:615) [info] at java.lang.Thread.run(Thread.java:745) [info] - should return false if jdi loader is not available (2 milliseconds) [info] + assertJavadoc [info] - should throw an assertion error if failed to load jdi (5 milliseconds) [info] - should do nothing if successfully loaded jdi (0 milliseconds) [info] Run completed in 1 second, 953 milliseconds. [info] Total number of tests run: 4 [info] Suites: completed 5, aborted 0 [info] Tests: succeeded 3, failed 1, canceled 0, ignored 0, pending 0 [info] - 1 TEST FAILED - [error] Failed tests: [error] org.senkbeil.debugger.DebuggerSpec [error] [scalaDebuggerApiTest.scala] org.senkbeil.debugger.DebuggerSpec: Tests FailedException: Tests unsuccessful [error] Total time 84 s, completed Oct 7, 2015 10:02:21 PM Exit code: 0 [info] scala-debugger senk$ sbt ++2.11.6 "testOnly org.senkbeil.debugger.DebuggerSpec"; echo "Exit code: $?"

A shirtless man sits in a dramatic chair while a failed Scala test log appears beneath him. The joke contrasts his glamorous, self-satisfied pose with the mundane frustration of one failed test and a nonzero exit code. It is used as a reaction to pretending that a disastrous technical result is still somehow stylish or under control.

• @profunctor_io / 6010 2020-12-18