Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Framework: Tracking excessive numbers of PR testing retries and failures #10849

Closed
bartlettroscoe opened this issue Aug 9, 2022 · 2 comments
Closed
Labels
CLOSED_DUE_TO_INACTIVITY Issue or PR has been closed by the GitHub Actions bot due to inactivity. MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. PA: Framework Issues that fall under the Trilinos Framework Product Area type: bug The primary issue is a bug in Trilinos code or tests

Comments

@bartlettroscoe
Copy link
Member

bartlettroscoe commented Aug 9, 2022

@trilinos/framework

Internal Issues:

Description

This issue is to note on and comment on some excessive usage of AT: RETEST and PR testing attempts and failures. This is a result of PR failures caused by the infrastructure and/or that can be reproduced locally. For example, the PR #10751 as of 8/9/2022 at 1 PM EDT is now up to 140 PR iteration failures and the AT: RETEST label as been manually set at least 132 times.

See discussion started in #3276 (comment) as well as the failures causing this in #10842, #10355, #10840, #10823, #10847 and #10841.

@bartlettroscoe bartlettroscoe added type: bug The primary issue is a bug in Trilinos code or tests PA: Framework Issues that fall under the Trilinos Framework Product Area labels Aug 9, 2022
@bartlettroscoe bartlettroscoe changed the title Tracking excessive numbers of PR testing retires and failures Tracking excessive numbers of PR testing retries and failures Aug 9, 2022
@bartlettroscoe bartlettroscoe changed the title Tracking excessive numbers of PR testing retries and failures Framework: Tracking excessive numbers of PR testing retries and failures Aug 9, 2022
@github-actions
Copy link

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and/or remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.
If it is ok for this issue to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.

@github-actions github-actions bot added the MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. label Aug 12, 2023
@github-actions
Copy link

This issue was closed due to inactivity for 395 days.

@github-actions github-actions bot added the CLOSED_DUE_TO_INACTIVITY Issue or PR has been closed by the GitHub Actions bot due to inactivity. label Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLOSED_DUE_TO_INACTIVITY Issue or PR has been closed by the GitHub Actions bot due to inactivity. MARKED_FOR_CLOSURE Issue or PR is marked for auto-closure by the GitHub Actions bot. PA: Framework Issues that fall under the Trilinos Framework Product Area type: bug The primary issue is a bug in Trilinos code or tests
Projects
None yet
Development

No branches or pull requests

1 participant