Open Stack

Hi Mat:

If I recall correctly, rdjenkins is actually running a version of the
plugin specifically built by Matty for it (should be the latest). I'm not
sure why it's still hitting the timeout issue mentioned earlier, so
we'll have to check with Matty and try to figure out what the deal with
that is.

Cheers,
-Nikhil


Lowery, Mathew writes:

> Hi Nikhil,
>
> This is great!
>
> You may have assumed this but I wanted to be explicit: To get the higher
> timeout, I think all that needs to be done is to upgrade the
> boot-hpcloud-vm plugin. Then the plugin will pass the current timeout
> (7200 in rdjenkins) down to the net-ssl-simple library. (This is all based
> on the assumption that rdjenkins is running an older version of the
> plugin.)
>
> Thanks,
> Mat
>
> On 2/17/14, 10:13 PM, "Nikhil Manchanda" <nikhil at manchanda.me> wrote:
>
>>
>>Hi Mathew:
>>
>>Nice work identifying these issues with the current Jenkins integration
>>tests! I'm looking into some of these issues at the moment and am
>>attempting to ensure that the appropriate fixes are merged so that the
>>Trove integration gate job is healthy again.
>>
>>Some of my comments are inline.
>>
>>Lowery, Mathew writes:
>>
>>> Hi all,
>>>
>>> Issue #1: Jobs that need more than one hour
>>[...]
>>
>>> Suggested action items:
>>>
>>>   *   If it is acceptable to have jobs that run over one hour, then
>>>   install the latest boot-hpcloud-vm plugin for Jenkins which will
>>>   increase the make the operation timeout match the idle timeout.
>>
>>Turns out that some of the configuration parameters changes checked in
>>pushed the gate job above this timeout threshold. For the time
>>being, I suggest we increase the timeout value of the gate job to cater
>>to this increase. However, we also need to take a closer look at our
>>test suite, to see how we might be able to parallelize tests and
>>speed things up.
>>
>>> Issue #2: The running time of all jobs is 1 hr 1 min
>>[...]
>>
>>> Suggested action items:
>>>
>>>   * Given that the minimum running time is one hour, I assume the
>>>   problem is in the net-ssh-simple library. Needs more investigation.
>>
>>I took a brief look at this and it seems like this might be a bug with the
>>underlying plugin. I will try and contact Matty Rhodes who is the author
>>of the plugin to take a look.
>>
>>>
>>> Issue #3: Jenkins console log line timestamps different between full
>>> and truncated views
>>[...]
>>> Suggested action items:
>>>
>>>   *   Upgrade the timestamper
>>>   plugin<https://wiki.jenkins-ci.org/display/JENKINS/Timestamper>.
>>
>>I've gone ahead and updated the timestamper plugin on the rdjenkins box,
>>so that this should no longer be an issue.
>>
>>Let me know if you find anything else.
>>
>>Cheers,
>>-Nikhil
>>
>>_______________________________________________
>>OpenStack-dev mailing list
>>OpenStack-dev at lists.openstack.org
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev