-
Notifications
You must be signed in to change notification settings - Fork 80
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
Porting to Solaris #16
Comments
Originally reported as mantis:0000229 at Fri Sep 7 12:27:52 2012. |
At Fri Sep 7 15:19:05 2012: Note that all or most of the failures are not related to Solaris per se as the same code fails on Linux. |
At Fri Sep 7 16:38:21 2012: Current failing tests as of f8d5b06 are
The JNI tests are failing as there is no JDK available |
At Fri Sep 7 17:09:33 2012 attached testlogs.tgz, 1514215 bytes, application/octet-stream. |
Issue migrated from Mantis to GitHub with Mantis status new and resolution open at Wed Sep 12 12:59:42 2012 using sp-mantis2github version 0.91 |
The jni tests 1 and 3 fail on Solaris because libservald.so is not being built on Solaris, presumably because of the 64-bit limitation (the NaCl libraries are not built with -fPIC). |
The dnahelper tests all PASS on Solaris, if run serially not concurrently. The failures documented in the attachment were all caused by long delays in the servald process when sending a request to the dnahelper child process. |
To help investigate issue #16, 'rhizomeprotocol' test case 1 failing on Solaris.
ca6d8f4 fixes the broken rhizomeprotocol tests. |
Same problem that broke most of the 'dnahelper' test fixtures; the dnahelper script was using #!/bin/sh, which on Solaris is not Bash.
All tests except the jni suite now pass on Solaris. You may have to run them serially not concurrently. |
All test cases pass on Solaris (see issue #16) except the 'jni' tests because there is no Java compiler available on Solaris, and the new 'rhizomeprotocol' tests from the rhizomedirect branch, which have always failed.
servald monitor on a solaris node fails, and the server reports: ERROR: monitor.c:326:monitor_new_client() getpeerucred(): Bad address [errno=14] |
Probably the monitor CLI client has never worked on Solaris, considering that it is not covered by any tests... |
To assist diagnosis of latest Solaris port bug, issue #16.
The 'solaris' branch has changes to port Serval to Solaris.
After some changes (and one outright bug fix 2ccbc54 basic things work.
Note that the version of Bash installed on serval1 is very old so I am using a hand built bash 4.2.
However many tests fail, eg
Mantis severity: minor
Mantis priority: normal
Mantis project: Porting
Can reproduce: N/A
The text was updated successfully, but these errors were encountered: