Updating REGRESSIONS based on last night's runs
Updating REGRESSIONS based on last night's runs

[Have I been applying the word spurious to our failures inappropriately?]

- a spurious pthread mutex assertion failure on iterators -- could be a one
  in a million problem we rarely see or a one in a thousand problem as a
  result of the other week's changes?
- MPI testing started running and gets 184 failures, many reported as SYM0172
- more opts regressions than the past few weeks due to reports errors
* spurious failures



git-svn-id: 88467cb1fb04b8a755be7e1ee1026be4190196ef@16742 3a8e244f-b0f2-452b-bcba-4c88e055c3ca

hildeth/chapel,sungeunchoi/chapel,CoryMcCartan/chapel,chizarlicious/chapel,chizarlicious/chapel,chizarlicious/chapel,hildeth/chapel,CoryMcCartan/chapel,CoryMcCartan/chapel,chizarlicious/chapel,CoryMcCartan/chapel,sungeunchoi/chapel,sungeunchoi/chapel,hildeth/chapel,hildeth/chapel,sungeunchoi/chapel,sungeunchoi/chapel,CoryMcCartan/chapel,chizarlicious/chapel,CoryMcCartan/chapel,chizarlicious/chapel,hildeth/chapel,chizarlicious/chapel,sungeunchoi/chapel,CoryMcCartan/chapel,hildeth/chapel,sungeunchoi/chapel,sungeunchoi/chapel,hildeth/chapel