diff options
| author | Chris Evich <cevich@redhat.com> | 2020-02-24 11:21:15 -0500 |
|---|---|---|
| committer | Chris Evich <cevich@redhat.com> | 2020-02-25 12:34:26 -0500 |
| commit | 9b9789c207d8b84ee37e9c37c613879369a8690c (patch) | |
| tree | 1bfcbdc98cfbcd82b6c2ec769b7ea529d2131cee /test/e2e/run_memory_test.go | |
| parent | 5973641404066dd5c1c66b41ff7f397490d80285 (diff) | |
| download | podman-9b9789c207d8b84ee37e9c37c613879369a8690c.tar.gz podman-9b9789c207d8b84ee37e9c37c613879369a8690c.tar.bz2 podman-9b9789c207d8b84ee37e9c37c613879369a8690c.zip | |
Fix cgroupsv2 run test, unexpected output
Sometime between 10th and 23rd of Feb. 2020, the behavior of crun
changed. Upon consulting with Giuseppe, the podman run tests for
`device-read-*` and `device-write-*` do not depend on the container
output for success, only the exit code. Add a comment and conditional
regarding this in case of cgroupsv2. Also noted that these tests
will likely require future refactoring/simplification.
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'test/e2e/run_memory_test.go')
| -rw-r--r-- | test/e2e/run_memory_test.go | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/test/e2e/run_memory_test.go b/test/e2e/run_memory_test.go index a45735a8a..d60f2a8cd 100644 --- a/test/e2e/run_memory_test.go +++ b/test/e2e/run_memory_test.go @@ -70,7 +70,11 @@ var _ = Describe("Podman run memory", func() { session.WaitWithDefaultTimeout() Expect(session.ExitCode()).To(Equal(0)) - Expect(session.OutputToString()).To(Equal("41943040")) + if cgroupsv2 { + Expect(session.OutputToString()).To(Equal("max")) + } else { + Expect(session.OutputToString()).To(Equal("41943040")) + } }) It("podman run memory-swappiness test", func() { |