On Thu, 8 May 2025 14:51:24 GMT, Leo Korinth wrote:
> This change tries to add timeout to individual testcases so that I am able to
> run them with a timeout factor of 1 in the future (JDK-8260555).
>
> The first commit changes the timeout factor to 0.7, so that I can run tests
> and test the
On Thu, 8 May 2025 16:43:10 GMT, Leo Korinth wrote:
>> This change tries to add timeout to individual testcases so that I am able
>> to run them with a timeout factor of 1 in the future (JDK-8260555).
>>
>> The first commit changes the timeout factor to 0.7, so that I can run tests
>> and test
On Thu, 8 May 2025 17:03:03 GMT, Leo Korinth wrote:
>> doc/testing.md line 385:
>>
>>> 383: (`-timeoutFactor`). Also, some test cases that programmatically wait a
>>> 384: certain amount of time will apply this factor. If we run in
>>> 385: interpreted mode (`-Xcomp`), [RunTest.gmk](../make/RunT
On Thu, 8 May 2025 14:51:24 GMT, Leo Korinth wrote:
> This change tries to add timeout to individual testcases so that I am able to
> run them with a timeout factor of 1 in the future (JDK-8260555).
>
> The first commit changes the timeout factor to 0.7, so that I can run tests
> and test the
This change tries to add timeout to individual testcases so that I am able to
run them with a timeout factor of 1 in the future (JDK-8260555).
The first commit changes the timeout factor to 0.7, so that I can run tests and
test the change (it will finally be changed to 1.0 in JDK-8260555). The n
On Thu, 8 May 2025 14:51:24 GMT, Leo Korinth wrote:
> This change tries to add timeout to individual testcases so that I am able to
> run them with a timeout factor of 1 in the future (JDK-8260555).
>
> The first commit changes the timeout factor to 0.7, so that I can run tests
> and test the
On Thu, 8 May 2025 16:04:53 GMT, Stefan Karlsson wrote:
>> This change tries to add timeout to individual testcases so that I am able
>> to run them with a timeout factor of 1 in the future (JDK-8260555).
>>
>> The first commit changes the timeout factor to 0.7, so that I can run tests
>> and
On Thu, 8 May 2025 14:51:24 GMT, Leo Korinth wrote:
> This change tries to add timeout to individual testcases so that I am able to
> run them with a timeout factor of 1 in the future (JDK-8260555).
>
> The first commit changes the timeout factor to 0.7, so that I can run tests
> and test the
On Thu, 8 May 2025 14:51:24 GMT, Leo Korinth wrote:
> This change tries to add timeout to individual testcases so that I am able to
> run them with a timeout factor of 1 in the future (JDK-8260555).
>
> The first commit changes the timeout factor to 0.7, so that I can run tests
> and test the
On Thu, 8 May 2025 14:51:24 GMT, Leo Korinth wrote:
> This change tries to add timeout to individual testcases so that I am able to
> run them with a timeout factor of 1 in the future (JDK-8260555).
>
> The first commit changes the timeout factor to 0.7, so that I can run tests
> and test the
On Thu, 8 May 2025 15:07:15 GMT, Chen Liang wrote:
>> Please review this patch to fix a bug where a method can be documented
>> multiple times
>> Consider these 4 classes
>>
>> A (interface)
>>/ \
>> / \
>> (abstract class) C
On Thu, 8 May 2025 14:53:41 GMT, Nizar Benalla wrote:
> Please review this patch to fix a bug where a method can be documented
> multiple times
> Consider these 4 classes
>
> A (interface)
>/ \
> / \
> (abstract class) C B
Please review this patch to fix a bug where a method can be documented multiple
times
Consider these 4 classes
A (interface)
/ \
/ \
(abstract class) C B ( interface)
\ /
\ /
13 matches
Mail list logo
