Bug 3764 - [Autobuilder] Missing provider for libva-intel-driver
Summary: [Autobuilder] Missing provider for libva-intel-driver
Status: RESOLVED FIXED
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.4
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.4 M4
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-01-21 11:59 UTC by Constantin Musca
Modified: 2013-01-29 06:11 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Constantin Musca 2013-01-21 11:59:35 UTC
This failure was identified for fri2, crownbay, emenlow and sys940:

http://autobuilder.yoctoproject.org:8010/builders/fri2/builds/267/steps/shell_34/logs/stdio
http://autobuilder.yoctoproject.org:8010/builders/sys940x/builds/114/steps/shell_34/logs/stdio
http://autobuilder.yoctoproject.org:8010/builders/emenlow/builds/240/steps/shell_34/logs/stdio
http://autobuilder.yoctoproject.org:8010/builders/crownbay/builds/256/steps/shell_34/logs/stdio

Error:
| Updating cache...               ######################################## [100%]
| 
| Computing transaction...error: Can't install va-intel-1.0-r1@core2: no package provides libva-intel-driver
| 
| Saving cache...
| 
| ERROR: Function failed: do_rootfs (see /srv/home/pokybuild/yocto-autobuilder/yocto-slave/crownbay/build/build/tmp/work/crownbay-poky-linux/core-image-sato-sdk/1.0-r0/temp/log.do_rootfs.1470 for further information)
NOTE: recipe core-image-sato-sdk-1.0-r0: task do_rootfs: Failed
ERROR: Task 23 (/srv/home/pokybuild/yocto-autobuilder/yocto-slave/crownbay/build/meta/recipes-sato/images/core-image-sato-sdk.bb, do_rootfs) failed with exit code '1'

Cheers,
Constantin
Comment 1 Darren Hart 2013-01-21 16:17:46 UTC
Nitin,

Is this an artifact of the recent graphics driver update?
Comment 2 Nitin Kamble 2013-01-22 19:06:41 UTC
I think this is something unrelated. For these BSPs emgd driver is used and not the intel-driver as seen in the error.
Comment 3 Nitin Kamble 2013-01-23 19:33:19 UTC
Something weird is happening on AB, the later run of the Ab does not show any of these issues.
Comment 4 Nitin Kamble 2013-01-25 18:32:01 UTC
This was some anomaly in AB run. This issue does not happen anymore.