-
Notifications
You must be signed in to change notification settings - Fork 186
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
[QA][CI] Have tests running with various deployment setup in CI #7614
Comments
@saw-jan This issue needs to be discussed whether to invest time for doing and running such things in drone as it seems to be whole lot of task. |
Setup with e2e PR: #10482 |
|
I can reproduce the large upload failure with a docker-compose setup. |
Now I can reproduce it even when running from host machine. If I use this compose, the large upload test passes. Note ocis:
image: owncloud/ocis-rolling:master
ports:
- 9200:9200
environment:
OCIS_URL: https://localhost:9200
... Run test with: BASE_URL_OCIS=localhost:9200 \
HEADLESS=true \
pnpm test:e2e:cucumber tests/e2e/cucumber/features/smoke/uploadResumable.feature But if I do the following then I cannot upload file larger than 9MB ocis:
image: owncloud/ocis-rolling:master
ports:
- 9200:9200
environment:
OCIS_URL: https://host.docker.internal:9200
...
extra_hosts:
- host.docker.internal:host-gateway Run test with: BASE_URL_OCIS=host.docker.internal:9200 \
HEADLESS=true \
pnpm test:e2e:cucumber tests/e2e/cucumber/features/smoke/uploadResumable.feature |
I see these logs: storageusers-2-1 | {"level":"info","service":"storage-users","pkg":"rhttp","traceid":"47503678543d4903986757df053c350c","time":"2024-11-19T10:25:42Z","line":"github.com/cs3org/reva/[email protected]/internal/http/interceptors/auth/auth.go:195","message":"skipping auth check for: /data/tus/2da25800-d76b-4257-82e4-18b92c086bb9"}
storageusers-2-1 | {"level":"warn","service":"storage-users","pkg":"rhttp","traceid":"47503678543d4903986757df053c350c","time":"2024-11-19T10:25:42Z","line":"github.com/cs3org/reva/[email protected]/internal/http/interceptors/auth/auth.go:248","message":"core access token not set"}
|
And using this cors config made the test pass ( 😵💫 ): OCIS_CORS_ALLOW_ORIGINS: https://host.docker.internal:9200,https://host.docker.internal:9201 |
Currently, we run tests against the ocis server started from a single binary. We want to have a CI setup where we can start multiple instances of a service (as a load balancing) so that we can test against various deployment strategies.
Tasks
[ ] unskipfixed with cors config ([QA][CI] Have tests running with various deployment setup in CI #7614 (comment))smoke
e2e test suite (see comment)Taken from:
The text was updated successfully, but these errors were encountered: