Changes

Summary

1. The last commit should've been marked as non-BFB since it corrected a crashing bug - so comparing output to no output caused the output to be considered different. This was missed because the BFB checking tests didn't fail, and that was because the commit that caused the crashing was marked non-BFB, so an unusual combo. In general though any commit that fixes crashing behavior should be labelled as bit changing. RESOLVED:73dc365c77ab4bf2405d753f167307ae9be330a0 (details)

The last commit should've been marked as non-BFB since it corrected a crashing bug - so comparing output to no output caused the output to be considered different. This was missed because the BFB checking tests didn't fail, and that was because the commit that caused the crashing was marked non-BFB, so an unusual combo. In general though any commit that fixes crashing behavior should be labelled as bit changing. RESOLVED:73dc365c77ab4bf2405d753f167307ae9be330a0