-
Notifications
You must be signed in to change notification settings - Fork 3
Re-enable failing CLI Test #256
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
Conversation
|
Kudos, SonarCloud Quality Gate passed!
|
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #256 +/- ##
=============================================
- Coverage 70.26% 70.24% -0.02%
Complexity 1052 1052
=============================================
Files 47 47
Lines 6070 6070
Branches 799 799
=============================================
- Hits 4265 4264 -1
+ Misses 1467 1466 -1
- Partials 338 340 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
|
||
| package io.dockstore.client.cli; | ||
|
|
||
| import java.io.IOException; |
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.
There's already a ticket on consistent imports sorting; I think these changes match the web service's layout, but ultimately that ticket should solve.
🤔 maybe you have a slightly custom classpath? |
I don't think I do; it should be whatever IntelliJ thinks it is, based on Maven... does it work for you? Here's what I get: |
Oh I see, assertions are not enabled by default for running, just for tests. Yeah, I get the same thing |
|
@denis-yuen made you an assignee; if no changes are requested by Steve nor Kathy, please go ahead and merge. If changes are requested, I'll respond when I get back from vacation. |
|
Got another review and merged, never mind. |
Description
Re-enable failing CLI test by turning off Java assertions in the org.hibernate and subpackages. It also enabled the removal of System.exit catch that is no longer necessary.
This is less than ideal, but note that in prod the web service is not running with assertions enabled.
Notes:
assert this.isInitializing(), I can see the assertion would fail if assertions were enabled.If this approach is agreed upon, I will create a followup ticket to figure out the underlying assertion failure. I think it's there for optimization purposes, i.e., a call is being made to initialize an already initialized collection:
Review Instructions
Since this is a change to an integration test, if the tests pass after it's merged, it's done, and no further review necessary.
Issue
SEAB-5854
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!
./mvnw clean install