Bug 12670 - [2.5 M3 RC1]MANUAL_BitBake:test dependancy explorer is launched with failed logs
Summary: [2.5 M3 RC1]MANUAL_BitBake:test dependancy explorer is launched with failed logs
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 2.5
Hardware: x86 Multiple
: Undecided normal
Target Milestone: 2.6
Assignee: Stephano Cetola
QA Contact:
URL:
Whiteboard:
: 12888 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-04-10 02:18 UTC by pravin
Modified: 2018-11-23 16:01 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
bitbake explorer log (77.29 KB, image/png)
2018-04-10 02:18 UTC, pravin
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description pravin 2018-04-10 02:18:57 UTC
Created attachment 4262 [details]
bitbake explorer log

following steps for reproducing issue.

1) clone poky
2) cd poky
3) source oe-init-build-env
4) bitbake core-image-full-cmdline
5) bitbake -u taskexp -g core-image-full-cmdline

After step 5th test dependancy explorer launched, but bitbake giving following Failed message.

"Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused"

I have attached screenshot.
Comment 1 pankaj yadav 2018-08-15 02:02:42 UTC
*** Bug 12888 has been marked as a duplicate of this bug. ***
Comment 2 Manish Das 2018-10-01 09:58:16 UTC
This issue is reproducible in the 2.6 M3 rc1 release as well
Comment 3 Richard Purdie 2018-10-09 22:33:13 UTC
Step 4 is not needed and takes a long time. I've removed it from the test case as other areas of testing cover that.

I've sent out a patch for the other part of this issue.
Comment 5 pankaj yadav 2018-11-21 01:42:56 UTC
This issue is reproducible in the 2.4.4RC1 release as well.
Cross verified on two different setup.
Comment 6 Richard Purdie 2018-11-23 16:01:41 UTC
This was applied to sumo but not rocko (2.4). I've applied it there now as well:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=rocko&id=8883ee32f2a77bf532832d4fad5c20912a1a3630