From: <owl...@go...> - 2013-01-25 16:32:25
|
Status: Accepted Owner: cmung...@gmail.com Labels: Type-Defect Priority-Medium New issue 46 by cmung...@gmail.com: Need to figure out standard method for error reporting in oort http://code.google.com/p/owltools/issues/detail?id=46 oort is often run via jenkins, and configured such that the console is sent to users / a list if there is an issue. one strategy is to just run oort. if there are issues then info is generated on stderr/stdout/console, and this goes at the end of the report, and is sent to the user if there is an error. this works mostly fine. however, the drawback is that there is no file for the overall report, it's not a build artifact, and there is no report that can be post-processed with grep. we've tried redirecting the output and exiting if there is an error. But this is awkward and problematic. E.g. see issue here, which is buried midway in the console. http://build.berkeleybop.org/job/build-phenoscape/190/consoleFull What would be best would be if there was an option such that output could be simultaneously generated on the console and to a file. This may be as simple as a log4j setting - or it may be harder. investigate. |
From: <owl...@go...> - 2013-02-07 17:51:36
|
Updates: Status: Fixed Comment #1 on issue 46 by HDie...@lbl.gov: Need to figure out standard method for error reporting in oort http://code.google.com/p/owltools/issues/detail?id=46 OORT has now an updated reporting mechanism. One can now create separate log files for errors and the full trace: The new CLI options: --error-report [error-report.txt] --trace-report [trace-report.txt] Both options canbe used as a boolean flag or append a file name to overwrite the default output file. |