On Thu, Jan 2, 2020 at 11:35 AM Daniel Shahaf <d.s_at_daniel.shahaf.name>
wrote:
> Nathan Hartman wrote on Thu, Jan 02, 2020 at 10:45:25 -0500:
> > Regarding the one test failure I had (autoprop_tests.py 7 with
> > [svn x bdb]), I've had two more since, both with bdb. These are
> > intermittent database errors and occur in varying places. (All fsfs
> > tests have passed every time.)
>
> Actually, all three backtraces so far are in sbox.build(), so something
> like
> this might be useful:
>
> [[[
> Index: subversion/tests/cmdline/basic_tests.py
> ===================================================================
> --- subversion/tests/cmdline/basic_tests.py (revision 1871981)
> +++ subversion/tests/cmdline/basic_tests.py (working copy)
> @@ -3319,6 +3319,7 @@
> null_prop_update_last_changed_revision,
> filtered_ls_top_level_path,
> ]
> +test_list = [ None ] + [ lambda sbox: sbox.build() ] * 2000
>
> if __name__ == '__main__':
> svntest.main.run_tests(test_list)
> ]]]
>
> … then pass «TESTS="subversion/tests/cmdline/basic_tests.py"» to make.
>
> (I didn't test that patch, so it might complain about a missing __doc__
> attribute, but you get the idea.)
>
> Cheers,
>
> Daniel
> (And you can use «operator.methodcaller('build')» to squeeze a few more
> cycles there)
I'm a bit confused here. Yes, the Python backtraces show it coming from
sbox.build but aren't these being instigated by the BDB errors/panics
(which are reported as a E160029)?
Thanks,
Nathan
Received on 2020-01-02 18:44:51 CET