-
Notifications
You must be signed in to change notification settings - Fork 62
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
[ML] Autodetect fatal error in gallery 302 #94
Comments
|
Looking at the build hash, this seems to be a regression introduced with #92. I assume this test has been run before. |
I suspect that this is probably caused by |
@tveasey This is indeed the problem and can/should be fixed as you proposed. But: I would like to further harden the code. |
…stream and harden accumulators to prevent empty containers. fixes elastic#94
…30674) This change adds version information in case a native ML process crashes, the version is important for choosing the right symbol files when analyzing the crash. Adding the version combines all necessary information on one line. relates elastic/ml-cpp#94
…30674) This change adds version information in case a native ML process crashes, the version is important for choosing the right symbol files when analyzing the crash. Adding the version combines all necessary information on one line. relates elastic/ml-cpp#94
…lastic#30674) This change adds version information in case a native ML process crashes, the version is important for choosing the right symbol files when analyzing the crash. Adding the version combines all necessary information on one line. relates elastic/ml-cpp#94
Found in
"native_code_info": { "version": "7.0.0-alpha1-SNAPSHOT", "build_hash": "d219beab8c7d34" }
Linux version 3.10.0-693.11.1.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) ) #1 SMP Mon Dec 4 23:52:40 UTC 2017
gallery2018
datasetcount
atbucket_span=15m
{"bool":{"must":[{"term":{"status":{"value":"302"}}}]}}
(from: 1970-01-02T10:00:00.000Z to: 2018-12-31T00:00:00.000Z)
Job fails with unexpected death of autodetect.
Occurs in repeated runs, at same latest timestamp
2018-10-09 15:29:11
(UTC).This corresponds with the end of the timeseries for
302
; however job end date was specified as2018-12-31 00:00:00
The text was updated successfully, but these errors were encountered: