Closed miguelcleon closed 6 years ago
@lsetiawan any idea why this is failing travis? It seemed like maybe it has to do with tests, but that doesn't seem to be the case.
@lsetiawan I'm writing some tests just in case that might fix it. It is difficult to imagine writing all of the tests that it might be a good idea to have. There are just so many.
I've restarted the job, it was a giving a file not found error, but it doesn't say what file.
@lsetiawan ok, it has continued to do this 4th or 5th time so far, the only thing I changed in all of those cases were the documentation.
@ocefpaf any idea why this is failing? The error we get is:
ERROR: file not found: discover
@ocefpaf I added a test because it looks like it might be a problem with test discovery? I don't know but it seemed like it would be worth trying here is the branch that failed https://travis-ci.org/ODM2/ODM2-Admin/builds/312503780?utm_source=github_status&utm_medium=notification
still failed and it didn't run the test.
I moved the test I added which works locally but it still did not run on Travis and it exited with the same error.
@miguelcleon and @lsetiawan the testing framework here was design for a installable package. Because #102 was never accepted we need to change the logic. See https://github.com/ODM2/ODM2-Admin/pull/191
Note that #191 will fail b/c we must configure the django app before running the tests. I'll leave that to the django experts :wink:
is my .travis.yml file wrong?
I think that #191 is the right fix to .travis.yml
to make the tests to run. But we do need need to configure the django app.
@lsetiawan ok, in this latest commit, I just changed thematrix:
section, I'm not sure what else to change at the moment. I need to work on something else for a little bit.
See https://github.com/ODM2/ODM2-Admin/pull/191/commits/12d37851dae467cb148f0f58bdcb795a547bb02a The matrix:
shouldn't need to change.
OK, latest commit attempts to replicate https://github.com/ODM2/ODM2-Admin/pull/191/commits/12d37851dae467cb148f0f58bdcb795a547bb02a maybe it will work
Now the error is OSError: libgeos-3.5.0.so: cannot open shared object file: No such file or directory
Seems to be a problem with gdal.
The import line it is failing is from models.py line 16:
from django.contrib.gis.db import models as gis_models
that is also the first django import line. I'm going to try moving it, to see if the next import also errors.
Gimme a sec, lemme try this out locally.
ok
latest commit fails on the below, other django.db and django.core imports worked.
from django.contrib.gis.geos import GEOSGeometry
I tried this locally and getting a different error... frustrating. hmm... django.contrib.gis.geos.error.GEOSException: Error encountered checking Geometry returned from GEOS C function "GEOSWKTReader_read_r"
I have the same exact packages as in travis.
maybe @ocefpaf has an idea about what else to try?
I'm away from my laptop for a few days but I'll try to take a quick look tomorrow.
On Dec 20, 2017 20:58, "Miguel Leon" notifications@github.com wrote:
maybe @ocefpaf https://github.com/ocefpaf has an idea about what else to try?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ODM2/ODM2-Admin/pull/190#issuecomment-353207430, or mute the thread https://github.com/notifications/unsubscribe-auth/AA6BL3zfZhpGim4D-qa5IXKz8uGx6Eowks5tCZEXgaJpZM4Q4LjC .
@lsetiawan the django
version used here is quite and inconsistent with conda-forge
's gdal
and geos
.
The options are:
conda-forge
and try to see if there are wheels for those;django
to 2.0 where the geos
string parsing was fixed, see https://github.com/django/django/commit/78c155cf2e5a27fd2db18c2d46953b1b0fdba829#diff-e0475de5c597e1c67bb40752a38f2276django >=1.10.6
Any those will require some considered effort! My recommendation is to "future proof" the app and go for django 2.0
. The second option would be the backport.
last PR failed on travis. It seems like that shouldn't have happened as it only contained doc updates