Skip to content

Commit

Permalink
Delete Cilium monitor verbose mode test
Browse files Browse the repository at this point in the history
[ upstream commit 7335aa3 ]

Another option would be to quarantine the test and find an assignee to
make the test more robust, but I assert that we don't need test coverage
for monitor verbose output.

Fixes: cilium#25178

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>
Signed-off-by: Yutaro Hayakawa <yutaro.hayakawa@isovalent.com>
  • Loading branch information
michi-covalent authored and YutaroHayakawa committed May 10, 2023
1 parent 7d0c1ec commit 9c109ff
Showing 1 changed file with 0 additions and 21 deletions.
21 changes: 0 additions & 21 deletions test/runtime/monitor.go
Original file line number Diff line number Diff line change
Expand Up @@ -101,27 +101,6 @@ var _ = Describe("RuntimeMonitorTest", func() {
ExpectWithOffset(1, res.WasSuccessful()).To(BeTrue(), "cannot update monitor config")
}

It("Cilium monitor verbose mode", func() {
monitorConfig()

ctx, cancel := context.WithCancel(context.Background())
res := vm.ExecInBackground(ctx, "cilium monitor -vv")
defer cancel()

Expect(vm.WaitEndpointsReady()).Should(BeTrue(), "Endpoints are not ready after timeout")

endpoints, err := vm.GetEndpointsIds()
Expect(err).Should(BeNil())

for k, v := range endpoints {
filter := fmt.Sprintf("FROM %s DEBUG:", v)
vm.ContainerExec(k, helpers.Ping(helpers.Httpd1))
Expect(res.WaitUntilMatch(filter)).To(BeNil(),
"%q is not in the output after timeout", filter)
Expect(res.Stdout()).Should(ContainSubstring(filter))
}
})

It("Cilium monitor event types", func() {
monitorConfig()

Expand Down

0 comments on commit 9c109ff

Please sign in to comment.