-
-
Notifications
You must be signed in to change notification settings - Fork 15.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
Test failures on ppc64le rhel 7.6 architecture #9479
Comments
I am sorry but I have no access to ppc64le hardware and so can not help... That said our dev environment is usually x86 |
Hi Norman, Thanks for the response. Can we bypass the 'conscript' dependency and still build netty with positive test case executions by using alternatives like jetty-alpn? You can get access to the power VM (Power8) by raising a VM request at OSU - http://osuosl.org/services/powerdev/request_hosting/. Thanks in advance for the help. Also please note that • I have commented below portion from pom.xml as it is x86_64 specific config. • Netty Package builds fine without test case verification (with '-Dmaven.test.skip=true' option) |
@SantoshMagdum done... |
Hi Norman, |
Yes I did but did not hear back yet
… Am 29.08.2019 um 10:32 schrieb SantoshMagdum ***@***.***>:
Hi Norman,
Did you get a chance to raise access request for guest OS for Power8 VM? Please let me know ticket/token ID. I shall followup for access.
Also, I had added ppc64le in below config to support ppc64le JDK.
^(x86_64|aarch_64|ppcle_64)$
Now I see netty-handler test cases are failing due for conscript dependency.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
To be more clear I filled the form but did never get an email ..
… On 29. Aug 2019, at 10:58, Norman Maurer ***@***.***> wrote:
Yes I did but did not hear back yet
> Am 29.08.2019 um 10:32 schrieb SantoshMagdum ***@***.***>:
>
>
> Hi Norman,
> Did you get a chance to raise access request for guest OS for Power8 VM? Please let me know ticket/token ID. I shall followup for access.
> Also, I had added ppc64le in below config to support ppc64le JDK.
> ^(x86_64|aarch_64|ppcle_64)$
> Now I see netty-handler test cases are failing due for conscript dependency.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub <#9479?email_source=notifications&email_token=AADLIQSSIBIE5K74AOXX74TQG6CR7A5CNFSM4IM3R4U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5NWRSY#issuecomment-526084299>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADLIQQPXEJYVVKMJFCXG6TQG6CR7ANCNFSM4IM3R4UQ>.
>
|
Hi Norman, |
@SantoshMagdum cool thanks! |
Hi Norman, |
@SantoshMagdum will do once I have some cycles. |
Motivation: At the moment it is not possible to build netty on a power 8 systems. Modifications: - Improve detection of the possibility of using Conscrypt - Skip testsuite-shading when not on x86_64 as this is the only platform for which we build tcnative atm - Only include classifier if on x86_64 for tcnative as dependency as this is the only platform for which we build tcnative atm - Better detect if UDT test can be run Result: Fixes #9479
@SantoshMagdum should be fixed by #9550. Please verify... Also it would be cool if we could keep the host and include it in our CI infrastructure to ensure we not regress :) |
Thanks Norman for checking. But the netty-handler was till throwing multiple errors like below -
I tried quickly to skip the test cases for netty-handler using below but errors were still pooping up -
Please suggest. For now we can go ahead with plain netty build without any test executions (skipping test cases 'mvn Dmaven.test.skip=true' builds netty without issues). |
Hmm I didn't do anything special and it just works with the PR applied:
|
Motivation: At the moment it is not possible to build netty on a power 8 systems. Modifications: - Improve detection of the possibility of using Conscrypt - Skip testsuite-shading when not on x86_64 as this is the only platform for which we build tcnative atm - Only include classifier if on x86_64 for tcnative as dependency as this is the only platform for which we build tcnative atm - Better detect if UDT test can be run Result: Fixes #9479
Motivation: At the moment it is not possible to build netty on a power 8 systems. Modifications: - Improve detection of the possibility of using Conscrypt - Skip testsuite-shading when not on x86_64 as this is the only platform for which we build tcnative atm - Only include classifier if on x86_64 for tcnative as dependency as this is the only platform for which we build tcnative atm - Better detect if UDT test can be run Result: Fixes #9479
Expected behavior
Actual behavior
Steps to reproduce
Minimal yet complete reproducer code (or URL to code)
Netty version
JVM version (e.g.
java -version
)OS version (e.g.
uname -a
)I am investigating more on 'conscript' build.
Kindly please suggest is there any way to use 'jetty-alpn' package instead of consscript.
Or is there any way to bypass the 'conscript' dependency and build netty with positive test cases executions.
The text was updated successfully, but these errors were encountered: