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
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 al
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.
Hi, Craig.
Yes, i thought about configurations test suits.
For now core team, maybe, should extend gate running time.
But for the tempest tests i would suggest to exclude some tests from
'gate'-group (the longest ones).
We need to deal with it asap, because gate failing for four or five days.
Bes
Trovesters,
One reason for the longer running test was that for the configuration
groups i added a creation of a new instance. This is to test a new instance
will be created with a configuration group applied. This might be causing
the run to be a little longer but i am surprised that its taking o
Hello, Mathew.
I'm seeing same issues with the gate.
I also tried to found out why gate job is failing. First ran into issue related
to cinder installation failure in devstack. But then I found same problem as
you described. The best option is to increase job time range.
Thanks for such researc
