Improve the futurize tests
run_futurize is running the futurize tests for the daily report.
The script is rough and is not providing the option to have details about the files that need to be refactored and which are the changes. This is important for a quick verification of new branches.
#1 Updated by Marco Mambelli almost 2 years ago
- Status changed from New to Feedback
- Assignee changed from Marco Mambelli to Dennis Box
changes are in v3/19109
Is a new version of run_futurize, more user-friendly and w/ more options
Once this code is committed this new version will be used for the CI tests so diffs will be available in the log files
$filename -i [other options] LOG_DIR Runs the Futurize tests on the current glideinwm subdirectory. No branch is checked out. $filename [options] BRANCH_NAMES LOG_DIR Runs Futurize tests in the glideinwms repository (a glidienwms subdirectory with the git repository must exist). Tests are run on each of the branches in the list. Test results are saved in LOG_DIR Note that the script is checking out the branch and running the tests. It is not cleaning up or restoring to the initial content. For something less intrusive use '-i' option to run in place without changing any source file. BRANCH_NAMES Comma separated list of branches that needs to be inspected (from glideinwms git repository) LOG_DIR Directory including log files -v verbose -h print this message -2 runs futurize stage 2 tests (default is stage 1) -l list files that need to be refactored -d print diffs about the refactoring