Ildar,
The maven test for asterixdb has already enabled the debug port in
https://github.com/apache/incubator-asterixdb/blob/master/pom.xml:
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
You can connect to the port (just that you need to the IP of the test
machine -- I'm not sure if it is the same as asterix-jenkins.ics.uci.edu or
not).
Also, once you attach a debugger to the JVM, timings can change and I'm
not sure if it will be harder or easier to see the issue.
Best,
Yingyi
On Wed, Nov 11, 2015 at 10:47 AM, Ildar Absalyamov <
[email protected]> wrote:
> Seems like issue https://issues.apache.org/jira/browse/ASTERIXDB-1159 is
> the most annoying.
> It also fails on Jenkins pretty often (could fail several times in the
> row), however I still cannot reproduce it on my machine.
> I see two solutions here: 1) run the build the same way Jenkins runs it
> (in docker container?). 2) remote debug on Jenkins directly
> I don’t know enough about Jenkins build process to go ahead with either
> solution. @Ian maybe you can shed a light on that?
>
> On Nov 11, 2015, at 10:32, Till Westmann <[email protected]> wrote:
>
> Hi,
>
> there are a number of issues that seem to cause sporadic test failures
> that impact everybody.
> These are the issues:
>
> https://issues.apache.org/jira/browse/ASTERIXDB-1137
> https://issues.apache.org/jira/browse/ASTERIXDB-1145
> https://issues.apache.org/jira/browse/ASTERIXDB-1156
> https://issues.apache.org/jira/browse/ASTERIXDB-1159
> https://issues.apache.org/jira/browse/ASTERIXDB-1164
>
> I think that we should resolve them as fast as possible (as in “start
> working on it today” :) ).
> If you are the assignee of one of those issues and are not able to work on
> it right away, please say so.
>
> Cheers,
> Till
>
>
> Best regards,
> Ildar
>
>
