Opened 9 years ago

Closed 9 years ago

#6136 closed defect (fixed)

PostGIS numerous bot failures

Reported by: robe Owned by: warmerdam
Priority: normal Milestone: 2.1.0
Component: default Version: svn-trunk
Severity: normal Keywords:
Cc:

Description

Just noticed our PostGIS bot debbie, has been failing on regressing GDAL Trunk (2.1).

I'm not sure if this is something I need to change in configuration. She's been failing since 9/26 -- commit r30715 (autotest r30716)

error part looks like this:

 ------------ Failures ------------
Script: ogr/ogr_geojson.py
  TEST: ogr_geojson_15 ... fail
Script: gcore/basic_test.py
  TEST: basic_test_11 ... fail
    line 350: fail
Script: gcore/gdal_api_proxy.py
  TEST: gdal_api_proxy_1 ... fail
  TEST: gdal_api_proxy_2 ... fail
  TEST: gdal_api_proxy_3 ... fail
  TEST: gdal_api_proxy_4 ... fail
Script: gcore/tiff_write.py
  TEST: tiff_write_70 ... fail (blowup)
Script: gcore/vrtmisc.py
  TEST: vrtmisc_12 ... fail (blowup)
Script: gcore/pam.py
  TEST: pam_3 ... fail (blowup)
  TEST: pam_13 ... fail (blowup)
Script: gdrivers/mem.py
  TEST: mem_1 ... fail (blowup)
Script: gdrivers/vrtpansharpen.py
  TEST: vrtpansharpen_11 ... fail (blowup)
Script: alg/polygonize.py
  TEST: polygonize_1_float ... fail (blowup)
Script: alg/reproject.py
  TEST: reproject_4 ... fail (blowup)
 ----------------------------------

Succeeded: 2869
Failed:    14 (8 blew exceptions)
Skipped:   1558
Expected fail:8
Duration:  05m30.6s

Latest run - http://debbie.postgis.net:8080/job/GDAL_Regress/3176/consoleFull

Let me know if any action I should take.

Thanks, Regina

Change History (4)

comment:1 by robe, 9 years ago

Oops slight amendment (I think I had a period where jenkins stopped), so not sure which commit is the culprit. Looks like the commit range is for r30689 - r30715

http://debbie.postgis.net:8080/job/GDAL_Trunk/3314/changes#detail21

comment:2 by robe, 9 years ago

At a cursory glance looks like a good chunk of failures are in the pymod calls.

Could it be because its using 2.0.1 egg, not sure where that came from or how to update it.

comment:3 by Even Rouault, 9 years ago

Regina, I'd rather think this is due to https://trac.osgeo.org/gdal/changeset/30564 that changed the path where the python bindings are installed. It seems your bot is running now against older python bindings. Some manual cleanup might be needed.

comment:4 by robe, 9 years ago

Resolution: fixed
Status: newclosed

Even thanks for the feedback. I think this is fixed. I'm not sure exactly what fixed it. I actually had 5 GDAL eggs including the GDAL 2.1.0 one so not sure why it picked that one.

I deleted the 2.0.1 and also reordered my PythonPath and then tests started passing again.

Note: See TracTickets for help on using tickets.