| Issue 205197: | VMTests fail with "No space left on device" | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
http://chromeos-botmaster.mtv.corp.google.com:8026/builders/x86-alex%20canary/builds/1180/steps/VMTest/logs/stdio INFO: testUpdateWipeStateful: Performing a delta update from /b/cbuild/x86-alex-canary-master/src/scripts/latest_image/R17-1233.0.0-a1-b1178/chromiumos_qemu_image.bin to /b/cbuild/x86-alex-canary-master/src/build/images/x86-alex/latest-cbuildbot/chromiumos_test_image.bin in a VM INFO: testUpdateKeepStateful: Running smoke suite to verify image. INFO: testUpdateWipeStateful: Running smoke suite to verify image. Using a pre-created KVM instance specified by /tmp/kvm.9223. mktemp: failed to create directory via template `/tmp/ssh_test.XXXX': No space left on device Failed to connect to virtual machine, retrying ... Persist requested. Use --ssh_port 9223 --kvm_pid /tmp/kvm.9223 to re-connect to it. Using a pre-created KVM instance specified by /tmp/kvm.9223. mktemp: failed to create directory via template `/tmp/ssh_test.XXXX': No space left on device Failed to connect to virtual machine, retrying ... Persist requested. Use --ssh_port 9223 --kvm_pid /tmp/kvm.9223 to re-connect to it. Using a pre-created KVM instance specified by /tmp/kvm.9223. mktemp: failed to create directory via template `/tmp/ssh_test.XXXX': No space left on device Failed to connect to virtual machine, retrying ... Persist requested. Use --ssh_port 9223 --kvm_pid /tmp/kvm.9223 to re-connect to it. Using a pre-created KVM instance specified by /tmp/kvm.9223. mktemp: failed to create directory via template `/tmp/ssh_test.XXXX': No space left on device Persist requested. Use --ssh_port 9223 --kvm_pid /tmp/kvm.9223 to re-connect to it. Stopping the KVM instance ====================================================================== FAIL: Tests if we can update after cleaning the stateful partition. ----------------------------------------------------------------------
Oct 27, 2011
#1
js...@chromium.org
Cc:
hungte@chromium.org sosa@chromium.org dalecurtis@chromium.org cmasone@chromium.org
Oct 27, 2011
(No comment was entered for this change.)
Labels:
-Area-RelEng Area-Build
Oct 27, 2011
Is this different than http://crosbug.com/21659 and http://crosbug.com/21970 ?
Cc:
-cmasone@chromium.org
Oct 27, 2011
This looks a bit strange - so we're updating to a 'chromiumos_test_image' from a 'chromiumos_qemu_image' on a VM? Is that even supposed to work?
Oct 27, 2011
That does look like a space issue in /tmp on that machine (well specifically /buildroot/chroot/tmp wherever that's mounted) @rkc The update should work fine given the update is only updating the rootfs. Ideally we would update to the qemu image but there were some bugs around that originally and we had worked around to using the test image at the time. The space on the device, etc should already be set up from original qemu image.
Nov 1, 2011
Occurred again: http://chromeos-botmaster.mtv.corp.google.com:8026/builders/x86-alex%20canary/builds/1204
Nov 2, 2011
Who should be assigned to this bug?
Labels:
Mstone-R17
Nov 2, 2011
Given it's a builder issue maybe to Chrome-infra?
Nov 2, 2011
Filed crbug.com/102751 to track this.
Status:
Available
Nov 11, 2011
crbug.com/102751 was marked WontFix. Marking this as Won't Fix as well.
Nov 22, 2011
Actually marking as WontFix.
Status:
WontFix
Apr 6, 2012
(No comment was entered for this change.)
Labels:
-Mstone-R17 Mstone-17
Mar 6, 2013
(No comment was entered for this change.)
Labels:
OS-Chrome
Mar 9, 2013
(No comment was entered for this change.)
Labels:
-Area-Build -Team-BuildRelease -Mstone-17 M-17 Build
|
||||||||||||
| ► Sign in to add a comment | |||||||||||||