Bug 5163

Summary: no external tools displayed when first trying to run QEMU - test case 48 failed on Ubuntu 12.04 x86-64 host(build 1.5 M4 rc2)
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: Ke Zou <ke.zou>
Component: eclipse-pluginAssignee: Chin Huat Ang <chin.huat.ang>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Medium CC: alexandru.c.georgescu, david.lerner26, ioanax.grigoropol, jose.perez.carranza, richard.purdie, tim.orling, valentinx.hangan, yi.zhao, yp.ep.watcher, yp.watcher
Version: 1.5   
Target Milestone: Future   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: New (Never tested)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
no external tools displayed none

Description Ke Zou 2013-09-11 02:30:45 UTC 
eclipse plugin test case 48 :
https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=48

Host: Ubuntu 12.04 x86-64
eclipse version: kepler
eclipse plugin build: yocto 1.5M4 rc2
http://autobuilder.yoctoproject.org/pub/nightly/20130828-3/eclipse-plugin/kepler/

Problem:
Follow the test case steps
After step1, nothing appears in Run -> External Tools menu
But on Fedora host, it is OK.
Comment 1 Alexandru Georgescu 2013-09-11 09:03:20 UTC 
Hi Ke,
Can you try the following workaround and see if it works?

In your project, do the following:
1. Open: Project -> Change Yocto Project settings
2. If a profile was created just select it again and press ok
3. Try to run qemu again: 
 Run -> External Tools -> "qemux86..."
4. If Step 3 fails, repeat steps 2-3 again.



As far as I know, this is an upstream bug from Eclipse and it isn't our plugin's fault. Using the workaround I described should list the qemu in the External tools.


Jessica, can you confirm that this is an upstream bug?
Comment 2 Jessica 2013-09-11 21:33:36 UTC 
I'll try to reproduce, but if it distro specific, does sounds like an upstream issue.
Comment 3 Ke Zou 2013-09-12 02:54:56 UTC 
Hi Alex,

The workaround works. Thanks.
If this is an upstream issue, I think i should withdraw this bug?

(In reply to comment #1)
> Hi Ke,
> Can you try the following workaround and see if it works?
> 
> In your project, do the following:
> 1. Open: Project -> Change Yocto Project settings
> 2. If a profile was created just select it again and press ok
> 3. Try to run qemu again: 
>  Run -> External Tools -> "qemux86..."
> 4. If Step 3 fails, repeat steps 2-3 again.
> 
> 
> 
> As far as I know, this is an upstream bug from Eclipse and it isn't our
> plugin's fault. Using the workaround I described should list the qemu in the
> External tools.
> 
> 
> Jessica, can you confirm that this is an upstream bug?
Comment 4 Alexandru Georgescu 2013-09-12 08:07:24 UTC 
Jessica, it reproduces all the time, when you first set up eclipse.
Comment 5 Jessica 2013-09-13 04:46:13 UTC 
So are you using the standard profile or you define your own profile? I'm using the standard profile and installed my eclipse plugin from http://autobuilder.yoctoproject.org/pub/nightly/20130912-1/eclipse-plugin/kepler/.  Everything works.
Comment 6 Alexandru Georgescu 2013-09-16 09:53:43 UTC 
For me it reproduces all the time (see attachment) in different distros, for juno and kepler too. I have tried using standard profile too, but I don't see why this is not a bug if the user has created his custom profile.


Jessica, did you try on a clean headless build for Eclipse?
You can also try by using a new Workspace.
Comment 7 Alexandru Georgescu 2013-09-16 09:58:10 UTC 
Created attachment 1500 [details]
no external tools displayed
Comment 8 David Lerner 2013-11-01 19:28:10 UTC 
I also found The  qemu target missing from the ‘Run | External Tools’ menu after setting the 'Yocto Adt Preference' fields per the setup described  in https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-eclipse-lab.pdf 
but using the 1.5 versions and qemux86-64 instead of qemux86.  

However, the qemu target appeared after creating a Yocto Autotools C hello world project.

This behavior was reproduced on 32/64 bit kepler and 32 bit juno for a qemux86_64 target using a 64bit host toolchain.
Comment 9 David Lerner 2013-11-01 19:31:40 UTC 
I also noticed that the qemu target is missing from the ‘Run | External Tools’ menu after setting the ‘Yocto Adt Preference' fields per the setup described in https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-eclipse-lab.pdf 
until the steps in that document to create a yocto autotools C hello world project.

This missing qemu tool entry behavior was reproduced on 32/64 bit kepler and 32 bit juno for a qemux86_64 target using a 64bit host toolchain.
Comment 10 Alexandru Georgescu 2013-11-04 08:37:46 UTC 
(In reply to comment #9)
> I also noticed that the qemu target is missing from the ‘Run | External
> Tools’ menu after setting the ‘Yocto Adt Preference' fields per the setup
> described in
> https://www.yoctoproject.org/sites/yoctoproject.org/files/elc2013-eclipse-
> lab.pdf 
> until the steps in that document to create a yocto autotools C hello world
> project.
> 
> This missing qemu tool entry behavior was reproduced on 32/64 bit kepler and
> 32 bit juno for a qemux86_64 target using a 64bit host toolchain.

Can you try my workaround (described earlier) and see if it shows?
Comment 11 David Lerner 2013-11-04 15:51:48 UTC 
Hi Alex,
The workaround that you suggest: "Project | Change Project Settings" is not available until a Yocto project is created and then that workaround seems unnecessary because merely creating and then selecting a Yocto C  project is sufficient to display the "run | external tools | qemu_x86_64-poky-linux" menu entry.
Comment 12 Alexandru Georgescu 2013-11-13 16:23:32 UTC 
(In reply to comment #11)
> Hi Alex,
> The workaround that you suggest: "Project | Change Project Settings" is not
> available until a Yocto project is created and then that workaround seems
> unnecessary because merely creating and then selecting a Yocto C  project is
> sufficient to display the "run | external tools | qemu_x86_64-poky-linux"
> menu entry.

For me it doesn't always work.
Comment 13 Richard Purdie 2015-04-28 21:44:52 UTC 
Reassign to Todor, this one is frustrating as it regularly shows up on QA reports.
Comment 14 Alexandru Georgescu 2015-08-06 15:56:20 UTC 
Hi Jose,
Is there something that can be done to prioritise this? As RP mentioned, this appeared in the QA reports, and is really annoying :)
Comment 15 Tim Orling 2016-08-10 21:46:36 UTC 
Does this bug still need attention?
Comment 16 Chin Huat Ang 2018-04-18 23:42:15 UTC 
I'm not sure how to reproduce the issue, I'm currently using the latest Eclipse Photon M6 release on Ubuntu 16.04.4 LTS. I noticed that the generated qemu-* external tool launch configuration sometimes do not appear immediately in Run -> External Tools, after the project has been created. Retrying the menu again fixes the problem, I suspect the new project wizard or creation process needs some time to complete the project creation which will eventually generate the launch configuration.

I've also tried to create multiple Target Profiles by setting each to different toolchain (i586 and aarch64), I do not see any issues in Run -> External Tools as the generated qemu-* external launch configuration show up as expected, I also tried to delete the generated launch configuration and I've verified that selecting a Target Profile will regenerate it as expected.

Please feel free to open this case if you still see the issue, and be sure to provide detail steps on how to reproduce it.