Add newline breaks in util.build_log_msg() to clean up order logging from mapper

[GoogleCodeExporter]

Add newline at the end of the printf output statement in util.py in 
build_log_msg() method.  

All logging that is happening from cdr_ecv_mapper.py is abysmal looking b/c 
your msg string doesn't have a newline break, so all subsequent lines don't 
wrap and continue in one big line.

Example:

2013-10-29 12:14.24 [CDR_ECV_MAPPER] Processing LT50260381997048AAA012013-10-29 
12:14.24 [CDR_ECV_MAPPER] Running command:./cdr_ecv.py --scene 
LT50260381997048AAA01 --order yvonne_allen@fws.gov-0101310288376 
--surface_reflectance --source_host edclxs140p --destination_host edclxs67p 
--source_type level1 2013-10-29 12:45.25 [CDR_ECV_MAPPER] Processing complete 
for LT50260381997048AAA01

What is the expected output? What do you see instead?

2013-10-29 12:14.24 [CDR_ECV_MAPPER] Processing LT50260381997048AAA01
2013-10-29 12:14.24 [CDR_ECV_MAPPER] Running command:./cdr_ecv.py --scene 
LT50260381997048AAA01 --order yvonne_allen@fws.gov-0101310288376 
--surface_reflectance --source_host edclxs140p --destination_host edclxs67p 
--source_type level1 
2013-10-29 12:45.25 [CDR_ECV_MAPPER] Processing complete for 
LT50260381997048AAA01

Tagging this as high priority defect for 2.2.1/2 release otherwise is makes any 
order troubleshooting visually cumbersome.

Original issue reported on code.google.com by adamdosch on 29 Oct 2013 at 7:04

[GoogleCodeExporter]

Original comment by davehil...@gmail.com on 26 Nov 2013 at 7:02

• Added labels: Milestone-2.2.2

[GoogleCodeExporter]

Original comment by davehil...@gmail.com on 10 Dec 2013 at 3:50

• Changed state: Verified