Bug 4842 - [Autobuilder] Failed to create SSTATE_DIR
Summary: [Autobuilder] Failed to create SSTATE_DIR
Status: RESOLVED FIXED
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5
Assignee: Beth Flanagan
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-07-11 08:18 UTC by Laurentiu Palcu
Modified: 2013-07-23 15:11 UTC (History)
5 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Laurentiu Palcu 2013-07-11 08:18:55 UTC 
It looks like the SSTATE_DIR cannot be created for some reason... Maybe the disk is full. Here's the error:

### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-toolchain-sdk
    adt-installer
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
WARNING: Host distribution "Debian-6.0.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
    Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
    Following is the list of potential problems / advisories:

    Failed to create SSTATE_DIR directory in which to run long name sanity check: No such file or directory.

ERROR: Execution of event handler 'check_sanity_eventhandler' failed

Full log can be found here: http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm-lsb/builds/174/steps/Building%20Images/logs/stdio
Comment 1 Beth Flanagan 2013-07-23 15:11:05 UTC 
this seems to be fixed now. My guess is that it was a disk full issue.