Mailing-List: contact dev-help@asterixdb.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <C13E464D-A645-4BD3-A175-FEC347F1C946@apache.org>
References: <C13E464D-A645-4BD3-A175-FEC347F1C946@apache.org>
Date: Mon, 4 Apr 2016 18:06:32 -0700
Message-ID: 
 <CAM0o-7ME3K3LhAWWov3em2q6NFjdkbZ=8jjzcG7T6KKHUk3JhA@mail.gmail.com>
Subject: Re: integration tests
From: Murtadha Al-Hubail <hubailmor@gmail.com>
To: dev@asterixdb.incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7bd76cb6bdbee0052fb2741a

--047d7bd76cb6bdbee0052fb2741a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I had a look at it. It is caused by a deadlock when a temporary dataset
triggers a flush.
It wasn=E2=80=99t detected when I introduced a change that eliminates FLUSH=
 logs
generation for temporary indexes because recovery test cases were broken.

I submitted a fix for it [1] and added a runtime test case. The build
should succeed after it gets merged.

Cheers,
Murtadha

[1] https://asterix-gerrit.ics.uci.edu/#/c/785/

On Mon, Apr 4, 2016 at 9:18 AM, Till Westmann <tillw@apache.org> wrote:

> Hi,
>
> since the last successful test run that took 55 mins [1] we seem to have
> more than doubled the runtime to time out at 2 hours [2].
> Does anybody have an idea what caused this?
>
> Cheers,
> Till
>
> [1] https://asterix-jenkins.ics.uci.edu/job/asterix-integration-tests/124=
/
> [2] https://asterix-jenkins.ics.uci.edu/job/asterix-integration-tests/130=
/
>

--047d7bd76cb6bdbee0052fb2741a--