You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
assertEquals("Current PID should match client credentials",
fails correctly, expecting pid, but getting 1.
If the test would continue, it would fail anyway, as all three pid, uid and gid are parsed wrongly during credential initialisation
linux x linux
myPid: 42170 # three real values
myUid: 1001
myGid: 1001
cc uid: 16383 # wrong client credentials
cc pid: 1
cc gid: -2070423904
sc uid: 16383 # samely wrong server credentials
sc pid: 1
sc gid: -2070421584
The values above are exemplar. They differs, canbe positive, but error is obvious.
Suspicion is going to endians or basic size type. Will continue digging.
Note, I had run all jnr-* tests on this ppc64le machine and no other projects (including ffi) had any issues. Only this one unixsocket's CredentialsFunctionalTest
The text was updated successfully, but these errors were encountered:
Hello!
When running on ppc64le, the test
jnr-unixsocket/src/test/java/jnr/unixsocket/CredentialsFunctionalTest.java
Line 79 in 0e180ee
If the test would continue, it would fail anyway, as all three pid, uid and gid are parsed wrongly during credential initialisation
linux x linux
myPid: 42170 # three real values
myUid: 1001
myGid: 1001
cc uid: 16383 # wrong client credentials
cc pid: 1
cc gid: -2070423904
sc uid: 16383 # samely wrong server credentials
sc pid: 1
sc gid: -2070421584
The values above are exemplar. They differs, canbe positive, but error is obvious.
I had debugged it into:
jnr-unixsocket/src/main/java/jnr/unixsocket/Credentials.java
Line 73 in 0e180ee
Which leads to jnr-ffi 's : https://github.com/jnr/jnr-ffi/blob/05cbacc8528e85b1dbff30be5b88cde4c6a9c6a7/src/main/java/jnr/ffi/Struct.java#L865 wehre it leaves my current knowlege a bit.
Suspicion is going to endians or basic size type. Will continue digging.
Note, I had run all jnr-* tests on this ppc64le machine and no other projects (including ffi) had any issues. Only this one unixsocket's CredentialsFunctionalTest
The text was updated successfully, but these errors were encountered: