#9700 increase wait time for indexing on failing test#9703
Merged
Conversation
pdurbin
approved these changes
Jul 12, 2023
Member
pdurbin
left a comment
pdurbin
left a comment
There was a problem hiding this comment.
Makes sense. I'm going ahead and approving this but let's check that the API tests pass on this PR before merging.
|
📦 Pushed preview images as 🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name. |
This was referenced Jul 26, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
The test for moving linked datasets is failing intermittently. This PR doubles the wait time for the required reindexing to occur.
Which issue(s) this PR closes:
Closes #9700 Fix Jenkins tests before 5.14 release
Special notes for your reviewer: This is the only test that has caused build failures over the last couple of days, but it's obviously not a comprehensive fix.
Suggestions on how to test this: No functional changes to review. continue to monitor the Jenkins build for improvements or at least reduced incidence of failures
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation:
Link to build status: https://jenkins.dataverse.org/job/IQSS-dataverse-develop/