-
-
Notifications
You must be signed in to change notification settings - Fork 660
Run long test in test-new #39867
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
Run long test in test-new #39867
Conversation
Documentation preview for this PR (built with commit 449b37f; changes) is ready! 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Hm, isn't it weird that https://github.com/sagemath/sage/actions/runs/14269492447/job/39999206478?pr=39867 takes only 9 minutes to build while https://github.com/sagemath/sage/actions/runs/14269492447/job/39999206890?pr=39867 takes 23 minutes to build? |
sagemathgh-39867: Run long test in test-new sagemath#39641 introduced an issue that long new tests are not ran in test-new. This is an issue because then the author is only notified by the failure when test-long finishes. (e.g. happened to me in sagemath#39733 .) ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#39867 Reported by: user202729 Reviewer(s): Tobias Diez
sagemathgh-39867: Run long test in test-new sagemath#39641 introduced an issue that long new tests are not ran in test-new. This is an issue because then the author is only notified by the failure when test-long finishes. (e.g. happened to me in sagemath#39733 .) ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#39867 Reported by: user202729 Reviewer(s): Tobias Diez
sagemathgh-39867: Run long test in test-new sagemath#39641 introduced an issue that long new tests are not ran in test-new. This is an issue because then the author is only notified by the failure when test-long finishes. (e.g. happened to me in sagemath#39733 .) ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#39867 Reported by: user202729 Reviewer(s): Tobias Diez
#39641 introduced an issue that long new tests are not ran in test-new.
This is an issue because then the author is only notified by the failure when test-long finishes. (e.g. happened to me in #39733 .)
📝 Checklist
⌛ Dependencies