-
Notifications
You must be signed in to change notification settings - Fork 17
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
Result file was not created for successful/failed run of gemini #236
Comments
Gemini detect error, but result file was not created and no any describe messages in log:
gemini result in console log:
When error detected, on one of test cluster node was running ENOSPC nemesis( simulate the end of space on node). But 2 other nodes are running without errors and not any errors in logs on them. |
This should be handled better now after application of PR #239 perhaps we can close this and repoen it after trying in the upcoming release @aleksbykov ? |
@dahankzter yes we can close it |
@dahankzter , unfortunately the issue is still reproduced.Not always
|
Due to issue scylladb#236 gemini result file could be not created. Let print the Sample result to stdout if error detected. This allow to investigate issue while the scylladb#236 is not fixed
Due to issue scylladb#236 gemini result file could be not created. Let print the Sample result to stdout if error detected. This allow to investigate issue while the scylladb#236 is not fixed
@roydahan, @aleksbykov , is this still the case ? I see we are doing .Sync on the end, so it should work properly, unless there is underlying golang issue that makes it loose data on exit. |
@dkropachev , yes, again got such results. Looks like gemini stucked on exiting: gemini output:
and there is no result file. |
@aleksbykov , Absense of
That part was redone using different mechanism at ef29ea5 So, i could have gone on |
@aleksbykov , did it happen recently ? |
gemini tool : v.1.6.9
gemini cmd:
Gemini finished exit status 0, but result log file was not created:
during run several actions for test cluster node were applyed:
NoCorruptRepair TerminateAndReplaceNode CorruptThenRepair TruncateMonkey AbortRepairMonkey
from output:
The text was updated successfully, but these errors were encountered: