nbconvert: Troubleshoot build error on RTD
RTD isn’t happy with the latest environment.yml changes and nbsphinx or ../. (https://github.com/jupyter/nbconvert/pull/432/files).
cc @michaelpacer P.S. If you create an account on RTD, I will add you as an admin/owner of the RTD instance. Just ping me once it is created 🌻
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 15 (15 by maintainers)
@michaelpacer You now have magic powers!
A 20 second intro to RTD administration (ignore if you already know this)
Advanced Settings Page
As currently set. The conda
environment.ymlfile should override these but YMMV.In fact, YMMV quite a bit with RTD builds. I don’t assume that a failed build means that my configuration is incorrect as sometimes RTD can be a bit stubborn about clearing out old cruft. As such, I set up a
test-projectfor prototyping builds (i.e.willingc/test-nbconvert).Builds Page
Click on a particular build to find out detail about how it failed.
You may also select a branch from the pull down and start a build.
Versions Page
Be nice to this page. It’s your friend.
On this page, you can click “edit” to enable or disable building of a branch.
Clicking the “wipe” button should clear out the cruft of old builds and what not. In practice, that does not always happen especially if RTD pushed changes recently.
My approach is typically the following if a build has failed but I think my code is fine:
Versions Main Menu
Versions tab from Admin Menu - does differ from Versions Main Menu
Ok, so I’m getting a strange error
“‘/opt/conda/envs/_build_placehold_placehold_placehold_placehold_placehold_placeho’ too short in: ncurses-5.9-9 Linking packages …”
Based on some of the other places where this has come up it might be a conda thing…and so I’m nuking my personal rtd builds because i might have given them too long of a name to manage.