On Windows, 'env' or 'printenv' may not exist.
Also switch back to 'env' which is specified by POSIX.1-2017. 'printenv' is not
standard (I picked it because 'printenv' exists on GnuWin32 but 'env' does not).
Differential D86496
[not][test] Fix disable-symbolization.test when 'printenv' is not available MaskRay on Aug 24 2020, 4:59 PM. Authored by
Details On Windows, 'env' or 'printenv' may not exist. Also switch back to 'env' which is specified by POSIX.1-2017. 'printenv' is not
Diff Detail
Event TimelineComment Actions This breaks check-llvm on windows: http://45.33.8.238/win/22625/step_11.txt Please take a look and revert for now if it takes a while to fix. Comment Actions It worked in a GnuWin32 environment previously but a Chromium (which did not install full GnuWin32) bot was unhappy. So I created this patch. Glad that Alexandre will handle it. Thanks! Comment Actions @thakis Do you think you can add printenv.exe into https://commondatastorage.googleapis.com/chromium-browser-clang/tools/gnuwin-XX.zip so we can enable the test again on Windows? Please see https://reviews.llvm.org/D86170#inline-799301 Comment Actions We have env as a lit builtin. Can we just use that? What's the not --crash supposed to do here? Why would env crash anyway? I miss context on what this test wants to do. Comment Actions I was under the false impression yesterday that the local env.exe (found in GnuWin32) wouldn't print the environment block, but it does. It seems the problem lies in how the commands are interpreted by lit. On Windows, with this test, we reach this: https://github.com/llvm/llvm-project/blob/master/llvm/utils/lit/lit/TestRunner.py#L645 - but on not Linux? |