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

Set Performance Test Suite graphs to Manual Runtype #9604

Merged
merged 28 commits into from
Mar 28, 2019

Conversation

scottmitchell
Copy link
Collaborator

Purpose

@saintentropy noticed that some of the test suite graphs were set to Automatic, which caused both graph to both Open and Run in the OpenModelBenchmark rather than wait for the RunModelBenchmark to Run.

Declarations

Check these if you believe they are true

  • The code base is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning, and are documented in the API Changes document.

FYIs

@saintentropy @mjkkirschner @reddyashish @QilongTang @alfarok @ColinDayOrg

@mjkkirschner
Copy link
Member

mjkkirschner commented Mar 27, 2019 via email

@QilongTang
Copy link
Contributor

This LG, @mjkkirschner I can also add new APIs to the DynamoModelTestBase to open graph in force manual mode, currently such API does not exist for performance test framework to use.

@@ -130,10 +130,10 @@ protected void EmptyScheduler()
}
}

protected void OpenModel(string relativeFilePath)
protected void OpenModel(string relativeFilePath, bool forceManualExecutionMode = false)
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@mjkkirschner @QilongTang Can we do this? Or do we need to add a new method?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@QilongTang I can remove this if you would rather just handle it as part of your task.

Copy link
Member

Choose a reason for hiding this comment

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

I think this is the way to do it.

Copy link
Member

Choose a reason for hiding this comment

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

I guess we need to consider that this might effect others who have written tests against the test base classes.....

I guess it's safest to add a new method unless you want to test this or do some research on the API compatibility of adding default arguments to protected methods?

Copy link
Contributor

Choose a reason for hiding this comment

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

That's good, can you run self CI just to make sure?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

For the record, this did pass the self CI, but I'm going to remove this change for now and just merge the RunType changes.

@scottmitchell scottmitchell merged commit 3bf9efb into DynamoDS:master Mar 28, 2019
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.

3 participants