Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

[Kirk Lund]

Ok, I wanted to give this discussion another night and we still have
consensus for making both stress-new-test non-required.

I just filed PR #6602  to change
stress-new-test from required to non-required. Please review!

On Wed, Jun 9, 2021 at 2:11 PM Anthony Baker  wrote:

> If we have consensus, no need to VOTE.
>
> > On Jun 9, 2021, at 12:52 PM, Owen Nichols  wrote:
> >
> > Ok, I'm on board with changing stress-new-test from a required PR check
> to non-required.  It's simple, codeowners still have the final say, and it
> neatly avoids the whole topic of overrides.  Time to take a [VOTE]?
> >
>
>

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

[Nabarun Nag]

Hi all,


  *   We need to discuss how to prevent more flaky tests to be introduced now 
that stress-test is not mandatory for PRs to be merged? Reviewers checking the 
PR must check the tests failing in stress test and if it is a test that has 
been introduced or changed in the PR, the PR must be blocked with a change 
request or rejected.
  *   Also, in my opinion, we need to re-introduce the stress test as a 
mandatory check for PRs to be merged once the flaky test percentage has been 
reduced.

Owen, will it be possible to put out a list of all the flaky tests and we can 
try to get these resolved collectively as a community. (results of the mass 
tests maybe). Thank you.


Regards
Nabarun Nag

From: Kirk Lund 
Sent: Thursday, June 10, 2021 9:37 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

Ok, I wanted to give this discussion another night and we still have
consensus for making both stress-new-test non-required.

I just filed PR #6602 

 to change
stress-new-test from required to non-required. Please review!

On Wed, Jun 9, 2021 at 2:11 PM Anthony Baker  wrote:

> If we have consensus, no need to VOTE.
>
> > On Jun 9, 2021, at 12:52 PM, Owen Nichols  wrote:
> >
> > Ok, I'm on board with changing stress-new-test from a required PR check
> to non-required.  It's simple, codeowners still have the final say, and it
> neatly avoids the whole topic of overrides.  Time to take a [VOTE]?
> >
>
>

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

[Owen Nichols]

@Naba, two places to find recent flaky failures are:
* Latest mass-test report[1]
* Recently-sighted "CI Failure" Jira tickets[2]

[1] 
https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-mass-test-run/jobs/create-mass-test-run-report/builds/19
[2] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20GEODE%20AND%20summary%20~%20%22CI%20Failure%22%20ORDER%20BY%20updated%20DESC

On 6/10/21, 9:50 AM, "Nabarun Nag"  wrote:

Hi all,


  *   We need to discuss how to prevent more flaky tests to be introduced 
now that stress-test is not mandatory for PRs to be merged? Reviewers checking 
the PR must check the tests failing in stress test and if it is a test that has 
been introduced or changed in the PR, the PR must be blocked with a change 
request or rejected.
  *   Also, in my opinion, we need to re-introduce the stress test as a 
mandatory check for PRs to be merged once the flaky test percentage has been 
reduced.

Owen, will it be possible to put out a list of all the flaky tests and we 
can try to get these resolved collectively as a community. (results of the mass 
tests maybe). Thank you.


Regards
Nabarun Nag

From: Kirk Lund 
Sent: Thursday, June 10, 2021 9:37 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

Ok, I wanted to give this discussion another night and we still have
consensus for making both stress-new-test non-required.

I just filed PR #6602 

 to change
stress-new-test from required to non-required. Please review!

On Wed, Jun 9, 2021 at 2:11 PM Anthony Baker  wrote:

> If we have consensus, no need to VOTE.
>
> > On Jun 9, 2021, at 12:52 PM, Owen Nichols  wrote:
> >
> > Ok, I'm on board with changing stress-new-test from a required PR check
> to non-required.  It's simple, codeowners still have the final say, and it
> neatly avoids the whole topic of overrides.  Time to take a [VOTE]?
> >
>
>

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

[Mark Hanson]

+1 to new report from Owen
+1 to re-introduce the stress-test

Great ideas Naba!

On 6/10/21, 9:50 AM, "Nabarun Nag"  wrote:

Hi all,


  *   We need to discuss how to prevent more flaky tests to be introduced 
now that stress-test is not mandatory for PRs to be merged? Reviewers checking 
the PR must check the tests failing in stress test and if it is a test that has 
been introduced or changed in the PR, the PR must be blocked with a change 
request or rejected.
  *   Also, in my opinion, we need to re-introduce the stress test as a 
mandatory check for PRs to be merged once the flaky test percentage has been 
reduced.

Owen, will it be possible to put out a list of all the flaky tests and we 
can try to get these resolved collectively as a community. (results of the mass 
tests maybe). Thank you.


Regards
Nabarun Nag

From: Kirk Lund 
Sent: Thursday, June 10, 2021 9:37 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

Ok, I wanted to give this discussion another night and we still have
consensus for making both stress-new-test non-required.

I just filed PR #6602 

 to change
stress-new-test from required to non-required. Please review!

On Wed, Jun 9, 2021 at 2:11 PM Anthony Baker  wrote:

> If we have consensus, no need to VOTE.
>
> > On Jun 9, 2021, at 12:52 PM, Owen Nichols  wrote:
> >
> > Ok, I'm on board with changing stress-new-test from a required PR check
> to non-required.  It's simple, codeowners still have the final say, and it
> neatly avoids the whole topic of overrides.  Time to take a [VOTE]?
> >
>
>

Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

[Dan Smith]

I'm also -0 on this one. I personally kinda like having the merge button 
disabled on my PRs until all the checks are passing so I don't have to think as 
much, and I'm not sure this problem is going to come up again soon. But I'm 
willing go with disabling it.

-Dan

From: Mark Hanson 
Sent: Thursday, June 10, 2021 10:15 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

+1 to new report from Owen
+1 to re-introduce the stress-test

Great ideas Naba!

On 6/10/21, 9:50 AM, "Nabarun Nag"  wrote:

Hi all,


  *   We need to discuss how to prevent more flaky tests to be introduced 
now that stress-test is not mandatory for PRs to be merged? Reviewers checking 
the PR must check the tests failing in stress test and if it is a test that has 
been introduced or changed in the PR, the PR must be blocked with a change 
request or rejected.
  *   Also, in my opinion, we need to re-introduce the stress test as a 
mandatory check for PRs to be merged once the flaky test percentage has been 
reduced.

Owen, will it be possible to put out a list of all the flaky tests and we 
can try to get these resolved collectively as a community. (results of the mass 
tests maybe). Thank you.


Regards
Nabarun Nag

From: Kirk Lund 
Sent: Thursday, June 10, 2021 9:37 AM
To: dev@geode.apache.org 
Subject: Re: [DISCUSS] Remove stress-new-test-openjdk11 requirement from PRs

Ok, I wanted to give this discussion another night and we still have
consensus for making both stress-new-test non-required.

I just filed PR #6602 

 to change
stress-new-test from required to non-required. Please review!

On Wed, Jun 9, 2021 at 2:11 PM Anthony Baker  wrote:

> If we have consensus, no need to VOTE.
>
> > On Jun 9, 2021, at 12:52 PM, Owen Nichols  wrote:
> >
> > Ok, I'm on board with changing stress-new-test from a required PR check
> to non-required.  It's simple, codeowners still have the final say, and it
> neatly avoids the whole topic of overrides.  Time to take a [VOTE]?
> >
>
>

Canceled: apache/geode-examples#543 (support/1.12 - a18cf3f)

[Travis CI]

Build Update for apache/geode-examples
-

Build: #543
Status: Canceled

Duration: ?
Commit: a18cf3f (support/1.12)
Author: Owen Nichols
Message: temporarily point to staging repo for CI purposes

View the changeset: 
https://github.com/apache/geode-examples/compare/22847e45387d...a18cf3f4f04a

View the full build log and details: 
https://travis-ci.com/github/apache/geode-examples/builds/228672791?utm_medium=notification&utm_source=email

  Restart your build: 
https://travis-ci.com/github/apache/geode-examples/builds/228672791?utm_medium=notification&utm_source=email

--

You can unsubscribe from build emails from the apache/geode-examples repository 
going to 
https://travis-ci.com/account/preferences/unsubscribe?repository=16807635&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.

Errored: apache/geode-examples#545 (rel/v1.12.3.RC1 - 85ffd22)

[Travis CI]

Build Update for apache/geode-examples
-

Build: #545
Status: Errored

Duration: 1 min and 3 secs
Commit: 85ffd22 (rel/v1.12.3.RC1)
Author: Owen Nichols
Message: Bumping version to 1.12.3

View the changeset: 
https://github.com/apache/geode-examples/compare/rel/v1.12.3.RC1

View the full build log and details: 
https://travis-ci.com/github/apache/geode-examples/builds/228672798?utm_medium=notification&utm_source=email


--

You can unsubscribe from build emails from the apache/geode-examples repository 
going to 
https://travis-ci.com/account/preferences/unsubscribe?repository=16807635&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.

Failed: apache/geode-native#3079 (rel/v1.12.3.RC1 - 717bbf7)

[Travis CI]

Build Update for apache/geode-native
-

Build: #3079
Status: Failed

Duration: 2 mins and 30 secs
Commit: 717bbf7 (rel/v1.12.3.RC1)
Author: Owen Nichols
Message: update Dockerfile and other variables to apache-geode 1.12.2

View the changeset: 
https://github.com/apache/geode-native/compare/rel/v1.12.3.RC1

View the full build log and details: 
https://travis-ci.com/github/apache/geode-native/builds/228672802?utm_medium=notification&utm_source=email


--

You can unsubscribe from build emails from the apache/geode-native repository 
going to 
https://travis-ci.com/account/preferences/unsubscribe?repository=16807653&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.

Canceled: apache/geode-examples#546 (support/1.12 - 3176db2)

[Travis CI]

Build Update for apache/geode-examples
-

Build: #546
Status: Canceled

Duration: ?
Commit: 3176db2 (support/1.12)
Author: Owen Nichols
Message: temporarily point to staging repo for CI purposes

View the changeset: 
https://github.com/apache/geode-examples/compare/d6ebb53ed4dd...3176db2c8f53

View the full build log and details: 
https://travis-ci.com/github/apache/geode-examples/builds/228676524?utm_medium=notification&utm_source=email

  Restart your build: 
https://travis-ci.com/github/apache/geode-examples/builds/228676524?utm_medium=notification&utm_source=email

--

You can unsubscribe from build emails from the apache/geode-examples repository 
going to 
https://travis-ci.com/account/preferences/unsubscribe?repository=16807635&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.

Errored: apache/geode-examples#548 (rel/v1.12.3.RC2 - 078f3b8)

[Travis CI]

Build Update for apache/geode-examples
-

Build: #548
Status: Errored

Duration: 1 min and 0 secs
Commit: 078f3b8 (rel/v1.12.3.RC2)
Author: Owen Nichols
Message: Revert "temporarily point to staging repo for CI purposes"

View the changeset: 
https://github.com/apache/geode-examples/compare/rel/v1.12.3.RC2

View the full build log and details: 
https://travis-ci.com/github/apache/geode-examples/builds/228676540?utm_medium=notification&utm_source=email


--

You can unsubscribe from build emails from the apache/geode-examples repository 
going to 
https://travis-ci.com/account/preferences/unsubscribe?repository=16807635&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.

Failed: apache/geode-native#3080 (rel/v1.12.3.RC2 - 717bbf7)

[Travis CI]

Build Update for apache/geode-native
-

Build: #3080
Status: Failed

Duration: 1 min and 44 secs
Commit: 717bbf7 (rel/v1.12.3.RC2)
Author: Owen Nichols
Message: update Dockerfile and other variables to apache-geode 1.12.2

View the changeset: 
https://github.com/apache/geode-native/compare/rel/v1.12.3.RC2

View the full build log and details: 
https://travis-ci.com/github/apache/geode-native/builds/228676549?utm_medium=notification&utm_source=email


--

You can unsubscribe from build emails from the apache/geode-native repository 
going to 
https://travis-ci.com/account/preferences/unsubscribe?repository=16807653&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at 
https://travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml 
file. See https://docs.travis-ci.com/user/notifications.