Commit a767a83
committed
perilog: raise non-fatal job exception on epilog failure
Problem: Job epilog failures do not raise job exceptions. This made
sense when the epilog was used for administrative purposes, but now
that most of that has moved to housekeeping, the epilog is meant to
include cleanup necessary for job completion, and therefore an epilog
failure should be reflected in the job eventlog and the user notified.
Raise a non-fatal job exception on epilog failure. A non-fatal
exception is used so that it does influence the job status while
still allowing the exception to be logged.
Fixes #62491 parent fce96cd commit a767a83
1 file changed
+19
-4
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
438 | 438 | | |
439 | 439 | | |
440 | 440 | | |
| 441 | + | |
| 442 | + | |
| 443 | + | |
| 444 | + | |
| 445 | + | |
| 446 | + | |
| 447 | + | |
| 448 | + | |
| 449 | + | |
| 450 | + | |
| 451 | + | |
| 452 | + | |
| 453 | + | |
| 454 | + | |
| 455 | + | |
| 456 | + | |
| 457 | + | |
| 458 | + | |
| 459 | + | |
441 | 460 | | |
442 | 461 | | |
443 | 462 | | |
444 | | - | |
445 | | - | |
446 | | - | |
447 | | - | |
448 | 463 | | |
449 | 464 | | |
450 | 465 | | |
| |||
0 commit comments