-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HADOOP-16905. Update jackson-databind to 2.10.3 to relieve us from th… #3748
Conversation
…e endless CVE patches. (apache#1876) (cherry picked from commit 69faaa1) Conflicts: hadoop-project/pom.xml
💔 -1 overall
This message was automatically generated. |
@brahmareddybattula Would you take a look? |
Good to update some file in the top tree (outside of all modules) to trigger the full QA (e.g. adding a line etc)? Once full QA is done, we can revert that change. |
💔 -1 overall
This message was automatically generated. |
Thank you @virajjasani for your comment. Updated the pom.xml to run the full unit tests. This precommit job didn't run all the tests because there is a test failure in hadoo-hdfs module and stopped testing. |
Filed HADOOP-18035 to run all the unit tests. |
The changelist available as part of build#2 is:
Hence, looks like revert commit was also part of the build and that's why full QA was not triggered (as per logs). Hopefully test failure in one module would not prevent full QA based on what I have seen in recent PRs but it's still strange that full QA was not triggered. Maybe because after applying revert commit, build did not recognize any changed on the main pom file. @aajisaka would you like to keep new line change in hadoop-main pom file for a while (~24 hr)? Once we get full QA results, we can revert it. Sounds good? |
For instance, two build results had multiple test failures (including hadoop-hdfs modules), still hadoop-yarn modules tests were executed (PR #3749). Let me dig-in bit more to understand this behaviour on the current PR. |
It is not the reason why full QA was not triggered. I commented in HADOOP-18035 why the subsequent modules were not executed in branch-3.2 and branch-2.10. |
I see, thanks @aajisaka |
Now HADOOP-18040 is merged. Let me run the full QA again. |
💔 -1 overall
This message was automatically generated. |
If |
Thanks. TestSLSRunner passed on my local. TestTimelineAuthFilterForV2 is always failing with and without the patch. I think it's okay to merge without binding +1 because this is a backport. |
Sounds good. Otherwise it looks good anyways. +1 (non-binding) |
Merged. Thank you @virajjasani for your review! |
…e endless CVE patches. (#1876)
(cherry picked from commit 69faaa1)
Conflicts:
hadoop-project/pom.xml
Description of PR
PR for testing by Jenkins. Backport HADOOP-16905 to branch-3.2. I'll backport HADOOP-17534 next.
How was this patch tested?
Not tested.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?