You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Tae-Geon Um <ta...@gmail.com> on 2015/09/22 09:32:42 UTC
Ubuntu CI is unstable
Hi all,
It looks like ubuntu CI is unstable again.
I will take a look and let you know if it is resolved.
Thanks.
Taegeon
Re: Ubuntu CI is unstable
Posted by Tae-Geon Um <ta...@gmail.com>.
> On Sep 30, 2015, at 1:37 PM, Dongjoon Hyun <do...@apache.org> wrote:
>
> Thank you for confirming. I also observed your change on maximum heap size,
> too.
>
> Here, what I asked is using JDK 1.7 on Dockerized Ubuntu. You already
> changed that in #575. How do you think about that?
>
Oh, even though we increase the maximum heap size, if we use JDK 1.7 in that machine, we got an Out of memory error ( https://builds.apache.org/job/Reef-pull-request-ubuntu/573/console <https://builds.apache.org/job/Reef-pull-request-ubuntu/573/console> )
[Reef-pull-request-ubuntu] $ /home/jenkins/tools/java/latest1.7/bin/java -Xmx2500m -Xms512m -XX:MaxPermSize=1024m -cp /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/tools/maven/apache-maven-3.0.4 /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven3-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 54609
2015-09-22 07:57:46,528 WARN io.netty.util.internal.logging.Slf4JLogger warn org.apache.reef.wake.remote.transport.netty.NettyMessagingTransportClientWorker-pool-135-thread-1 An exception was thrown by org.apache.reef.wake.remote.transport.netty.NettyChannelFutureListener.operationComplete()
java.lang.OutOfMemoryError: Java heap space
This is why I’ve changed the JDK from 1.7 to 1.8 :)
> Dongjoon.
>
> On Wednesday, 30 September 2015, Taegeon Um <ta...@gmail.com> wrote:
>
>> Hi, Dongjoon
>>
>> 2015. 9. 30. 오전 1:38에 "Dongjoon Hyun" <dongjoon@apache.org <javascript:;>>님이
>> 작성:
>>>
>>> Hi, Tae-Geon.
>>>
>>> Could you use JDK 1.7 back again, please?
>>> In the REEF Jenkins ubuntu build environment, I found JDK is not the only
>>> difference.
>>> I guess the root cause might be not enough memory on OS.
>>>
>>>
>>
>> Thanks for your investigation.
>>
>> Yes. I think this is the root cause. The build server has small memory. We
>> cannot change the memory configuration.
>>
>> I've tried to increase heap size, but it doesn't work because of the small
>> memory.
>>
>> But when I changed the jdk from 1.7 to 1.8, it works.
>> Maybe, this is because 1.8 uses memory efficiently?
>>
>>>
>>> *# 574 (Failed, JDK 1.7, Ubuntu 14.04 VM with 4GB RAM?)*
>>> https://builds.apache.org/job/Reef-pull-request-ubuntu/574/consoleFull
>>> ...
>>> Building remotely on jenkins-ubuntu-1404-4gb-445 (jenkins-cloud-4GB
>>> cloud-slave Ubuntu ubuntu)
>>> ...
>>> /home/jenkins/tools/java/latest1.7/bin/java -Xmx2800m -Xms512m
>>> -XX:MaxPermSize=1024m -cp
>>>
>>
>> /jenkins/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
>>> org.jvnet.hudson.maven3.agent.Maven3Main
>>> /home/jenkins/tools/maven/apache-maven-3.0.4 /jenkins/slave.jar
>>> /jenkins/maven3-interceptor.jar /jenkins/maven3-interceptor-commons.jar
>>> 48332
>>> Error occurred during initialization of VM
>>> ====> It's VM initialization error, not testsuite error.
>>>
>>>
>>> *# 575 (Success, JDK 1.8, Dockerized Ubuntu with more memory?)*
>>> https://builds.apache.org/job/Reef-pull-request-ubuntu/575/consoleFull
>>> ...
>>> Building remotely on ubuntu-5 (docker Ubuntu ubuntu5 ubuntu)
>>> ...
>>> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.8.0/bin/java
>>> -Xmx2800m -Xms512m -XX:MaxPermSize=1024m -cp
>>>
>>
>> /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
>>> org.jvnet.hudson.maven3.agent.Maven3Main
>>> /home/jenkins/tools/maven/apache-maven-3.0.4
>>> /home/jenkins/jenkins-slave/slave.jar
>>> /home/jenkins/jenkins-slave/maven3-interceptor.jar
>>> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 56368
>>> ...
>>> SUCCESS
>>>
>>>
>>> I hope we can use JDK 1.7 in build tests.
>>>
>>> Warmly,
>>> Dongjoon.
>>>
>>>
>>> On Wed, Sep 30, 2015 at 12:36 AM, Markus Weimer <markus@weimo.de
>> <javascript:;>> wrote:
>>>
>>>> Good to hear!
>>>>
>>>> Markus
>>>>
>>>> On Tue, Sep 29, 2015 at 3:15 AM, Dongjoon Hyun <dongjoon@apache.org
>> <javascript:;>>
>>>> wrote:
>>>>> I have tested with JDK 1.7 on my Ubuntu 15.04 several times since
>> last CI
>>>>> failure, but it looks good on my Ubuntu.
>>>>> It might be Apache build server specific problem.
>>>>>
>>>>> Regards,
>>>>> Dongjoon.
>>>>>
>>>>> On Tue, Sep 29, 2015 at 1:37 PM, Brian Cho <chobrian@gmail.com
>> <javascript:;>> wrote:
>>>>>
>>>>>> FWIW, my Macbook runs the tests fine with 1.7. It must be either a
>>>> Ubuntu
>>>>>> or Apache build server specific problem.
>>>>>>
>>>>>> Thanks,
>>>>>> Brian
>>>>>>
>>>>>> On Mon, Sep 28, 2015 at 8:18 AM, Markus Weimer <markus@weimo.de
>> <javascript:;>>
>> wrote:
>>>>>>
>>>>>>> On Tue, Sep 22, 2015 at 5:44 AM, Tae-Geon Um <taegeonum@gmail.com
>> <javascript:;>>
>>>>>> wrote:
>>>>>>>> It seems like the problem has been resolved by changing java
>> version
>>>>>>> from 1.7 to 1.8
>>>>>>>
>>>>>>> Great! However, does that mean we now officially need 1.8? That
>> would
>>>>>>> be a bummer, as we'd outpace the ecosystem in our requirements.
>>>>>>>
>>>>>>> Markus
>>>>>>>
>>>>>>
>>>>
>>
Re: Ubuntu CI is unstable
Posted by Dongjoon Hyun <do...@apache.org>.
Thank you for confirming. I also observed your change on maximum heap size,
too.
Here, what I asked is using JDK 1.7 on Dockerized Ubuntu. You already
changed that in #575. How do you think about that?
Dongjoon.
On Wednesday, 30 September 2015, Taegeon Um <ta...@gmail.com> wrote:
> Hi, Dongjoon
>
> 2015. 9. 30. 오전 1:38에 "Dongjoon Hyun" <dongjoon@apache.org <javascript:;>>님이
> 작성:
> >
> > Hi, Tae-Geon.
> >
> > Could you use JDK 1.7 back again, please?
> > In the REEF Jenkins ubuntu build environment, I found JDK is not the only
> > difference.
> > I guess the root cause might be not enough memory on OS.
> >
> >
>
> Thanks for your investigation.
>
> Yes. I think this is the root cause. The build server has small memory. We
> cannot change the memory configuration.
>
> I've tried to increase heap size, but it doesn't work because of the small
> memory.
>
> But when I changed the jdk from 1.7 to 1.8, it works.
> Maybe, this is because 1.8 uses memory efficiently?
>
> >
> > *# 574 (Failed, JDK 1.7, Ubuntu 14.04 VM with 4GB RAM?)*
> > https://builds.apache.org/job/Reef-pull-request-ubuntu/574/consoleFull
> > ...
> > Building remotely on jenkins-ubuntu-1404-4gb-445 (jenkins-cloud-4GB
> > cloud-slave Ubuntu ubuntu)
> > ...
> > /home/jenkins/tools/java/latest1.7/bin/java -Xmx2800m -Xms512m
> > -XX:MaxPermSize=1024m -cp
> >
>
> /jenkins/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
> > org.jvnet.hudson.maven3.agent.Maven3Main
> > /home/jenkins/tools/maven/apache-maven-3.0.4 /jenkins/slave.jar
> > /jenkins/maven3-interceptor.jar /jenkins/maven3-interceptor-commons.jar
> > 48332
> > Error occurred during initialization of VM
> > ====> It's VM initialization error, not testsuite error.
> >
> >
> > *# 575 (Success, JDK 1.8, Dockerized Ubuntu with more memory?)*
> > https://builds.apache.org/job/Reef-pull-request-ubuntu/575/consoleFull
> > ...
> > Building remotely on ubuntu-5 (docker Ubuntu ubuntu5 ubuntu)
> > ...
> > /home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.8.0/bin/java
> > -Xmx2800m -Xms512m -XX:MaxPermSize=1024m -cp
> >
>
> /home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
> > org.jvnet.hudson.maven3.agent.Maven3Main
> > /home/jenkins/tools/maven/apache-maven-3.0.4
> > /home/jenkins/jenkins-slave/slave.jar
> > /home/jenkins/jenkins-slave/maven3-interceptor.jar
> > /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 56368
> > ...
> > SUCCESS
> >
> >
> > I hope we can use JDK 1.7 in build tests.
> >
> > Warmly,
> > Dongjoon.
> >
> >
> > On Wed, Sep 30, 2015 at 12:36 AM, Markus Weimer <markus@weimo.de
> <javascript:;>> wrote:
> >
> > > Good to hear!
> > >
> > > Markus
> > >
> > > On Tue, Sep 29, 2015 at 3:15 AM, Dongjoon Hyun <dongjoon@apache.org
> <javascript:;>>
> > > wrote:
> > > > I have tested with JDK 1.7 on my Ubuntu 15.04 several times since
> last CI
> > > > failure, but it looks good on my Ubuntu.
> > > > It might be Apache build server specific problem.
> > > >
> > > > Regards,
> > > > Dongjoon.
> > > >
> > > > On Tue, Sep 29, 2015 at 1:37 PM, Brian Cho <chobrian@gmail.com
> <javascript:;>> wrote:
> > > >
> > > >> FWIW, my Macbook runs the tests fine with 1.7. It must be either a
> > > Ubuntu
> > > >> or Apache build server specific problem.
> > > >>
> > > >> Thanks,
> > > >> Brian
> > > >>
> > > >> On Mon, Sep 28, 2015 at 8:18 AM, Markus Weimer <markus@weimo.de
> <javascript:;>>
> wrote:
> > > >>
> > > >> > On Tue, Sep 22, 2015 at 5:44 AM, Tae-Geon Um <taegeonum@gmail.com
> <javascript:;>>
> > > >> wrote:
> > > >> > > It seems like the problem has been resolved by changing java
> version
> > > >> > from 1.7 to 1.8
> > > >> >
> > > >> > Great! However, does that mean we now officially need 1.8? That
> would
> > > >> > be a bummer, as we'd outpace the ecosystem in our requirements.
> > > >> >
> > > >> > Markus
> > > >> >
> > > >>
> > >
>
Re: Ubuntu CI is unstable
Posted by Taegeon Um <ta...@gmail.com>.
Hi, Dongjoon
2015. 9. 30. 오전 1:38에 "Dongjoon Hyun" <do...@apache.org>님이 작성:
>
> Hi, Tae-Geon.
>
> Could you use JDK 1.7 back again, please?
> In the REEF Jenkins ubuntu build environment, I found JDK is not the only
> difference.
> I guess the root cause might be not enough memory on OS.
>
>
Thanks for your investigation.
Yes. I think this is the root cause. The build server has small memory. We
cannot change the memory configuration.
I've tried to increase heap size, but it doesn't work because of the small
memory.
But when I changed the jdk from 1.7 to 1.8, it works.
Maybe, this is because 1.8 uses memory efficiently?
>
> *# 574 (Failed, JDK 1.7, Ubuntu 14.04 VM with 4GB RAM?)*
> https://builds.apache.org/job/Reef-pull-request-ubuntu/574/consoleFull
> ...
> Building remotely on jenkins-ubuntu-1404-4gb-445 (jenkins-cloud-4GB
> cloud-slave Ubuntu ubuntu)
> ...
> /home/jenkins/tools/java/latest1.7/bin/java -Xmx2800m -Xms512m
> -XX:MaxPermSize=1024m -cp
>
/jenkins/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
> org.jvnet.hudson.maven3.agent.Maven3Main
> /home/jenkins/tools/maven/apache-maven-3.0.4 /jenkins/slave.jar
> /jenkins/maven3-interceptor.jar /jenkins/maven3-interceptor-commons.jar
> 48332
> Error occurred during initialization of VM
> ====> It's VM initialization error, not testsuite error.
>
>
> *# 575 (Success, JDK 1.8, Dockerized Ubuntu with more memory?)*
> https://builds.apache.org/job/Reef-pull-request-ubuntu/575/consoleFull
> ...
> Building remotely on ubuntu-5 (docker Ubuntu ubuntu5 ubuntu)
> ...
> /home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.8.0/bin/java
> -Xmx2800m -Xms512m -XX:MaxPermSize=1024m -cp
>
/home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
> org.jvnet.hudson.maven3.agent.Maven3Main
> /home/jenkins/tools/maven/apache-maven-3.0.4
> /home/jenkins/jenkins-slave/slave.jar
> /home/jenkins/jenkins-slave/maven3-interceptor.jar
> /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 56368
> ...
> SUCCESS
>
>
> I hope we can use JDK 1.7 in build tests.
>
> Warmly,
> Dongjoon.
>
>
> On Wed, Sep 30, 2015 at 12:36 AM, Markus Weimer <ma...@weimo.de> wrote:
>
> > Good to hear!
> >
> > Markus
> >
> > On Tue, Sep 29, 2015 at 3:15 AM, Dongjoon Hyun <do...@apache.org>
> > wrote:
> > > I have tested with JDK 1.7 on my Ubuntu 15.04 several times since
last CI
> > > failure, but it looks good on my Ubuntu.
> > > It might be Apache build server specific problem.
> > >
> > > Regards,
> > > Dongjoon.
> > >
> > > On Tue, Sep 29, 2015 at 1:37 PM, Brian Cho <ch...@gmail.com> wrote:
> > >
> > >> FWIW, my Macbook runs the tests fine with 1.7. It must be either a
> > Ubuntu
> > >> or Apache build server specific problem.
> > >>
> > >> Thanks,
> > >> Brian
> > >>
> > >> On Mon, Sep 28, 2015 at 8:18 AM, Markus Weimer <ma...@weimo.de>
wrote:
> > >>
> > >> > On Tue, Sep 22, 2015 at 5:44 AM, Tae-Geon Um <ta...@gmail.com>
> > >> wrote:
> > >> > > It seems like the problem has been resolved by changing java
version
> > >> > from 1.7 to 1.8
> > >> >
> > >> > Great! However, does that mean we now officially need 1.8? That
would
> > >> > be a bummer, as we'd outpace the ecosystem in our requirements.
> > >> >
> > >> > Markus
> > >> >
> > >>
> >
Re: Ubuntu CI is unstable
Posted by Dongjoon Hyun <do...@apache.org>.
Hi, Tae-Geon.
Could you use JDK 1.7 back again, please?
In the REEF Jenkins ubuntu build environment, I found JDK is not the only
difference.
I guess the root cause might be not enough memory on OS.
*# 574 (Failed, JDK 1.7, Ubuntu 14.04 VM with 4GB RAM?)*
https://builds.apache.org/job/Reef-pull-request-ubuntu/574/consoleFull
...
Building remotely on jenkins-ubuntu-1404-4gb-445 (jenkins-cloud-4GB
cloud-slave Ubuntu ubuntu)
...
/home/jenkins/tools/java/latest1.7/bin/java -Xmx2800m -Xms512m
-XX:MaxPermSize=1024m -cp
/jenkins/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
org.jvnet.hudson.maven3.agent.Maven3Main
/home/jenkins/tools/maven/apache-maven-3.0.4 /jenkins/slave.jar
/jenkins/maven3-interceptor.jar /jenkins/maven3-interceptor-commons.jar
48332
Error occurred during initialization of VM
====> It's VM initialization error, not testsuite error.
*# 575 (Success, JDK 1.8, Dockerized Ubuntu with more memory?)*
https://builds.apache.org/job/Reef-pull-request-ubuntu/575/consoleFull
...
Building remotely on ubuntu-5 (docker Ubuntu ubuntu5 ubuntu)
...
/home/jenkins/jenkins-slave/tools/hudson.model.JDK/jdk-1.8.0/bin/java
-Xmx2800m -Xms512m -XX:MaxPermSize=1024m -cp
/home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/tools/maven/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar
org.jvnet.hudson.maven3.agent.Maven3Main
/home/jenkins/tools/maven/apache-maven-3.0.4
/home/jenkins/jenkins-slave/slave.jar
/home/jenkins/jenkins-slave/maven3-interceptor.jar
/home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 56368
...
SUCCESS
I hope we can use JDK 1.7 in build tests.
Warmly,
Dongjoon.
On Wed, Sep 30, 2015 at 12:36 AM, Markus Weimer <ma...@weimo.de> wrote:
> Good to hear!
>
> Markus
>
> On Tue, Sep 29, 2015 at 3:15 AM, Dongjoon Hyun <do...@apache.org>
> wrote:
> > I have tested with JDK 1.7 on my Ubuntu 15.04 several times since last CI
> > failure, but it looks good on my Ubuntu.
> > It might be Apache build server specific problem.
> >
> > Regards,
> > Dongjoon.
> >
> > On Tue, Sep 29, 2015 at 1:37 PM, Brian Cho <ch...@gmail.com> wrote:
> >
> >> FWIW, my Macbook runs the tests fine with 1.7. It must be either a
> Ubuntu
> >> or Apache build server specific problem.
> >>
> >> Thanks,
> >> Brian
> >>
> >> On Mon, Sep 28, 2015 at 8:18 AM, Markus Weimer <ma...@weimo.de> wrote:
> >>
> >> > On Tue, Sep 22, 2015 at 5:44 AM, Tae-Geon Um <ta...@gmail.com>
> >> wrote:
> >> > > It seems like the problem has been resolved by changing java version
> >> > from 1.7 to 1.8
> >> >
> >> > Great! However, does that mean we now officially need 1.8? That would
> >> > be a bummer, as we'd outpace the ecosystem in our requirements.
> >> >
> >> > Markus
> >> >
> >>
>
Re: Ubuntu CI is unstable
Posted by Markus Weimer <ma...@weimo.de>.
Good to hear!
Markus
On Tue, Sep 29, 2015 at 3:15 AM, Dongjoon Hyun <do...@apache.org> wrote:
> I have tested with JDK 1.7 on my Ubuntu 15.04 several times since last CI
> failure, but it looks good on my Ubuntu.
> It might be Apache build server specific problem.
>
> Regards,
> Dongjoon.
>
> On Tue, Sep 29, 2015 at 1:37 PM, Brian Cho <ch...@gmail.com> wrote:
>
>> FWIW, my Macbook runs the tests fine with 1.7. It must be either a Ubuntu
>> or Apache build server specific problem.
>>
>> Thanks,
>> Brian
>>
>> On Mon, Sep 28, 2015 at 8:18 AM, Markus Weimer <ma...@weimo.de> wrote:
>>
>> > On Tue, Sep 22, 2015 at 5:44 AM, Tae-Geon Um <ta...@gmail.com>
>> wrote:
>> > > It seems like the problem has been resolved by changing java version
>> > from 1.7 to 1.8
>> >
>> > Great! However, does that mean we now officially need 1.8? That would
>> > be a bummer, as we'd outpace the ecosystem in our requirements.
>> >
>> > Markus
>> >
>>
Re: Ubuntu CI is unstable
Posted by Dongjoon Hyun <do...@apache.org>.
I have tested with JDK 1.7 on my Ubuntu 15.04 several times since last CI
failure, but it looks good on my Ubuntu.
It might be Apache build server specific problem.
Regards,
Dongjoon.
On Tue, Sep 29, 2015 at 1:37 PM, Brian Cho <ch...@gmail.com> wrote:
> FWIW, my Macbook runs the tests fine with 1.7. It must be either a Ubuntu
> or Apache build server specific problem.
>
> Thanks,
> Brian
>
> On Mon, Sep 28, 2015 at 8:18 AM, Markus Weimer <ma...@weimo.de> wrote:
>
> > On Tue, Sep 22, 2015 at 5:44 AM, Tae-Geon Um <ta...@gmail.com>
> wrote:
> > > It seems like the problem has been resolved by changing java version
> > from 1.7 to 1.8
> >
> > Great! However, does that mean we now officially need 1.8? That would
> > be a bummer, as we'd outpace the ecosystem in our requirements.
> >
> > Markus
> >
>
Re: Ubuntu CI is unstable
Posted by Brian Cho <ch...@gmail.com>.
FWIW, my Macbook runs the tests fine with 1.7. It must be either a Ubuntu
or Apache build server specific problem.
Thanks,
Brian
On Mon, Sep 28, 2015 at 8:18 AM, Markus Weimer <ma...@weimo.de> wrote:
> On Tue, Sep 22, 2015 at 5:44 AM, Tae-Geon Um <ta...@gmail.com> wrote:
> > It seems like the problem has been resolved by changing java version
> from 1.7 to 1.8
>
> Great! However, does that mean we now officially need 1.8? That would
> be a bummer, as we'd outpace the ecosystem in our requirements.
>
> Markus
>
Re: Ubuntu CI is unstable
Posted by Markus Weimer <ma...@weimo.de>.
On Tue, Sep 22, 2015 at 5:44 AM, Tae-Geon Um <ta...@gmail.com> wrote:
> It seems like the problem has been resolved by changing java version from 1.7 to 1.8
Great! However, does that mean we now officially need 1.8? That would
be a bummer, as we'd outpace the ecosystem in our requirements.
Markus
Re: Ubuntu CI is unstable
Posted by Tae-Geon Um <ta...@gmail.com>.
It seems like the problem has been resolved by changing java version from 1.7 to 1.8
Taegeon
> On Sep 22, 2015, at 5:09 PM, Brian Cho <ch...@gmail.com> wrote:
>
> Thanks Taegeon!
>
> -Brian
>
> On Tue, Sep 22, 2015 at 4:32 PM, Tae-Geon Um <ta...@gmail.com> wrote:
>
>> Hi all,
>>
>> It looks like ubuntu CI is unstable again.
>> I will take a look and let you know if it is resolved.
>>
>> Thanks.
>> Taegeon
>>
>>
Re: Ubuntu CI is unstable
Posted by Brian Cho <ch...@gmail.com>.
Thanks Taegeon!
-Brian
On Tue, Sep 22, 2015 at 4:32 PM, Tae-Geon Um <ta...@gmail.com> wrote:
> Hi all,
>
> It looks like ubuntu CI is unstable again.
> I will take a look and let you know if it is resolved.
>
> Thanks.
> Taegeon
>
>