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

Fix cache policy bug #4789

Merged
merged 2 commits into from May 5, 2023
Merged

Fix cache policy bug #4789

merged 2 commits into from May 5, 2023

Conversation

philippjfr
Copy link
Member

Fixes #4785

@codecov
Copy link

codecov bot commented May 5, 2023

Codecov Report

Merging #4789 (36b6094) into main (f351189) will decrease coverage by 0.57%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main    #4789      +/-   ##
==========================================
- Coverage   83.37%   82.81%   -0.57%     
==========================================
  Files         268      268              
  Lines       37899    37901       +2     
==========================================
- Hits        31599    31387     -212     
- Misses       6300     6514     +214     
Flag Coverage Δ
ui-tests 39.13% <20.00%> (-1.56%) ⬇️
unitexamples-tests 73.34% <80.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
panel/io/cache.py 84.45% <66.66%> (-0.30%) ⬇️
panel/tests/io/test_cache.py 97.12% <100.00%> (ø)

... and 7 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@philippjfr philippjfr merged commit 956de9b into main May 5, 2023
11 of 15 checks passed
@philippjfr philippjfr deleted the fix_cache_policy branch May 5, 2023 22:51
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.

cache policy not functionning
1 participant