test-appliance: wait for set-disk-auto-delete to complete

In gce-setup-scratch, we need to wait for the command to set the
scratch disk for auto-deletion.  Otherwise the gce-setup-scratch
script will often finish first, and this will cause the
set-disk-auto-delete commant to get killed prematurely.

Also save the gce-setup-* log files in /var/log instead of /results,
since most of the time we don't need to keep them in the archived
results tarfiles.

Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2 files changed
tree: 02567c5390a81d74cebe4a242d96624902529c2b
  1. .dockerignore
  2. .gitignore
  3. .travis.yml
  4. COPYING
  5. Dockerfile
  6. Documentation/
  7. Makefile
  8. README.md
  9. acl/
  10. android-compat/
  11. attr/
  12. build-all
  13. config
  14. config.docker
  15. dbench/
  16. do-all
  17. do-update
  18. e2fsprogs-libs/
  19. gen-tarball
  20. get-all
  21. get-versions
  22. kernel-configs/
  23. kvm-xfstests/
  24. libaio/
  25. misc/
  26. popt/
  27. setup-buildchroot
  28. update-all
README.md

xfstests-bld

The xfstests-bld project was originally designed as system to make it easy to build xfstests in way that isolated it from the versions of various libraries such as libaio, xfsprogs, that were available in a particular distribution. It has since evolved to have four primary functions:

More details about how to use xfstests-bld to carry out these three functions can be found in the Documentation directory.

If you are first getting started using xfstests, you should probably read the Quickstart guide first. If you don't know much about xfstests, you may also want to read this introduction to xfstests.

License

The xfstests-bld project has been made available under the terms of the GNU General Public License, version 2. A copy can be found in the file named COPYING in the distribution.