-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Switch to setup-micromamba action #7213
base: main
Are you sure you want to change the base?
Conversation
fedefb7
to
c490e50
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #7213 +/- ##
===========================================
+ Coverage 55.50% 75.92% +20.41%
===========================================
Files 101 100 -1
Lines 16862 16875 +13
===========================================
+ Hits 9360 12813 +3453
+ Misses 7502 4062 -3440 |
c490e50
to
03bebb6
Compare
I think the error may be fixed here: pymc-devs/pytensor#678 |
|
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.
Looks much simpler.
Do we need pymc-devs/pytensor#678 here? |
Worth a try. |
Ok, rebased. |
Yeah, you can only rerun failed runs once everything is done |
Just started the rerun. Any idea why I can't view logs (see screenshot)? Is this a GH outage? |
Viewing the CI logs is still really flaky for me, but somehow I was able to get a glimpse of:
Then for attempt #2, which I believe was post-rebase, I think I was still seeing the old "filename too long" error. 😢 But I can't access the logs in order to paste them here... Am I the only one who is having trouble viewing the CI logs? |
Regarding
|
@ricardoV94, here I at least have a "Re-run" link, even though it doesn't appear to have actually triggered a rerun yet. |
Description
Related Issue
Checklist
Type of change
📚 Documentation preview 📚: https://pymc--7213.org.readthedocs.build/en/7213/