JUnit: include more detailed information about panic

[pohly]

When a test aborts with a panic, the generic information ("Test
Panicked", single source line) is not enough. We also better include
the error that was handed to panic() and a full stacktrace to
determine the root cause.

[pohly]

I'm getting a test failure also without this PR:

[Fail] Flags Specs [It] should run the race detector when told to 
/nvme/gopath/src/github.com/onsi/ginkgo/integration/flags_test.go:110

[pohly]

The https://travis-ci.org/onsi/ginkgo/builds/427319025?utm_source=github_status&utm_medium=notification test run failed because gopkg.in seems to be down (parse https://gopkg.in/yaml.v2?go-get=1: no go-import meta tags) - I just saw that same error in a Kubernetes CI run.

[nodo]

I have restarted the build, let's see if it becomes green.

[nodo]

@pohly do you think you would be able to add a test for the new functionality?

[pohly]

Andrea Nodari <notifications@github.com> writes:

@pohly do you think you would be able to add a test for the new functionality?

Yes, but not this week.

[nodo]

Sure no worries @pohly. Feel free to ping me if you need help.

[pohly]

@node finally got around to extending the tests. I hope this is what you had in mind.

[williammartin]

@nodo Can you review? It seems like you last had context.

[pohly]

@nodo ping

[nodo]

Thanks @pohly ! Looks good to me 👍