-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
TimeSeriesLifecycleActionsIT muliple tests fail #53738
Comments
Pinging @elastic/es-core-features (:Core/Features/ILM+SLM) |
@jkakavas this class has over 45 tests, I don't think we should mute the entire class because 3-4 tests fail, that can lead to a regression for the stable tests in this class. There is an issue already open #53488 to refactor it into multiple classes, but I think muting the entire class is a bad idea here. |
fair enough, I'll revert this. |
Please do mute the tests that did fail, I agree wholeheartedly for doing that, I just don't want to skip all the passing tests in this class. |
I just want to note that there are many tests that fail in this suite, not just 2,3 : https://build-stats.elastic.co/app/kibana#/discover?_g=(refreshInterval:(pause:!t,value:0),time:(from:now-30d,mode:quick,to:now))&_a=(columns:!(test),index:e58bf320-7efd-11e8-bf69-63c8ef516157,interval:auto,query:(language:lucene,query:TimeSeriesLifecycleActionsIT),sort:!(time,desc)) and it's hard for me ( as in random ES person on test triage ) to know if the historical failures of the last month are fixed in the meantime, or just never muted etc. We can take a failure at a time if you think this is better, I don't have a reason to push back, I just wanted to make sure the extent of the failures is known |
we have 3 open issues https://github.com/elastic/elasticsearch/search?q=TimeSeriesLifecycleActionsIT&type=Issues so I thnk we can consolidate all these here and I'll mute the whole class
https://gradle-enterprise.elastic.co/s/p6yto4rhlkr2a
as a note
testRetryFailedDeleteAction
seems to started failing when #52494 was merged ( see here )The text was updated successfully, but these errors were encountered: