-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
release 3.1.0 #115
release 3.1.0 #115
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Acceptance test failures suggest there really is a problem. I think holding off pushing a new release until the issue is resolved or at least understood is best.
@tuxmea I won't have time to look into this in the next days. You think you've any chance to do it? |
I first have to implement the postgres_exporter (work paid by customer) - then I can look into failing tests. |
I am able to reproduce the rror running the travis tests locally: Test were OK on first run and produced the service prometheus starting on the second run. |
restart on-failure did not work, as prometheus just did not start properly. setting restart to always. fixes voxpupuli#114 needed for voxpupuli#115
Addressed concerns from @alexjfisher |
restart on-failure did not work, as prometheus just did not start properly. setting restart to always. fixes voxpupuli#114 needed for voxpupuli#115
release 3.1.0
restart on-failure did not work, as prometheus just did not start properly. setting restart to always. fixes voxpupuli#114 needed for voxpupuli#115
release 3.1.0
No description provided.