Nightly build failures

[Kirk Lund <kl...@apache.org>]

I'm looking at Geode Nightly Build #724. The console output shows
that MemoryThresholdsOffHeapDUnitTest, however the Test Results shows zero
failures.

The failure in the console output does not show the full stack so there's
no way to determine which assertion failed.

#724 console output shows failure in MemoryThresholdsOffHeapDUnitTest:
https://builds.apache.org/job/Geode-nightly/724/console

#724 test results shows zero failures:
https://builds.apache.org/job/Geode-nightly/724/testReport/

Why are these two screens so out of sync with each other for #724? Anyone
know how to get the full stack trace for the assertion failure (I can't do
anything without that)?

Re: Nightly build failures

[Kirk Lund <kl...@apache.org>]

If the Geode Nightly Build is running FlakyTests but not adding those
results to the Test Results, then I'm 100% for removing the execution of
FlakyTests from the nightly build job.

If others want the nightly build to run FlakyTests, then would someone
please add it to the Test Results so we can see the full stack trace when a
FlakyTest fails.


On Mon, Jan 23, 2017 at 10:52 AM, Kirk Lund <kl...@apache.org> wrote:

> I'm looking at Geode Nightly Build #724. The console output shows that
> MemoryThresholdsOffHeapDUnitTest, however the Test Results shows zero
> failures.
>
> The failure in the console output does not show the full stack so there's
> no way to determine which assertion failed.
>
> #724 console output shows failure in MemoryThresholdsOffHeapDUnitTest:
> https://builds.apache.org/job/Geode-nightly/724/console
>
> #724 test results shows zero failures:
> https://builds.apache.org/job/Geode-nightly/724/testReport/
>
> Why are these two screens so out of sync with each other for #724? Anyone
> know how to get the full stack trace for the assertion failure (I can't do
> anything without that)?
>
>