uflacs tests (gtest) can't br run from top-level ffc directory

[Prof Garth Wells]

The uflacs tests that use gtest fail if run from the top-level ffc directory.

It would be handy if this would work - it would make the pipelines testing neater because there was have some path issues when running pytest via python -m pytest foo.

[Martin Sandve Alnæs]

py.test test/uflacs

works here?

[Martin Sandve Alnæs]

Ok, it fails with python -m pytest test/uflacs.

[Prof Garth Wells]

Could be a different issue from the title of the report. py.test and pythin -m pytest are not the same (despite what is written in the pytest docs). They handle paths differently.

[Martin Sandve Alnæs]

I'm trying to make the paths consistently absolute, there were a couple of exceptions.

[Prof Garth Wells]

This I've seen is related to PYTHONPATH, at least with pipelines where tests are run as root.

[Martin Sandve Alnæs]

This is weird: ffc.backends.ufc.get_include_path() returns /home/martinal/dev/fenics-dev/ffc/test/uflacs/crosslanguage/ffc/backends/ufc when run from test/uflacs/conftest.py

[Martin Sandve Alnæs]

ffc.__main__ does funny things with sys.path, but removing that didn't help...

[Martin Sandve Alnæs]

In get_include_dir:

In [1]: __file__
Out[1]: 'ffc/backends/ufc/__init__.py'

In [2]: os.path.abspath(__file__)
Out[2]: '/home/martinal/dev/fenics-dev/ffc/test/uflacs/crosslanguage/ffc/backends/ufc/__init__.py'

[Martin Sandve Alnæs]

Why is file not absolute?

[Martin Sandve Alnæs]

Fix on the way.