sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-11-22 00:14:55 -05:00
Code Issues Packages Projects Releases Wiki Activity

Blacklist travis-ci qt5 tests and remove i.fft test

Browse Source
This commit is contained in:
Médéric RIBREUX 2016-05-28 19:10:42 +02:00
parent 8d1bec33a0
commit 59faf95c1d
3 changed files with 17 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
ci/travis/linux/qt5/blacklist.txt
View File

@ -13,3 +13,4 @@ PyQgsVirtualLayerDefinition
PyQgsVirtualLayerProvider PyQgsVirtualLayerProvider
qgis_composermapgridtest qgis_composermapgridtest
qgis_composerutils qgis_composerutils
ProcessingGrass7AlgorithmsTest

17
python/plugins/processing/tests/README.md
View File

@ -54,23 +54,6 @@ The above translates to
name: expected/polys_densify.gml 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 Params and results
------------------ ------------------

29
python/plugins/processing/tests/testdata/grass7_algorithm_tests.yaml vendored
View File

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