-
Notifications
You must be signed in to change notification settings - Fork 117
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
failing unit-test #645
Comments
@epifanio Try to run the tests with docs are outdated. We already using |
@cehbrecht , I ran the
I got a few skips (grass, mapserver) - I guess because of my basic configuration - the only failure was on What will be the best approach to build some up-to-date documentation? I guess also the OSGeoLive demo and quickstart are affected, right? I will work on a |
@epifanio thanks for looking at the "dusty" docs :) I don't know about OSGeoLive demo. @ldesousa @jachym do you have hints? I think the pipline with sphinx/readthedocs is broken: A quickstart sounds good :) Could be part of the sphinx docs ... or the |
@epifanio When we start a new pywps project, we use a cookiecutter template: It already contains a For some of our production deployments we use an ansible playbook (with nginx, postgres): For our Rook WPS we use the |
In other projects we are currently looking into writing docs with Markdown: It is a bit more fun to write in Markdown than in reStructuredText ;) Future options :) |
@cehbrecht thanks for all the pointers! I managed to get a basic WSGI WPS service running from the official HTTPD docker image. I am using Postgres as the DB backend. I found the cooky-cutter templating system very cool and quite useful for a production-like scenario, but hard to integrate into the official pywps repository to have a basic/simple CI workflow to run the test (like we have for the other geopython projects). I was thinking of building a basic docker-compose+dockerfile that could be used to build and test the latest pywps, and then add a few bits of instruction to make a simple demo up and running. For a potential demo for the OSGeoLive, looks like the processes available in the emu repository are a good starting point, perhaps with a notebook or two to test the processes using owslib. The OSGeoLive has already a jupyter environment. |
@epifanio The cookiecutter template has a Example in Emu: This could also be a Some processes in Emu were taken from the original pywps, like |
Description
Attempt to install and run unit-test
The software installs without error, following the documentation - trying to run the test, it fails with the following error:
After commenting the failing import and its related call() to
test_storage
, the rror becomes:Environment
Debian SID
3.9.10
git master
Steps to Reproduce
follow the documentation to run unit-test after successful installation
Additional Information
The text was updated successfully, but these errors were encountered: