summaryrefslogtreecommitdiff
path: root/test/e2e/run_cpu_test.go
diff options
context:
space:
mode:
authorbaude <bbaude@redhat.com>2018-02-05 09:29:46 -0600
committerAtomic Bot <atomic-devel@projectatomic.io>2018-02-05 15:41:06 +0000
commit910baf433fdbc6ad6d85cfeacb5ccc59b37aa634 (patch)
treefb8b711f8af61b1657f032a48d527fae3981fda6 /test/e2e/run_cpu_test.go
parent989f5e30627eb90a66fa06f87c40d161476395ed (diff)
downloadpodman-910baf433fdbc6ad6d85cfeacb5ccc59b37aa634.tar.gz
podman-910baf433fdbc6ad6d85cfeacb5ccc59b37aa634.tar.bz2
podman-910baf433fdbc6ad6d85cfeacb5ccc59b37aa634.zip
Deprecate --format for podman top
Issue #169 describes a common failure when running podman top where if the commands inside the container container a space in them, podman will panic. This was occuring because we take the output from ps and attempt to format it nicely for output and things like JSON. Given that this cannot be predicted or dealt with programatically, the decision was made to deprecate the format switch and simply output what ps provides us. Migrated top integration tests to ginkgo. Resolves Issue: https://github.com/projectatomic/libpod/issues/169 Signed-off-by: baude <bbaude@redhat.com> Closes: #291 Approved by: rhatdan
Diffstat (limited to 'test/e2e/run_cpu_test.go')
0 files changed, 0 insertions, 0 deletions