gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2020-04-21	benchmarks: use absolute bazel target	Michael Pratt
	bazel run :benchmarks only works from the benchmarks directory. bazel run //benchmarks works from anywhere in the workspace. Also fix help commands, which should be a multiline code section.
2020-02-17	Add flag to run without building baked images.	gVisor bot
	Adds flag to :benchmarks to allow running without building "baked images", which depends on gcloud. Users can skip gcloud workflows using the following: blaze run --define gcloud=off :benchmarks -- my-command-without-gcloud "run-gcp" will not work with the flag set, but all other commands will. PiperOrigin-RevId: 295627718
2020-02-06	Add logic to run from baked images.	Zach Koopmans
	Change adds the following: - logic to run from "baked images". See [GVISOR_DIR]/tools/images - installers which install modified files from a workspace. This allows users to run benchmarks while modifying runsc. - removes the --preemptible tag from built GCE instances. Preemptible instances are much more likely to be preempted on startup, which manifests for the user as a failed benchmark. I don't currently have a way to detect if a VM has been preempted that will work for this change. https://cloud.google.com/compute/docs/instances/preemptible#preemption_process https://cloud.google.com/compute/docs/instances/preemptible#preemption_selection PiperOrigin-RevId: 293697949
2020-01-15	Update commandline and get local runs working.	Zach Koopmans
	PiperOrigin-RevId: 289937063
2019-12-02	Import benchmark-tools to main repository.	Zach Koopmans
	This has adapted for use with bazel from the original commit a26e93769ebefd82593a43e22fb13a09717cfa6d. In particular, the style has been made consistent with internal python style guidelines, and the packages (including the main entrypoint) have been refactored in order to allow bazel testing targets. PiperOrigin-RevId: 283484433