conda-forge.github.io: Feedstock Repo script failing
Running into an exception for the last 2 days in the feedstocks_repo build. This appears to be far enough into the script that none of us noticed. This can be seen in the log and down below.
Prefix: /home/travis/conda/tmp_envs/f5607ad6e1b89da01f30
Running command: ['python', '/home/travis/build/conda-forge/conda-forge.github.io/scripts/update_teams.py', './feedstocks_repo/feedstocks']
Traceback (most recent call last):
File "/home/travis/build/conda-forge/conda-forge.github.io/scripts/update_teams.py", line 91, in <module>
contents = env.from_string(''.join(fh)).render()
File "/home/travis/conda/tmp_envs/f5607ad6e1b89da01f30/lib/python3.5/site-packages/jinja2/environment.py", line 989, in render
return self.environment.handle_exception(exc_info, True)
File "/home/travis/conda/tmp_envs/f5607ad6e1b89da01f30/lib/python3.5/site-packages/jinja2/environment.py", line 754, in handle_exception
reraise(exc_type, exc_value, tb)
File "/home/travis/conda/tmp_envs/f5607ad6e1b89da01f30/lib/python3.5/site-packages/jinja2/_compat.py", line 37, in reraise
raise value.with_traceback(tb)
File "<template>", line 2, in top-level template code
jinja2.exceptions.UndefinedError: 'str object' has no attribute 'get'
CalledProcessError: Command '['python', '/home/travis/build/conda-forge/conda-forge.github.io/scripts/update_teams.py', './feedstocks_repo/feedstocks']' returned non-zero exit status 1
cc @pelson
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 42 (42 by maintainers)
Commits related to this issue
- Merge pull request #142 from ericdill/fix-139 WIP: Fixing #139 by using conda build MetaData object to load meta.yaml info — committed to conda-forge/conda-forge.github.io by jakirkham 8 years ago
Nice work on this yourself, @ericdill. The biggest piece was your code. π
Ouch! That long?!
β¦or maybe do something else interesting that you want to complete. I think we have a good sense of what is going on here now. Given what little time you have, maybe it can be better spent.
Ohhhhh I think I figured out the problem.
auditwheelhas the following build section:Donβt both of these skip sections result in the build section being totally empty? I bet that if we added number: 0 to the build section that this recipe would parse just fine
Oh does it work in 1.20.1 too? I know it works in master
@jakirkham Lets continue this discussion on #142.
Ok, give me a few minutes. PR incoming
Absolutely! Thanks for tracking this down, @pelson.