JITTester often uses the `hasCode` method (in fact, in almost every generated
test). Given that the method can be unstable between runs or in interpreted vs
compiled runs, it can create false-positives.
This PR fixes the issue by adding support for method templates similar to the
ones used in C
On Mon, 8 Apr 2024 10:50:00 GMT, Evgeny Nikitin wrote:
> Improve RNG usage in said tests:
>
> 1. The RNG is not created by our Utils class, as suggested in our JTReg tests;
> 2. The seed, accordingly, is not a fixed value now, but truly random;
> 3. The tests that had been cre
Improve RNG usage in said tests:
1. The RNG is not created by our Utils class, as suggested in our JTReg tests;
2. The seed, accordingly, is not a fixed value now, but truly random;
3. The tests that had been creating their own Random instances, are now using
RAND static member from the AbstractV
in external processes' output and human-readable
> escaping of it;
Evgeny Nikitin has updated the pull request incrementally with one additional
commit since the last revision:
Ignore large files
-
Changes:
- all: https://git.openjdk.org/jdk/pull/12527/files
- new: https:/
Please review a set of improvements that should improve working with other
fuzzing generators and usage of JitTesterDriver with tests generated not by the
JITTester:
- Provide better separation of individual test generation from java file
writing, compiling, executing, etc.;
- Introduce distinc
On Thu, 24 Nov 2022 13:23:13 GMT, Claes Redestad wrote:
> When concatenating Strings, OutOfMemoryError should be thrown on all overflow
> conditions. This fixes a case that erroneously thro IAE on concatenations of
> long (`length > Integer.MAX_VALUE/2`) UTF16 strings due failing to check for
