Beth, I noticed following recent autobuilder failures for meta-intel. And also tested these locally and I don’t see these issues in my local testing. So I think these issues are caused by the autobuilder setup. Especially sharing of sstate cache from other builds probably have led to these issues on autobuilder. Can you fix the autobuilder setup to avoid these false issues? Thanks, Nitin http://autobuilder.yoctoproject.org:8010/builders/chiefriver/builds/103/steps/shell_34/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/chiefriver/builds/103/steps/shell_60/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/emenlow/builds/243/steps/shell_34/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/emenlow/builds/243/steps/shell_60/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/fri2/builds/270/steps/shell_34/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/fri2/builds/270/steps/shell_60/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/jasperforest/builds/245/steps/shell_34/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/jasperforest/builds/245/steps/shell_60/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/romley/builds/220/steps/shell_34/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/romley/builds/220/steps/shell_60/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/sugarbay/builds/256/steps/shell_34/logs/stdio http://autobuilder.yoctoproject.org:8010/builders/sugarbay/builds/256/steps/shell_60/logs/stdio
This isn't an autobuilder issue. Someone needs to fix valgrind so it doesn't pull in this librbary if its present on the host. Paul already tried this once: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a1ac22a73c226e268bea90eaa043b3da4695d577 but it appears it isn't enough.
I did test that this actually prevented linking to the installed library on my machine, so I don't know what can still be going wrong ...
Nitin, I don't know what you're looking at but these failures are from two weeks ago. The bugs was resolved by Pauls commit. There are a ton of new meta-intel failures related to fontconfig but the valgrind issue is dealt with.
RP, I don't see any fontconfig failure in the recent logs like this: http://autobuilder.yoctoproject.org:8010/builders/chiefriver/builds/119/steps/shell_34/logs/stdio I tested these images on my build machines and they were building fine for me. So I asked in email to check the autobuilder config. As I did not see any response to that email, I thought the issue is still present. And the error logs looked same to me. How do you say there are fontconfig issues in the recent meta-intel failures? Thanks, Nitin
The last thing in the logs: | Running intercept scripts: | > Executing update_font_cache i.e. the font cache from fontconfig. There are multiple other build failures in this area and its very recently changed so I suspect something is wrong in that area. Its not 100% certain though.