postgis dump restore test is broken

[robe]

So I was trying to troubleshoot why travis is failing on dump restore test, and I get a failure as well (at least when testing against postgresql 10 beta2.

pg_dump: too many command-line arguments (first is "-f")
Try "pg_dump --help" for more information.

At first glance it looks like args are out of order. database name should be the last thing in output. I'll try to fix.

[robe]

In 15528:

Fix dump/restore test (arguments out of order)
Closes #3801 for PostGIS 2.4.0
Turn off interrupt tests on dronie, too many false failures

[robe]

Well that fixed my dump restore check but travis is still failing he gets a different error so his issue might be differnt. I'm going to turn off dump/restore testing on travis to rule out that.

[robe]

okay travis's problems seem to be permission related. On closer inspection.

psql:/home/travis/build/postgis/postgis/regress/00-regress-install/share/contrib/postgis/postgis.sql:97: ERROR:  could not access file "/home/travis/build/postgis/postgis/regress/00-regress-install/lib/postgis-2.4": Permission denied

-----------------------------------------------------------------------------

make[1]: *** [check] Error 1

make[1]: Leaving directory `/home/travis/build/postgis/postgis/regress'

make: *** [check] Error 1

I'm not sure why this changed. Before it started failing last commit was just a change to NEWS file. So must be a change in travis itself with permissions.

[robe]

In 15530:

try to fix travis check failures by sudoing more stuff.
References #3801 for PostGIS 2.4.0

[robe]

Okay figured out the problem with travis is that it got autoupgraded from precise to trusty and for some reason our script causes permission denied on trusty. So I forced a downgrade to precise at r15531 and so far it's working.

I'll open a separate ticket for travis.