slfan1989 opened a new pull request, #8832:
URL: https://github.com/apache/hadoop/pull/8832

   ### Description of PR
   
   JIRA: YARN-12029. Fix race in 
TestYarnNativeServices.testCreateServiceWithPlacementPolicy after flex.
   
   `testCreateServiceWithPlacementPolicy` can read the previous `STABLE` state 
before the ApplicationMaster processes an asynchronous flex request, causing 
the test to fail unexpectedly.
   
   Wait for the requested container count, the component's `FLEXING` state, and 
a non-stable service state before checking that the service cannot stabilize. 
Apply this to both the 3-to-5 and 5-to-4 transitions.
   
   Replace the broad exception handlers with explicit 
`assertThrows(TimeoutException.class, ...)` assertions, while preserving
   the existing container-count, anti-affinity, and final stability checks.
   
   This change only updates test code.
   
   ### How was this patch tested?
   
   CI.
   
   ### For code changes:
   
   - [ ] Does the title of this PR start with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: Have the integration tests been executed and the 
endpoint
         declared according to the connector-specific documentation? *Note: 
Automated CI
         testing doesn't cover all cases so manual testing with cloud storage 
is still
         required.*
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   ### AI Tooling
   
   If an AI tool was used:
   
   - [ ] The PR includes the phrase "Contains content generated by <tool>"
         where <tool> is the name of the AI tool used.
   - [ ] My use of AI contributions follows the ASF legal policy
         https://www.apache.org/legal/generative-tooling.html
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to