Apparently the problem is that testTEST is not initialized. If testTEST is initialized, this problem doesn't happen. However, I don't understand why that's allowed to happen. The better behavior would be for nothing to happen, or for a runtime error to occur instead of just silently doing completely the wrong thing.