On Mon, 13 Jan 2025 14:42:04 GMT, Jaikiran Pai wrote:
>> Can I please get a review for this test-only change which proposes to skip
>> this test when the `main()` is launched through a virtual thread?
>>
>> This test was introduced in https://bugs.openjdk.org/browse/JDK-8233018 ,
>> before vir
There few compiler warning disabled in the testlibary build.
They should be fixed or localized and removed from build to prevent new
possible issues.
The main goal is to avoid new such issues in the testlibrary.
Tested with tier1-5 to ensure that all tests were passed.
-
Commit mes
> There few compiler warning disabled in the testlibary build.
> They should be fixed or localized and removed from build to prevent new
> possible issues.
>
> The main goal is to avoid new such issues in the testlibrary.
> Tested with tier1-5 to ensure that all tests we
> There few compiler warning disabled in the testlibary build.
> They should be fixed or localized and removed from build to prevent new
> possible issues.
>
> The main goal is to avoid new such issues in the testlibrary.
> Tested with tier1-5 to ensure that all tests we
On Thu, 16 Jan 2025 05:31:44 GMT, David Holmes wrote:
>> Leonid Mesnik has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> revert change
>
> test/lib/jdk/test/lib/format/ArrayDiff.java line 110:
>
&g
On Thu, 16 Jan 2025 07:09:46 GMT, Alan Bateman wrote:
>> Leonid Mesnik has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> revert change
>
> test/lib/jdk/test/lib/thread/VThreadPinner.java line 97:
>
>
On Thu, 16 Jan 2025 18:14:39 GMT, Leonid Mesnik wrote:
>> There few compiler warning disabled in the testlibary build.
>> They should be fixed or localized and removed from build to prevent new
>> possible issues.
>>
>> The main goal is to avoid new such issues
On Wed, 15 Jan 2025 23:48:33 GMT, Leonid Mesnik wrote:
> There few compiler warning disabled in the testlibary build.
> They should be fixed or localized and removed from build to prevent new
> possible issues.
>
> The main goal is to avoid new such issues in the testlibrary.
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
10 matches
Mail list logo
