Catching up on past 6 weeks regressions...
Tuesday afternoon REGRESSIONS snapshot
Updating description of walk#9 failure
Merge branch 'master' of https://github.com/chapel-lang/chapel into triage-sep-blc
Merge branch 'master' of https://github.com/chapel-lang/chapel into triage-sep-blc
Snapshot of 9/17 regressions

I'm still working my way through the darwin mail, but needed to put this
aside for a moment.
I think the darwin regression list is now accurate for the first time in ages
Trying to wrap up REGRESSIONS for the day
Merge pull request #470 from bradcray/triage-sep-blc

Midweek REGRESSIONS update (plus lots of backlog and cleanup)

This is a significant housecleaning pass over REGRESSIONS in
preparation for the 1.10 release.


The REGRESSIONS fail had (once again) gotten way out of date in terms
of issues not being logged, not being assigned, and fixed issues not
having been removed.  This pass goes a long way toward bringing it up
to date with reality and assigning recent issues to people.  Many
issues have been fixed since I started on my regressions/triage rant
last week, so thanks for everyone's efforts there.  Meanwhile, Thomas
and I have started a discussion on how to make triage less porous so
that we're not letting issues fall between the cracks as they have
been.

Here are the major changes worth calling out:

* removed the "futures" section and added a comment to the leading
  comment that says the same thing.

* removed passing futures (there aren't any anymore) and section
  (because these aren't regressions and aren't going to cause anyone
  to lose sleep; IMO, they should be assigned and retired ASAP, which
  I think we're mostly pretty good at.

* removed the special section on error matching .bad files because I
  think of these as regressions that should either be in the general
  section or a more specific section if they're specific to that
  configuration.  I.e., they should be treated like any other
  regression.

* removed most commentary on why tests are failing, mostly because it
  seems to accumulate without getting pruned.  Ultimately, I'd like to
  see this go into an issue tracking system (and by "ultimately", I
  mean "in the next six months")

* resorted the categories themselves, in order to:
  - move less important configurations down
  - move gasnet-/nolocal-related sections closer to one another

* removed the VM-based performance regressions section because we
  retired these (and took them off the main mailing lists even before
  that)

* brought the darwin section much more up-to-date now that testing
  should be stable

* significant updates to the cray-prgenv-cray section and cygwin
  sections that were further behind reality than most

* a pass over all major sections comparing what was listed to what
  is currently failing