Issue #6510 has been updated by James Turnbull. Target version deleted (queued)
---------------------------------------- Bug #6510: Using --stdout-only mode obscures error repoting https://projects.puppetlabs.com/issues/6510 Author: Dominic Maraglia Status: Unreviewed Priority: Normal Assignee: Nick Lewis Category: Harness Target version: Patch: None Keywords: errored log.rb quirt failure Branch: The test harness halts on fatal errors in test code; unfortunately, the harness does not print out the error in stdout/stderr when running in --stdout-only. Running a broken test, results echoed to stdout do not display the Ruby error. This appears to happen in lib/log.rb <pre> /systest.rb -c tmp --type skip -t tests/acceptance/cfg_file_test.rb -s --debug tests/acceptance/cfg_file_test.rb errored </pre> Running the same code, but sending results to a log files results in: <pre> Test Case tests/acceptance/cfg_file_test.rb reported: #<SyntaxError: compile error tests/acceptance/cfg_file_test.rb:29: syntax error, unexpected tIDENTIFIER, expecting '}'> </pre> In this case the Ruby error is reported in logs/time_date/summary.txt Ruby runtime errors should be reported on the same file descriptor as STDOUT. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
