Closed Bug 757692 Opened 13 years ago Closed 13 years ago

run_signscript should never return success for a killed worker

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

Details

(Whiteboard: [signing])

Attachments

(1 file)

We currently rely on proc.poll()'s return value to decide what we return. However, workers that don't handle SIGINT well or otherwise return 0 when killed can result in unwanted behaviour.
Set a flag when the timer runs out. If the flag is set, we should ignore the child's return code and use -1 instead. There may be a more elegant way to refactor the block and avoid using the flag, but it's not coming to me right now.
Attachment #626296 - Flags: feedback?(bhearsum)
Comment on attachment 626296 [details] [diff] [review] Set error rc when child process is killed Will try to look at this soon, Catlee should probably look, too.
Attachment #626296 - Flags: feedback?(catlee)
Attachment #626296 - Flags: feedback?(catlee) → feedback+
Assignee: nobody → bhearsum
Whiteboard: [signing]
Assignee: bhearsum → edransch.contact
Attachment #626296 - Flags: feedback?(bhearsum) → review+
Looks like this just needs to be checked in. I'll see if I can do that later this week.
Assignee: edransch.contact → nobody
Assignee: nobody → bhearsum
Comment on attachment 626296 [details] [diff] [review] Set error rc when child process is killed This patch applied cleanly to lib/python/signing/server.py and passes all tests. It looks sane and safe still, so I went ahead and landed it. Planning to restart the signing servers today.
Attachment #626296 - Flags: checked-in+
All signing servers have been updated for this change.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: