When BBINCLUDELOGS is set, the output for a failing task looks a bit like:

ERROR: Function failed: do_configure (see /fast/git/.../tmp-eglibc/work/armv7a-vfp-oe-linux-gnueabi/eglibc-initial/2.16-r14+svnr20393/temp/log.do_configure.9006 for further information)
ERROR: Logfile of failure stored in: /fast/git/.../tmp-eglibc/work/armv7a-vfp-oe-linux-gnueabi/eglibc-initial/2.16-r14+svnr20393/temp/log.do_configure.9006
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
[...]
| ERROR: Function failed: do_configure (see /fast/git/.../tmp-eglibc/work/armv7a-vfp-oe-linux-gnueabi/eglibc-initial/2.16-r14+svnr20393/temp/log.do_configure.9006 for further information)
ERROR: Task 709 (/fast/git/bcm7425-oe/build-bcm7425/../oe-core/meta/recipes-core/eglibc/eglibc-initial_2.16.bb, do_configure) failed with exit code '1'

However, the file advertised in the first and penultimate lines as containing "further information" (and mentioned again in the second line) does not, in fact contain anything of the sort; it simply holds the same text that bitbake has already printed.  Encouraging users to go and look at it just leads to annoyance, and putting this advice within the file itself seems particularly useless.