Dummy PR to test error reporting after GitHub Actions are enabled

[kevinrushforth]

This PR is intended only for testing purposes to show what will happen after the GitHub Actions build / test runs are enabled in PR #33

In this example I have injected a build failure on Windows and a test failure on Mac. Linux should pass. I'm only interested in how these failures are reported by Skara in this dummy PR.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change must be properly reviewed

Testing

	Linux x64	Windows x64	macOS x64
Build / test	✔️ (1/1 passed)	❌ (1/1 failed)	❌ (1/1 failed)

Failed test tasks

• Windows x64
• macOS x64

Download

$ git fetch https://git.openjdk.java.net/jfx pull/339/head:pull/339
$ git checkout pull/339

[bridgekeeper]

👋 Welcome back kcr! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[kevinrushforth]

The above test results are as expected.

As a possible follow-up RFE it might be helpful if the results showed whether it was the build step or the test step that failed, but it's easy enough to look at the failing workflow and see that, so that can be a future enhancement. We would need to discuss with the Skara folks about what changes would be needed on our end and/or their end.