unstable builds

Hello all, I had to do some work on my gerrit patch, after rebasing and submit my build becomes unstable but Jenkins build log shows every module has built and its a success https://asterix-gerrit.ics.uci.edu/#/c/935 am I doing anything wrong? -- Kaveen Rodrigo Personal Website -

buildbot success in on asterixdb-master-docs

The Buildbot has detected a restored build on builder asterixdb-master-docs while building . Full details are available at: https://ci.apache.org/builders/asterixdb-master-docs/builds/170 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: orcus_ubuntu Build Reason: The Nightly

Re: unstable builds

It seems some of the tests have failed, as evident from https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-notopic/2259/org.apache.asterix$asterix-app/testReport/ the errors that are yielding are mostly cannot bind problems, looking over my code to see if there is anything conflicting, But

Re: unstable builds

It seems there is some existing instance on the docker instance and hence it complains that the port is already used. Best, Yingyi On Wed, Aug 17, 2016 at 10:37 AM, Kaveen Rodrigo wrote: > It seems some of the tests have failed, as evident from >

Re: unstable builds

No, the issue is in your change when resolving merge conflicts, you are starting all of the servers twice. The servers are now stored in a list and not as individual fields. Take a look at

Re: unstable builds

I'm a bit puzzled, I thought for each build system spawns an instance to build. Any idea how can I resolve this and re trigger the build? any place I should start looking. thanks in advance On 17 August 2016 at 23:09, Yingyi Bu wrote: > It seems there is some existing

Re: unstable builds

My bad now I understand Shouldn't have blindingly resolved conflicts , I'll get on and change that. sorry for the troubles , thanks On 17 August 2016 at 23:14, Michael Blow wrote: > No, the issue is in your change when resolving merge conflicts, you are > starting all of

Re: unstable builds

The integraiton tests have been faced with some issues lately, but the other tests should be fine. On Wed, Aug 17, 2016 at 3:58 AM, Kaveen Rodrigo wrote: > Hello all, > > I had to do some work on my gerrit patch, after rebasing and submit my > build becomes unstable but

Re: unstable builds

I retriggered it for you, I don't think your changes would have anything to do with that test failure. On Wed, Aug 17, 2016 at 11:49 AM, Kaveen Rodrigo wrote: > Thanks Micheal, I fixed the problem after letting the system do testing for > a while, It has become unstable

Jenkins build became unstable: asterix-integration-tests e61534ee

See

Re: [jira] [Commented] (ASTERIXDB-1587) upsert runtime assumes that the datatype comes from the same dataverse as the dataset

>> But in this case it seemed like the test was unnecessary, although I do have tests on my BAD branch that require this change. It seems useful to me as it will protect the system against future changes. Could you submit a separate new change which only has a test case? Thanks a lot! Best,

Re: [jira] [Commented] (ASTERIXDB-1587) upsert runtime assumes that the datatype comes from the same dataverse as the dataset

Steven, Can you add a regression test before you closing that issue? (Typically, fixing ASTERIXDB- should have a test case in the change.) Thanks! Best, Yingyi On Wed, Aug 17, 2016 at 6:05 PM, ASF subversion and git services (JIRA) < j...@apache.org> wrote: > > [