Open tcmitchell opened 2 years ago
The build jobs succeeded when rerun so it remains a mystery how VERBOSE was set to True
to trigger the exception in this issue. There were other exceptions relating to online services that were not available, so that might have triggered it.
If the online services (validator, SynBioHub) are down regularly for overnight builds we might want to change the build schedule to a different time. We could work with the owners of those services to understand what their maintenance schedule is to understand what time windows should be avoided.
Several unit tests failed with the following stack trace during the overnight builds. Why these unit tests went down this path is still a mystery. But they did, which means if a user sets VERBOSE to
True
they would see the same exception.Either change these debug prints to handle the booleans, or remove them. And if they're going to get updated, consider changing them to logging statements instead of
print
s.