-
Notifications
You must be signed in to change notification settings - Fork 56
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
[BOT] Fix docs for ci_tools #1483
Conversation
Hello again! Thank you for this new pull request 🤩. Here is your checklist. Please tick items off when you have completed them or determined that they are not necessary for this pull request:
|
/bot run docs |
/bot run docs |
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.
Good job ! Your PR is using all the code it added/changed.
Hey @pyccel/pyccel-dev ! @EmilyBourne has just created this great new pull request! Check it out and let me know what you think! |
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.
This looks good
Hey @yguclu, @EmilyBourne, this PR is looking pretty good. @EmilyBourne and @sboof911 think it is ready to merge. Could you add your expertise to confirm that this follows all the coding conventions and fits in Pyccel's future plans? Thanks 😄 |
/bot run pr_tests |
Unfortunately your PR is not passing the tests so it is not quite ready for review yet. Let me know when it is fixed with |
Minor changes to comment block.
/bot run pr_tests |
Unfortunately your PR is not passing the tests so it is not quite ready for review yet. Let me know when it is fixed with |
Hey @yguclu, @EmilyBourne, this PR is looking pretty good. @EmilyBourne and @sboof911 think it is ready to merge. Could you add your expertise to confirm that this follows all the coding conventions and fits in Pyccel's future plans? Thanks 😄 |
Hey @yguclu, @EmilyBourne, this PR is looking pretty good. @EmilyBourne and @sboof911 think it is ready to merge. Could you add your expertise to confirm that this follows all the coding conventions and fits in Pyccel's future plans? Thanks 😄 |
/bot run pr_tests |
Unfortunately your PR is not passing the tests so it is not quite ready for review yet. Let me know when it is fixed with |
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.
Good job ! Your PR is using all the code it added/changed.
Coverage should not raise an issue if an
except
statement is not covered (we do not enforce coverage for error statements such asraise
anderrors.report
, this is similar and the body of theexcept
clause will still raise an issue if anything more complex is used). This PR addsexcept
to the exceptions.Correcting this leads to an error with the documentation. The error arises because
numpydoc
imports all files that it tests so all possible dependencies must be installed. This is corrected in this PR. This issue has previously been misunderstood and fixed by trying to import from different locations. The unnecessary code is therefore removed.The tests were triggering manually on this branch to ensure it can pass and to test the fix.