-
Bug
-
Resolution: Not an Issue
-
P1
-
None
-
jt4.1
for example, execution of regression test sun/rmi/transport/proxy/MultipleContentLengthHeadersTest.java takes about 5 sec with jtreg 3 and about 2.5 min with jtreg 4.1
as work around option -status:fail or -noreport options can be used
we need to rerun failures, for example, to determine regressions; to check is failure reproducible only on current host/platform or not; -status:fail option assumes that tests should be rerun with the same res dir but usually we run tests via aurora and res dir located on hosts which are too far from out location; copying of res dir will take too long time
it is a regression, please fix it
as work around option -status:fail or -noreport options can be used
we need to rerun failures, for example, to determine regressions; to check is failure reproducible only on current host/platform or not; -status:fail option assumes that tests should be rerun with the same res dir but usually we run tests via aurora and res dir located on hosts which are too far from out location; copying of res dir will take too long time
it is a regression, please fix it