2013/5/10  <ryan / ruby-lang.org>:
> ryan    2013-05-10 09:55:03 +0900 (Fri, 10 May 2013)
>
>   New Revision: 40628
>
>   http://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=rev&revision=40628
>
>   Log:
>     Fixed minitest dependency bug by removing env PARALLEL checks (no clue why that was there). Exactly the same minitest code tho.

This change breaks line-by-line structure of the test results in verbose mode.

For example I can see following results.

TestMiniTestMock#test_not_verify_if_new_expected_method_is_not_called
= 0.00 s = .
TestMiniTestMock#test_assign_per_mock_return_values =
TestMiniTestMock#test_mock_is_a_blank_slate = 0.00 s = 0.00 s = .
.TestMiniTestMock#test_verify_allows_called_args_to_be_loosely_specified =
0.00 s = .TestMiniTestMock#test_expect_with_non_array_args =
0.00 s = .
TestMiniTestRunner#test_run_failing = 0.01 s = .
TestMiniTestRunner#test_run_skip_verbose = 0.01 s = .

http://www.rubyist.net/~akr/chkbuild/debian/ruby-trunk/log/20130510T015500Z.log.html.gz

This make the result very difficult to process automatically.

In my case, chkbiuld (my continuous integration) compares build log between
previous build and next build line-by-line.

This line-by-line structure breakage caused useless changes hunks as follows.

http://www.rubyist.net/~akr/chkbuild/debian/ruby-trunk/log/20130510T015500Z.diff.html.gz

Is there any way to preserve line-by-line structure in the results?
-- 
Tanaka Akira