>>I did put this into testing anyway and it triggered errors in several selftests: >> >>bitbake-selftest: >>https ://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1792/steps/11/logs/stdio >> >>and oe-selftest: >>https ://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1792/steps/14/logs/stdio >> >>(these occurred in all the selftest builds but I've just linked to one). >It seems in these tests multiconfig targets can have more than 2 colons. Probably changing "== 2" to ">= 2" should help. >I tried "bitbake-selftest" and with this change and it passed. Unfortunately now I don't have access to machine that could handle all oe-selftest. Could we agree that I will send second patch so it will be tested on autobuider? Sorry, I misunderstood your words and thought some other than multiconfig cases failed on other builds, while in fact it was just multiconfig failures. Running "oe-selftest -a" would take ages on my machine. With the ">= 2" "bitbake-selftest" already passed and "oe-selftest -r multiconfig" is correctly building things, instead of failing on "RunQueue" step. As soon as the multiconfig tests pass I will submit a new patch to bitbake-devel. Best regards, Tomasz Dziendzielsk