Skip to content

K8s tests silently fail due to lack of pipe fail option being set #1626

@ianvernon

Description

@ianvernon
  • set pipe fail option in k8s test scripts
  • triage all master builds since commit 75b7d94 , which introduced this regression to see if there were any legitimate failures caused by merges to master. The reason that the aforementioned commit caused this failure is because it piped the debug output of the tests to tee, which masks the return code of the test running. This means that a test could fail, but the end result of piping to tee has a return code of zero, meaning the build thinks the tests passed just fine. This is a serious regression in the CI.
  • add a final test that checks the output from each test's debug file, to ensure that all tests indeed passed to avoid these regressions in the Bash scripts.

Metadata

Metadata

Assignees

Labels

priority/highThis is considered vital to an upcoming release.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions