
V Mon, 3 Sep 2018 12:31:52 +0000 Arvin Schnell <aschnell@suse.com> napsáno:
On Thu, Aug 16, 2018 at 04:33:56PM +0200, Stefan Hundhammer wrote:
Test results:
rake test:unit in yast-storage-ng took 22:30 (yes, 22 min 30 sec!) on my machine before that.
Using parallel tests reduced this to 4:50. The code and the tests were running on a local XFS filesystem, not on NFS.
Moving the y2log from my NFS home to that local XFS reduced it to 0:37 (!!).
Redirecting the y2log to /dev/null reduced it to 0:31 (!!).
This is as simple as
export Y2LOG_FILE=/dev/null
Y2SLOG_FILE is the right variable (who knows why).
rake test:unit
or, for just that one call,
Y2LOG_FILE=/dev/null rake test:unit
This is really worthwhile.
Thanks, that is indeed worthwhile.
In general I would expect a testsuite to generate a logfile per test in the local directory. Otherwise finding the log for a single test seems almost impossible.
ciao Arvin
Just hint. When I need to inspect specific test, I usually do something like rm ~/.y2log and then rspec <my_test.rb>:<line of failing test> so e.g. rspec bootloader_test.rb:140 adn this writes only logs for the specific test. It works also for e.g. context block. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org