Hello,
I agree it would be helpful if the test handled this failure condition
with a more informative message.
Thanks,
-Joe
On 6/9/2016 7:31 AM, Roger Riggs wrote:
Hi,
It might be worthwhile to add code to the test to check the GNOME
configuration
and skip the test if incorrect. At the least the failure of the test
could pinpoint the configuration error.
Misconfigured systems will continue to exist and quickly identifying
them would save
time on head scratching.
Roger
On 6/9/2016 3:45 AM, Alan Bateman wrote:
On 09/06/2016 01:26, Rajan Halade wrote:
Thanks Joe! I see only following exception in jtr so it's hard to
know that it is due to machine misconfiguration.
I've looked at the logs and it seems to be an issue with the GNOME
configuration. No issue excluding it for now but we need to track
down this issue
-Alan