Skip to content

Stabilize test #1132

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

Merged
merged 1 commit into from
Apr 22, 2025
Merged

Stabilize test #1132

merged 1 commit into from
Apr 22, 2025

Conversation

smallhive
Copy link
Contributor

Sometimes, the runtime took a bit more time, and data was wiped out from the cache. Therefore, sometimes we get nil from the condition. We reduced the condition check for 1 second to ensure we had no nil result for the Never check. Simultaneously, we increased Eventually check interval. This condition checks that the cache is going to be empty during these two seconds. In one second and a few milliseconds in fact.

@smallhive smallhive requested a review from roman-khimov as a code owner April 22, 2025 07:00
Copy link

codecov bot commented Apr 22, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 25.77%. Comparing base (e720f27) to head (bb7304a).
Report is 18 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1132   +/-   ##
=======================================
  Coverage   25.77%   25.77%           
=======================================
  Files          89       89           
  Lines       15572    15575    +3     
=======================================
+ Hits         4013     4014    +1     
- Misses      11103    11105    +2     
  Partials      456      456           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Member

@roman-khimov roman-khimov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Commit message formatting is weird
  2. Unstable TestObjectsListCache/lifetime #1130 isn't mentioned.
  3. Looks like the test is inherently racy, but OK.

Closes #1130.

Sometimes, the runtime took a bit more time, and data was wiped out from the cache.
Therefore, sometimes we get nil from the condition. We reduced the condition check
for 1 second to ensure we had no nil result for the Never check. Simultaneously,
we increased Eventually check interval. This condition checks that the cache is going to be empty
during these two seconds. In one second and a few milliseconds in fact.

Signed-off-by: Evgenii Baidakov <evgenii@nspcc.io>
@smallhive smallhive force-pushed the fix-test-with-cache branch from bb7304a to b3ca4df Compare April 22, 2025 11:11
@smallhive
Copy link
Contributor Author

Updated

@smallhive smallhive requested a review from roman-khimov April 22, 2025 11:11
@roman-khimov roman-khimov merged commit 6a2d73e into master Apr 22, 2025
12 of 15 checks passed
@roman-khimov roman-khimov deleted the fix-test-with-cache branch April 22, 2025 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants