Geode unit tests 'develop/DistributedTest' took too long to execute
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/73
Geode unit tests 'develop/DistributedTest' took too long to execute
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/74
Re: [SECURITY] CVE-2017-9796 Apache Geode OQL bind parameter vulnerability
Please remove me from all future emails and distributions. Thanks, Kevin Sent from my iPhone > On Jan 9, 2018, at 5:05 PM, Anthony Baker wrote: > > CVE-2017-9796 Apache Geode OQL bind parameter vulnerability > > Severity: Important > > Vendor: The Apache Software Foundation > > Versions Affected: Apache Geode 1.0.0 through 1.2.1 > > Description: > A malicious user with read access to specific regions within a Geode > cluster may execute OQL queries containing a region name as a bind > parameter that allow read access to objects within unauthorized > regions. > > Mitigation: > Users of the affected versions should upgrade to Apache Geode 1.3.0 or later. > > Credit: > This issue was reported responsibly to the Apache Geode Security Team > by Dan Smith from Pivotal. > > References: > [1] https://issues.apache.org/jira/browse/GEODE-3248 > [2] > https://cwiki.apache.org/confluence/display/GEODE/Release+Notes#ReleaseNotes-SecurityVulnerabilities > > --- > The Geode PMC
Errored: apache/geode#5544 (develop - a4329ad)
Build Update for apache/geode - Build: #5544 Status: Errored Duration: 22 minutes and 34 seconds Commit: a4329ad (develop) Author: Sarge Message: GEODE-4255: Remove mandatory failure on macOS. View the changeset: https://github.com/apache/geode/compare/da3384d8a817...a4329ad497a3 View the full build log and details: https://travis-ci.org/apache/geode/builds/327813431?utm_source=email&utm_medium=notification -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Geode unit tests completed in 'develop/FlakyTest' with non-zero exit code
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/FlakyTest/builds/109
[Spring CI] Spring Data GemFire > Nightly-ApacheGeode > #794 was SUCCESSFUL (with 2324 tests)
--- Spring Data GemFire > Nightly-ApacheGeode > #794 was successful. --- Scheduled 2326 tests in total. https://build.spring.io/browse/SGF-NAG-794/ -- This message is automatically generated by Atlassian Bamboo
Geode unit tests completed in 'develop/DistributedTest' with non-zero exit code
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/DistributedTest/builds/75
Full diffs in Jira comments
I noticed that we are once again getting full diffs added to Jira comments for Pull Requests. (see https://issues.apache.org/jira/browse/GEODE-3965). I've reopened https://issues.apache.org/jira/browse/INFRA-15727.
ExecutorServiceRule
GEODE-4239: Create JUnit Rule to facilitate reuse of ExecutorService pattern for concurrent integration tests I just merged GEODE-4239 to develop. This introduces a new JUnit rule called ExecutorServiceRule. The commit also updates about 8 tests to use this rule. ExecutorServiceRule provides a reusable mechanism for executing tasks asynchronously in tests. It creates an ExecutorService which is terminated after the scope of the rule and can be used in tests for hangs, deadlocks, and infinite loops. You can use this in any type of test (Unit Test, Integration Test, Distributed Test). If you're doing any sort of waiting in a test, then you probably want to move that from Unit Test to Integration Test category. RegionVersionVectorTest is an example of a Unit Test usage that's ok. You can use it as a method @Rule or a @ClassRule. The javadocs on ExecutorServiceRule explain how to use it. You can also look at these tests for example usage: * AbortableTaskServiceJUnitTest * BlockingProcessStreamReaderWindowsTest * DLockServiceLeakTest * FileProcessControllerIntegrationTest * GMSEncryptJUnitTest * InterruptDiskJUnitTest * MainLauncherJUnitTest * RegionVersionVectorTest ExecutorServiceRule is directly tested by these new tests: * ExecutorServiceRuleTest * ExecutorServiceRuleIntegrationTest
Build for version 1.5.0-build.302 of Apache Geode failed.
= The build job for Apache Geode version 1.5.0-build.302 has failed. Build artifacts are available at: http://files.apachegeode-ci.info/builds/1.5.0-build.302/geode-build-artifacts-1.5.0-build.302.tgz Test results are available at: http://files.apachegeode-ci.info/builds/1.5.0-build.302/test-results/build/ Job: https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/Build/builds/328 =
Geode unit tests 'release-1.4.0/DistributedTest' took too long to execute
Pipeline results can be found at: Concourse: https://concourse.apachegeode-ci.info/teams/main/pipelines/release-1.4.0/jobs/DistributedTest/builds/9
