Skip to content

Conversation

pdhanoya-splunk
Copy link
Contributor

Made following changes to address flakiness related to MC test.

  • Changed wait time to 1500 seconds.
  • Added check to verify MC pod stays in ready state.


// defaultTestTimeout is the max timeout in seconds before async test failed.
defaultTestTimeout = 900
defaultTestTimeout = 1500
Copy link
Collaborator

Choose a reason for hiding this comment

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

What is the reason for increasing this timeout?

Copy link
Contributor Author

@pdhanoya-splunk pdhanoya-splunk Oct 20, 2020

Choose a reason for hiding this comment

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

MC deployment is taking longer hence 1500 seconds to make tests more stable. Also this is worst case scenario ideally the test will be spending around ~600 seconds in this stage.

@pdhanoya-splunk pdhanoya-splunk merged commit 0d1eab5 into develop Oct 27, 2020
@pdhanoya-splunk pdhanoya-splunk deleted the mctestdelay branch October 27, 2020 23:25
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.

5 participants