We have some tests that started failing when I upgraded to v2.14 this week.
It looks passing a null object to Debug.Write now throws a NullReferenceException whereas it didn't before (confirmed with v2.13).
I'm not sure if this is expected or not. Is it a bug with v2.14 or is Debug.Write expected to throw with a null object, and therefore our code needs updated?
Build/Test Issues
tests failing with v2.14 (Debug.Write throws)
Started by larsendaniel on 2,573 views
Remco NCrunch Developer
#7189
07 Apr 2015 21:49 UTC
Hi, thanks for posting!
There were no deliberate changes in v2.14 to make this throw an exception on null being written using Debug.Write, though looking at the code I think it may be possible that this is a regression in v2.14. I've noted it down to be fixed in the next release.
I recommend adjusting your code to avoid the null writes for the time being. Thanks for making me aware of this.
Cheers,
Remco
There were no deliberate changes in v2.14 to make this throw an exception on null being written using Debug.Write, though looking at the code I think it may be possible that this is a regression in v2.14. I've noted it down to be fixed in the next release.
I recommend adjusting your code to avoid the null writes for the time being. Thanks for making me aware of this.
Cheers,
Remco
Post a reply
Log in to reply.