Workaround for issue 4047: in some configurations of
the Crash Reporter on OSX test_subprocess will trigger the reporter. This patch prints a warning when the Crash Reporter will get triggered intentionally, which should avoid confusing people.
This commit is contained in:
parent
e8d252dbcb
commit
102d11a6d6
|
@ -559,6 +559,21 @@ class _SuppressCoreFiles(object):
|
|||
except (ImportError, ValueError, resource.error):
|
||||
pass
|
||||
|
||||
if sys.platform == 'darwin':
|
||||
# Check if the 'Crash Reporter' on OSX was configured
|
||||
# in 'Developer' mode and warn that it will get triggered
|
||||
# when it is.
|
||||
#
|
||||
# This assumes that this context manager is used in tests
|
||||
# that might trigger the next manager.
|
||||
value = subprocess.Popen(['/usr/bin/defaults', 'read',
|
||||
'com.apple.CrashReporter', 'DialogType'],
|
||||
stdout=subprocess.PIPE).communicate()[0]
|
||||
if value.strip() == b'developer':
|
||||
print("this tests triggers the Crash Reporter, "
|
||||
"that is intentional", end='')
|
||||
sys.stdout.flush()
|
||||
|
||||
def __exit__(self, *args):
|
||||
"""Return core file behavior to default."""
|
||||
if self.old_limit is None:
|
||||
|
|
Loading…
Reference in New Issue