Skip to content

tests: make test pool names more collision resistant #978

@bmr-cymru

Description

@bmr-cymru

We currently call out test pools "pool0" (lvm2thin), and "pool1" (stratis), which is very imaginative, and probably could be better.

We have never had problems with this but let's consider making these something like "lvm_test_pool" and "stratis_test_pool" or similar.

Both have constants in tests/_util.py but there are also places in the test suite that hard code these values (those could—and probably should—be easily eliminated), so a little manual checking is needed. The emergency cleanup script (tests/bin/cleanup.sh) would also need updating.

Metadata

Metadata

Assignees

Type

No fields configured for Task.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions