Socorro/Pre-PHX Smoketest Schedule: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(</bug_needed>)
(note)
Line 5: Line 5:
*** crashes are collected without error
*** crashes are collected without error
*** all submitted crashes are collected
*** all submitted crashes are collected
*** at what point do collectors fall over?
** how:  
** how:  
*** <strike>grinder ({{bug|619815}}) + 20 VMs ({{bug|619814}})</strike>
*** <strike>grinder ({{bug|619815}}) + 20 VMs ({{bug|619814}})</strike>
*** Lars added stats and iteration to submitter.py for initial smoke-test {{bug|622311}}
*** Lars added stats and iteration to submitter.py for initial smoke-test {{bug|622311}}
*** 40 seamicro nodes standing by to test
** when:
** when:
*** waiting on deps in tracking {{bug|619811}}
*** waiting on deps in tracking {{bug|619811}}
*** tentative date - Monday Jan 10 2010
* what component failure tests we will run
* what component failure tests we will run
** disable individual components to see test failure/recovery
** disable individual components to see test failure/recovery
Line 17: Line 20:
*** processor
*** processor
*** others?
*** others?
* Outstanding issues
** how many crashes to use?
*** 500 random real-world crashes?

Revision as of 01:28, 7 January 2011

bug 619817

  • What we are going to test and how in terms of load
    • what:
      • crashes are collected without error
      • all submitted crashes are collected
      • at what point do collectors fall over?
    • how:
      • grinder (bug 619815) + 20 VMs (bug 619814)
      • Lars added stats and iteration to submitter.py for initial smoke-test bug 622311
      • 40 seamicro nodes standing by to test
    • when:
      • waiting on deps in tracking bug 619811
      • tentative date - Monday Jan 10 2010
  • what component failure tests we will run
    • disable individual components to see test failure/recovery
      • hbase
      • postgresql
      • monitor
      • processor
      • others?
  • Outstanding issues
    • how many crashes to use?
      • 500 random real-world crashes?