-
Notifications
You must be signed in to change notification settings - Fork 14
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
3.7.1.50 #111
Merged
Merged
3.7.1.50 #111
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
PalNilsson
commented
Feb 13, 2024
- Updated lsetup ‘root pilot’ to lsetup ‘root pilot-default’
- Requested by A. De Silva
- Updated python executable for running open_remote_file script (now explicit ‘python3’)
- Requested by A. De Silva
- Reporting error code 1310 when exception has been caught while executing payload
- Never include output files in log
- Previously, output files were left in payload work dir for looping jobs
- Requested by T. Korchuganova
- Now reporting support for IPv6 (or lack of) in pilot log
- Dumping explicit IPs to log
- Using get() instead of direct dictionary lookup to prevent problem with transfer() call in harvester related code
- Housekeeping
- Processed ~60% of all files with Flynt (+ manual changes for the strings that Flynt missed or couldn’t handle)
- Flynt converts strings from from % and .format to f-strings
- Linting with pylint status: ~50% of all module have a score of 9-10
- Processed ~60% of all files with Flynt (+ manual changes for the strings that Flynt missed or couldn’t handle)
- When the pilot has intercepted an external kill signal, it sends SIGTERM followed by SIGKILL 3 s later to the main payload process
- The 3 s delay might be too short and could lead to lingering payload threads, so it was increased to 10 s
- Added new pilot error code (1208) for SIGINT
- Rubin
- Do not abort pilot when getJob returns None
- Now experiment specific
- Requested by W. Guan
- Do not abort pilot when getJob returns None
- Bug fixes
- The exit code for a failed download of a new proxy (following an expired proxy/certificate) was lost. The job should now fail as expected
- Reported by R. Walker
- Updated and corrected shell exit code conversions after kill signal
- Now reporting unique exit code for different kill signals
- Reported by P. Love
- Fixed an issue with real-time logging in multi-job pilots
- The real-time logging was prevented from starting in later jobs
- The exit code for a failed download of a new proxy (following an expired proxy/certificate) was lost. The job should now fail as expected
# Conflicts: # pilot/control/job.py
updates to support finegrainedproc eventservice
…cted RT logic for multi-jobs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.