On integrating Travis CI with the master branch in this commit 68d51a5d7458025a5cc317d81d3cb59a9d801ecc , the unit tests are failing. In this PR I try to resolve the issue and get the unit tests running successfully on Travis CI. You may view the build log through this link
The second change that happened with this PR is addition of some .msh files required to run unit tests as exceptions in .gitignore. The unit tests were failing earlier on Travis CI because the mesh files were not present in the git repo and some unit tests required those mesh files to run the tests.
Warning:
In Travis CI, only CPU backend of arrayfire is installed. So, to run pytest successfully, the arrayfire backends must be set to 'cpu' in all the files. We can later figure out how to change the backend in Travis CI. But it can't be done right now because backends are hardcoded in the dg_maxwell library.
Do not write unit tests which require visual verification of matplotlib figures. Visual verification of unit tests can't be done on Travis CI.
On integrating
Travis CIwith the master branch in this commit 68d51a5d7458025a5cc317d81d3cb59a9d801ecc , the unit tests are failing. In this PR I try to resolve the issue and get the unit tests running successfully onTravis CI. You may view the build log through this linkThe second change that happened with this PR is addition of some
.mshfiles required to run unit tests as exceptions in.gitignore. The unit tests were failing earlier on Travis CI because the mesh files were not present in the git repo and some unit tests required those mesh files to run the tests.Warning:
pytestsuccessfully, thearrayfirebackends must be set to 'cpu' in all the files. We can later figure out how to change the backend in Travis CI. But it can't be done right now because backends are hardcoded in thedg_maxwelllibrary.