git.madduck.net Git - etc/vim.git/commit

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

author	Richard Si <63936253+ichard26@users.noreply.github.com>
	Sat, 8 May 2021 09:34:25 +0000 (05:34 -0400)
committer	GitHub <noreply@github.com>
	Sat, 8 May 2021 09:34:25 +0000 (11:34 +0200)
commit	036bea4aa0e2b9b3fe50d0d49addc811cce61fa4
tree	00f8304ce1f887c3ed1eb2aac2196a1064485eee	tree \| snapshot
parent	f2ea461e9e9fa5c47bb61fd72d512c748928badc	commit \| diff

Speed up tests even more (#2205)

There's three optimizations in this commit:

1. Don't check if Black's output is stable or equivalant if no changes
   were made in the first place. It's not like passing the same code
   (for both source and actual) through black.assert_equivalent or
   black.assert_stable is useful. It's not a big deal for the smaller
   tests, but it eats a lot of time in tests/test_format.py since
   its test cases are big. This is also closer to how Black works IRL.

2. Use a smaller file for `test_root_logger_not_used_directly` since
   the logging it's checking happens during blib2to3's startup so the
   file doesn't really matter.

3. If we're checking a file is formatting (i.e. test_source_is_formatted)
   don't run Black over it again with `black.format_file_in_place`.
   `tests/test_format.py::TestSimpleFormat.check_file` is good enough.

tests/test_black.py		diff \| blob \| history
tests/test_format.py		diff \| blob \| history

madduck's git repository

Legalese