T5975a.run.stdout 2>T5975a.run.stderr Actual stderr output differs from expected: --- /dev/null 2014-02-05 03:11:58.000000000 +0000 +++ ./ghci/scripts/T5975a.run.stderr 2014-02-05 03:11:58.103200000 +0000 @@ -0,0 +1,2 @@

#8737: T5975a fails when using official Windows Python distribution --------------------------+------------------------------------------------ Reporter: ezyang | Owner: Type: bug | Status: new Priority: low | Milestone: Component: Test | Version: 7.8.1-rc1 Suite | Operating System: Windows Keywords: | Type of failure: Incorrect result at runtime Architecture: | Test Case: T5975a Unknown/Multiple | Blocking: Difficulty: | Unknown | Blocked By: | Related Tickets: | --------------------------+------------------------------------------------ Using the official MSYS2 instructions: {{{ =====> T5975a(ghci) 988 of 3859 [0, 0, 0] cd ./ghci/scripts && touch föøbàr1.hs cd ./ghci/scripts && HC='C:/msys64/home/Administrator/ghc/inplace/bin/ghc- stage2.exe' HC_OPTS='-dcore-lint -dcmm-lint -dno-debug-output -no-user- package-db -rtsopts -fno-ghci-history ' 'C:/msys64/home/Administrator/ghc/inplace/bin/ghc-stage2.exe' --interactive -v0 -ignore-dot-ghci -dcore-lint -dcmm-lint -dno-debug- output -no-user-package-db -rtsopts -fno-ghci-history <T5975a.script + +<no location info>: can't find file: föøbàr1.hs *** unexpected failure for T5975a(ghci) }}} When we disable the cleanup hook and look at the directory listing, we see that Python has created the following file: "föøbàr1.hs". I think this is some sort of encoding problem, since we see similar behavior when running a simple Python script: {{{ #coding=utf-8 open('föøbàr1.hs', 'w').write("") }}} Maybe this bug shows up in MSYS as well, but I haven't checked. -- Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8737> GHC <http://www.haskell.org/ghc/> The Glasgow Haskell Compiler