-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
sympy-bot sometimes does not report doctest failures #94
Comments
Is it returning non-zero? That's how it checks if the tests failed or not. |
Do you happen to still have the log locally in your terminal history? The return code will be printed there (but it's not included in the report). |
Sorry for being so unresponsive; I'm quite busy with uni. Since sympy-bot reported "fail" anyway (due to the mathml test). The bin/doctest command does return non-zero, if this is what you are asking. [NB this can be tested, for example, in commit dfb0dfa.] |
I must have misread the logic in SymPy-bot then, because it looked like it reports failure based solely on the exit value. |
Hi, currently I collect ideas for my GSoC proposal about improving functionality and fixing bugs in sympy-bot. ness01, sympy/sympy-bot@dfb0dfa is no longer valid and gives 404, I'll thank to you if you could help me to reproduce it. |
no it's a sympy commit: sympy/sympy@dfb0dfa |
ok, I asked because in sympy/sympy-bot#94 (comment) you referred to sympy-bot |
That link was auto-created by github. You should be able to verify this issue by checking out said sympy On 26.03.2012 13:49, Michael Mayorov wrote:
|
Which is actually non-trivial to do, so you should also add a way to do this in sympy-bot. |
In a recent pull request, I ran the bot and it reported no failuers [0]. However, there was a doctest failure in the tutorial.
[0] http://reviews.sympy.org/report/agZzeW1weTNyDAsSBFRhc2sYn8wLDA
Note that the bot reports failure, because the mathml test indeed fails. But the doctest fails too, without being reported!
The text was updated successfully, but these errors were encountered: