-
Notifications
You must be signed in to change notification settings - Fork 31
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
[#429] Send correct <option>
value for StartupPack
#430
Conversation
The following test failures were encountered with this change. It's not clear to me whether these were caused by the change. This was tested using the docker compose setup defined in the
|
Preparing to test against |
All tests passed against |
Ah, interesting. |
This may mean we need a separate branch for 4.3 or we need to make the tests operate differently based on the iRODS version. |
Made a few more changes. Running tests again against |
Learned that the final two test failures are due to Jargon not supporting the expanded permission levels in 4.3. If all tests pass, I'll run the test suite against 4.2 to make sure everything is still good. |
All tests passed for Running against If all tests pass, I'll do a final pass over the changes to make sure everything is handled correctly. |
All tests passed for Will double check the code changes before merging. |
jargon-core/src/main/java/org/irods/jargon/core/connection/IRODSServerProperties.java
Show resolved
Hide resolved
jargon-core/src/test/java/org/irods/jargon/core/pub/DataObjectAOImplTest.java
Outdated
Show resolved
Hide resolved
jargon-core/src/test/java/org/irods/jargon/core/pub/CollectionAOImplTest.java
Outdated
Show resolved
Hide resolved
jargon-core/src/test/java/org/irods/jargon/core/pub/QuotaAOImplTest.java
Outdated
Show resolved
Hide resolved
jargon-core/src/test/java/org/irods/jargon/core/pub/UserAOTest.java
Outdated
Show resolved
Hide resolved
jargon-core/src/test/java/org/irods/jargon/core/pub/CollectionAOImplTest.java
Outdated
Show resolved
Hide resolved
To determine whether the server version detection function is correct, I did the following:
Here are the test results ...
I'm now going to include all changes to the tests and see if they pass against iRODS 4.3.0. If they pass, then the server version detection function is fine as is. |
3e931d5
to
52edb9b
Compare
And here are the results.
These results represent the difference between 4.3.0 and 4.3.1. We'll have to add another server version detection method for 4.3.1. |
08f56f8
to
6486b6c
Compare
Latest run against 4.3.0.
Once I work this out, I'll run against 4.2.12 and 4.3.1. |
Test results against 4.3.1. The quota tests assumptions need to be changed so that the failing tests only run when the iRODS version is pre 4.3.0.
|
The failing test captured here, #430 (comment), just needs to skipped when testing against 4.3.0 because iRODS 4.3.0 has already shipped. The issue exists in 4.3.1, then we'll fix it for 4.3.2. |
All tests passed against 4.3.1 with this PR.
Rerunning against 4.3.0 again. |
so good. go go go. |
jargon-core/src/test/java/org/irods/jargon/core/pub/BulkFileOperationsAOImplTest.java
Outdated
Show resolved
Hide resolved
jargon-core/src/test/java/org/irods/jargon/core/pub/BulkFileOperationsAOImplTest.java
Outdated
Show resolved
Hide resolved
Another failure against 4.3.0.
Skipping since it is fixed in 4.3.1. |
Had to skip one user-tagging test for 4.3.0. All tests pass against iRODS 4.3.0 now.
Running tests against iRODS 4.2.12. |
All tests passed against iRODS 4.2.12.
Running against iRODS 4.3.1. |
The tests passed against 4.3.1, but it required a few runs to get there. The failures I saw were all due to the Bulk/StructuredFile APIs. I'm going to run the tests again just so we capture the failures, but I don't think they are a blocker for this PR since we're planning on replacing those APIs.
|
Here's the failure I'm seeing against 4.3.1.
Rerunning that test (without relaunching the docker containers) results in the test passing. That indicates the test may not be idempotent. Rerunning all tests (without relaunching the docker containers) in BulkFileOperationsAOImplTest pass too. The failure only occurs when running from a fresh environment (i.e. no previous run has occurred). |
Created #435 for the failing test. This isn't a blocker for this PR. |
15a93b8
to
d20cbf8
Compare
…3 permission levels.
d20cbf8
to
e609b41
Compare
This is required for proper communication over TLS/SSL.
Will run the test suite soon.