Summary:
When the rebase destination has renamed a file, and copytrace failed to figure
out anything useful, make it possible to manually input the rename destination.
I'm using it to resolve conflicts caused by landing the bindings rename.
Reviewed By: xavierd
Differential Revision: D17367857
fbshipit-source-id: 55d9ed3a9641e40cc43518e9662fd803cbc00620
Summary:
Copytrace modified the global definitions table which was making it very difficult to keep track of side-effects as the code was executed, as well as making it harder to replace the fancyopts calls with native Rust.
Since the copytrace behavior can be achieved through a configuration, it now will no longer modify the global definitions table, and will display the correct flag for a user to use in order to get this same behavior.
Reviewed By: quark-zju
Differential Revision: D15902449
fbshipit-source-id: 1c254162d56823e65085b7047bb37513f187b487
Summary:
Those tests were converted using:
echo *.t | xargs -P20 -n1 python -m testutil.dott.translate --black --verify
They run 5x faster (via run-tests.py), and 10x faster (via python directly).
run-tests.py on old .t files, 652 CPU seconds:
% time ./run-tests.py `cat list-t.txt` --noprogress
.................................................................................................................................
# Ran 129 tests, 0 skipped, 0 failed.
./run-tests.py `cat list-t.txt` --noprogress 505.30s user 146.37s system 1451% cpu 44.899 total
run-tests.py on new py tests, 135 CPU seconds:
% time ./run-tests.py `cat list-py.txt` --noprogress
.............................................................................................................................
# Ran 125 tests, 0 skipped, 0 failed.
./run-tests.py `cat list-py.txt` --noprogress 55.73s user 78.80s system 744% cpu 18.061 total
vanilla python on new tests, 59 CPU seconds:
% time (for i in `cat list-py.txt`; do python $i; done;)
( for i in `cat list-py.txt`; do; python $i; done; ) 41.61s user 17.47s system 90% cpu 1:05.31 total
The new tests also have auto fix ability. `python test-foo-t.py --fix` will
autofix the code.
Reviewed By: xavierd
Differential Revision: D16172902
fbshipit-source-id: dda53990a7dfff5ac214c1237e4206a4d67e8e48
