-
Notifications
You must be signed in to change notification settings - Fork 5
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
Changes to test-framework introduced during last 2 days of debugging. #845
Conversation
…ty to specify new package to install.
…ll capability into own script.
…into jack/reset-db
@@ -71,6 +71,20 @@ parse_command_line() { | |||
done | |||
} | |||
|
|||
# Make sure that we do not have any instances running, not even as |
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.
Why is test
not under production? All production-related tests should be under production
folder, not under a top-level test
folder?
Any test should be located under the folder of the specific product that is being tested, not separated from that.
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.
@@ -421,6 +421,10 @@ int wait_for_processing_to_complete(bool is_explicit_pause, int rule_1_sample_ba | |||
const int no_delta_count_before_break = 300 / c_processing_pause_in_microseconds; | |||
int current_no_delta_attempt = 0; | |||
|
|||
char buffer[4096]; | |||
int space_left = 1024; | |||
char * start_pointer = buffer; |
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.
Because test
is not under production, this code is not subject to the cleanup we do via clang-tidy. One of the benefits of having this code under production is that all formatting issues that can be handled automatically by clang-tidy, actually do get handled by it.
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.
which is why I have ./lint.sh
which I run before each commit. are you spotting a formatting error that it missed?
test/proposal.md
Outdated
@@ -0,0 +1,93 @@ | |||
# Directory Reset Proposal | |||
|
|||
Based on feedback provided by Dax, I have thought very |
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.
Check the production README guidelines for md files. In particular, we should not break long lines.
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.
this is a temporary file, and should not have been included in the commit.
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.
That is fine, but you should still check the guidelines for future reference. :)
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.
All this code should be moved under `production\tests, which would also add the benefit of running clang-tidy on the code.
Various small changes:
ps
for any instances of gaia database before installingtest/utils/monitor_lsof.sh
to package up the FD tracking used for Tobin (also to establish a good pattern for these)test/utils
directory tolint.sh
mink.cpp
, will break the test on purpose as the timeout should never occurexpected_output.json
forsmoke
test comparison