ion-test-driver workflow will fail whenever lines are added/removed from a file that produces expected errors.

[tgregg]

This happens because the failure message includes the line number from which the error originated. Example here. This requires developers to manually look through the test-driver results and determine that they are false positives, introducing the risk of an incorrect evaluation that results in a behavioral change being allowed through. We should consider whether the best solution is to build ion-c in release mode (instead of debug mode) in ion-test-driver, or to change the evaluation logic in ion-test-driver, or something else.