Feel free to rename, recategorize or alter any of these tests. Sorry for
all the typos in my 1st email!
On Mon, Apr 30, 2018 at 5:05 PM, Kirk Lund wrote:
> I just merged in PR #1886 (https://github.com/apache/geode/pull/1886)
> which renames the remaining regression tests that were using TRAC #s
I just merged in PR #1886 (https://github.com/apache/geode/pull/1886) which
renames the remaining regression tests that were using TRAC #s in the name
of the test class.
I'm going to make a 2nd pass to look for TRAC #s in test method names and
rename those as well before resolving GEODE-1279.
If
---
Spring Data GemFire > Nightly-ApacheGeode > #903 was successful.
---
Scheduled
2380 tests in total.
https://build.spring.io/browse/SGF-NAG-903/
--
This
Please review the ASF policy on signing releases [1]. I think these points are
pertinent:
- The release manager signs the release. That provides the verification that
the release binaries were in fact created by the release manager and have not
been modified. Multiple signatures are not requ
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/309
Pipeline results can be found at:
Concourse:
https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/477
Build Update for apache/geode
-
Build: #7746
Status: Broken
Duration: 22 mins and 3 secs
Commit: 4b9dc96 (develop)
Author: Galen O'Sullivan
Message: GEODE-5065 Increase timeout for a flaky distributed test. And cleanup.
(#1821)
GEODE-5065 Increase timeout for
-1
I don't see Mike's key in the KEYS file on either rel/v1.6.0.RC1
(5ce726bd7b4f8d2648fd011a807a1bcc624ddfa5) or on develop.
It seems odd to me to add a new key and use it to sign the release
without using an already-existing key to sign the release as well. If
someone's trying to verify a
Deleted my local copy of ‘rel/v1.6.0.RC1’ and refetched. The tag now correctly
points to this commit: 5ce726bd7
With that change, I’ll vote +1.
Aside on voting: for releases a -1 doesn’t automatically veto the release
candidate [1]. It is, however, a strong signal that the community may no
