Last three recipes have failed on merge into master
See original GitHub issueSeems like we’ve hit an api limit in:
https://travis-ci.org/conda-forge/staged-recipes/builds/196331121
GitHub API Rate Limit Info:
---------------------------
Currently remaining 5000 out of 5000.
Will reset in 0:59:59.349455.
Calculating the recipes which need to be turned into feedstocks.
No local changes to save
Current branch master is up to date.
No stash found.
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
GitHub API Rate Limit Info:
---------------------------
Currently remaining 5000 out of 5000.
Will reset in 0:59:58.597998.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How to avoid broken master with Pipelines for Merged Results ...
A maintainer sees a failed pipeline in the merge request. ... All they need to do is develop features with Pipelines for Merged...
Read more >How do I safely merge a Git branch into master?
I have to look in git log for the commit point on the test branch, switch back to master branch then do git...
Read more >Dealing with non-fast-forward errors - GitHub Docs
See the > 'Note about fast-forwards' section of 'git push --help' for details. You can fix this by fetching and merging the changes...
Read more >Git Merge | Atlassian Git Tutorial
Merging is Git's way of putting a forked history back together again. The git merge command lets you take the independent lines of...
Read more >git-rebase Documentation - Git
You will have to resolve any such merge failure and run git rebase ... For example, running git rebase master on the following...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It looks like the
ipympl
recipe is in a folder calledjupyter-matplotlib
and build is failing becauseconda-forge/ipympl-feedstock
was created, but a later part of the code is checking for and failing to findconda-forge/jupyter-matplotlib-feedstock
.I opened #2312 to fix this by renaming the
jupyter-matplotlib
folder to ipympl, so the two match, which should let things start building again. #2313 should fix the bug in earnest, but that should get more careful review, since I’m not as confident that there aren’t other points where a mismatch could cause breakdown.It is a good point @minrk, but it definitely slips below the radar. Really this should be handled programmatically. Either the linter should be catching the directory/package name mismatches as this is trivial to do programmatically and it is easy for human reviewers to miss or we should just always use the package name as the directory name shouldn’t really matter. Oddly enough I think adding this to the linter is easier.
xref: https://github.com/conda-forge/staged-recipes/issues/1073