-
-
Notifications
You must be signed in to change notification settings - Fork 314
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 new Tweetest Parameters with a fresh set of application repositories #2686
Comments
As a starting point at #172 (we should go through others in the list to see if they are suitable for external_custom, but starting at zookeeper)
|
@smlambert Thank you for pointing out the test! Should I check whether the tests can be run using the changes in #2660? |
Yes, and in fact what I was hoping is that we can get #2660 merged, so then we can run testing in Grinder_Tweetest, to save you from having to run locally. However, given many committers are out until Monday (so likely won't be merged until then), if you feel inspired please do so. We should also review the remaining tests listed in #172 to see if others (in the list that are 'unchecked') are appropriate candidates for external_custom and could be added to this issues list for 'testing a fresh set'. |
Thank you so much @smlambert ! I will try to run the test above and all those listed in the related issue list to check if they can be added to our eligible test lists :) |
TEST RESULTS FOR ZOOKEEPER with the following parameters set: Results for make _external_custom: The BUILD was successful for make compile but not for make _external_custom. I hope make _external_custom is the correct command. |
@smlambert I was running the tests and was wondering where could I find the EXTERNAL_TEST_CMD for each test? |
I am updating this doc with the list of all the tests with their required parameters for external_custom: |
Closing as complete. |
No description provided.
The text was updated successfully, but these errors were encountered: