Skip to main content

Browse the archive

Revision 3446ec2b6020af2c8481fef379ebbdcbd04e9959 authored by Paul Chaignon on 21 April 2023, 11:46:42 UTC, committed by Nick Young on 26 July 2023, 01:02:34 UTC 
test: Print error messages in case of failure
 
[ upstream commit 67a3ab3533a7f77aa4241c0da6b04f5b31da9af9 ]

[ Backporter's notes: the changes had to be manually backported to the
  appropriate files for v1.11, as they were renamed in
  ffd7e57b377f982fb57cf574564b7f1debef74a4 since then.

  (main > v1.11)
  test/k8s/datapath_configuration.go > test/k8sT/DatapathConfiguration.go
]

If we check res.WasSuccessful() instead of res, then ginkgo won't print
the error message in case the command wasn't successful.

Signed-off-by: Paul Chaignon <paul@cilium.io>
Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
1 parent 0470ee5
Raw File
CONTRIBUTING.md 
# How to Contribute

See the [Developer / Contributor
Guide](https://docs.cilium.io/en/stable/contributing/development/contributing_guide/) for detailed information on
how to contribute, get started and find good first issues.
back to top