[CI/Build]Reduce the time consumption for LoRA tests #7396
Merged
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.
The current CI LoRA tests is quite time-consuming, which hampers the development of LoRA-related features. Based on testing on my local
single 3090, the three most time-consuming tests are:Therefore, I make the following modifications:
test_punica_variationandtest_punica_sizes, I reduce the number of test items as much as possible without impacting the test scope.test_layer_variationdirectly, there are two main reasons:PEFTinitializes LoRA weights by setting lora_b weights to zero, this may prevent it from achieving its intended test effects.Additionally, I clean up some redundant code.
ping @Yard1 @simon-mo