Shard migration: Migrate cnf-testsuite org shards to main testsuite #2226
+192
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
require
statements) and delete cnf-testsuite org shards fromshard.yaml
.We have come to the conclusion that the shards should be moved to
src/modules/<shard_name>/...
, please comment if you know of a better placement.The pull request is currently being blocked by #2221 and a future(?) cluster_tools pull request change, once these are done, we can proceed with moving them to main testsuite project.
Any major code refactors are subject to future pull requests, this is only migration.
Change log:
tar
(found out that due to duplicity conflicts between/lib
andsrc/modules
, the code breaks, thus we cannot merge until all shards are resolved). View this actions run for further info.find
shard absorbed intotar
(specificallytar_spec.cr
, since thefind
shard only had a single function and it was only used in the spec tests oftar
).Issues:
Refs: #2219
How has this been tested:
Types of changes:
Checklist:
Documentation
Code Review
Issue