whizard is hosted by Hepforge, IPPP Durham

Opened 9 years ago

Closed 9 years ago

#755 closed defect (wontfix)

Test suite completely broken on El Capitan

Reported by: Juergen Reuter Owned by: kilian
Priority: P0 Milestone: v2.2.8
Component: core Version: 2.2.7
Severity: blocker Keywords:
Cc:

Description

On Mac OS X Darwin 10.11 (El Capitan) both the unit and functional test suite do not work before installation of WHIZARD. The reason is that the shared libraries on which the unit tests or the process libraries of the functional tests depend cannot be loaded by using DYLD_LIBRARY_PATH as the System Integrity Protocol (SIP) of El Capitan doesn't allow passing such variables to child processes. One solution (besides revising the whole test suite) would be to demand make install as a hook when performing make check. Opinions?

Change History (8)

comment:1 Changed 9 years ago by Juergen Reuter

As discussed with WK, procedure would be that developers have to switch off SIP, and the user is told to do make installcheck instead of make check. Or we use the hook as above.

comment:2 Changed 9 years ago by Juergen Reuter

As David Strubbe (MIT) suggested (actually he seems to be writing and maintaining some very interesting software packages on highly parallel methods for density functional methods) there is a solution for Macports, so my fear that El Capitan would break the Macports functionality of WHIZARD is gone. I guess there is no way to put the testsuite back on functional with SIP turned on (unless using an installhook to be executed before make check which would contradict all rules for autotools). I added notes in the manual, in the Wiki Page and in the 'BUGS' file. If there are no objections I'm tempted to close this ticket as 'won't fix' with a heavy heart. Comments?

comment:3 Changed 9 years ago by Juergen Reuter

Still waiting for comments !!!!!!!

comment:4 Changed 9 years ago by kilian

I'd go pragmatic and proceed as described.

After all, we (the devs) are responsible for testing. The testsuite is important to check if a given build environment/OS combination is sane. However, for Mac, the environment should be rather well defined, so it's not so important to have all tests on the user side.

comment:5 Changed 9 years ago by Juergen Reuter

Well, I have to switch off SIP anyhow as I build the release on my laptop, otherwise making releases would be hilariously constrained in the future. So Macports-User are safe with the changes bei Daniel Stubbe and people installing it themselves are warned in the manual and the Wiki etc. So, closing as won't fix?

comment:6 Changed 9 years ago by kilian

Yep.

comment:7 Changed 9 years ago by Juergen Reuter

Sadly closing as won't fix.

comment:8 Changed 9 years ago by Juergen Reuter

Resolution: wontfix
Status: newclosed
Note: See TracTickets for help on using tickets.