-
Notifications
You must be signed in to change notification settings - Fork 1
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
LPD-47903 NPE in HttpInvoker due to httpURLConnection.getErrorStream returning null #2502
Conversation
CI is automatically triggering the following test suites:
|
ci:test:relevant |
ci:test:site-management |
✔️ ci:test:sf - 1 out of 1 jobs passed in 3 minutesClick here for more details.Base Branch:Branch Name: master Sender Branch:Branch Name: LPD-47903 1 Successful Jobs:For more details click here. |
Jenkins Build:test-portal-source-format#3203 Jenkins Report:jenkins-report.html Jenkins Suite:sf Pull Request:liferay-headless#2502 Testray Routine:EE Pull Request Testray Build:[master] ci:test:sf - jonathanmccann > liferay-headless - PR#2502 - 2025-01-31[14:51:52] Testray Build ID:`124882705` Testray Importer:publish-testray-report#14319 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#6013 Jenkins Report:jenkins-report.html Jenkins Suite:site-management Pull Request:liferay-headless#2502 Testray Routine:EE Pull Request Testray Build:[master] ci:test:site-management - jonathanmccann > liferay-headless - PR#2502 - 2025-01-31[14:52:42] Testray Build ID:`125050576` Testray Importer:publish-testray-report#36069 |
Jenkins Build:test-portal-acceptance-pullrequest(master)#14422 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-headless#2502 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - jonathanmccann > liferay-headless - PR#2502 - 2025-01-31[14:52:32] Testray Build ID:`125071869` Testray Importer:publish-testray-report#33514 |
ci:test:relevant |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I've relaunched the tests just to make sure everything is working as expected since it seems the previous execution ran into many issues.
If everything works I will forward it. Thanks!
✔️ ci:test:stable - 25 out of 25 jobs passed❌ ci:test:relevant - 77 out of 102 jobs passed in 3 hours 24 minutesClick here for more details.Base Branch:Branch Name: master Upstream Comparison:Branch GIT ID: 5a1b51d1511d7580bf1c1e95834f6ecbb25dcf9a ci:test:stable - 25 out of 25 jobs PASSED25 Successful Jobs:ci:test:relevant - 77 out of 102 jobs PASSED25 Failed Jobs:
77 Successful Jobs:For more details click here.Failures unique to this pull:
Test bundle downloads: |
Jenkins Build:test-portal-acceptance-pullrequest(master)#12941 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-headless#2502 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - jonathanmccann > liferay-headless - PR#2502 - 2025-02-05[09:55:59] Testray Build ID:`129810001` Testray Importer:publish-testray-report#28181 |
Failures don't seem related. I'm forwarding it. |
ci:forward |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
Skipping previously passed test suites:
|
Jenkins Build:test-portal-acceptance-pullrequest(master)#20218 Jenkins Report:jenkins-report.html Jenkins Suite:relevant Pull Request:liferay-headless#2502 Testray Routine:EE Pull Request Testray Build:[master] ci:test:relevant - jonathanmccann > liferay-headless - PR#2502 - 2025-02-06[00:33:53] Testray Build ID:`130476448` Testray Importer:publish-testray-report#43564 |
ci:forward:force |
CI is automatically triggering the following test suites:
The pull request will automatically be forwarded to the user
|
Skipping previously completed test suites:
|
All required test suite(s) completed. |
Pull request has been successfully forwarded to brianchandotcom#158550 |
What is this trying to solve?
https://liferay.atlassian.net/browse/LPD-47903
How am I fixing it?
In certain cases
httpURLConnection.getErrorStream()
can returnnull
as defined in the spec - https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/net/HttpURLConnection.html#getErrorStream()This was caught in one of Site Management's tests where we expect the action to fail and confirm it fails with the correct status code.
I updated the template to only process the
inputStream
if it exists. Please let me know your thoughts on the change and if you see an alternative approach that you would prefer instead. Thank you.How can you verify that it works?
In
headless-site-test
rungw testIntegration --tests *.SiteResourceTest