image_to_vm.sh broken?

[n00dles]

Hi all,

Having some weird issues with image_to_vm, basically I get the
following error when trying to run it

ERROR : script called: ./image_to_vm.sh '--format=vmware' '--
board=x86-generic'
ERROR : Backtrace: (most recent call is last)
ERROR : file image_to_vm.sh, line 122, called: die_err_trap
'TEMP_DIR=$(mktemp -d)' '1'
ERROR :
ERROR : Command failed:
ERROR : Command 'TEMP_DIR=$(mktemp -d)' exited with nonzero code:
1
ERROR : (Note bash sometimes misreports "command not found" as
exit code 1 instead of 127)


Strangely, setting TEMP_DIR statically gives the same result. Any
ideas?

[Mike Frysinger]

works for me. you're running this inside the chroot right ?

what do you see if you run:
mktemp; echo $?
or if you run:
mktemp -d; echo $?
-mike

[n00dles]

hi mike,

yeh running the the chroot. i'm sure it is me, although everything
else (builds, image_to_usb) seems to be working fine.

The mktemp command itself is working if i just run it, i see a file
(or directory with -d) get created and it exits 0. I also get
directories created when i execute the script, but it still bombs out
with that err.

The build release i end up with is R21-2278 if it makes a diff. Maybe
I'll just wipe everything and try again.

[mbb]

Hi, I'm having this same issue, how did you end up resolving this?

[Aaron]

[Aaron]

Not sure if you've resolved this. My case is if I build test image, image_to_vm fails this way. It works for dev image.  

[Mike Frysinger]

someone else just hit this bug, and it wasn't actually mktemp failing.
they didn't have a .bin image to convert, and the bash backtrace
reported the wrong line (one earlier than the actual failing point).

in the future, please post the *full* output and not just the ending
snippet when something fails. keeps us from chasing our tails.
-mike

> --
> Chromium OS discuss mailing list: chromium-...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-discuss?hl=en

[Chris Masone]

The short version is that I called 'build_image test', which makes a test image instead of a standard image.  image_to_vm.sh has an option (--test_image) that the help claims "Copies normal image to chromiumos_test_image.bin, modifies it for test. (default: false)"

This will also, it turns out, magically find your existing test image and just use it.

[Chris Sosa]

On Wed, Aug 22, 2012 at 9:30 AM, Chris Masone <cma...@chromium.org> wrote:
> The short version is that I called 'build_image test', which makes a test
> image instead of a standard image. image_to_vm.sh has an option
> (--test_image) that the help claims "Copies normal image to
> chromiumos_test_image.bin, modifies it for test. (default: false)"

Yeah, this isn't ideal. I'll be sending out a doc for a re-write of a
lot of these build scripts to have a consistent user experience within
the week. Stay tuned.

-Sosa