On Mon, Jul 12, 2010 at 10:42 PM, Rafael Folco <[email protected]> wrote: > I got the following errors while running bonnie++ on autotest 0.11 and > 0.12. The errors below don't happen on 0.10. > # cat bonnie.ERROR > 07/11 08:27:11 ERROR| utils:0105| [stderr] bonnie++.cpp:137: > warning: unused parameter ‘sig’ > 07/11 08:27:11 ERROR| utils:0105| [stderr] bonnie++.cpp:137: > warning: unused parameter ‘unused’ > 07/11 08:27:14 ERROR| utils:0105| [stderr] Using uid:0, gid:999. > 07/11 08:35:10 ERROR| utils:0105| [stderr] Writing with > putc()...done > 07/11 08:35:29 ERROR| utils:0105| [stderr] Writing > intelligently...done > 07/11 08:36:09 ERROR| utils:0105| [stderr] Rewriting...done > 07/11 08:43:56 ERROR| utils:0105| [stderr] Reading with > getc()...done > 07/11 08:44:17 ERROR| utils:0105| [stderr] Reading > intelligently...done > 07/11 08:44:43 ERROR| utils:0105| [stderr] start > 'em...done...done...done... > 07/11 08:50:52 ERROR| utils:0105| [stderr] Create files in > sequential order...done. > 07/11 08:53:03 ERROR| utils:0105| [stderr] Stat files in sequential > order...done. > 07/11 09:39:41 ERROR| utils:0105| [stderr] Delete files in > sequential order...done. > 07/11 09:45:59 ERROR| utils:0105| [stderr] Create files in random > order...done. > 07/11 09:48:12 ERROR| utils:0105| [stderr] Stat files in random > order...done. > 07/11 11:04:40 ERROR| utils:0105| [stderr] Delete files in random > order...done. > > ./client/common_lib/utils.py on 0.11 and 0.12: > tee.write(data) > > ./client/common_lib/utils.py on 0.11 and 0.10: > if tee: > tee.write(data) > > I'm not sure why tee.write is producing those errors when running bonnie > ++. Could someone please take a look at it? This may be affecting > others...
By convention, whenever a program writes to stderr instead of stdout, the messages get logged as an ERROR by autotest's logging system. It is not an error really, it's just that bonnie chooses to print messages to stderr instead of stdout. A real error would be thrown if bonnie's returned exit code != 0, which didn't happen. So there's nothing to worry about, some programs just have this bad habit of spitting non-error output to the standard error output :) Cheers, Lucas > Thanks, > > Rafael > > _______________________________________________ > Autotest mailing list > [email protected] > http://test.kernel.org/cgi-bin/mailman/listinfo/autotest > -- Lucas _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
