On 4/24/2014 12:12 PM, Gibbs, David wrote:
On 4/24/2014 9:47 AM, Kevin A. McGrail wrote:
Bizarre... The non-replicatable behavior is very confusing.
And you were able to replicate this on a modern CentOS box?
Yep.
Even tried it on another system that's running Centos 5.
OK, I just tried it on yet another box ... this one is more 'virgin', as it's
ONLY used as a XEN virtual host.
This time all the tests passed.
So it's got to be something in the other systems configuration or environment
... but the question is what.
It's clearly focused on the "able-to-use" test. Are there any external
dependencies related to that test? Maybe some of my modules are out of date & need to be
updated? I did have a bunch of modules that wanted upgrades, so I upgraded a handful of them
but no difference.
That's a test that basically tests if the compilation worked.
On the sa_compile.t, there is a line that says:
system_or_die "$instdir/foo/$temp_binpath/sa-compile --keep-tmps"; # --debug
Can you turn on --debug and run prove -v t/sa_compile again. Then
hopefully sa-compile throws a hint...
