Bug 12406

Summary:	Multiconfig for machines with same architectures
Product:	[Build System, Metadata & Runtime] BitBake	Reporter:	David Bensoussan <minipada>
Component:	bitbake	Assignee:	Richard Purdie <richard.purdie>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	poky.bs.watcher, poky.watcher, randy.macleod
Version:	2.4
Target Milestone:	4.99
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Don't know

Description David Bensoussan 2017-12-07 13:07:01 UTC

I am working with multiple machines, including raspberrypi3 and raspberrypi-cm3.
While executing

$ bitbake mc:raspberrypi-cm3:rpi-basic-image mc:raspberrypi3:rpi-basic-image

I encounter issues (FileExists or compilation ones). They appear when bitbake work on the same package for the 2 machines. Since the architecture is the same and the build directory is also the same, there are concurrency errors which don't appear if the 2 tasks are done separately.

I am not aware of the complexity of solving the issue, by detecting when recipes have the same names and when buildirs are also the same, but this would add a lot of value and speed to the multiconfig setup.

I am using 
OS: Ubuntu 16.04
poky: rocko
meta-openembedded: rocko
meta-raspberrypi: master

Thanks,

David Bensoussan
Synapticon GmbH

Comment 1 Richard Purdie 2018-09-22 02:03:56 UTC

I had a look at this, admittedly on sumo and not rocko and the code seemed to do the right things, not allowing two tasks with the same stamp to run at once.

Do you have any more details on which errors exactly you're seeing?

Comment 2 Richard Purdie 2018-10-18 12:50:21 UTC

Could you provide more information about the errors you're seeing please?

Comment 3 David Bensoussan 2018-11-19 20:23:20 UTC

Some packages were compiled for 2 different targets at the same time in the same workspace. Files were accessed at the same time throwing errors.

I tested using rpi3 and rpi-cm3 as targets at the time.

I don't have the build anymore as it happened too long ago...

Comment 4 Stephen K Jolley 2018-11-23 19:31:30 UTC

I believe the question has been answered.  If you still need more information please ask and reset back into NEEDINFO.

Comment 5 Richard Purdie 2018-12-08 21:59:01 UTC

I can believe there is some problem here but we need more information to reproduce and fix it. If you have a test case which shows the issue which we can reproduce please reopen or file a new bug but I don't think there is anything we can work with from here as this stands, sorry. The tests I made worked as expected...