Uh oh!
There was an error while loading. Please reload this page.
TEZ-4667: Correct the test case testInMemAllocationWithJvmMaxMemory - #445
Conversation
tez-yetus
commented
Nov 24, 2025
🎊 +1 overall
This message was automatically generated. |
abstractdog
commented
Nov 25, 2025
@maheshrajus: thanks for taking care of this, a few questions:
|
maheshrajus
commented
Nov 26, 2025
@abstractdog INFO [Time-limited test] impl.TestSimpleFetchedInputAllocator (TestSimpleFetchedInputAllocator.java:testInMemAllocationWithJvmMaxMemory(99)) - jvmMax: 1073741824 here RequestSize should be greater than InMemThreshold. Then only it will allocate from the DISK. So it is failing in some env only. In any case we should put more RequestSize . So currently Test sample: |
abstractdog
commented
Nov 26, 2025
I still feel the test case is shady in its current form, and I'm afraid this fix won't make it any clearer requestSize should be greater than inMemThreshold, which is a lower bound, also I guess it has an upper bound constraint (jvm memory, or whatever), am I right to assume that? could this line be clearer to comply with those constraints and work in every scenario (regardless of the jvmMax) |
@abstractdog I will make requestSize simple instead of jvm memory and "(long) (0.4f * inMemThreshold) + 100L" checks. Lower bound value already tested in existed test cases. i will put requestSize size more than inMemThreshold and test the scenario Planning to modify like this: |
tez-yetus
commented
Dec 5, 2025
🎊 +1 overall
This message was automatically generated. |
maheshrajus
commented
Dec 8, 2025
@abstractdog Can you review and approve the changes ? thanks ! |
Uh oh!
There was an error while loading. Please reload this page.
This test case is failing in some env when requested memory is less compared to available memory.
We need to increase the requested memory so that it will not fail.