diff options
| author | Thomas Knudsen <busstoptaktik@users.noreply.github.com> | 2018-02-12 22:45:20 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-02-12 22:45:20 +0100 |
| commit | ab2d175bf1674e3472576250281e7fdb68f09198 (patch) | |
| tree | ba037e2dac5033c49ec44486562fb7f35ca8fe4e /appveyor.yml | |
| parent | 715ec0b90aec05f15554c6591ea8cfd09d5cf043 (diff) | |
| download | PROJ-ab2d175bf1674e3472576250281e7fdb68f09198.tar.gz PROJ-ab2d175bf1674e3472576250281e7fdb68f09198.zip | |
Rename gie_failing to work around MS wildcard bug (#799)
For reasons unknown to anyone but the geniuses from Redmond: In
MSWindows, the wildcard pattern "*.gie" expands to all files having
an extension *starting* with ".gie".
In other words "dir *.gie" will list files with extension ".gie"
*and* with extension ".gie_failing".
This means that running "gie test\gigs\*.gie" will run all gigs
tests, even the ones known to fail.
So rather than getting a quick check for regressions, one gets
a lot of noise and no easy way to be sure whether any regressions
have appeared.
To work around this oddity, we rename all files ending in
".gie_failing" to end in ".gie.failing" - and while at it,
adding all the non-failing gigs tests to the AppVeyor test suite.
This extends the regression test suite, run at the end of each
AppVeyor integration, to over 2500 individual tests.
Test coverage, however, is still hovering just below 75%, so
there's still plenty of room and reason for additional tests.
Diffstat (limited to 'appveyor.yml')
| -rw-r--r-- | appveyor.yml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/appveyor.yml b/appveyor.yml index 52993558..11f16b5d 100644 --- a/appveyor.yml +++ b/appveyor.yml @@ -62,7 +62,7 @@ test_script: - dir ..\test\gie - echo "Contents of PROJ_LIB " %PROJ_LIB% - dir %PROJ_LIB% - - gie.exe ..\test\gie\*.gie + - gie.exe ..\test\gie\*.gie ..\test\gigs\*.gie deploy: off |