-
Notifications
You must be signed in to change notification settings - Fork 18
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
fix(build): Fix E2E tests #1526
Conversation
|
||
|
||
protected def singleAwaitingRequest(request: HttpRequest, duration: Duration = 5999.milliseconds): HttpResponse = { | ||
protected def singleAwaitingRequest(request: HttpRequest, duration: Duration = 7999.milliseconds): HttpResponse = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just in case you wonder why this odd number. It is easier to find the correct setting that needs to be tweaked. The timeout output is often not clear where it happened.
@@ -105,6 +105,52 @@ | |||
"@value" : "http://0.0.0.0:3336/ark:/72163/1/0001/H6gBWUuJSuuO=CilHV8kQwk/bXMwnrHvQH2DMjOFrGmNzgz.20180528T155203897Z" | |||
} | |||
}, | |||
"anything:hasGeometry" : { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume these values were introduced in #1514 but since the e2e tests were not run the difference in the test data was not detected.
Actually, what happened is that at some point we added ARK URLs and UUIDs to values. After that, some hard-coded data that was supposed to fail validation (e.g. it had a boolean property with a string object, to check whether |
… into fix/1525-e2e-tests
@subotic I don't understand what's happening. It does:
But then it says:
There is also this strange error, as if GraphDB sent a header saying that its response would be in GZIP format but the client couldn't unpack the file:
|
When I run all the tests outside Docker, they all pass. |
When I run the tests locally using |
Then
No, the only way would be to kill the created
|
I've updated the Docker image and restarted the tests. Let's see if this all that is needed. |
So do we still need this in
|
I don't think so. |
OMG the tests passed! |
Now it's failing because of this:
|
Which test changed after the merge? GraphDB doesn't have enough memory. |
No tests changed, it was the merge of #1527. Can we give GraphDB more memory? |
@subotic Does this mean we can't use GitHub CI? |
I don‘t think so.
This means that we need to find a way how it can work with Github CI. Unfortunately, there is no alternative. After doing some calculations, running it on our own hardware is not feasible cost wise. We could try and isolate the high memory tests with a HighMemory test tag and run them separately? |
OK the tests that use a lot of memory are the ones that create large texts with lots of standoff. I think we don't really need to run these in CI anyway, so I set them to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM :-)
e2e-tests-with-coverage
target inMakefile
.InstanceChecker
.InstanceChecker
access to the non-standard names of certain JSON properties.ResourcesRouteV2E2ESpec
InstanceCheckerSpec
ClientApiRouteE2ESpec
to loadanything-data.ttl
, now needed for client code generation.IIIF_BASE_URL
placeholder in E2E test files, because the Sipi URL is different when tests are run in Docker.Fixes #1525.