Debugging Averted
Jun. 5th, 2025 06:33 pmBefore going into a marathon debugging session to try to find yesterday's problem, I figured that I would do some more code inspection first. I took a look at serialization for the involved classes just to make sure that there wasn't anything weird there. There wasn't.
Ok, let's try this. This branch works. That branch doesn't. Our source code is in Git. Let's get the complete list of all of the files that have differences between the two branches. It's a longish list, but it just requires a lot of clicking, swearing, and the use of some of my favorite not-available-on-Linux software, Tortoise Git.
And eventually, the problem was found in the most likely spot, which was the routine that was failing. In order to get the unit tests to run correctly, I had commented out what appeared to be an unnecessary line of code. Unfortunately, the unit tests ran much better without that line of code, but the actual software would object strenuously to its absence when a model conversion was needed. This is sort of the classic case of winning the battle and losing the war.
I have restored the commented-out line of code and life is now much better.
I will figure out how to fix the unit tests in a better way at a later date. :)
Ok, let's try this. This branch works. That branch doesn't. Our source code is in Git. Let's get the complete list of all of the files that have differences between the two branches. It's a longish list, but it just requires a lot of clicking, swearing, and the use of some of my favorite not-available-on-Linux software, Tortoise Git.
And eventually, the problem was found in the most likely spot, which was the routine that was failing. In order to get the unit tests to run correctly, I had commented out what appeared to be an unnecessary line of code. Unfortunately, the unit tests ran much better without that line of code, but the actual software would object strenuously to its absence when a model conversion was needed. This is sort of the classic case of winning the battle and losing the war.
I have restored the commented-out line of code and life is now much better.
I will figure out how to fix the unit tests in a better way at a later date. :)