-
Notifications
You must be signed in to change notification settings - Fork 92
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
[434] Allow to filter jobs in ZyteJobsComparisonMonitor by close_reason #440
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #440 +/- ##
==========================================
- Coverage 79.51% 79.48% -0.04%
==========================================
Files 76 76
Lines 3237 3242 +5
Branches 537 539 +2
==========================================
+ Hits 2574 2577 +3
- Misses 593 594 +1
- Partials 70 71 +1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me!
We should add some unittest to cover the new addition, and it would be nice to run some test job in ScrapyCloud to verify these changes (Installing Spidermon in the requierements.txt from git+https://github.com/shafiq-muhammad/spidermon@shafiq-434
should get you these changes). After that's addressed we should be good to go 👍
Just a quick FYI @shafiq-muhammad @curita, I believe the pipeline is failing due to a regression from pytest 8.1.1 to 8.2.0. My validation was:
Hope this helps (and is correct regardless of environment). |
Yes, it looks like Pytest 8.2.0 release has caused a lot of troubles according to their issues page. |
Adds limit for nested dict stats computation
Added a new setting
SPIDERMON_JOBS_COMPARISON_CLOSE_REASONS
to allowZyteJobsComparisonMonitor
to filter by the ScrapyCloud jobs with theirclose_reason
stat.