During testing processes clang.exe*32 occupy all CPU time and block execution

[llvmbot]

Bugzilla Link	10808
Resolution	WORKSFORME
Resolved on	Sep 09, 2011 13:22
Version	unspecified
OS	Windows NT
Reporter	LLVM Bugzilla Contributor

Extended Description

Native mingw32 two-stage clang build has issues with both llvm and clang tests performed on second stage.
Seems four processes clang.exe*32 occupy all CPU time and block execution.

Description of the build:
Native two-stage clang build, both stage use equal clang configuration:
--prefix=private_install_dir
--build=i686-pc-mingw32 --host=i686-pc-mingw32
--target=i686-pc-mingw32 --disable-bindings
--without-llvmgcc --without-llvmgxx
--enable-optimized --enable-assertions

Build machine information:
Windows 7 Professional x64(English) Service Pack1
Intel Xeon CPU W3530 @ 2.80 GHz, 12GB of RAM

g++.exe (GCC) 4.5.2
GNU Binutils 2.21.53.20110804
This is perl, v5.8.8 built for msys-64int
Python 2.6.6
cmake version 2.8.4

clang revisions that was tested:
138687
138579
138443
138298

[llvmbot]

Native mingw32 two-stage clang build has issues with both llvm and clang tests
performed on second stage.
Seems four processes clang.exe*32 occupy all CPU time and block execution.

Then, what is clang.exe doing? Compiling llvm and clang on stage2, or testing clang/test?

If you met hanging up in clang tests, please try to kill individual clang.exe from taskmgr.exe, and report list of killed tests.

clang revisions that was tested:
138687
138579
138443
138298

Are they all suspicious?
Would you like to try bisecting?

FYI, That was in April when I tried multistage clang build on msys mingw. (Then it was succeeded)

[llvmbot]

Then, what is clang.exe doing? Compiling llvm and clang on stage2, or testing
clang/test?

It's testing. clang tests and llvm tests both have this issue.

From buildbot point of view looks like the nexts testing have something simular/the same and execution of tests blocked:
http://bb.pgr.jp/builders/clang-i686-msys/builds/461/steps/test_clang/logs/stdio

Are they all suspicious?
These are revisions that I tested and they all had this issue.

[llvmbot]

Then, what is clang.exe doing? Compiling llvm and clang on stage2, or testing
clang/test?

It's testing. clang tests and llvm tests both have this issue.

I don't understand. IIRC, llvm tests don't use clang. (except llvm/test/LLVMC on stage2)

From buildbot point of view looks like the nexts testing have something
simular/the same and execution of tests blocked:
http://bb.pgr.jp/builders/clang-i686-msys/builds/461/steps/test_clang/logs/stdio

FYI, for me, 4 tests hang.

http://bb.pgr.jp/builders/clang-i686-msys/builds/464
I have confirmed it to terminate suspious clang.exe (s) from taskmgr.
Failing Tests (4):
Clang :: Modules/diamond.c
Clang :: Modules/load_failure.c
Clang :: Modules/lookup.cpp
Clang :: Modules/lookup.m

Please make sure to try with disabling (eliminating temporarily) 4 tests above.

Are they all suspicious?
These are revisions that I tested and they all had this issue.

I have got the issue since r138679. investigating.

[llvmbot]

My bot has been fixed by r138852.

BTW, did you try "make clean"?

[llvmbot]

The issue seems fixed.
I built two-stage clang for revision 139270 and tests on both two stages completed (but not all tests PASS).
I tried both two-stage Release+Asserts and Debug+Asserts, no tests hang anymore.

[llvmbot]

I have not reproduced your issue.

Please reconfirm dependency issue, if you are using msys-make.
Sometimes msys-make tends not to understand mingw32-gcc-generated dependencies (*.d).

Feel free to reopen or file issues on msys-mingw. I will go on checking on msys-mingw.

[llvmbot]

I use msys-mingw.