-
Notifications
You must be signed in to change notification settings - Fork 492
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
AccessIT Failing on Develop #5287
Comments
Something is broken enough that I can't even get the phoenix test suite to execute. I'm getting the following failure:
See https://build.hmdc.harvard.edu:8443/job/phoenix.dataverse.org-deploy-develop/304/console When stage 2 (deployment) doesn't finish like this, stage 3 (API tests) can't run. See http://guides.dataverse.org/en/4.9.4/developers/testing.html#how-the-phoenix-tests-work |
The phoenix server.log is saying this:
I should have emailed dataverse-dev after pull request #5267 was merged. In the future, we're going to run an experiment where developers can put instructions in their pull requests: #5284. |
I forgot that I put https://github.com/IQSS/dataverse/blob/96800f0f25e09d6b816bfb000fa68752b7184eed/doc/release-notes/5011-search-by-dataverse-alias.md in my merged pull request. 😄 |
I emailed the dev community to let them know about the Solr schema change: https://groups.google.com/d/msg/dataverse-dev/WwPRY23FyAA/VYeiHx0PBQAJ I re-ran the tests on phoenix and as of https://build.hmdc.harvard.edu:8443/job/phoenix.dataverse.org-apitest-develop/290/ we are down the known failures with account conversion in #5260 @sekmiller and I are still messing with his dev environment so I won't close this quite yet. |
All set here |
When adding integration tests for the request file access API I discovered that the AccessIT tests are failing in develop. Not sure at the moment which merge is causing the failure.
The text was updated successfully, but these errors were encountered: