Skip to content
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

Enable xdoctest runner in CI for real this time #83816

Closed
wants to merge 37 commits into from

Conversation

Erotemic
Copy link
Contributor

@Erotemic Erotemic commented Aug 21, 2022

Builds on #83317 and enables running the doctests. Just need to figure out what is causing the failures.

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu

@facebook-github-bot
Copy link
Contributor

facebook-github-bot commented Aug 21, 2022

🔗 Helpful links

✅ No Failures (0 Pending)

As of commit 7b38a9a (more details on the Dr. CI page):

Expand to see more

💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

@facebook-github-bot facebook-github-bot added the oncall: distributed Add this issue/PR to distributed oncall triage queue label Aug 21, 2022
@albanD albanD removed their request for review August 22, 2022 15:52
@Erotemic Erotemic force-pushed the dev/enable-xdoctest-for-real branch 2 times, most recently from f0b140b to ef7aa07 Compare August 24, 2022 13:35
@Erotemic
Copy link
Contributor Author

Latest commits disable more of the doctests in hopes that some subset of them are causing the errors, if so I'll start to hone in on exactly which ones are problematic.

While doing this I started linting the doctests to help ensure they also conform with pep8 standards.

@ngimel ngimel added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Aug 24, 2022
@Erotemic Erotemic force-pushed the dev/enable-xdoctest-for-real branch from eab13ab to db3f034 Compare August 28, 2022 00:30
@ezyang
Copy link
Contributor

ezyang commented Dec 26, 2022

nuuuu you pushed lol. I was pretty sure the previous ci was going to be ok. I've confirmed the lief errors are not your fault and was going to bypassed them

@Erotemic
Copy link
Contributor Author

It had already failed by the time I force pushed. Your POSIX branch (57dcd93) is merged in what I recently pushed.

Either way, if you want to try something, I won't touch it.

@ezyang
Copy link
Contributor

ezyang commented Dec 26, 2022

well, now we wait. The failures I'm expecting to see are the py-lief binary ones, as well as a mypy failure on sm86

@ezyang
Copy link
Contributor

ezyang commented Dec 29, 2022

@pytorchbot merge -f "all failures are preexisting failures"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/binaries Trigger all binary build and upload jobs on the PR ciflow/trunk Trigger trunk jobs on your pull request cla signed Merged oncall: distributed Add this issue/PR to distributed oncall triage queue open source release notes: quantization release notes category release notes: releng release notes category Stale triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants