On Wed, Sep 24, 2014 at 2:57 PM, Jay Vyas <[email protected]> wrote: > Hi Tim. > > I generally deploy bigtop using the vagrant recipes, which set this memory, > users, init hdfs automatically . Meanwhile, when we test vendor distros, > those settings are usually also set for you. > > And you're right the pig tests aren't idemopotent. Would love to see a jira > for test idemootency. I think some others are also not idemopotent. > > Glad the smoke-tests framework is working for you. I think your the 3rd > person I know who has used it as a quick way to get up and running with > bigtop smoke tests. > > Would you like to summarize your findings in a JIra outlining improvements > that you'd like to see? If so I can work on them this wknd.
I can't echo that suggestion enough: we soooo do need folks like you, Tim, to help us with keeping things up-to-date. To answer one of the questions you asked earlier: the smoke tests used to be executed nightly (and most definitely on every release). What has changed recently is that Bigtop has suffered quite a fundamental meltdown of our EC2 infra. I'm rebuilding some of it right now, but the progress is slow. Not trying to come up with excesses -- just explaining the situation. Given that we're standardizing our CI on Docker, though, Bigtop is now a perfect place to get to play with that bit of coolness. So... if you're interested -- I'd be more than happy to give you a lowdown on what needs to be done. Thanks, Roman.
