Name |
Last commit
|
Last update |
---|---|---|
.. | ||
install | ||
jenkins | ||
packer | ||
vagrant | ||
vpc-tools | ||
import_xml_courses.py | ||
jinja_check.py | ||
sync_hooks.sh |
``` 13:08:11 + ret=0 13:08:11 + echo 0 13:08:11 0 13:08:11 + '[' 0 -ne 0 ']' 13:08:11 Build step 'Virtualenv Builder' marked build as failure 13:08:11 [ssh-agent] Stopped. 13:08:11 Finished: FAILURE ``` The example above is a snippet from jenkins which the integration test runs into, meaning it is often suceeding but reporting it as failure. There is still an issue with the cms worker which is related to 'stopwaitsecs' which is really high for all workers due to grading. That work will need to be refactored so that cms workers don't wait so long before killing the worker. The problem is the same as what is described here but more investigation will be useful. http://stackoverflow.com/questions/9971627/why-is-celery-not-shutting-down-cleanly
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
install | Loading commit data... | |
jenkins | Loading commit data... | |
packer | Loading commit data... | |
vagrant | Loading commit data... | |
vpc-tools | Loading commit data... | |
import_xml_courses.py | Loading commit data... | |
jinja_check.py | Loading commit data... | |
sync_hooks.sh | Loading commit data... |