Skip to content
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

Closed
ekraffmiller opened this issue Nov 1, 2023 · 5 comments
Closed

Github Action failing for e2e test #213

ekraffmiller opened this issue Nov 1, 2023 · 5 comments

Comments

@ekraffmiller
Copy link
Contributor

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:
Screenshot 2023-11-01 at 10 33 09 AM

@pdurbin
Copy link
Member

pdurbin commented Nov 1, 2023

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...

      - name: Dump docker logs on failure
        if: failure()
        uses: jwalton/gh-docker-logs@v2
        with:
          dest: './logs'
      - name: Tar logs
        if: failure()
        run: tar cvzf ./logs.tgz ./logs
      - name: Upload logs to GitHub
        if: failure()
        uses: actions/upload-artifact@master
        with:
          name: logs.tgz
          path: ./logs.tgz

... 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.

pdurbin added a commit that referenced this issue Nov 1, 2023
For troubleshooting this issue:

- #213
@pdurbin
Copy link
Member

pdurbin commented Nov 1, 2023

I would suggest dumping a copy of the logs so we can determine what's failing.

I just made a pull request for this:

@pdurbin
Copy link
Member

pdurbin commented Nov 1, 2023

e2e tests are failing because deployment of the Dataverse war file is failing with Boot Command deploy failed PlainTextActionReporterFAILUREDescription: deploy AdminCommandError occurred during deployment: Exception while loading the app : jakarta.ejb.CreateException: Initialization failed for Singleton ConfigCheckService.

Maybe it's this? Could not create directory /dv/docroot for docroot space (see dataverse.files.docroot): class java.nio.file.AccessDeniedException? Not sure.

From dev_dataverse.log.txt via logs.tgz at https://github.com/IQSS/dataverse-frontend/actions/runs/6723081302?pr=214

pdurbin added a commit that referenced this issue Nov 1, 2023
@pdurbin
Copy link
Member

pdurbin commented Nov 2, 2023

Fixed by this PR:

Closing. Thanks, @poikilotherm ❤️ !

@pdurbin pdurbin closed this as completed Nov 2, 2023
pdurbin added a commit that referenced this issue Nov 2, 2023
@pdurbin
Copy link
Member

pdurbin commented Jan 12, 2024

jayanthkomarraju pushed a commit to jayanthkomarraju/dataverse-frontend that referenced this issue May 31, 2024
For troubleshooting this issue:

- IQSS#213
jayanthkomarraju pushed a commit to jayanthkomarraju/dataverse-frontend that referenced this issue May 31, 2024
jayanthkomarraju pushed a commit to jayanthkomarraju/dataverse-frontend that referenced this issue May 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants