Re: [openstack-dev] [infra][devstack-gate] mad rechecks

2014-07-09 Thread 68x DTS
A
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra][devstack-gate] mad rechecks

2014-07-08 Thread Joe Gordon
On Sat, Jul 5, 2014 at 4:18 AM, Jeremy Stanley fu...@yuggoth.org wrote:

 On 2014-07-04 13:17:12 +0300 (+0300), Sergey Skripnick wrote:
 [...]
  Is there any hope that jobs will just work? Such number of
  failures leads to significant amount of extra work for test nodes.

 There is indeed hope. Most of the failures observed in integration
 testing are because OpenStack is *broken* in various subtle ways
 which become more obvious when tested in volume with parallel
 operations. Others are because of poorly-written tests. Please join
 the effort to fix OpenStack and improve (or remove) broken tests.

 http://status.openstack.org/elastic-recheck/

 However, if our typical response to our inability as a project to
 successfully test our code is to just keep writing more code and
 rechecking over and over rather than pitching in on fixing the bugs
 which impede testing, there may be no hope after all.



I couldn't agree more.


 --
 Jeremy Stanley

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra][devstack-gate] mad rechecks

2014-07-05 Thread Jeremy Stanley
On 2014-07-04 13:17:12 +0300 (+0300), Sergey Skripnick wrote:
[...]
 Is there any hope that jobs will just work? Such number of
 failures leads to significant amount of extra work for test nodes.

There is indeed hope. Most of the failures observed in integration
testing are because OpenStack is *broken* in various subtle ways
which become more obvious when tested in volume with parallel
operations. Others are because of poorly-written tests. Please join
the effort to fix OpenStack and improve (or remove) broken tests.

http://status.openstack.org/elastic-recheck/

However, if our typical response to our inability as a project to
successfully test our code is to just keep writing more code and
rechecking over and over rather than pitching in on fixing the bugs
which impede testing, there may be no hope after all.
-- 
Jeremy Stanley

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra][devstack-gate] mad rechecks

2014-07-05 Thread Joshua Harlow
Has there ever been any talk of a full release cycle or two that *just* focus 
on stability at scale (aka only working on changes that get toward this goal) 
and not miscellaneous features (defining what's miscellaneous or not is 
obviously hard...)?

I know that  is dangerous/controversial talk but maybe it's time we started 
asking that question and start to pose this to the TC...

I feel it starts to become needed to avoid all hope being lost (and hoping that 
it will happen out of the good nature of people's hearts likely won't make it 
reality IMHO).

Thoughts?

Sent from my really tiny device...

 On Jul 5, 2014, at 4:24 AM, Jeremy Stanley fu...@yuggoth.org wrote:
 
 On 2014-07-04 13:17:12 +0300 (+0300), Sergey Skripnick wrote:
 [...]
 Is there any hope that jobs will just work? Such number of
 failures leads to significant amount of extra work for test nodes.
 
 There is indeed hope. Most of the failures observed in integration
 testing are because OpenStack is *broken* in various subtle ways
 which become more obvious when tested in volume with parallel
 operations. Others are because of poorly-written tests. Please join
 the effort to fix OpenStack and improve (or remove) broken tests.
 
http://status.openstack.org/elastic-recheck/
 
 However, if our typical response to our inability as a project to
 successfully test our code is to just keep writing more code and
 rechecking over and over rather than pitching in on fixing the bugs
 which impede testing, there may be no hope after all.
 -- 
 Jeremy Stanley
 
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [infra][devstack-gate] mad rechecks

2014-07-04 Thread Sergey Skripnick


After 2 days and 11 rechecks I finally got +1

https://review.openstack.org/#/c/104123/

failed jobs:

job times
check-dg-tempest-dsvm-full  1
check-dg-tempest-dsvm-full-reexec   3
check-grenade-dsvm  3
check-grenade-dsvm-partial-ncpu 3
check-tempest-dsvm-full-havana  1
check-tempest-dsvm-neutron  1
check-tempest-dsvm-neutron-heat-slow1
check-tempest-dsvm-postgres-full1
check-tempest-dsvm-postgres-full-icehouse   1


Is there any hope that jobs will just work? Such number of failures leads  
to

significant amount of extra work for test nodes.


--
Regards,
Sergey Skripnick

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [infra][devstack-gate] mad rechecks

2014-07-04 Thread Martin Geisler
Sergey Skripnick sskripn...@mirantis.com writes:

 After 2 days and 11 rechecks I finally got +1

 https://review.openstack.org/#/c/104123/

 failed jobs:

 job times
 check-dg-tempest-dsvm-full  1
 check-dg-tempest-dsvm-full-reexec   3
 check-grenade-dsvm  3
 check-grenade-dsvm-partial-ncpu 3
 check-tempest-dsvm-full-havana  1
 check-tempest-dsvm-neutron  1
 check-tempest-dsvm-neutron-heat-slow1
 check-tempest-dsvm-postgres-full1
 check-tempest-dsvm-postgres-full-icehouse   1


 Is there any hope that jobs will just work? Such number of failures
 leads to significant amount of extra work for test nodes.

I recently submitted some patches that cleaned up the comment headers of
Python files. Since I was editing a comment, I was surprised to see test
failures. I counted 12 failed and 61 successful test runs -- about 16%
of the test runs failed for no good reason.

-- 
Martin Geisler

http://google.com/+MartinGeisler


pgp10BD5WPkym.pgp
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev