[JIRA] [acceptance-test-harness] (JENKINS-31357) TestRecorderRule can cause test failures via HeadlessException (on Mac)

[tom.fenne...@gmail.com (JIRA)]

Title: Message Title

Tom FENNELLY commented on JENKINS-31357   Re: TestRecorderRule can cause test failures via HeadlessException (on Mac) Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 62.937 sec <<< FAILURE! - in plugins.WorkflowPluginTest helloWorld(plugins.WorkflowPluginTest) Time elapsed: 62.864 sec <<< ERROR! java.awt.HeadlessException: null at sun.java2d.HeadlessGraphicsEnvironment.getDefaultScreenDevice(HeadlessGraphicsEnvironment.java:77) at org.jenkinsci.test.acceptance.recorder.TestRecorderRule.startRecording(TestRecorderRule.java:66) at org.jenkinsci.test.acceptance.recorder.TestRecorderRule.starting(TestRecorderRule.java:60) at org.junit.rules.TestWatcher.startingQuietly(TestWatcher.java:102) at org.junit.rules.TestWatcher.access$000(TestWatcher.java:46) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:53) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1$2$1.evaluate(JenkinsAcceptanceTestRule.java:162) at org.jenkinsci.test.acceptance.junit.FilterRule$1.evaluate(FilterRule.java:63) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.jenkinsci.test.acceptance.junit.JenkinsAcceptanceTestRule$1.evaluate(JenkinsAcceptanceTestRule.java:60) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:254) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:149) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Looks like it's caused by having -Djava.awt.headless=true set. I could just disable that in this case, but I thought the TestRecorderRule feature was an aid to testing and shouldn't be a reason why the harness would fail. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.