Working on Geode with IntelliJ 2018.3

2018-12-13 Thread Kirk Lund
IntelliJ 2018.3.1 downloads sources jars for the jars of old geode versions
that the geode-old-versions module refers to. The Javadoc {@link class}
editor support in IJ 2018.3.1 then seems to randomly reference some of the
Geode classes in those old geode jars instead of local .java files in the
project.

My recommendation is to stick to IntelliJ 2018.2.x until someone using
2018.3.x reports back to the dev list that the above problem is fixed. Or
you can use 2018.3.1 and just realize you won't have the IDE support for
editing Javadocs that you may have been used to.

IntelliJ also has a Gradle option that I think you should avoid like the
plague if you're working on Geode. Do *NOT* disable this:

*Preferences -> Build, Execution, Deployment -> Build Tools -> Gradle ->
"Store generated project files externally"*

Disabling the above results in classpath errors when trying to run dunit
tests in IntelliJ.

If anyone has more information on any of the above (especially how to fix
or workaround it) then please share!


Pull Request builder timing out

2018-12-13 Thread Galen O'Sullivan
On the PR for https://github.com/apache/geode/pull/2938, the StressNewTest
and (in two different runs of the same code) other jobs fail occasionally.

I'm inclined to think that the Upgrade and Acceptance test failures were
caused by flaky tests, and I can keep rerunning the PR build.

The StressNewTest issue is probably because the tests take a long time to
run. We can't see what tests run or how long they took because the
StressNewTests have an archive but no results page.

If StressTest is going to take too long, should I ignore it and push, or is
there a way to disable it or dial it down for this PR? I know we've had
discussions on the list about not merging if the pipeline is, but I think
the StressTest failures are due to the pipeline not allowing enough time,
and it's meant to fix a test issue.

StressTest jobs:
https://concourse.apachegeode-ci.info/builds/24422
https://concourse.apachegeode-ci.info/builds/24423
https://concourse.apachegeode-ci.info/builds/24061
https://concourse.apachegeode-ci.info/builds/24062

UpgradeTest: https://concourse.apachegeode-ci.info/builds/24060
AcceptanceTest: https://concourse.apachegeode-ci.info/builds/24415


Thanks,
Galen


Re: Pull Request builder timing out

2018-12-13 Thread Owen Nichols
This PR changes 17 tests.  At 50 repeats each, that’s 850 tests.  I’m not sure 
if StressNew does all 850 serially — if it does, they would have to complete in 
under 10 seconds per test to duck the concourse timeout (currently set a little 
over 2 hours).

Approximately how long do you expect each of these tests to take?
Would it make sense to break up the PR into 2 PRs with fewer changed tests in 
each?
Or do we just need to increase the timeout for StressNew to a much bigger value 
(what is reasonable, anyway? 6 hours? 12 hours?).

If you’d like to change the timeout for this job, the following lines may be 
relevant: 

ci/pipelines/shared/jinja.variables.yml lines 111-118:
- name: “StressNew"
  ...
  CALL_STACK_TIMEOUT: "7200"
  execute_test_timeout: 2h15m


If we think there are good reasons to keep the 2-hour time limit in place, and 
there are extenuating reasons why your changes cannot be stressed within this 
time period, I propose we should be able to substitute additional manual 
reviewers in place of the imperfect automatic check here to get this approved.

-Owen

> On Dec 13, 2018, at 2:20 PM, Galen O'Sullivan  wrote:
> 
> On the PR for https://github.com/apache/geode/pull/2938, the StressNewTest
> and (in two different runs of the same code) other jobs fail occasionally.
> 
> I'm inclined to think that the Upgrade and Acceptance test failures were
> caused by flaky tests, and I can keep rerunning the PR build.
> 
> The StressNewTest issue is probably because the tests take a long time to
> run. We can't see what tests run or how long they took because the
> StressNewTests have an archive but no results page.
> 
> If StressTest is going to take too long, should I ignore it and push, or is
> there a way to disable it or dial it down for this PR? I know we've had
> discussions on the list about not merging if the pipeline is, but I think
> the StressTest failures are due to the pipeline not allowing enough time,
> and it's meant to fix a test issue.
> 
> StressTest jobs:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__concourse.apachegeode-2Dci.info_builds_24422&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=5pwPNRvtAJAFP7w9SGYR-NUqYcl8RSrvSLXHd5dKU-o&m=q8-azNJP7a-Vb_gLuTJaHlC9VFqSd-uIaW85r2xRriY&s=KbF1dF4tF8e-rmTrJEVwrFjCuqNHZAhtphTogHN4U5k&e=
> https://urldefense.proofpoint.com/v2/url?u=https-3A__concourse.apachegeode-2Dci.info_builds_24423&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=5pwPNRvtAJAFP7w9SGYR-NUqYcl8RSrvSLXHd5dKU-o&m=q8-azNJP7a-Vb_gLuTJaHlC9VFqSd-uIaW85r2xRriY&s=SGe4aOZYEEVTrEMoMK73p5EjzNANF7wtenF7w7vxtAQ&e=
> https://urldefense.proofpoint.com/v2/url?u=https-3A__concourse.apachegeode-2Dci.info_builds_24061&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=5pwPNRvtAJAFP7w9SGYR-NUqYcl8RSrvSLXHd5dKU-o&m=q8-azNJP7a-Vb_gLuTJaHlC9VFqSd-uIaW85r2xRriY&s=T_8qb6cjL_qdcEbUsuITFtIXZnVoH6mKgXF22sYTL-Q&e=
> https://urldefense.proofpoint.com/v2/url?u=https-3A__concourse.apachegeode-2Dci.info_builds_24062&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=5pwPNRvtAJAFP7w9SGYR-NUqYcl8RSrvSLXHd5dKU-o&m=q8-azNJP7a-Vb_gLuTJaHlC9VFqSd-uIaW85r2xRriY&s=bcNQQeaLkfe_i5FL5MXu4eWNkhwjFfxksDLAkXkjV0c&e=
> 
> UpgradeTest: 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__concourse.apachegeode-2Dci.info_builds_24060&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=5pwPNRvtAJAFP7w9SGYR-NUqYcl8RSrvSLXHd5dKU-o&m=q8-azNJP7a-Vb_gLuTJaHlC9VFqSd-uIaW85r2xRriY&s=IcWIfcx5y0MagkEI7xC9hgt9RTpYj9k881orD5lPau0&e=
> AcceptanceTest: 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__concourse.apachegeode-2Dci.info_builds_24415&d=DwIBaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=5pwPNRvtAJAFP7w9SGYR-NUqYcl8RSrvSLXHd5dKU-o&m=q8-azNJP7a-Vb_gLuTJaHlC9VFqSd-uIaW85r2xRriY&s=_2_nAWdcjyyqKQjP9o6riCgrZb3HnQJ8nDog3Lzdoj4&e=
> 
> 
> Thanks,
> Galen