-
Notifications
You must be signed in to change notification settings - Fork 16
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
Github Action failing for e2e test #213
Comments
As promised at standup, I added this to the agenda for tomorrow's containerization meeting: https://docs.google.com/document/d/1iE-DHDxWNK6OYNgqnLPo3i6pIH6Danw5rysXL_COjVc/edit?usp=sharing It looks like the last time the e2e test passed was Sep 22 at https://github.com/IQSS/dataverse-frontend/actions/runs/6275476306 I would suggest dumping a copy of the logs so we can determine what's failing. We use this...
... over at https://github.com/gdcc/api-test-runner/blob/main/.github/workflows/develop.yml Also, while 6 minutes (360 seconds) should be enough, we could simply increase the wait time and hope that fixes it. |
For troubleshooting this issue: - #213
I just made a pull request for this: |
e2e tests are failing because deployment of the Dataverse war file is failing with Maybe it's this? From dev_dataverse.log.txt via logs.tgz at https://github.com/IQSS/dataverse-frontend/actions/runs/6723081302?pr=214 |
Fixed by this PR: Closing. Thanks, @poikilotherm ❤️ ! |
For troubleshooting this issue: - IQSS#213
run fix-fs-perms.sh dv IQSS#213
The e2e test is consistently failing in Github Actions because the wait for containers to be ready times out.
Here is an example action-
https://github.com/IQSS/dataverse-frontend/actions/runs/6709488248/job/18232645812
and output:
The text was updated successfully, but these errors were encountered: