Adjust an assert check in other.test_emcc to be more relaxed on the generated LLVM output. On Windows, the text outputted by LLVM varied somewhat, so testing for string containment instead works better.

1 files changed, 1 insertions, 1 deletions

diff --git a/tests/runner.py b/tests/runner.py
index 3efb55b3..778da174 100755
--- a/tests/runner.py
+++ b/tests/runner.py
@@ -7251,7 +7251,7 @@ Options that are modified or new in %s include:
         self.assertContained('error: invalid preprocessing directive', output[1])
         self.assertContained("error: use of undeclared identifier 'cheez", output[1])
         self.assertContained('2 errors generated', output[1])
-        assert output[1].split('2 errors generated.')[1].replace('\r', '').replace('\n', '') == 'emcc: compiler frontend failed to generate LLVM bitcode, halting'
+        assert 'emcc: compiler frontend failed to generate LLVM bitcode, halting' in output[1].split('2 errors generated.')[1]
 
         # emcc src.cpp -c    and   emcc src.cpp -o src.[o|bc] ==> should give a .bc file
         #      regression check: -o js should create "js", with bitcode content