Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
I'm not really sure if this is a problem. I don't think GLOG should be enabled if using Python anyways. However, I have it turned on for my local builds since I use it sometimes for instrumentation. Recently, when running python tests I get the following failure from test_memory.py
def check_env_var(name, expected, *, expect_warning=False): code = f"""if 1: import pyarrow as pa pool = pa.default_memory_pool() assert pool.backend_name in {expected!r}, pool.backend_name """ env = dict(os.environ) env['ARROW_DEFAULT_MEMORY_POOL'] = name res = subprocess.run([sys.executable, "-c", code], env=env, universal_newlines=True, stderr=subprocess.PIPE) if res.returncode != 0: print(res.stderr, file=sys.stderr) res.check_returncode() # fail errlines = res.stderr.splitlines() if expect_warning: > assert len(errlines) == 1 E assert 2 == 1 E + where 2 = len(['WARNING: Logging before InitGoogleLogging() is written to STDERR', "W0408 01:23:43.401316 18454 memory_pool.cc:128] Unsupported backend 'nonexistent' specified in ARROW_DEFAULT_MEMORY_POOL (supported backends are 'jemalloc', 'system')"])