On Tue, 31 Oct 2023 18:54:26 GMT, Thomas Schatzl <tscha...@openjdk.org> wrote:
> Had a discussion with @albertnetymk and we came to the following agreement > about naming: > >"allocation failure" - allocation failed in the to-space due to memory >exhaustion >"pinned" - the region/object has been pinned >"evacuation failure" - either pinned or allocation failure > >I will apply this new naming asap. Done. I left out the `G1EvacFailureInjector` (it only injects allocation failures, not evacuation failures) related renamings as this adds lots of noise (including the debug options). I'll file a follow-up and assign it to me. Tier1 seems to pass, will redo upper tiers again. The only noteworthy externally visible change is that the `(Evacuation Failure)` tag in log messages is now `(Allocation Failure)`. I did not want combinations of `(Evacuation Failure)` and additionally `(Pinned) (Allocation Failure)`, but maybe it is fine, or just fine to keep only `(Evacuation Failure)` as before and assume that users enable higher level logging to find out details. ------------- PR Comment: https://git.openjdk.org/jdk/pull/16342#issuecomment-1790570048
