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

Not able to run promtool tests without cloning the repo #4711

Closed
kentsanggds opened this Issue Oct 9, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@kentsanggds
Copy link

kentsanggds commented Oct 9, 2018

Bug Report

What did you do?

I tried to use homebrew to install the latest version of the promtool, but although I managed to upgrade to 2.4.2 promtool test would fail. I eventually got it working by cloning the repo and building it on my machine.

However I would also like to run the alert tests on Travis using wget to download the release -

https://github.com/prometheus/prometheus/releases/download/v2.4.2/prometheus-2.4.2.linux-amd64.tar.gz

It doesn't appear to work and without it, I can't introduce the promtool tests as part of the CI workflow

Tried to build in travis using this travis yml - https://github.com/alphagov/prometheus-aws-configuration-beta/blob/cd99a07d691692179397f417adbdb045dffb95d4/.travis.yml

What did you expect to see?

promtool running the tests successfully

What did you see instead? Under which circumstances?

Promtool failing with - promtool: error: expected command but got "test", try --help

  • System information:

Ubuntu trusty

  • Prometheus version:

2.4.2

@simonpasquier

This comment has been minimized.

Copy link
Member

simonpasquier commented Oct 9, 2018

The promtool test command isn't part of any official release yet. You have to compile the binary from the master branch.

@kentsanggds

This comment has been minimized.

Copy link
Author

kentsanggds commented Oct 9, 2018

Thanks, any timescale on when it will be released?

@simonpasquier

This comment has been minimized.

Copy link
Member

simonpasquier commented Oct 9, 2018

Sure. The project has recently opted for a 6 weeks release cadence. Since 2.4.0 has been released 4 weeks ago, 2.5.0 should be there in 2 weeks.

@lock lock bot locked and limited conversation to collaborators Apr 7, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.