Skip to contentSkip to conversation

Change in bitbake behaviour?

DISCUSSION Gary Thomas 2 participants 5 messages Sep 21, 2015 – Sep 23, 2015

lore
Share & tools
lore
#0 lore raw

I just updated to the latest Poky/Yocto master
and I noticed this change in behaviour when I tried to stop a build:
Keyboard Interrupt, closing down...

NOTE: Tasks Summary: Attempted 86 tasks of which 36 didn't need to be rerun and all succeeded.
ERROR: Command execution failed: Stopped build

Summary: There was 1 ERROR message shown, returning a non-zero exit code. Execution was interrupted, returning a non-zero exit code. timed out

It took more than a minute between the last two lines at which time I thought it might be hung. I left it and then found the "timed out" line somewhat later.

Is this to be expected?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw

Hi Gary,

Quoted 12 lines · On Monday 21 September 2015 06:35:54 Gary Thomas wrote:

I just updated to the latest Poky/Yocto master
and I noticed this change in behaviour when I tried to stop a build:
Keyboard Interrupt, closing down...

NOTE: Tasks Summary: Attempted 86 tasks of which 36 didn't need to be
rerun and all succeeded. ERROR: Command execution failed: Stopped build

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Execution was interrupted, returning a non-zero exit code.
timed out

Quoted 5 lines

It took more than a minute between the last two lines at which time I thought it might be hung. I left it and then found the "timed out" line somewhat later.

Is this to be expected?

No, this sounds like a bug - but was this somehow related to your other build issue or do you still see this?

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#2 lore raw
Quoted 15 lines · Paul Eggleton

Hi Gary,

Quoted 12 lines · On Monday 21 September 2015 06:35:54 Gary Thomas wrote:

I just updated to the latest Poky/Yocto master
and I noticed this change in behaviour when I tried to stop a build:
Keyboard Interrupt, closing down...

NOTE: Tasks Summary: Attempted 86 tasks of which 36 didn't need to be
rerun and all succeeded. ERROR: Command execution failed: Stopped build

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Execution was interrupted, returning a non-zero exit code.
timed out

Quoted 8 lines
Quoted 5 lines

It took more than a minute between the last two lines at which time I thought it might be hung. I left it and then found the "timed out" line somewhat later.

Is this to be expected?

No, this sounds like a bug - but was this somehow related to your other build issue or do you still see this?

No, I'm still seeing it, but only occasionally. It's most pronounced if I try and abort a build, but I have seen it also with a successful run (it hangs when seemingly complete the prints 'timed out' after a fairly long time)

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#3 lore raw
Quoted 27 lines · On Wednesday 23 September 2015 07:49:34 Gary Thomas wrote:
Quoted 26 lines · Paul Eggleton

Hi Gary,

Quoted 22 lines · On Monday 21 September 2015 06:35:54 Gary Thomas wrote:

I just updated to the latest Poky/Yocto master
and I noticed this change in behaviour when I tried to stop

a build:
Keyboard Interrupt, closing down...

NOTE: Tasks Summary: Attempted 86 tasks of which 36 didn't need to be

rerun and all succeeded. ERROR: Command execution failed: Stopped build

Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Execution was interrupted, returning a non-zero exit code.

timed out

It took more than a minute between the last two lines at which time I thought it might be hung. I left it and then found the "timed out" line somewhat later.

Is this to be expected?

Quoted 7 lines
Quoted 2 lines

No, this sounds like a bug - but was this somehow related to your other build issue or do you still see this?

No, I'm still seeing it, but only occasionally. It's most pronounced if I try and abort a build, but I have seen it also with a successful run (it hangs when seemingly complete the prints 'timed out' after a fairly long time)

OK... is a PR server enabled in your configuration and if so is it being started automatically or running on a different machine?

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#4 lore raw
Quoted 31 lines · Paul Eggleton
Quoted 30 lines · On Wednesday 23 September 2015 07:49:34 Gary Thomas wrote:
Quoted 28 lines · Paul Eggleton

Hi Gary,

Quoted 15 lines · On Monday 21 September 2015 06:35:54 Gary Thomas wrote:

I just updated to the latest Poky/Yocto master
and I noticed this change in behaviour when I tried to stop

a build:
Keyboard Interrupt, closing down...

NOTE: Tasks Summary: Attempted 86 tasks of which 36 didn't need to be

rerun and all succeeded. ERROR: Command execution failed: Stopped build

Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Execution was interrupted, returning a non-zero exit code.

Quoted 7 lines

timed out

It took more than a minute between the last two lines at which time I thought it might be hung. I left it and then found the "timed out" line somewhat later.

Is this to be expected?

No, this sounds like a bug - but was this somehow related to your other build issue or do you still see this?

Quoted 7 lines
Quoted 4 lines

No, I'm still seeing it, but only occasionally. It's most pronounced if I try and abort a build, but I have seen it also with a successful run (it hangs when seemingly complete the prints 'timed out' after a fairly long time)

OK... is a PR server enabled in your configuration and if so is it being started automatically or running on a different machine?

Started automatically on this machine. I routinely have this in my local.conf:
# Enable local PR server - edit this to use a shared server PRSERV_HOST = "localhost:0"

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------