-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
TestVUIntegrationMetrics
is broken, make it into an integration test
#2799
Comments
hmm actually, this test is probably not just flaky, it seems like it's buggy 😕 notice the different metric registry addresses here:
This shouldn't happen after #2594, all of the An integration test would be a good place for its replacement, especially since we don't have any integration tests that do |
TestVUIntegrationMetrics
is flaky, make it into an integration testTestVUIntegrationMetrics
is broken, make it into an integration test
I have fixed the thing that is reported here in #3012 . But IMO the underlying reason why Hopefully after the linked fix it will actually present itself 🤞 |
For the record. After an internal discussion, we decided to clean a milestone since the issue was jumping between milestones without completion. Once we determine which milestone it lands, we set the right one. |
This test:
k6/js/runner_test.go
Lines 824 to 885 in 4e4e5b1
Has been quite flaky recently, with failures like this:
Looking at how it validates things and how ancient it is, it is a good candidate for moving it away from the
js/
package and either making it an integration test or changing an already existing integration test to test the same things. Just for fun, I did some archeology, and the test has existed for more than 5 years roughly in its current form, so it's time for it to retire 😅The text was updated successfully, but these errors were encountered: