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
PHOENIX-6329 Eliminate or serialize minicluster restart operations in Integration tests #1078
Conversation
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.
+1 (non-binding) for the changes, pending QA. Another PR for testing PR#1080
pom.xml
Outdated
@@ -343,18 +343,6 @@ | |||
</goals> | |||
</execution> | |||
<execution> | |||
<id>HBaseManagedTimeTests</id> |
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.
Oh this is not even being used
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.
Must have been copied from HBase, then lurked here for years...
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.
Looking at again, this still might have effect on Pherf.
It probably should be purged, but not today.
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
Last test also had a setup error, but it wasn't the timeout error. |
@@ -708,7 +705,7 @@ protected static String getOrganizationId() { | |||
|
|||
private static long timestamp; | |||
|
|||
public static long nextTimestamp() { | |||
public static synchronized long nextTimestamp() { |
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 like this is recent addition right? We could include deletePriorMetaData()
too?
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.
Or maybe just synchronizing deletePriorMetaData()
could be enough as it would cover deletePriorTables()
, nextTimestamp()
and deletePriorSchemas()
?
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.
Those are only used when running the tests on a real cluster, which feature is broken in many ways.
Almost no-one uses it, and it doesn't affect the maven test suite.
And by the pherf tests, which really should be fixed :)
It doesn't hurt to synchronize it.
Set all stateful priected static methods to synchronized as well. |
FWIW, synchronizing all these methods could be subtask of PHOENIX-6288 and good to directly check for results in multibranch? In the meanwhile we can keep PHOENIX-6288 opened until we get 2-3 multibranch build results without init errors. WDYT @stoty ? |
Although PR build#4 should finish sometime soon hopefully. |
💔 -1 overall
This message was automatically generated. |
bbc7962
to
f8a6deb
Compare
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
408cf22
to
f470256
Compare
💔 -1 overall
This message was automatically generated. |
be59311
to
5ed35eb
Compare
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
a4f02a6
to
2baf251
Compare
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
… Integration tests
💔 -1 overall
This message was automatically generated. |
No description provided.