mirror of
https://github.com/flatcar/scripts.git
synced 2025-08-09 14:06:58 +02:00
d1679ab864
Right now, output directories are hardcoded in boot.desc. This means that
cros_make_image_bootable will still write to the directories mentioned in
build_image, even if it's working on a different directory. This can
mess with the buildbot, because it can cause cros_make_image_bootable
to mess with the files created for existing images.
This change fixes flaky failures where the buildbot fails with warnings
stating that vmlinuz_hd.vblock does not exist. See bug 19956.
BUG=chromium-os:19956
TEST=Run full canary trybot run and verify cros_make_image_bootable uses
files from the right directory now.
Change-Id: Ib390aa84570b077cbc8b69b757998056acc091ea
Reviewed-on: http://gerrit.chromium.org/gerrit/7282
Reviewed-by: Will Drewry <wad@chromium.org>
Tested-by: David James <davidjames@chromium.org>
|
||
|---|---|---|
| .. | ||
| cros_au_test_harness | ||
| cros_get_chrome_version | ||
| cros_image_to_target.py | ||
| cros_make_image_bootable | ||
| cros_package_to_live | ||
| cros_resign_image.sh | ||
| cros_revert_image.sh | ||
| cros_run_parallel_vm_tests | ||
| cros_run_vm_test | ||
| cros_run_vm_update | ||
| cros_run_wifi_tests.sh | ||
| cros_sign_to_ssd | ||
| cros_start_vm | ||
| cros_stop_vm | ||
| cros_update_image.sh | ||
| cros_workon_make | ||
| ctest | ||
| loman | ||
| loman_unittest.py | ||
| loman.py | ||