summaryrefslogtreecommitdiff
path: root/vendor/go.etcd.io/bbolt/bolt_ppc.go
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2020-10-05 13:22:34 -0400
committerChris Evich <cevich@redhat.com>2020-10-05 13:32:26 -0400
commit81c0bb4b6bc0a8392c299a63fb4480d1a132d09b (patch)
treeac52bdf93dd6c8dd0521519b156bf38b2b9e05ce /vendor/go.etcd.io/bbolt/bolt_ppc.go
parent1b16fcfd14b9e761849e53ac2b83c964ad8ac5a9 (diff)
downloadpodman-81c0bb4b6bc0a8392c299a63fb4480d1a132d09b.tar.gz
podman-81c0bb4b6bc0a8392c299a63fb4480d1a132d09b.tar.bz2
podman-81c0bb4b6bc0a8392c299a63fb4480d1a132d09b.zip
Cirrus: Skip deep testing on branches
Previous to this commit, the entire suite of CI tasks run in a PR, run again for every merge (a.k.a. branch push). This wastes time and resources with substantively overlapping testing. The primary reason to test on branch-push, is providing coverage for merge-semantics. In other words, problems introduced due to the sequence of PR merging. For this purpose, the vast majority of problems can be caught quickly by a small subset of automated tests. If deeper debugging is necessary, then opening a test-PR is a small price to ask for the enormous amount of time/resource savings with more limited branch-push testing. Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'vendor/go.etcd.io/bbolt/bolt_ppc.go')
0 files changed, 0 insertions, 0 deletions