Skip to content
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

Re-Add the now optional method to automatically analyze crashes #5435

Merged
merged 5 commits into from Jun 6, 2018

Conversation

dothebart
Copy link
Contributor

  • the user or CI may now specify --coreCheck true if the testsuite
    should perform automatic core analysis for him.

This eases the process of evaluating crashes on different targets like windows and mac.

* the user or CI may now specify `--coreCheck true` if the testsuite
  should perform automatic core analysis for him.
@dothebart dothebart requested a review from dhly-etc May 23, 2018 09:04
@jsteemann
Copy link
Contributor

jsteemann commented Jun 1, 2018

@jsteemann
Copy link
Contributor

@dothebart : please resolve the merge conflict

@jsteemann jsteemann added this to the devel milestone Jun 4, 2018
Copy link
Contributor

@dhly-etc dhly-etc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few minor changes requested here. Has the failure case been manually tested to see that it produces a backtrace on each platform? The normal Jenkins PR test won't really suffice since there shouldn't be any coredumps to analyze.

@@ -82,6 +82,7 @@ let optionsDocumentation = [
' - `prefix`: prefix for the tests in the xml reports',
'',
' - `rr`: if set to true arangod instances are run with rr',
' - `coreCheck`: if set to true we will try to locate coredumps and get a backtrace from it',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"if set to true, we will attempt to locate a coredump to produce a backtrace in the event of a crash"

@@ -85,7 +85,7 @@ function upgrade (options) {

const argv = toArgv(args);

result.upgrade.first = pu.executeAndWait(pu.ARANGOD_BIN, argv, options, 'upgrade', tmpDataDir);
result.upgrade.first = pu.executeAndWait(pu.ARANGOD_BIN, argv, options, 'upgrade', tmpDataDir, options.enableCoreCheck);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this options.coreCheck elsewhere?

@@ -95,7 +95,7 @@ function upgrade (options) {

++result.upgrade.total;

result.upgrade.second = pu.executeAndWait(pu.ARANGOD_BIN, argv, options, 'upgrade', tmpDataDir);
result.upgrade.second = pu.executeAndWait(pu.ARANGOD_BIN, argv, options, 'upgrade', tmpDataDir, options.enableCoreCheck);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this options.coreCheck elsewhere?

@neunhoef neunhoef merged commit b2777c4 into devel Jun 6, 2018
@fceller fceller deleted the feature/auto-debug-parametrizeable branch June 27, 2018 07:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants