Skip to content

Commit

Permalink
Blacklist travis-ci qt5 tests and remove i.fft test
Browse files Browse the repository at this point in the history
  • Loading branch information
Médéric RIBREUX committed May 29, 2016
1 parent 8d1bec3 commit 59faf95
Show file tree
Hide file tree
Showing 3 changed files with 17 additions and 32 deletions.
1 change: 1 addition & 0 deletions ci/travis/linux/qt5/blacklist.txt
Expand Up @@ -13,3 +13,4 @@ PyQgsVirtualLayerDefinition
PyQgsVirtualLayerProvider
qgis_composermapgridtest
qgis_composerutils
ProcessingGrass7AlgorithmsTest
17 changes: 0 additions & 17 deletions python/plugins/processing/tests/README.md
Expand Up @@ -54,23 +54,6 @@ The above translates to
name: expected/polys_densify.gml
```

For GRASS 7 raster outputs
--------------------------

If you want to create a test for a GRASS 7 module which exports a raster output, you will need extra steps. There isa great chance that your GRASS 7 installation will be different from the Travis-Ci environment (for the moment, it is provided by [osgeo4travis archive]( and it is based on GRASS 7.0.2). It means that your raster hashes will be different from the ones produced in Travis-Ci (GRASS adds a metadata which contains the GRASS version in the GTiff).

Here are a few instructions (for Debian based GNU/Linux distributions) to assure you use the same version of GRASS than in Travis-Ci:

* Install osgeo4travis binaries into your home directory:
`curl -L https://github.com/opengisch/osgeo4travis/archive/qt4bin.tar.gz | tar -xzC ${HOME} --strip-components=1`
* Modify the grass70 script which incorporates a hardlink to /home/travis:
`sed -i 's#/home/travis#'${HOME}'#g' ${HOME}/osgeo4travis/bin/grass70`
* Launch QGIS with the following command:
`PATH=${HOME}/osgeo4travis/bin:$PATH LD_LIBRARY_PATH=${HOME}/osgeo4travis/lib:$LD_LIBRARY_PATH qgis`

From now, you will be using osgeo4travis GRASS 7 installation in QGIS Processing and you can proceed with the above method to easily produce unit tests.


Params and results
------------------

Expand Down
Expand Up @@ -313,21 +313,22 @@ tests:
- '4541.9055'
- '4369.2930'
- '128.6900'

- algorithm: grass7:i.fft
name: GRASS7 i.fft
params:
GRASS_REGION_PARAMETER: '344500.0,358400.0,6682800.0,6693700.0'
input:
name: custom/grass7/float_raster.tif
type: raster
results:
imaginary:
hash: 94249384dd8b6019f0024501bc9a093cba9dd025c183d3fb46d77027
type: rasterhash
real:
hash: 09ab93c65aa2dde4da422b62a5ed3e38208e2da072cec2b0eb837a47
type: rasterhash

# this doesn't work in travis-ci environment (probably due to libfftw version).
# - algorithm: grass7:i.fft
# name: GRASS7 i.fft
# params:
# GRASS_REGION_PARAMETER: '344500.0,358400.0,6682800.0,6693700.0'
# input:
# name: custom/grass7/float_raster.tif
# type: raster
# results:
# imaginary:
# hash: 94249384dd8b6019f0024501bc9a093cba9dd025c183d3fb46d77027
# type: rasterhash
# real:
# hash: 09ab93c65aa2dde4da422b62a5ed3e38208e2da072cec2b0eb837a47
# type: rasterhash

This comment has been minimized.

Copy link
@m-kuhn

m-kuhn May 29, 2016

Member

Do you think it's worth adding a different comparison check besides rasterhash? Maybe a raster file with some tolerance?
It shouldn't be the first choice but maybe it would help in some cases...


- algorithm: grass7:i.segment
name: GRASS7 i.segment
Expand Down

0 comments on commit 59faf95

Please sign in to comment.