Skip to contentSkip to conversation

Over-exuberant error printing?

DISCUSSION Gary Thomas 2 participants 3 messages May 24, 2011 – May 26, 2011

lore
Share & tools
lore
#0 lore raw

Building from today's master (3504c3a9b1af5a3405e0a03a5ade50b82535b6dd) if I get an error, I get two lines printed for each real line, e.g.

| ERROR: The stack trace of python calls that resulted in this exception/failure was:
| ERROR: The stack trace of python calls that resulted in this exception/failure was:
| ERROR:   File "sstate_task_postfunc", line 10, in <module>
| ERROR:   File "sstate_task_postfunc", line 10, in <module>
| ERROR:
| ERROR:
| ERROR:   File "sstate_task_postfunc", line 4, in sstate_task_postfunc
| ERROR:   File "sstate_task_postfunc", line 4, in sstate_task_postfunc

etc.

This is new behavior - any ideas?

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

Building from today's master (3504c3a9b1af5a3405e0a03a5ade50b82535b6dd) if I get an error, I get two lines printed for each real line, e.g.

| ERROR: The stack trace of python calls that resulted in this exception/failure was:
| ERROR: The stack trace of python calls that resulted in this exception/failure was:
| ERROR:   File "sstate_task_postfunc", line 10, in <module>
| ERROR:   File "sstate_task_postfunc", line 10, in <module>
| ERROR:
| ERROR:
| ERROR:   File "sstate_task_postfunc", line 4, in sstate_task_postfunc
| ERROR:   File "sstate_task_postfunc", line 4, in sstate_task_postfunc
Quoted 4 lines

etc.

This is new behavior - any ideas?

I've been seeing this as well and hadn't dug in to sort it out yet. You said it is new behavior, have you bisected to determine when it occured?

Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#2 lore raw
Quoted 15 lines · Darren Hart
Quoted 12 lines · Gary Thomas

Building from today's master (3504c3a9b1af5a3405e0a03a5ade50b82535b6dd) if I get an error, I get two lines printed for each real line, e.g.

| ERROR: The stack trace of python calls that resulted in this exception/failure was:
| ERROR: The stack trace of python calls that resulted in this exception/failure was:
| ERROR:   File "sstate_task_postfunc", line 10, in<module>
| ERROR:   File "sstate_task_postfunc", line 10, in<module>
| ERROR:
| ERROR:
| ERROR:   File "sstate_task_postfunc", line 4, in sstate_task_postfunc
| ERROR:   File "sstate_task_postfunc", line 4, in sstate_task_postfunc

etc.

Quoted 6 lines
Quoted 2 lines

This is new behavior - any ideas?

I've been seeing this as well and hadn't dug in to sort it out yet. You said it is new behavior, have you bisected to determine when it occured?

Not yet - I was mostly hoping that someone else had seen such behaviour (as you obviously have) and verified that I'm not the only one :-)

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