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

   
   ### Description of PR
   
   1. Container executor creates directories incorrectly. yarn is unable to 
create appdir
   2. code is incorrectly freeing memory in method create_app_dirs a pointer to 
app_dir is created, then a primary_app_dir is set to app_dir, then appdir is 
free()ed. This results in undefined behavior.
   3. No unit test was calling create_app_dirs (one was added)  
   4. better comments were added explaing the different partial failures 
possible in the function
   
   ### How was this patch tested?
   Unit tests pass. Unit tests were added
   
   ### For code changes:
   
   - [ Y] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ NA] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ NA] 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)?
   - [ NA] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   ### AI Tooling
   
   This PR was made by hand the 'old school way'
   If an AI tool was used:
   
   - [ NA ] The PR includes the phrase "Contains content generated by <tool>"
         where <tool> is the name of the AI tool used.
   - [ NA ] 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