You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have recently been working with a version of Condor that was custom compiled on Gentoo. Due to some differences between Gentoo and Debian, most executables put out the following message to standard error:
/usr/bin/../lib/libcrypto.so.1.0.0: no version information available (required by /lib64/libcondor_utils_8_4_9.so)
In this particular case, this amounts to a warning and condor still works fine. However this causes an issue with condorpy because error catching statements like the one found here:
This causes condorpy to raise an error anytime something is written to standard error. However, the case cited above and a few other cases indicate that Condor will often write warnings to standard error, making this approach to aggressive. I suggest only raising errors on specific errors, rather than doing a catch all on the standard error (though I would still recommend logging anything that comes through standard error).
The text was updated successfully, but these errors were encountered:
I have recently been working with a version of Condor that was custom compiled on Gentoo. Due to some differences between Gentoo and Debian, most executables put out the following message to standard error:
/usr/bin/../lib/libcrypto.so.1.0.0: no version information available (required by /lib64/libcondor_utils_8_4_9.so)
In this particular case, this amounts to a warning and condor still works fine. However this causes an issue with condorpy because error catching statements like the one found here:
https://github.com/tethysplatform/condorpy/blob/master/condorpy/htcondor_object_base.py#L130
This causes condorpy to raise an error anytime something is written to standard error. However, the case cited above and a few other cases indicate that Condor will often write warnings to standard error, making this approach to aggressive. I suggest only raising errors on specific errors, rather than doing a catch all on the standard error (though I would still recommend logging anything that comes through standard error).
The text was updated successfully, but these errors were encountered: