I haven't run the functional suite myself for this RC. I seem to recall having run the tests on a single VM at some point in the past. Maybe the VM needs to have enough resources to run all the containers requested, though?
On Sun, Mar 12, 2017 at 7:05 PM, jonma...@gmail.com <jonma...@gmail.com> wrote: > Having trouble remembering: is there a requirement for more than one node > manager for the functional tests? Seeing the logging below during a test, > and my initial attempt at running the functional suite was against a single > node HDP installation. > > 2017-03-12 21:43:43,424 [AmExecutor-006] INFO state.AppState > (AppState.java:reviewOneRole(2170)) - COMMAND_LOGGER: Asking for 1 more > nodes(s) for a total of 2 > 2017-03-12 21:43:43,424 [AmExecutor-006] DEBUG state.RoleHistory > (RoleHistory.java:findRecentNodeForNewInstance(606)) - There are 0 node(s) > to consider for COMMAND_LOGGER > 2017-03-12 21:43:43,424 [AmExecutor-006] INFO state.RoleHistory > (RoleHistory.java:findRecentNodeForNewInstance(625)) - No node found for > COMMAND_LOGGER > > > On Sun, Mar 12, 2017 at 6:17 PM, jonma...@gmail.com <jonma...@gmail.com> > wrote: > > > Anyone else attempted running the functional suite? I'm getting some > > errors against an HDP 2.4 cluster (2.4.2.0-258): > > > > Failed tests: > > AppsThroughAgentIT.testCreateFlex:86->CommandTestBase. > > expectLiveContainerCountReached:1367->SliderTestUtils. > > repeatUntilSuccess:1405->CommandTestBase.assertContainersLive:1327-> > > SliderTestUtils.assertContainersLive:780 assert expected == actual > > | | | > > 2 | 1 > > false > > AppsUpgradeIT.testUpgrade:167->CommandTestBase. > > expectContainerRequestedCountReached:1300->SliderTestUtils. > > repeatUntilSuccess:1405->Assert.fail:88 expected request count of > > COMMAND_LOGGER = 1 not reached, actual: 0 after 90000 ms > > ExternalComponentIT.testExternalComponent:103->CommandTestBase. > > expectLiveContainerCountReached:1367->SliderTestUtils. > > repeatUntilSuccess:1405->CommandTestBase.assertContainersLive:1327-> > > SliderTestUtils.assertContainersLive:780 assert expected == actual > > | | | > > 1 | 0 > > false > > UniqueComponentNamesIT.testCreateFlex:95->CommandTestBase. > > expectLiveContainerCountReached:1367->SliderTestUtils. > > repeatUntilSuccess:1405->CommandTestBase.assertContainersLive:1327-> > > SliderTestUtils.assertContainersLive:780 assert expected == actual > > | | | > > 1 | 0 > > false > > > > Tests in error: > > AgentWebPagesIT.testAgentWeb:131->awaitRestEndpointLive: > > 218->SliderTestUtils.repeatUntilSuccess:1380 » UniformInterface > > AgentPingSocketIT.testAgentPingSocket:91->CommandTestBase. > > awaitRegistryOutfileContains:1453->SliderTestUtils. > > repeatUntilSuccess:1405->CommandTestBase.slider:288 » Slider > > AMConfigPublishingIT.testCreate:130->CommandTestBase.slider:288 » > > Slider Expec... > > > > Tests run: 76, Failures: 4, Errors: 3, Skipped: 1 > > > > I'll dig in some more and debug to see if it's a config/setup issue, or > > perhaps my cluster is simply less performant and is taking too long to > > deploy certain apps, but wondering if anyone else has run these tests on > > the release candidate? > > > > -- Jon > > > > > > On Fri, Mar 10, 2017 at 2:06 PM, Gour Saha <gs...@hortonworks.com> > wrote: > > > >> Apologies, fixing the broken link of the source artifacts this time - > >> https://dist.apache.org/repos/dist/dev/incubator/slider/0.92 > >> .0-incubating-RC0 > >> > >> -Gour > >> > >> On 3/10/17, 10:53 AM, "Gour Saha" <gs...@hortonworks.com<mailto: > >> gs...@hortonworks.com>> wrote: > >> > >> All, > >> Kindly note that the Source Artifacts have been moved to - > >> https://dist.apache.org/repos/dist/dev/incubator/slider/0.92 > >> .0-incubating-R > >> C0 > >> <https://dist.apache.org/repos/dist/dev/incubator/ > slider/0.92.0-incubating-RC0> > >> > >> Please do not use the link from the original email which pointed to the > >> release stage. > >> > >> > >> Billie, > >> Thank you for looking into the release candidate. > >> > >> My public key was already in the KEYS file. The key info was also added > in > >> the KEYS file before I staged the release. It was not committed to svn, > >> which I did just now (right above my public key). > >> > >> I did notice the release vs dev staging link during the candidate build, > >> but continued with the release as instructed in Slider's release process > >> documentation. I am fixing the release process document in our site > right > >> now. I have also moved the source artifacts from the release to the dev > >> stage. > >> > >> Let me know if you see anything else not followed as per standard. > >> > >> -Gour > >> > >> > >> On 3/10/17, 9:44 AM, "Billie Rinaldi" <billie.rina...@gmail.com<mailto: > >> billie.rina...@gmail.com>> wrote: > >> > >> Gour, thanks for putting up a release candidate! Two important things > with > >> respect to release logistics: the release should be staged at > >> https://dist.apache.org/repos/dist/dev/incubator/slider/ > >> <http://dist.apache.org/repos/dist/dev/incubator> rather than > >> https://dist.apache.org/repos/dist/release/incubator/slider/ > >> <https://dist.apache.org/repos/dist/release/incubator/slider > >> /0.92.0-incuba > >> ting-RC0 > >> <https://dist.apache.org/repos/dist/release/incubator/ > slider/0.92.0-incubating-RC0> > >> > > >> <https://dist.apache.org/repos/dist/release/incubator/slider > >> /0.92.0-incuba > >> ting-RC0 > >> <https://dist.apache.org/repos/dist/release/incubator/ > slider/0.92.0-incubating-RC0> > >> > > >> ... the "release" path means that the staged candidate is being > >> distributed > >> to all the mirrors. Maybe it would be possible to svn mv the > >> 0.92.0-incubating-RC0 directory to the dev path? Also, please append > your > >> key to the KEYS file at > >> https://dist.apache.org/repos/dist/release/incubator/slider/KEYS. There > >> are > >> instructions at the top of the file. > >> > >> I will continue reviewing RC0. > >> > >> On Thu, Mar 9, 2017 at 11:16 PM, Gour Saha <gs...@hortonworks.com > <mailto: > >> gs...@hortonworks.com>> wrote: > >> > >> Hello, > >> > >> This is a call for a vote on the Apache Slider (incubating) release > >> 0.92.0-incubating-RC0 > >> > >> Source artifacts: > >> https://dist.apache.org/repos/dist/release/incubator/slider/ > >> 0.92.0-incubating-RC0 > >> > >> Staged artifacts: > >> > >> https://repository.apache.org/content/repositories/ > orgapacheslider-1017/ > >> > >> Git source: > >> https://git-wip-us.apache.org/repos/asf?p=incubator-slider.g > >> it;a=commit;h=c41b1c7051d02c02b0d78cab859c7e15d0af92c9 > >> > >> Git commit SHA1: c41b1c7051d02c02b0d78cab859c7e15d0af92c9 > >> > >> Issues fixed: > >> https://issues.apache.org/jira/browse/SLIDER/fixforversion/12339846/ > >> > >> Release Notes: > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > >> ctId=12315422&version=12339846 > >> > >> PGP key: > >> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=gourksa > >> h...@apache.org<mailto:h...@apache.org> > >> > >> [ ] +1 Release Apache Slider (incubating) 0.92.0-incubating-RC0 > >> [ ] +0 No opinion > >> [ ] -1 Do not release Apache Slider (incubating) 0.92.0-incubating-RC0 > >> > >> Voting lasts 72 working hours, until Tuesday 2017/03/14 2315 PST > >> > >> I will start with my +1 vote. > >> > >> -Gour > >> > >> > >> > >> > >> > >> > > > > > > -- > > Sent from some random computer.... > > > > > > -- > Sent from some random computer.... >
