Skip to content

Build error with build id #8574742 #5287

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

Closed
pllim opened this issue Feb 13, 2019 · 4 comments
Closed

Build error with build id #8574742 #5287

pllim opened this issue Feb 13, 2019 · 4 comments
Labels
Support Support question

Comments

@pllim
Copy link
Contributor

pllim commented Feb 13, 2019

Details

We have recently switched from specifying a separate pip requirement file to using https://github.com/ejeschke/ginga/blob/master/readthedocs.yml with dependencies defined in https://github.com/ejeschke/ginga/blob/962ef1a0c341daf6668de9a5663b1beff6c79dcf/setup.cfg#L53-L54
(ejeschke/ginga#739). We have also switched from GitHub Services to using webhooks (ejeschke/ginga#744). I actually don't think the webhook switch has anything to do with this error, but rather the switch from requirements to YML broke something that was not triggered because GitHub Services stopped working.

Any help would be greatly appreciated. Thanks!

cc @ejeschke

Expected Result

Successful build.

Actual Result

Build failed with a cryptic and ironic "successful" message:

Successfully installed Jinja2-2.10 MarkupSafe-1.1.0 ...
@pllim
Copy link
Contributor Author

pllim commented Feb 13, 2019

FWIW, I tried wiping the "latest" build twice but without success.

@pllim pllim changed the title Build error id 8574742 Build error with build id #8574742 Feb 13, 2019
@stsewd stsewd added the Support Support question label Feb 13, 2019
@pllim
Copy link
Contributor Author

pllim commented Feb 15, 2019

Doh, there was a missing quote in the YAML! Sorry for the noise. 😬

@pllim pllim closed this as completed Feb 15, 2019
@stsewd
Copy link
Member

stsewd commented Feb 15, 2019

Hmm, we should give a better error though

@stsewd
Copy link
Member

stsewd commented Feb 18, 2019

So, when parsing the yaml, this generates ['recomended', "docs'"] It adds the ' to the element, so the error comes from another step. So, I think a better hint is #4288

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Support Support question
Projects
None yet
Development

No branches or pull requests

2 participants