Commit 29eccf6
committed
Force SIGTERM broadcast at epoch/validation boundaries
When broadcast_sigterm_every_n_steps > 1, SIGTERM could arrive between
broadcasts near the end of an epoch. Without a forced check, rank 0
would exit while other ranks hang waiting at the next collective
(e.g. validation barrier). This adds a forced broadcast whenever the
epoch ends or validation is about to start.1 parent b2ea3e2 commit 29eccf6
2 files changed
Lines changed: 41 additions & 0 deletions
File tree
- src/lightning/pytorch/loops
- tests/tests_pytorch/loops
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
397 | 397 | | |
398 | 398 | | |
399 | 399 | | |
| 400 | + | |
| 401 | + | |
| 402 | + | |
| 403 | + | |
| 404 | + | |
| 405 | + | |
| 406 | + | |
| 407 | + | |
| 408 | + | |
| 409 | + | |
| 410 | + | |
| 411 | + | |
400 | 412 | | |
401 | 413 | | |
402 | 414 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
261 | 261 | | |
262 | 262 | | |
263 | 263 | | |
| 264 | + | |
| 265 | + | |
| 266 | + | |
| 267 | + | |
| 268 | + | |
| 269 | + | |
| 270 | + | |
| 271 | + | |
| 272 | + | |
| 273 | + | |
| 274 | + | |
| 275 | + | |
| 276 | + | |
| 277 | + | |
| 278 | + | |
| 279 | + | |
| 280 | + | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
| 286 | + | |
| 287 | + | |
| 288 | + | |
| 289 | + | |
| 290 | + | |
| 291 | + | |
| 292 | + | |
0 commit comments