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
Try SAGE_ROOT as base of argument to "sage -t" #5902
Comments
comment:1
Attachment: sage_scripts-sage-test-path.patch.gz Looks good to me! |
Author: Tim Abbott |
Reviewer: Mike Hansen |
comment:3
It should not work. "sage -t" is supposed to take the path to a file. If you're not in SAGE_ROOT, then devel/sage/sage/rings/polynomial/pbori.pyx is not a file. It's like with any other unix command. E.g., you wouldn't expect
to magically work if you're not in SAGE_ROOT. Note that Mike Hansen just gave this a positive review. I strongly disagree. |
comment:4
Hi William, My motivation for this change was that when you run "sage -testall", for each test it prints out what it is running as sage -t devel/sage/sage/rings/polynomial/pbori.py since $SAGE_ROOT/sage changes directory to SAGE_ROOT before proceeding. So that if you copy-and-paste that output from "sage -testall" to run the test a second time, it doesn't work. |
Merged: sage-4.1.alpha2 |
Changed merged from sage-4.1.alpha2 to sage-4.1.alpha3 |
Running
seems to not work for me sometimes when the current working directory is not SAGE_ROOT. I don't really understand what is going wrong here, since there is a "cd" in $SAGE_ROOT/sage, but I've heard other people complain about issues with this.
The attached patch caused the problems to go away for me.
Component: doctest coverage
Author: Tim Abbott
Reviewer: Mike Hansen
Merged: sage-4.1.alpha3
Issue created by migration from https://trac.sagemath.org/ticket/5902
The text was updated successfully, but these errors were encountered: