Martin, can you please take a look at why gitlab CI fails ?
I'm not sure it has to do with any of your recent commits.
It would be great if gitlab-ci could be configured to notify the
mailing list instead of just me ...

----- Forwarded message from GitLab <git...@mg.gitlab.com> -----

Date: Wed, 20 Feb 2019 21:01:54 +0000
From: GitLab <git...@mg.gitlab.com>
Subject: libgeos | Pipeline #48453688 has failed for master | edc36747
Reply-To: GitLab <nore...@gitlab.com>
List-Id: geos/libgeos <381840.libgeos.geos.gitlab.com>

Your pipeline has failed.

Project: libgeos ( https://gitlab.com/geos/libgeos )
Branch: master ( https://gitlab.com/geos/libgeos/commits/master )

Commit: edc36747 ( 
https://gitlab.com/geos/libgeos/commit/edc36747409058cb10aeb8d9505d280dfbfcf697 
)
Commit Message: Port JTS InteriorPointArea improvements

Commit Author: Martin Davis

Pipeline #48453688 ( https://gitlab.com/geos/libgeos/pipelines/48453688 ) 
triggered by Sandro Santilli ( https://gitlab.com/strk )
had 1 failed build.

Job #164870085 ( https://gitlab.com/geos/libgeos/-/jobs/164870085 )

Stage: test
Name: test
Trace: Makefile:595: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/builds/geos/libgeos/src'
Makefile:477: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/builds/geos/libgeos'
Makefile:424: recipe for target 'all' failed
make: *** [all] Error 2
section_end:1550696510:build_script
section_start:1550696510:after_script
section_end:1550696512:after_script
section_start:1550696512:upload_artifacts_on_failure
section_end:1550696513:upload_artifacts_on_failure
ERROR: Job failed: exit code 1



-- 
You're receiving this email because of your account on gitlab.com.


----- End forwarded message -----
_______________________________________________
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Reply via email to