Status update:

We have now fully migrated to the new build server, and
build.geoserver.org points
to the new server.

Note that many builds are failing after the migration; see below for
details. Also note that the build email notifications are currently
disabled to avoid spam while we are resolving the build failures.
For any of the failures listed below that relate to test failures, if you
are familiar with the tests in question, your input would be appreciated.

*General/global issues:*

If you notice an error along the lines of "Failled to download artifact
(Operation Timed Out)" - we've been seeing a lot of this; It seems to be
related to large numbers of maven downloads caused by an initially empty
maven repository, and usually goes away by the second or third run of the
job. This seems to be the main failure affecting most of the jobs and
should hopefully go away after a few days. Until then, the build queue will
be pretty full, since every job needs to go through a few (slow) runs to
fill the local maven repo.

The issue with format characters in log outputs (e.g. [1;34m ...[m) seems
to be back. I have configured MAVEN_OPTS=-Dstyle.color=never, but that has
had no effect. Anyone got any other ideas?

*Project-specific issues:*

*GeoTools* - Master is *failing* on gt-ogr-bridj tests (apparently due to
change in C bindings?) Temporarily removing from build and rerunning.
  PostGIS and MySQL online tests are *passing* (I was a bit surprised by
MySQL passing, as I neither installed nor configured it, so that may be a
false positive. I did install and configure PostGIS, so that is a
legitimate success).
  Docs are* passing*

*GeoWebCache* - Most recent builds have all *passed*. I saw a gwc-wmts
failure earlier on that appears to have been a false alarm.

*GeoServer* - Master is currently unstable, but with a different failure
each time. Most recent was a timout uploading artifacts. Prior to that was
test failures in geofence-server.
  Docs: Build succeeds, upload fails. Investigating...

*GeoFence* - Master has an auth failure downloading geodb. I'm not sure if
this was even passing after the repo migration a couple weeks ago, so if
one of the project owners can take a look at this, that would be
appreciated.

Cheers,
Torben

On Sun, May 3, 2020 at 4:45 PM Torben Barsballe <torbenbarsba...@gmail.com>
wrote:

> Hello All,
>
> Please be aware that we are migrating build.geoserver.org to a new server
> this weekend (extending into Monday). As such, it may unavailable and/or
> semi-functional on Sunday and/or Monday. Thanks for your patience during
> the migration process.
>
> Cheers,
> Torben Barsballe
>
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to