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
There is another semi-related failure in pcds-5.5.1-dev.
The static symbol pVersionCAC which whatrecord uses to determine the binary version is not present in the conda-forge epics-base softIoc executable, as it's instead part of the bundled shared library libca.so:
(pcds-5.5.1-dev) $ gdb epics/lib/linux-x86_64/libca.so.4.13.8
(gdb) p pVersionCAC
$1 = "@(#) EPICS 7.0.5, CA Client Library"
The test suite makes too many PCDS-specific assumptions about the environment to be useful.
Additionally, most facilities (outside of SLAC!) use dynamic linking for their EPICS binaries.
The tool may need to be extended to better support dynamic linking - which may make it a bit too complicated:
Running a softIoc binary just to have it load shared libraries (i.e., break main; continue; p pVersionCAC) even just to main seems bad and a bit error-prone
It could rely on ldd (on Linux, at least) to match the libca shared library and get info with gdb from there (this also seems complicated and error-prone)
I'd say for now:
xfail gdb tests
Keep assuming statically-built softIoc for our own purposes
If anyone shows interest in the tool from a facility that uses dynamic linking, re-evaluate at that point
Expected Behavior
Tests should have parity on the TravisCI and when run locally at LCLS.
Current Behavior
The gdb test fails when run on psbuild-rhel7, see pcdshub/pcds-envs#253
Possible Solution
Idk, it might be a server configuration issue
Steps to Reproduce (for bugs)
Context
This adds some noise to the pcds-envs unit testing suite.
Your Environment
pcds-5.5.0
The text was updated successfully, but these errors were encountered: