<html>
    <head>
      <base href="http://llvm.org/bugs/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - Deadlock in llvm-lit on windows 7"
   href="http://llvm.org/bugs/show_bug.cgi?id=22335">22335</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Deadlock in llvm-lit on windows 7
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Test Suite
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>trunk
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>PC
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Windows NT
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>lit
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>unassignedbugs@nondot.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>sgundapa@codeaurora.org
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>daniel@zuster.org, llvmbugs@cs.uiuc.edu
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr></table>
      <p>
        <div>
        <pre>I am observing a deadlock with llvm-lit on windows 7.
When I attached a debugger, the communicate() call is blocked.

In file utils/lit/lit/TestRunner.py
<span class="quote">>    # FIXME: There is probably still deadlock potential here. Yawn.
>   procData = [None] * len(procs)
>    procData[-1] = procs[-1].communicate()</span >

I am invoking python directly on windows to run the unit tests. 
C:\Python27\python.exe C:\build\llvm\Release\bin\llvm-lit.py -v -j 12 --param
build_mode=Release --param build_config=Win32
llvm_site_config=C:\llvm_on_win\nightly\build\llvm\tools\polly\test\lit.site.cfg
test
Note: If I invoke with ā€œ-j 1ā€ , the unit tests finish but took a lot of time.
There is no deadlock. I am using python version 2.7.6.

At this moment, I believe the issue is caused by stdout filling the OS buffer
there by blocking the communicate() call.
It is possible some of the unit tests dump a lot of text/data to stdout. FYI, I
have a couple of unit tests of my own in the code base.
On Linux, there is no deadlock but on windows I am hitting a deadlock 7 out of
10 times. I tried invoking python with ā€œ-uā€ but in vain.

When I looked at llvm-lit code, I saw the code to avoid deadlocks but there was
no guarantee, like the one I pasted above.
Would appreciate if some one take a look at it and provide more context on
deadlocks.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>