mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-09-26 01:27:53 +00:00
7c6873b23d
The hardware used for podman-machine testing is fairly stable/predictable because it's bare-metal. This is a nearly ideal environment for collection of benchmarking data. Arrange for that to happen, and the resulting data to be collected. Also keep track of the benchmark-basis details in a machine-readable `env` file along side the raw and parsed benchmarks. Signed-off-by: Chris Evich <cevich@redhat.com> |
||
|---|---|---|
| .. | ||
| 99-do-not-use-google-subnets.conflist | ||
| check_go_changes.sh | ||
| CIModes.md | ||
| cirrus_yaml_test.py | ||
| lib.sh | ||
| lib.sh.t | ||
| logcollector.sh | ||
| logformatter | ||
| logformatter.t | ||
| postbuild.sh | ||
| pr-removes-fixed-skips | ||
| pr-removes-fixed-skips.t | ||
| pr-should-include-tests | ||
| pr-should-include-tests.t | ||
| prebuild.sh | ||
| required_host_ports.txt | ||
| runner.sh | ||
| setup_environment.sh | ||
| swagger_stack_trace.png | ||
| timestamp.awk | ||
| win-installer-install.ps1 | ||
| win-installer-main.ps1 | ||
| win-podman-machine-verify.ps1 | ||
