-
-
Notifications
You must be signed in to change notification settings - Fork 491
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
spkg-check.in: Do not use sdh_make to do 'make check', to avoid misleading messages #29501
Comments
comment:1
Maybe just create a new function called |
This comment has been minimized.
This comment has been minimized.
New commits:
|
This comment has been minimized.
This comment has been minimized.
Commit: |
Author: Matthias Koeppe |
comment:7
maybe, for uniformity, not |
comment:8
I worded it like this because if SAGE_CHECK=warn, then it is not an error but only a warning. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
Dependencies: #29510 |
comment:11
rebased on top of #29510 to remove a merge conflict |
comment:12
needs review |
Reviewer: Dima Pasechnik, John Palmieri |
comment:13
Looks good to me. |
comment:14
Thank you! |
Changed branch from u/mkoeppe/spkg_check_in__do_not_use_sdh_make_to_do__make_check_ to |
sdh_make
, even when used formake check
, prints the misleading message "Error building $PKG_NAME"In the present ticket, we fix this.
We note that when
sdh_make
is used for building inspkg-install.in
, there is duplication with a message printed bysage-spkg
afterwards. For example in https://github.com/mkoeppe/sage/runs/581877049:However, as this does not have the potential to mislead, we will take care of this on another ticket.
Depends on #29510
CC: @dimpase @jhpalmieri @embray
Component: build
Author: Matthias Koeppe
Branch/Commit:
c53ddc7
Reviewer: Dima Pasechnik, John Palmieri
Issue created by migration from https://trac.sagemath.org/ticket/29501
The text was updated successfully, but these errors were encountered: