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 price spike check to use correct scaling and compare rates #1691

Merged
merged 1 commit into from
Sep 24, 2024

Conversation

dpaiton
Copy link
Member

@dpaiton dpaiton commented Sep 24, 2024

No description provided.

@dpaiton dpaiton enabled auto-merge (squash) September 24, 2024 19:29
@dpaiton dpaiton merged commit 3ee7d90 into main Sep 24, 2024
4 checks passed
@dpaiton dpaiton deleted the dpaiton/fix-check-price-spike branch September 24, 2024 19:36
Copy link

codecov bot commented Sep 24, 2024

Codecov Report

Attention: Patch coverage is 50.00000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 81.84%. Comparing base (0971d8f) to head (23a9093).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
...c/agent0/hyperfuzz/system_fuzz/invariant_checks.py 50.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1691      +/-   ##
==========================================
+ Coverage   81.77%   81.84%   +0.07%     
==========================================
  Files          99       99              
  Lines        7647     7650       +3     
==========================================
+ Hits         6253     6261       +8     
+ Misses       1394     1389       -5     
Flag Coverage Δ
unittests 81.84% <50.00%> (+0.07%) ⬆️

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

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

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