25119a7e78
The JVM caches `Integer` objects. This is known. A test in Painless was relying on the JVM not caching the particular integer `1000`. It turns out that when you provide `-XX:+AggressiveOpts` the JVM *does* cache `1000`, causing the test to fail when that is specified. This replaces `1000` with a randomly selected integer that we test to make sure *isn't* cached by the JVM. *Hopefully* this test is good enough. It relies on the caching not changing in between when we check that the value isn't cached and when we run the painless code. The cache now is a simple array but there is nothing preventing it from changing. If it does change in a way that thwarts this test then the test fail fail again. At least when that happens the next person can see the comment about how it is important that the integer isn't cached and can follow that line of inquiry. Closes #24041 |
||
|---|---|---|
| .. | ||
| aggs-matrix-stats | ||
| ingest-common | ||
| lang-expression | ||
| lang-mustache | ||
| lang-painless | ||
| percolator | ||
| reindex | ||
| repository-url | ||
| transport-netty4 | ||
| build.gradle | ||