8u352 regression: segfaults around javadoc

[Thorsten Glaser]

Hi,

in a second attempt, 7 (wheezy) again failed, again in javadoc,
but 11 (bullseye) built; unstable is still building for a couple
of hours because it tries the tests (even if some are known to
fail).

This kind of fragility is… not reassuring.

I can think of one possible cause that would make sense. Does
anything in the tests influence other Java processes on the same
machine? The build chroots are just that and also run as the same
Unix user, so they’re not isolatted from each other (on my machine;
those official Debian build machines that run more than one instance
hopefully isolate more but I build on my dev tower).

… otoh, even that’d not explain the SIGSEGV now, would it?

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

                        ****************************************************
/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against      Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also,     https://www.tarent.de/newsletter
╱ ╲ header encryption!
                        ****************************************************