-
Notifications
You must be signed in to change notification settings - Fork 479
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
IQSS/8957 JWT creation test for DRS Archiver #8958
IQSS/8957 JWT creation test for DRS Archiver #8958
Conversation
Conflicts: src/main/java/edu/harvard/iq/dataverse/engine/command/impl/LocalSubmitToArchiveCommand.java
or create ones to compare with our local one. I'l probably add this back in the DRS archiver where we'll have other means to send the hashes.
probably not required - good practice/helped in debugging to be able to check sourcecode online which is for the current version.
note that the write to file part of the bag generation already tests the hash values of the individual files internally.
there are archived copies, or one can archive this dataset
(same signature as Dataset in 3b - inherit?)
GDCC/8914-COAR-compliant_messaging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm seeing a failure...
[ERROR] Failures:
[ERROR] DRSSubmitToArchiveCommandTest.createJWT:115
Doesn't https://github.com/IQSS/dataverse/runs/8216433360?check_suite_focus=true#step:5:1132 show it ran and didn't fail? |
@pdurbin - I don't see any reason it should fail only in jenkins - can a new run be triggered to see if this is repeatable? |
GDCC/9016-handle-no-file-PID-case-in-metrics
This is a small amount of code - a test that should pass. It was accidentally left out of earlier PRs. Shouldn't take much review or QA. Size 3 |
What this PR does / why we need it: Just a simple test created for HDC 3A / Archiving to DRS that didn't make it into the main PR.
Which issue(s) this PR closes:
Closes #8957
Special notes for your reviewer:
Suggestions on how to test this: Verify the test runs and doesn't fail in the auto build.
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: