Skip to content

Mute ydb/tests/olap/ttl_tiering/ttl_delete_s3.py.TestDeleteS3Ttl.test_data_unchanged_after_ttl_change #13828

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

Closed
maximyurchuk opened this issue Jan 24, 2025 · 0 comments
Assignees
Labels

Comments

@maximyurchuk
Copy link
Collaborator

ydb/tests/olap/ttl_tiering/ttl_delete_s3.py.TestDeleteS3Ttl.test_data_unchanged_after_ttl_change

Add line to muted_ya.txt:
ydb/tests/olap/ttl_tiering ttl_delete_s3.py.TestDeleteS3Ttl.test_data_unchanged_after_ttl_change

Owner: TEAM:@ydb-platform/cs

Read more in mute_rules.md

Summary history:
Success rate 40%
Pass:2 Fail:3

Test run history: link

More info in dashboard

XJIE6 pushed a commit that referenced this issue Apr 8, 2025
Split test `test_data_unchanged_after_ttl_change` into a working one with less strict conditions and unmuting it.
Also, added three more with stronger conditions which are skipped untill corresponding issues would be fixed
XJIE6 pushed a commit that referenced this issue Apr 10, 2025
Unmute test `test_data_unchanged_after_ttl_change` by increasing `max_read_staleness_ms`, setting `set_fast_compaction`, increasing random data amount and general refactoring
@XJIE6 XJIE6 closed this as completed Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants