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

Retry the mongo config #10926

Merged
merged 1 commit into from Nov 19, 2019

Conversation

SimonRichardson
Copy link
Member

@SimonRichardson SimonRichardson commented Nov 19, 2019

Checklist


Description of change

The following attempts to get the mongo memory profile to check that
it has been set in the config. It would seem that sometimes the
mongo service is slow and so it requires that to change, so that it
can then be correctly reflected in the config.

QA steps

cd tests && ./main.sh controller

The following attempts to get the mongo memory profile to check that
it has been set in the config. It would seem that sometimes the
mongo service is slow and so it requires that to change, so that it
can then be correctly reflected in the config.
@SimonRichardson SimonRichardson changed the base branch from develop to 2.7 November 19, 2019 16:05
Copy link
Member

@hmlanigan hmlanigan left a comment

Choose a reason for hiding this comment

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

LGTM

@hmlanigan
Copy link
Member

$$merge$$

@jujubot jujubot merged commit 7fb2dcb into juju:2.7 Nov 19, 2019
@SimonRichardson SimonRichardson deleted the fix-controller-integration-test branch November 19, 2019 20:26
@wallyworld wallyworld mentioned this pull request Nov 25, 2019
jujubot added a commit that referenced this pull request Nov 25, 2019
#10945

## Description of change

Merge 2.7 with these PRs

#10927 fix panic actions in output
#10926 retry the mongo config
#10912 actions2functions
#10929 fix k8s cr tests
#10935 pad controller timeout
#10937 fix typo in juju compat code
#10938 reduce action stdout size in tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants