On Fri, 27 Jun 2025 07:51:54 GMT, Henry Jen wrote:
>> Create a jar directly from the memory instead of real file, this should
>> reduce the I/O overhead which likely the reason for the time out.
>> The issue is not reproducible locally, and fails intermittently, so we
>> simply trying to reduce
> Create a jar directly from the memory instead of real file, this should
> reduce the I/O overhead which likely the reason for the time out.
> The issue is not reproducible locally, and fails intermittently, so we simply
> trying to reduce time needed.
> The jar file created is verified manually
On Fri, 27 Jun 2025 04:59:58 GMT, Henry Jen wrote:
>> Create a jar directly from the memory instead of real file, this should
>> reduce the I/O overhead which likely the reason for the time out.
>> The issue is not reproducible locally, and fails intermittently, so we
>> simply trying to reduce
On Fri, 27 Jun 2025 06:28:32 GMT, Eirik Bjørsnøs wrote:
>> Henry Jen has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Adapt review feedbacks
>
> test/jdk/tools/jlink/JLink2Packages.java line 130:
>
>> 128: /**
>> 129: * Gene
On Fri, 27 Jun 2025 06:38:06 GMT, Henry Jen wrote:
>> test/jdk/tools/jlink/JLink2Packages.java line 130:
>>
>>> 128: /**
>>> 129: * Generate test class with main() does
>>> 130: * System.out.println("JLink2PackagesTest started.");
>>
>> The test currently does not use this
On Fri, 27 Jun 2025 04:59:58 GMT, Henry Jen wrote:
>> Create a jar directly from the memory instead of real file, this should
>> reduce the I/O overhead which likely the reason for the time out.
>> The issue is not reproducible locally, and fails intermittently, so we
>> simply trying to reduce
> Create a jar directly from the memory instead of real file, this should
> reduce the I/O overhead which likely the reason for the time out.
> The issue is not reproducible locally, and fails intermittently, so we simply
> trying to reduce time needed.
> The jar file created is verified manually
On Thu, 26 Jun 2025 06:16:06 GMT, Henry Jen wrote:
>> Create a jar directly from the memory instead of real file, this should
>> reduce the I/O overhead which likely the reason for the time out.
>> The issue is not reproducible locally, and fails intermittently, so we
>> simply trying to reduce
On Thu, 26 Jun 2025 06:16:06 GMT, Henry Jen wrote:
>> Create a jar directly from the memory instead of real file, this should
>> reduce the I/O overhead which likely the reason for the time out.
>> The issue is not reproducible locally, and fails intermittently, so we
>> simply trying to reduce
On Thu, 26 Jun 2025 06:56:17 GMT, Eirik Bjørsnøs wrote:
> For these simple class files I would assume using the class file API to
> generate the class files directly without involving javac at all would both
> simplify this test and run faster.
Here's a branch on top of your PR with an explora
On Thu, 26 Jun 2025 06:16:06 GMT, Henry Jen wrote:
>> Create a jar directly from the memory instead of real file, this should
>> reduce the I/O overhead which likely the reason for the time out.
>> The issue is not reproducible locally, and fails intermittently, so we
>> simply trying to reduce
On Thu, 26 Jun 2025 06:16:06 GMT, Henry Jen wrote:
>> Create a jar directly from the memory instead of real file, this should
>> reduce the I/O overhead which likely the reason for the time out.
>> The issue is not reproducible locally, and fails intermittently, so we
>> simply trying to reduce
> Create a jar directly from the memory instead of real file, this should
> reduce the I/O overhead which likely the reason for the time out.
> The issue is not reproducible locally, and fails intermittently, so we simply
> trying to reduce time needed.
> The jar file created is verified manually
On Thu, 26 Jun 2025 01:48:33 GMT, Henry Jen wrote:
>> Create a jar directly from the memory instead of real file, this should
>> reduce the I/O overhead which likely the reason for the time out.
>> The issue is not reproducible locally, and fails intermittently, so we
>> simply trying to reduce
> Create a jar directly from the memory instead of real file, this should
> reduce the I/O overhead which likely the reason for the time out.
> The issue is not reproducible locally, and fails intermittently, so we simply
> trying to reduce time needed.
> The jar file created is verified manually
On Wed, 25 Jun 2025 14:38:03 GMT, Henry Jen wrote:
> Create a jar directly from the memory instead of real file, this should
> reduce the I/O overhead which likely the reason for the time out.
> The issue is not reproducible locally, and fails intermittently, so we simply
> trying to reduce tim
Create a jar directly from the memory instead of real file, this should reduce
the I/O overhead which likely the reason for the time out.
The issue is not reproducible locally, and fails intermittently, so we simply
trying to reduce time needed.
The jar file created is verified manually running j
17 matches
Mail list logo
