kubernetes/test/e2e/upgrades
Patrick Ohly 136f89dfc5 e2e: use error wrapping with %w
The recently introduced failure handling in ExpectNoError depends on error
wrapping: if an error prefix gets added with `fmt.Errorf("foo: %v", err)`, then
ExpectNoError cannot detect that the root cause is an assertion failure and
then will add another useless "unexpected error" prefix and will not dump the
additional failure information (currently the backtrace inside the E2E
framework).

Instead of manually deciding on a case-by-case basis where %w is needed, all
error wrapping was updated automatically with

    sed -i "s/fmt.Errorf\(.*\): '*\(%s\|%v\)'*\",\(.* err)\)/fmt.Errorf\1: %w\",\3/" $(git grep -l 'fmt.Errorf' test/e2e*)

This may be unnecessary in some cases, but it's not wrong.
2023-02-06 15:39:13 +01:00
..
apps e2e: use error wrapping with %w 2023-02-06 15:39:13 +01:00
auth e2e: use error wrapping with %w 2023-02-06 15:39:13 +01:00
autoscaling e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
network e2e: use error wrapping with %w 2023-02-06 15:39:13 +01:00
node e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
storage e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
upgrade_suite.go e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00
upgrade.go e2e: use Ginkgo context 2022-12-16 20:14:04 +01:00