In Jenkins LD_LIBRARY_PATH is exported so the test runs fine. On my box,
I always have to export the variable to make the suite pass.
I could of course export permanently the variable in my environment. But
what about contributors who would like to make as7 module itests pass?
It took me sometime when I first saw this to understand why the suite
was failing.
Besides, I think it's not really a requirement to have this variable
detected. That's why I'd prefer to get rid of these lines.
Thomas
Le 25/04/2013 17:43, Jay Shaughnessy a écrit :
You may not be missing anything. But has this presented a problem?
On 4/24/2013 4:38 PM, Thomas Segismont wrote:
> Hi,
>
> As part of as7 plugin integration tests, we check on platform other
> than Windows that the detected start script environment will always
> have an LD_LIBRARY_PATH entry.
>
> See
http://pastebin.com/s0vkm28s
>
> The thing is that this will only be true if the shell from which AS7
> was started had an LD_LIBRARY_PATH variable.
>
> So I think we should get rid of this part. Am I missing something?
>
> Thanks,
> Thomas
> _______________________________________________
> rhq-devel mailing list
> rhq-devel(a)lists.fedorahosted.org
>
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel