Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

A test run should start with clean slate #648

Closed
msterin opened this issue Oct 26, 2016 · 1 comment
Closed

A test run should start with clean slate #648

msterin opened this issue Oct 26, 2016 · 1 comment
Assignees
@kerneltime
Labels
component/ci-infrastructure P0
Milestone
0.8 release

Comments

@msterin
Copy link
Contributor

msterin commented Oct 26, 2016

Since we serialize test runs on the same test bed, we should start each run as a clean slate.
This will prevent people being blocked by bug not related to current PR

We had many cases when a failed test for some PR was blocking other / unrelated PR CI runs.

The suggestion is to clean up all volumes at the end of each run. If there are some volumes to cleanup that indicates that a unit test or a test did not clean up - so we should YELL and fail a run if the cleanup was performed.
@msterin msterin added the P0 label Oct 26, 2016
@msterin msterin added this to the 0.8 release milestone Oct 26, 2016
@kerneltime
Copy link
Contributor

Related to #508

@kerneltime kerneltime mentioned this issue Nov 16, 2016
Merged
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Assignees

@kerneltime kerneltime

Labels
component/ci-infrastructure P0
Projects
None yet
Milestone
0.8 release
Development

No branches or pull requests
2 participants
@kerneltime @msterin