You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If create_clone is called before case.setup is called on a case bad things can happen.
For example #1272 where the second case does not have the pio_typename set correctly.
I think that the correct action for this is to require case_setup is called on case1 before create_clone can be.
This would require refactoring the system_tests_compare_two script so that case1 setup is done before the case clone.
The text was updated successfully, but these errors were encountered:
No this wouldn't solve the problem: The problem is that the PIO_TYPENAME valid_values is set during the build phase depending on what supporting libraries pio found during it's build. If create_clone is run prior to the first case being built AND --keepexe is used then the second case is never required to do a build and so the valid_values list for pio_typename is not updated. When the case1 build is done there is no way to know that more than one case depends on the build and so no way to update clones with the correct valid_values.
avoid a problem with pio_typename in clone with keepexe
Print a warning if create_clone is run before case1 is built. Add code to system_tests_compare_two to update pio_typename in case2 after case1 build is complete.
Test suite: scripts_regression_tests
Test baseline:
Test namelist changes:
Test status: bit for bit
Fixes#1304
User interface changes?:
Code review: @gold2718@billsacks@mvertens
If create_clone is called before case.setup is called on a case bad things can happen.
For example #1272 where the second case does not have the pio_typename set correctly.
I think that the correct action for this is to require case_setup is called on case1 before create_clone can be.
This would require refactoring the system_tests_compare_two script so that case1 setup is done before the case clone.
The text was updated successfully, but these errors were encountered: