-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-26834 Adapt ConnectionRule for both sync and async connections (branch-2) #4220
HBASE-26834 Adapt ConnectionRule for both sync and async connections (branch-2) #4220
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
The master forward-port is posted on #4221 |
@busbey do you have any idea why this might be? Is there something missing from the hadoop.three profile in one of the submodules that is required for invoking tests on this module? The failing build is prefixed with this warning.
|
Oh. That |
This comment was marked as outdated.
This comment was marked as outdated.
that flag is supposed to get set over here: https://github.com/apache/hbase/blob/master/dev-support/hbase-personality.sh#L170-L175 so either our branch pattern matching is broken, something else is overriding the setting, or this execution flow somehow skips |
Okay, well. JDK11 aside, the failures in JDK8 build look like worker resource exhaustion and unrelated to this change. None of those test classes use this Rule, so... |
@busbey my earlier diagnosis was not entirely accurate -- this is not PR's fault. I reproduce the same behavior when I run a single test out of a single module (with JDK11, Hadoop3, branch-2). i.e.,
|
945ab47
to
742cb4d
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
The failed UT seems because I set java.io.tmpdir to target on the mvn command line... We should have set it explicitly in surefire arg line, not sure why setting it on mvn command line would effect this... Let me dig more. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
Failure in |
This is needed primarily for branch-2 codelines where there's no easy bridge from AsyncConnection to Connection.