fix: group job error call#3448
Conversation
📝 WalkthroughWalkthroughThe changes enhance error logging within the job processing workflow. In the Changes
Sequence Diagram(s)sequenceDiagram
participant Scheduler as JobScheduler
participant Group as GroupJob
participant Job as Individual Job
Scheduler->>Scheduler: schedule(job)
alt Job is a GroupJob
Scheduler->>Group: log_error(msg, indent, aux_logs, ...)
Group->>Group: Sort jobs by rule name
loop For each sorted job
Group->>Job: log_error(msg, indent=True, ...)
end
else Job is not a GroupJob
Scheduler->>Scheduler: Use standard error logging
end
Suggested reviewers
Tip ⚡🧪 Multi-step agentic review comment chat (experimental)
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
🧰 Additional context used📓 Path-based instructions (1)`**/*.py`: Do not try to improve formatting. Do not suggest ...
⏰ Context from checks skipped due to timeout of 90000ms (35)
🔇 Additional comments (3)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
🤖 I have created a release *beep* *boop* --- ## [9.0.1](v9.0.0...v9.0.1) (2025-03-14) ### Bug Fixes * group job error call ([#3448](#3448)) ([3d53863](3d53863)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This wasn't caught earlier, likely due to how we check for tests that expect failure. The `test_group_jobs_fail` test was failing, but it was b/c of this issue. Perhaps should check for the expected exception. ### QC <!-- Make sure that you can tick the boxes below. --> * [ ] The PR contains a test case for the changes or the changes are already covered by an existing test case. * [ ] The documentation (`docs/`) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake). <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced error logging to display grouped job errors in a sorted, consistent order for clearer troubleshooting. - Introduced tailored error logging during job scheduling, ensuring that errors for grouped jobs are handled separately for improved clarity. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Johannes Köster <johannes.koester@tu-dortmund.de>
🤖 I have created a release *beep* *boop* --- ## [9.0.1](snakemake/snakemake@v9.0.0...v9.0.1) (2025-03-14) ### Bug Fixes * group job error call ([snakemake#3448](snakemake#3448)) ([3d53863](snakemake@3d53863)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This wasn't caught earlier, likely due to how we check for tests that expect failure. The
test_group_jobs_failtest was failing, but it was b/c of this issue. Perhaps should check for the expected exception.QC
docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).Summary by CodeRabbit