[liblouis-liblouisxml] Re: Running test harness
- From: Ken Perry <kperry@xxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Wed, 10 Sep 2014 13:38:57 +0000
Can do that but it will be fun getting the time zone right. I have a meeting
in 24 minutes. My skype is ken.perry.aph if you add me we can see if we can
get together and see what is going on. I really need to get this fixed if I am
going to finish those 735 problems in the current tests. I think I have a
bunch fixed but I cannot test grr.
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Mesar Hameed
Sent: Wednesday, September 10, 2014 9:22 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Running test harness
Hi,
In addition, if runHarness is run directly, we have code that adds the correct
table path.
if 'HARNESS_DIR' in os.environ:
# we assume that if HARNESS_DIR is set that we are invoked from
# the Makefile, i.e. all the paths to the Python test files and
# the test tables are set correctly.
harness_dir = os.environ['HARNESS_DIR']
else:
# we are not invoked via the Makefile, i.e. we have to set up the
# paths (LOUIS_TABLEPATH) manually.
harness_dir = "."
# make sure local test braille tables are found
os.environ['LOUIS_TABLEPATH'] = '../tables,../../tables'
So things still looks normal from the information that has been given.
Ken, if you are able to give me ssh access into your ubuntu machine, I could
spend a few minutes looking around/try to see whats going wrong.
We could run a skype/screen session so that we can communicate and follow what
is being done.
Mesar
On Wed 10/09/14,14:44, Christian Egli wrote:
> On 09/10/2014 09:54 AM, Michael Whapples (Redacted sender
> mwhapples@xxxxxxx for DMARC) wrote:
> >Ideally if possible we should try and make the test harness use
> >liblouis from the source/build directories rather than the public
> >install. May be it should set LOUIS_TABLEPATH environment variable or
> >call the lou_setDataPath function. As for loading the correct
> >libraries, may be it should load using an absolute path to the shared
> >library in the build directory. I think those two things would
> >sufficiently isolate the test harness from the external environment.
>
> This should work if you invoke the test harness from the Makefile,
> i.e. if you run `make runall` inside the harness directory. The
> Makefile sets up the environment so that the test harness should find
> all its "stuff" (tables, library, Python bindings) in the build directory.
>
> In reality however not all seems to be that rosy. `make runall` is not
> automatically invoked when calling `make check` (as it should be). I
> just tried to run it and it took my machine to a halt. Maybe I should
> have built the Python bindings first? They are not built by default.
>
> So all I'm saying that yes I agree that the tests have to be isolated
> from the installed environment and yes when invoked from the Makefile
> it is set up so that they should be isolated.
>
> Thanks
> Christian
>
> --
> Christian Egli
> Swiss Library for the Blind, Visually Impaired and Print Disabled
> Grubenstrasse 12, CH-8045 Zürich, Switzerland
>
> For a description of the software, to download it and links to project
> pages go to http://www.abilitiessoft.com
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
