Socorro/Pre-PHX Smoketest Schedule: Difference between revisions

Revision as of 22:19, 10 January 2011

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, using socorro-loadtest.sh
- when:
  - waiting on deps in tracking bug 619811
  - tentative start date - Monday Jan 10 2010
    - minimum 2-3 days testing; as much as we can get
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?
  - pool of 500 random real-world crashes?

@@ Line 9: / Line 9: @@
 *** <strike>grinder ({{bug|619815}}) + 20 VMs ({{bug|619814}})</strike>
 *** Lars added stats and iteration to submitter.py for initial smoke-test {{bug|622311}}
-*** 40 seamicro nodes standing by to test
+*** 40 seamicro nodes standing by to test, using [https://bug619814.bugzilla.mozilla.org/attachment.cgi?id=502200 socorro-loadtest.sh]
 ** when:
 *** waiting on deps in tracking {{bug|619811}}