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 non-bot jobs leaking into known_jobs + make sure that job manager logs to correct file #79

Merged
merged 6 commits into from
Nov 21, 2022

Conversation

trz42
Copy link
Contributor

@trz42 trz42 commented Nov 18, 2022

Tested on AWS cluster (see trz42/software-layer#46 (comment)). Will run a final test using this PR as it includes recently merged PRs (no conflicts) and minor tweaks to the logging from the job manager.

Follow-up to #63

Closes #33

While non-bot jobs are not processed in process_new_job they could still leak into the list of known jobs via
```python
known_jobs = current_jobs

at the end of the main loop in the job manager. To fix this we collect a list of non-bot jobs and remove them from the dictionary current_jobs just before that is assigned to known_jobs. The function process_new_job was slightly modified to return False if it processes a non-bot job and True otherwise.
Also using f-strings when using '{var}'.
… fix-non-bot-job-leaking

Pull in recentlt merged PRs.
@trz42
Copy link
Contributor Author

trz42 commented Nov 18, 2022

Verified on another cluster that this works. So, PR is ready to be reviewed.

@boegel boegel changed the title Fix non-bot jobs leaking into known_jobs Fix non-bot jobs leaking into known_jobs + make sure that job manager logs to correct file Nov 21, 2022
@boegel boegel merged commit 01cdc30 into EESSI:main Nov 21, 2022
@boegel boegel added the bug label Nov 21, 2022
@trz42 trz42 deleted the fix-non-bot-job-leaking branch February 24, 2023 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Job manager crashes when it encounters a non-bot job
3 participants