Re: [DISCUSSION] Stop using the Geode Repository for Feature/WIP Branches

-1 for “banning” The Geode community has strong precedent for protecting developers’ freedom to choose what works best for them. Maybe check if your graphical git tool-of-choice allows a branch filter regex, or consider git clone --single-branch? -Owen On June 11, 2020 at 5:23:20 PM PDT,

Re: [DISCUSSION] Stop using the Geode Repository for Feature/WIP Branches

+1 for ban the use of geode repo for feature branches. Less clutter is better. From: Jacob Barrett Sent: Tuesday, June 2, 2020 3:42 PM To: dev@geode.apache.org Subject: [DISCUSSION] Stop using the Geode Repository for Feature/WIP Branches I know this has been

Re: [DISCUSSION] Stop using the Geode Repository for Feature/WIP Branches

> Suppose I want to commit to another contributor's fork. How can they grant > me permission to do so? (This is a common predicament for me when I'm > reviewing doc PRs.) Just as a note: if there is a PR and it is from a fork, the person who opens the PR can check a box that says "Allow

Re: [PROPOSAL] increase AcceptanceTest timeout

Ok, let's just keep an eye on it for now. Thanks! On Thu, Jun 11, 2020 at 12:53 PM Owen Nichols wrote: > This timeout is separate from the test timeout. > > AcceptanceTest currently has a 90-minute timeout for running tests. > These tests usually take 60-65 minutes. > > The timeout you

Re: [PROPOSAL] backport GEODE-8238 to support/1.13

OK, Bruce -- merge away. Thanks, Dave On Thu, Jun 11, 2020 at 12:47 PM Dick Cavender wrote: > +1 > > -Original Message- > From: Eric Shu > Sent: Thursday, June 11, 2020 11:33 AM > To: dev@geode.apache.org > Subject: Re: [PROPOSAL] backport GEODE-8238 to support/1.13 > > +1 >

Re: [PROPOSAL] increase AcceptanceTest timeout

This timeout is separate from the test timeout. AcceptanceTest currently has a 90-minute timeout for running tests. These tests usually take 60-65 minutes. The timeout you mentioned is just for uploading the report. It is currently set at 1 hour, although normally only takes about 30 seconds.

RE: [PROPOSAL] backport GEODE-8238 to support/1.13

+1 -Original Message- From: Eric Shu Sent: Thursday, June 11, 2020 11:33 AM To: dev@geode.apache.org Subject: Re: [PROPOSAL] backport GEODE-8238 to support/1.13 +1 From: Owen Nichols Sent: Thursday, June 11, 2020 10:58 AM To: dev@geode.apache.org

Re: [PROPOSAL] backport GEODE-8238 to support/1.13

+1 From: Owen Nichols Sent: Thursday, June 11, 2020 10:58 AM To: dev@geode.apache.org Subject: Re: [PROPOSAL] backport GEODE-8238 to support/1.13 +1 --- Sent from Workspace ONE

[PROPOSAL] increase AcceptanceTest timeout

I think we need to bump up the max time for AcceptanceTest jobs. Here's an example of an AcceptanceTest job hanging due to timeout in archival (after the execution of tests already finished):

Re: [INFO] Distributed Test runs in bulk results.

Thanks Mark! Can you highlight any surprises in these results compared to previous runs? Anthony > On Jun 10, 2020, at 10:59 PM, Mark Hanson wrote: > > Hello All, > > I have been doing bulk test runs of DistributedTestOpenJDK8, in this case > over 200. Here is a simplified report to kind

Re: [PROPOSAL] backport GEODE-8238 to support/1.13

+1 --- Sent from Workspace ONE Boxer On June 11, 2020 at 10:52:19 AM PDT, Bruce Schuchardt wrote: This ticket concerns loss of a message and a subsequent hang during shutdown. The problem is also in support/1.13 and I’d like to backport to that branch.

[PROPOSAL] backport GEODE-8238 to support/1.13

This ticket concerns loss of a message and a subsequent hang during shutdown. The problem is also in support/1.13 and I’d like to backport to that branch. https://issues.apache.org/jira/browse/GEODE-8238 It’s a small change to fix a problem introduced in changes for GEODE-7727.

New launcher acceptance tests

The new launcher acceptance tests that I merged to develop yesterday are failing on Windows because they specify "java" instead of "java.exe". I'm updating and will submit a PR very soon.

Re: Problem in rolling upgrade since 1.12

Thanks for the info, Bill. I have found another issue in rolling upgrade since 1.12. I have observed that when there are custom jars previously deployed, the locator is not able be started in the new version and the following exception is thrown: Exception in thread "main"

RE: [INFO] Distributed Test runs in bulk results.

I think a report like this is very useful to have real data about which flaky tests fail more often. It would be great if a report like this were automatically generated and updated after each CI execution. In a project I was working before a similar report was implemented and it was very

[INFO] Distributed Test runs in bulk results.

Hello All, I have been doing bulk test runs of DistributedTestOpenJDK8, in this case over 200. Here is a simplified report to kind of help you see what I am seeing and I think everybody sees with random failures as part of the PR process. It is very easy to cause failures like this by not