bitbake listtasks broken

bitbake listtasks broken

[Gary Thomas]

Filed as bug #548

This command [no longer?] produces any output:
   bitbake recipe -c listtasks

$ bitbake qemu -c listtasks
NOTE: Handling BitBake files: | (0756/0756) [100 %]
Parsing of 756 .bb files complete (0 cached, 756 parsed). 913 targets, 34 skipped, 0 masked, 0 errors.

OE Build Configuration:
BB_VERSION        = "1.11.0"
METADATA_BRANCH   = "local_master"
METADATA_REVISION = "94b1fda09671b58aafb54983e4a6e499f6ffc369"
TARGET_ARCH       = "i586"
TARGET_OS         = "linux"
MACHINE           = "qemux86"
DISTRO            = "poky"
DISTRO_VERSION    = "0.9+snapshot-20101125"
TARGET_FPU        = ""

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing runqueue
NOTE: Full skip list set([])
NOTE: Running task 1 of 1 (ID: 0, /tmp/poky-amltd/meta/recipes-devtools/qemu/qemu_0.12.4.bb, do_listtasks)
NOTE: package qemu-0.12.4-r22: task do_listtasks: Started
NOTE: package qemu-0.12.4-r22: task do_listtasks: Succeeded
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 0 failed.


-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: bitbake listtasks broken

[Gary Thomas]

On 11/25/2010 04:06 AM, Gary Thomas wrote:
> Filed as bug #548
>
> This command [no longer?] produces any output:
> bitbake recipe -c listtasks
>
> $ bitbake qemu -c listtasks
> NOTE: Handling BitBake files: | (0756/0756) [100 %]
> Parsing of 756 .bb files complete (0 cached, 756 parsed). 913 targets, 34 skipped, 0 masked, 0 errors.
>
> OE Build Configuration:
> BB_VERSION = "1.11.0"
> METADATA_BRANCH = "local_master"
> METADATA_REVISION = "94b1fda09671b58aafb54983e4a6e499f6ffc369"
> TARGET_ARCH = "i586"
> TARGET_OS = "linux"
> MACHINE = "qemux86"
> DISTRO = "poky"
> DISTRO_VERSION = "0.9+snapshot-20101125"
> TARGET_FPU = ""
>
> NOTE: Resolving any missing task queue dependencies
> NOTE: Preparing runqueue
> NOTE: Executing runqueue
> NOTE: Full skip list set([])
> NOTE: Running task 1 of 1 (ID: 0, /tmp/poky-amltd/meta/recipes-devtools/qemu/qemu_0.12.4.bb, do_listtasks)
> NOTE: package qemu-0.12.4-r22: task do_listtasks: Started
> NOTE: package qemu-0.12.4-r22: task do_listtasks: Succeeded
> NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 0 failed.

To be fair, it does do something, but the results are hidden in
the temp/log.do_listtasks file.  Certainly not what the documentation
implies...

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: bitbake listtasks broken

[Tian, Kevin]

>From: Gary Thomas
>Sent: Thursday, November 25, 2010 7:38 PM
>
>On 11/25/2010 04:06 AM, Gary Thomas wrote:
>> Filed as bug #548
>>
>> This command [no longer?] produces any output:
>> bitbake recipe -c listtasks
>>
>> $ bitbake qemu -c listtasks
>> NOTE: Handling BitBake files: | (0756/0756) [100 %]
>> Parsing of 756 .bb files complete (0 cached, 756 parsed). 913 targets, 34 skipped, 0
>masked, 0 errors.
>>
>> OE Build Configuration:
>> BB_VERSION = "1.11.0"
>> METADATA_BRANCH = "local_master"
>> METADATA_REVISION = "94b1fda09671b58aafb54983e4a6e499f6ffc369"
>> TARGET_ARCH = "i586"
>> TARGET_OS = "linux"
>> MACHINE = "qemux86"
>> DISTRO = "poky"
>> DISTRO_VERSION = "0.9+snapshot-20101125"
>> TARGET_FPU = ""
>>
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: Preparing runqueue
>> NOTE: Executing runqueue
>> NOTE: Full skip list set([])
>> NOTE: Running task 1 of 1 (ID: 0,
>/tmp/poky-amltd/meta/recipes-devtools/qemu/qemu_0.12.4.bb, do_listtasks)
>> NOTE: package qemu-0.12.4-r22: task do_listtasks: Started
>> NOTE: package qemu-0.12.4-r22: task do_listtasks: Succeeded
>> NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 0 failed.
>
>To be fair, it does do something, but the results are hidden in
>the temp/log.do_listtasks file.  Certainly not what the documentation
>implies...
>

Previously python tasks were not logged, so do_listtasks get its output to the console.

Now all python and shell tasks are logged, that's why you see output in a log file now.

But I agree that it's not convenient to search WORKDIR for such information. I'm working
a fix by use bb.msg.note instead.

Thanks
Kevin

Re: bitbake listtasks broken

[Richard Purdie]

On Fri, 2010-11-26 at 10:29 +0800, Tian, Kevin wrote:
> >From: Gary Thomas
> >Sent: Thursday, November 25, 2010 7:38 PM
> >
> >On 11/25/2010 04:06 AM, Gary Thomas wrote:
> >> Filed as bug #548
> >>
> >> This command [no longer?] produces any output:
> >> bitbake recipe -c listtasks
> >>
> >> $ bitbake qemu -c listtasks
> >> NOTE: Handling BitBake files: | (0756/0756) [100 %]
> >> Parsing of 756 .bb files complete (0 cached, 756 parsed). 913 targets, 34 skipped, 0
> >masked, 0 errors.
> >>
> >> OE Build Configuration:
> >> BB_VERSION = "1.11.0"
> >> METADATA_BRANCH = "local_master"
> >> METADATA_REVISION = "94b1fda09671b58aafb54983e4a6e499f6ffc369"
> >> TARGET_ARCH = "i586"
> >> TARGET_OS = "linux"
> >> MACHINE = "qemux86"
> >> DISTRO = "poky"
> >> DISTRO_VERSION = "0.9+snapshot-20101125"
> >> TARGET_FPU = ""
> >>
> >> NOTE: Resolving any missing task queue dependencies
> >> NOTE: Preparing runqueue
> >> NOTE: Executing runqueue
> >> NOTE: Full skip list set([])
> >> NOTE: Running task 1 of 1 (ID: 0,
> >/tmp/poky-amltd/meta/recipes-devtools/qemu/qemu_0.12.4.bb, do_listtasks)
> >> NOTE: package qemu-0.12.4-r22: task do_listtasks: Started
> >> NOTE: package qemu-0.12.4-r22: task do_listtasks: Succeeded
> >> NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 0 failed.
> >
> >To be fair, it does do something, but the results are hidden in
> >the temp/log.do_listtasks file.  Certainly not what the documentation
> >implies...
> >
> 
> Previously python tasks were not logged, so do_listtasks get its output to the console.
> 
> Now all python and shell tasks are logged, that's why you see output in a log file now.
> 
> But I agree that it's not convenient to search WORKDIR for such information. I'm working
> a fix by use bb.msg.note instead.

Good thinking, I didn't realise it was poking sysout directly. I've a
local patch switching this to use bb.plain() which is the most
appropriate formatting in this case.

Cheers,

Richard