sdf-jkl opened a new pull request, #11935: URL: https://github.com/apache/arrow-rs/pull/11935
# Which issue does this PR close? Closes #11548. # Rationale for this change From @Jefffrey's [review of #11631](https://github.com/apache/arrow-rs/pull/11631#pullrequestreview-5598578977): > some follow up work would be a way to notify if this miri run fails (e.g. auto create an issue) # What changes are included in this PR? Failed scheduled Miri runs in `apache/arrow-rs` open a `Daily Miri checks failed` issue linking the failed run and commit. Further failures leave an existing alert alone; maintainers close it after Miri passes again. Manual runs and forks do not create alerts. # Are these changes tested? Validated with a temporary workflow on my fork using simulated Miri partitions and the same alert script, with the repository/event guard adapted for manual fork runs: - A failure created [alert issue #8](https://github.com/sdf-jkl/arrow-rs/issues/8). - A [repeat failure](https://github.com/sdf-jkl/arrow-rs/actions/runs/40513403680) created no duplicate issue or comment. - A [successful run](https://github.com/sdf-jkl/arrow-rs/actions/runs/40513291680) produced no alert. # Are there any significant user-facing changes? No. AI assisted with the workflow implementation, documentation, and validation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
