Anmar,
The EFI shell application when coupled with the fastmodel seems to create
a 'perfect storm' for parsing the characters in LAVA. We are unable to
accurately parse the resulting UEFI shell application when it is ran on the
fastmodel. UEFI + vexpress works.
We have yet to find a solution within LAVA to fix the UEFI shell +
fastmodel situation.
Possible next steps.
1. Reduce the complexity of the UEFI shell output by disabling color
codes (would need to be tested)
2. Investigate Fastmodel emulation when running UEFI shell. To root
cause this, we may need to understand why the fastmodel emulators are
causing delays which seem to break escape sequences and make parsing the
UEFI Shell very difficult.
3. Blind-execute EFI applications
4. Send more engineers after the parsing
5. Semi-blind, maybe implement partial match capability?
On 3 September 2013 13:01, Anmar Oueja <email address hidden> wrote:
> So what is the final decision Alan?
>
> --
> You received this bug notification because you are a member of Linaro
> Validation Team, which is subscribed to LAVA Dispatcher.
> https://bugs.launchpad.net/bugs/1197582
>
> Title:
> UEFI shell color codes makes it impossible to parse output with
> pexpect.
>
> Status in LAVA Dispatcher:
> Confirmed
>
> Bug description:
> For reference:
>
> http://www.nwdrone.com/scheduler/job/1178/log_file
>
> [a] Boot Manager
> [b] Shell
> [c] Reboot
> [d] Shutdown
> Start:
> Invalid input, please choose a menu option from the list above
> Start: b
> [2J [01;01H [01;01HUEFI Interactive Shell v2.0. UEFI v2.31 (ARM
> Versatile Express EFI Jun 19 2013 21:21:03, 0x00000000). Revision 1.02
> [1m [33m [40mMapping table [0m [37m [40m
> [1m [33m [40m FS1: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40mF6:
> VenHw(C5B9C74A-6D72-4719-99AB-C59F199091EB)
> [1m [33m [40m FS0: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40mHD3b:;BLK2:
>
> VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(1,MBR,0x00000000,0x3F,0x19FC0)
> [1m [33m [40m BLK6: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(E7223039-5836-41E1-B542-D7EC736C5E59)
> [1m [33m [40m BLK0: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(02118005-9DA7-443A-92D5-781F022AEDBB)
> [1m [33m [40m BLK4: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(1F15DA3C-37FF-4070-B471-BB4AF12A724A)
> [1m [33m [40m BLK5: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(CC2CBF29-1498-4CDD-8171-F8B6B41D0909)
> [1m [33m [40m BLK1: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)
> [1m [33m [40m BLK3: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
>
> VenHw(09831032-6FA3-4484-AF4F-0A000A8D3A82)/HD(2,MBR,0x00000000,0x1A000,0x3CE000)
> [22;01HPress [1m [37m [40mESC [0m [37m [40m in 5 seconds to skip [1m
> [33m [40mstartup.nsh [0m [37m [40m or any other key to continue.
>
> As you can see from the job above, LAVA is unable to parse the output
> due to the presense of color codes used in the UEFI shell. This is a
> major blocker as LAVA cannot be used to test UEFI properly, and should
> be fixed ASAP.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/lava-dispatcher/+bug/1197582/+subscriptions
>
Anmar,
The EFI shell application when coupled with the fastmodel seems to create
a 'perfect storm' for parsing the characters in LAVA. We are unable to
accurately parse the resulting UEFI shell application when it is ran on the
fastmodel. UEFI + vexpress works.
We have yet to find a solution within LAVA to fix the UEFI shell +
fastmodel situation.
Possible next steps.
1. Reduce the complexity of the UEFI shell output by disabling color
codes (would need to be tested)
2. Investigate Fastmodel emulation when running UEFI shell. To root
cause this, we may need to understand why the fastmodel emulators are
causing delays which seem to break escape sequences and make parsing the
UEFI Shell very difficult.
3. Blind-execute EFI applications
4. Send more engineers after the parsing
5. Semi-blind, maybe implement partial match capability?
On 3 September 2013 13:01, Anmar Oueja <email address hidden> wrote:
> So what is the final decision Alan? /bugs.launchpad .net/bugs/ 1197582 www.nwdrone. com/scheduler/ job/1178/ log_file 6D72-4719- 99AB-C59F199091 EB) 6FA3-4484- AF4F-0A000A8D3A 82)/HD( 1,MBR,0x0000000 0,0x3F, 0x19FC0) 5836-41E1- B542-D7EC736C5E 59) 9DA7-443A- 92D5-781F022AED BB) 37FF-4070- B471-BB4AF12A72 4A) 1498-4CDD- 8171-F8B6B41D09 09) 6FA3-4484- AF4F-0A000A8D3A 82) 6FA3-4484- AF4F-0A000A8D3A 82)/HD( 2,MBR,0x0000000 0,0x1A000, 0x3CE000) /bugs.launchpad .net/lava- dispatcher/ +bug/1197582/ +subscriptions
>
> --
> You received this bug notification because you are a member of Linaro
> Validation Team, which is subscribed to LAVA Dispatcher.
> https:/
>
> Title:
> UEFI shell color codes makes it impossible to parse output with
> pexpect.
>
> Status in LAVA Dispatcher:
> Confirmed
>
> Bug description:
> For reference:
>
> http://
>
> [a] Boot Manager
> [b] Shell
> [c] Reboot
> [d] Shutdown
> Start:
> Invalid input, please choose a menu option from the list above
> Start: b
> [2J [01;01H [01;01HUEFI Interactive Shell v2.0. UEFI v2.31 (ARM
> Versatile Express EFI Jun 19 2013 21:21:03, 0x00000000). Revision 1.02
> [1m [33m [40mMapping table [0m [37m [40m
> [1m [33m [40m FS1: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40mF6:
> VenHw(C5B9C74A-
> [1m [33m [40m FS0: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40mHD3b:;BLK2:
>
> VenHw(09831032-
> [1m [33m [40m BLK6: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(E7223039-
> [1m [33m [40m BLK0: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(02118005-
> [1m [33m [40m BLK4: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(1F15DA3C-
> [1m [33m [40m BLK5: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(CC2CBF29-
> [1m [33m [40m BLK1: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
> VenHw(09831032-
> [1m [33m [40m BLK3: [0m [37m [40m [1m [37m [40mAlias(s): [0m [37m
> [40m
>
> VenHw(09831032-
> [22;01HPress [1m [37m [40mESC [0m [37m [40m in 5 seconds to skip [1m
> [33m [40mstartup.nsh [0m [37m [40m or any other key to continue.
>
> As you can see from the job above, LAVA is unable to parse the output
> due to the presense of color codes used in the UEFI shell. This is a
> major blocker as LAVA cannot be used to test UEFI properly, and should
> be fixed ASAP.
>
> To manage notifications about this bug go to:
> https:/
>
--
Alan Bennett, Engineering Manager, Linaro LAVA Team www.linaro. org/>* **│ *Open source software for ARM SoCs www.facebook. com/pages/ Linaro> | twitter. com/#%21/ linaroorg> | www.linaro. org/linaro- blog/>
Linaro.org <http://
| Follow Linaro*:* Facebook <http://
Twitter <http://
Blog<http://
irc: akbennett | <email address hidden> |
<email address hidden>