{"version":"2.1.234","anchor":"eval-runner-handles-sigterm-and-records-which-signal-ended-t","canonical_anchor":"eval-runner-handles-sigterm-and-records-which-signal-ended-t","heading":"Eval runner handles SIGTERM and records which signal ended the run","tier":"internal","area":"Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/eval-runner-handles-sigterm-and-records-which-signal-ended-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Eval runner handles SIGTERM and records which signal ended the run\n\nThe eval runner now handles SIGTERM as well as interrupt, and reports which ended the run.\n\n**What**\n\nThe eval CLI now handles SIGTERM as well as SIGINT, printing its own message and latching whichever signal arrived first so the run can report how it ended.\n\n**Details**\n\n- Eval temporary directories are resolved through realpath before use.\n- The HTML report relabels the judge evidence block to explain that an image appears there as a description of what was sent.\n\n**Evidence**\n\n`Terminated \u2014 finishing up\u2026`\n\n- Area: Eval\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}