10132 2016-08-12 13:34:26 +0000 Clarifications/corrections to '2.3.1. Viewing Logs from Failed Tasks' 2016-08-12 21:51:18 +0000 1 1 9 Documentation Reference handbook 2.2 x86 Multiple RESOLVED FIXED 12 July 2016: RESOLVED Undecided normal 2.2 M4 1 ulfalizer srifenbark bluelightning poky.doc.watcher poky.watcher srifenbark --- --- Done (doc changes complete) oldest_to_newest 65123 0 ulfalizer 2016-08-12 13:34:26 +0000 The following note at the end of '2.3.1. Viewing Logs from Failed Task' no longer seems to be true and should be removed: Presently, the output from Python tasks is sent directly to the console. Here's a test recipe that shows this. The stdout/stderr output from the Python task ends up in log.do_pythontask and is not printed to the terminal. LICENSE = "CLOSED" python do_pythontask() { print("to stdout") print("to stderr", file=sys.stderr) } addtask pythontask before do_build Additionally, the current description makes it sound like you manually have to hunt down the correct run.do_taskname.<pid> file. It's never mentioned that there are symlinks that point to the latest one. I suggest rewriting things as follows (note that only the second paragraph includes the <pid> part now). The log for a task can be found in the file ${[WORKDIR]}/temp/log.do_taskname. For example, the log for the do_compile task of the QEMU minimal image for the x86 machine (qemux86) might be tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_compile. To see the commands BitBake ran to generate that log, look at the corresponding run.do_taskname file in the same directory. log.do_taskname and run.do_taskname are really symbolic links to log.do_taskname.<pid> and log.run_taskname.<pid>, where <pid> is the <pid> the task had when it ran. The symlinks always point to the files corresponding to the most recent run. (Note the linkification of WORKDIR.) Cheers, Ulf 65124 1 ulfalizer 2016-08-12 13:37:32 +0000 Version 2: The log for a task can be found in the file ${[WORKDIR]}/temp/log.do_taskname. For example, the log for the do_compile task of the QEMU minimal image for the x86 machine (qemux86) might be in tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_compile. To see the commands BitBake ran to generate a log, look at the corresponding run.do_taskname file in the same directory. log.do_taskname and run.do_taskname are really symbolic links to log.do_taskname.<pid> and log.run_taskname.<pid>, where <pid> is the <pid> the task had when it ran. The symlinks always point to the files corresponding to the most recent run. 65153 2 srifenbark 2016-08-12 20:50:47 +0000 Ulf, See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#usingpoky-debugging-viewing-logs-from-failed-tasks and let me know of any problems. Thanks, Scott 65155 3 ulfalizer 2016-08-12 20:56:57 +0000 * All the .pid's could be removed from the first paragraph. The only thing people usually care about is the latest version of the log/run files, which they'll get via the symlinks. The second paragraph then mentions the .pid files. * ${WORKDIR} could be linkified in ${WORKDIR}/temp/log.do_taskname. Cheers, Ulf 65162 4 srifenbark 2016-08-12 21:33:30 +0000 Ulf, How is this? http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#usingpoky-debugging-viewing-logs-from-failed-tasks scott 65164 5 ulfalizer 2016-08-12 21:37:08 +0000 Looks good now! Thanks, Ulf 65169 6 srifenbark 2016-08-12 21:51:18 +0000 nice - 3 for 3. Set to RESOLVED and doc flag off. Scott