-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
debugging builds #6101
Comments
Do you have more output above your pasted output? You can also increase the debug output. Please also have a look at my attempt for TPP one year ago: https://github.com/bioconda/bioconda-recipes/compare/tpp?expand=1 TPP is not an easy one to start with :( Fee also free to start a WIP PR or a branch so that we can see the travis log and help you. |
Okay, I found this further up:
which explains what is wrong but not why it's failing in Docker and not on my system.
Can you (easily) guide me on how to do this or direct me to relevant documentation?
Is it considered okay/polite to submit a PR that I know is going to fail testing? |
Yes, that was my jumping-off point but I decided to go with TPP 5.0 because I can't get 4.8 to compile anymore even on my regular system. |
In worse cases I think this is not a problem. And TPP is a worse case and deserves help from as much people as we can get :) It fails probably in Docker for you, because in Docker there are very less libraries installed - you really need to specify all dependencies, even zlib and such. Try to do |
Thanks, this is exactly what I was looking for. I will see where I can take this and then return if I have further questions. |
I'm trying to put together my first bioconda recipes and am having trouble debugging. I follow the the instructions here using
simulate-travis.py
but the builds are failing and all I can see toward the end of the output iswhich doesn't seem to give any specifics. I can't find any relevant logs in
/tmp/miniconda
and I'm assuming that since it is a Docker build the relevant output gets lost with the instance.I can run the
build.sh
just fine outside of Docker, so I'm assuming there is something wrong in the Docker environment. How can I go about debugging this? Any advice is appreciated.FYI, the recipe in question is here and is related to galaxyproteomics/tools-galaxyp#108
The text was updated successfully, but these errors were encountered: