Bug 4206

Summary: yocto-bsp "Browse" build location button does not work
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: Alexandru Georgescu <alexandru.c.georgescu>
Component: eclipse-pluginAssignee: Ioana Grigoropol <ioanax.grigoropol>
Status: VERIFIED FIXED QA Contact: Andra Necula <andrax.g.necula>
Severity: normal    
Priority: Medium CC: andrax.g.necula, ioanax.grigoropol, jessica.zhang, yp.ep.watcher, yp.watcher
Version: 1.4   
Target Milestone: 1.4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
yocto-bsp error none

Description Alexandru Georgescu 2013-04-05 13:25:41 UTC
Created attachment 1159 [details]
yocto-bsp error

eclipse-poky:5e20d3c32072ddd91dceb8b2b793ef13f25b915e


1. Install eclipse plugin.
2. Open yocto-bsp
3. in yocto-bsp window fill in all the data for:

Metadata location
BSP name
BSP output location
Kernel architecture/Qemu Architecture

4. For Build Location use the "Browse" button and select a folder.
5. press next and select a kernel from the new window


EXPECTED RESULTS

5. The kernel can be selected 

ACTUAL RESULTS

5. The following error appears (see attachment)



OTHER COMMENTS

In step 4, if the user enters MANUALLY the Build location without using the Browse button, the kernel can be selected. So the issue is related to the Browse button in the "yocto-bsp Main page".
Comment 1 Ioana Grigoropol 2013-04-05 14:51:15 UTC
Patch sent to list.
Comment 2 Jessica 2013-04-05 22:55:36 UTC
Hi,

I couldn't reproduce the error with the "browse" button so how exactly to reproduce it?  Also, please figure out the exact command that we ended up sending to yocto-bsp tool, by all means, it shouldn't end up with traceback but with a meaningful error message to the user, so a bug should be filed against it as well...

Thanks,
Jessica
Comment 3 Ioana Grigoropol 2013-04-08 14:50:27 UTC
The bug can be reproduced on master doing the following:

- open yocto-bsp menu
- set metadata location
- set build location directory using browse button and without interferring with the text field at all
- set output location to new directory
- press "Next"
- select a Kernel from the combo

The problem is that we only check the build directory when the focus is lost in the text field, and we do not take into account when the value of this field is populated using "Browse" button.
In either case, this scenario should not happen, meaning, when the user reaches the second page we should have a functional build directory.
The eror is not reproducible if the build directory exists, and thus is not a problem with the actual command.
Comment 5 Andra Necula 2014-08-19 11:50:11 UTC
Verified with eclipse Kepler, on master branch
commit 2d1660112e54653f7bb763939d0416472c49fe01

Cheers! Andra N.