<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>53220</bug_id>
          
          <creation_ts>2011-01-26 19:49:06 -0800</creation_ts>
          <short_desc>back-during-onload-hung-page.php causes Chromium WebKit bot to fail</short_desc>
          <delta_ts>2011-01-27 11:54:31 -0800</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>Tools / Tests</component>
          <version>528+ (Nightly build)</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows 7</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>0</everconfirmed>
          <reporter name="Charles Reis">creis</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>eric</cc>
    
    <cc>mihaip</cc>
    
    <cc>ojan</cc>
    
    <cc>rniwa</cc>
    
    <cc>tony</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>340701</commentid>
    <comment_count>0</comment_count>
    <who name="Charles Reis">creis</who>
    <bug_when>2011-01-26 19:49:06 -0800</bug_when>
    <thetext>One of the Chromium WebKit bots is frequently failing because the PHP process for back-during-onload-hung-page.php doesn&apos;t exit for over 600 seconds.  The tests that rely on this file are passing, but they just need it not to respond during the test.  They would still pass if we reduced the timeout from 1000 seconds to something more reasonable, like 60.

URL to the bot:
http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Win%20(deps)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>340702</commentid>
    <comment_count>1</comment_count>
      <attachid>80290</attachid>
    <who name="Charles Reis">creis</who>
    <bug_when>2011-01-26 19:51:24 -0800</bug_when>
    <thetext>Created attachment 80290
Patch</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>340722</commentid>
    <comment_count>2</comment_count>
    <who name="Eric Seidel (no email)">eric</who>
    <bug_when>2011-01-26 22:33:53 -0800</bug_when>
    <thetext>I take it we don&apos;t have code in run-webkit-tests/new-run-webkit-tests to kill run-away http servers (or in this case php processes?)  Should we?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>340904</commentid>
    <comment_count>3</comment_count>
    <who name="Charles Reis">creis</who>
    <bug_when>2011-01-27 09:57:59 -0800</bug_when>
    <thetext>(In reply to comment #2)
&gt; I take it we don&apos;t have code in run-webkit-tests/new-run-webkit-tests to kill run-away http servers (or in this case php processes?)  Should we?

I don&apos;t know much about those scripts, but they appear to try to kill the process but fail in this case.  Here&apos;s one of the error messages from the bot, which looks like it tried and failed to kill the PHP process (according to Nicolas, who found out which process it was after the fact):

command timed out: 600 seconds without output, killing pid 19192
SIGKILL failed to kill process
using fake rc=-1
program finished with exit code -1

remoteFailed: [Failure instance: Traceback from remote host -- Traceback (most recent call last):
Failure: buildbot.slave.commands.TimeoutError: SIGKILL failed to kill process
]


(From: http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Win%20(deps)/builds/334/steps/webkit_tests/logs/stdio)

Maybe we just need a more effective approach for killing such processes?  We only see the problem on one of the bots, so it might be specific to something in the config.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>340961</commentid>
    <comment_count>4</comment_count>
      <attachid>80290</attachid>
    <who name="Ryosuke Niwa">rniwa</who>
    <bug_when>2011-01-27 11:12:02 -0800</bug_when>
    <thetext>Comment on attachment 80290
Patch

Clearing flags on attachment: 80290

Committed r76816: &lt;http://trac.webkit.org/changeset/76816&gt;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>340962</commentid>
    <comment_count>5</comment_count>
    <who name="Ryosuke Niwa">rniwa</who>
    <bug_when>2011-01-27 11:12:07 -0800</bug_when>
    <thetext>All reviewed patches have been landed.  Closing bug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>340978</commentid>
    <comment_count>6</comment_count>
    <who name="Tony Chang">tony</who>
    <bug_when>2011-01-27 11:54:31 -0800</bug_when>
    <thetext>(In reply to comment #3)
&gt; (In reply to comment #2)
&gt; &gt; I take it we don&apos;t have code in run-webkit-tests/new-run-webkit-tests to kill run-away http servers (or in this case php processes?)  Should we?
&gt; 
&gt; I don&apos;t know much about those scripts, but they appear to try to kill the process but fail in this case.  Here&apos;s one of the error messages from the bot, which looks like it tried and failed to kill the PHP process (according to Nicolas, who found out which process it was after the fact):
&gt; 
&gt; command timed out: 600 seconds without output, killing pid 19192
&gt; SIGKILL failed to kill process
&gt; using fake rc=-1
&gt; program finished with exit code -1

Maybe I misunderstand, but it looks like the buildbot process is trying to kill the NRWT process.  Maybe it&apos;s failing to kill the NRWT because it&apos;s holding on to the lighttpd process which holds on to the php process?  I bet it wouldn&apos;t be too hard to add a &quot;kill all php.exe processes&quot; when stopping the httpd, but it might cause collateral damage.

I bet apache handles this better.  Another reason to try and switch to apache (although I&apos;m not volunteering).

Nice detective work!</thetext>
  </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>80290</attachid>
            <date>2011-01-26 19:51:24 -0800</date>
            <delta_ts>2011-01-27 11:12:02 -0800</delta_ts>
            <desc>Patch</desc>
            <filename>bug-53220-20110126195123.patch</filename>
            <type>text/plain</type>
            <size>1223</size>
            <attacher name="Charles Reis">creis</attacher>
            
              <data encoding="base64">SW5kZXg6IExheW91dFRlc3RzL0NoYW5nZUxvZwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09Ci0tLSBMYXlvdXRUZXN0cy9D
aGFuZ2VMb2cJKHJldmlzaW9uIDc2NjQwKQorKysgTGF5b3V0VGVzdHMvQ2hhbmdlTG9nCSh3b3Jr
aW5nIGNvcHkpCkBAIC0xLDMgKzEsMTUgQEAKKzIwMTEtMDEtMjYgIENoYXJsaWUgUmVpcyAgPGNy
ZWlzQGNocm9taXVtLm9yZz4KKworICAgICAgICBSZXZpZXdlZCBieSBOT0JPRFkgKE9PUFMhKS4K
KworICAgICAgICBiYWNrLWR1cmluZy1vbmxvYWQtaHVuZy1wYWdlLnBocCBjYXVzZXMgQ2hyb21p
dW0gV2ViS2l0IGJvdCB0byBmYWlsCisgICAgICAgIGh0dHBzOi8vYnVncy53ZWJraXQub3JnL3No
b3dfYnVnLmNnaT9pZD01MzIyMAorCisgICAgICAgIFJlZHVjZXMgdGhlIHRpbWVvdXQgb24gYSBz
Y3JpcHQgdGhhdCBzaG91bGRuJ3QgZmluaXNoIGR1cmluZyBhIHRlc3QuCisgICAgICAgIFRoaXMg
YXZvaWRzIHByb2JsZW1zIGluIG9uZSBvZiB0aGUgQ2hyb21pdW0gV2ViS2l0IGJ1aWxkZXJzLgor
CisgICAgICAgICogaHR0cC90ZXN0cy9oaXN0b3J5L3Jlc291cmNlcy9iYWNrLWR1cmluZy1vbmxv
YWQtaHVuZy1wYWdlLnBocDogUmVkdWNlIHRpbWVvdXQuCisKIDIwMTEtMDEtMjUgIEplciBOb2Js
ZSAgPGplci5ub2JsZUBhcHBsZS5jb20+CiAKICAgICAgICAgVW5yZXZpZXdlZCBidWlsZCBmaXg6
IGFkZCBmYWlsaW5nIHRlc3QgdG8gZ3RrL1NraXBwZWQuCkluZGV4OiBMYXlvdXRUZXN0cy9odHRw
L3Rlc3RzL2hpc3RvcnkvcmVzb3VyY2VzL2JhY2stZHVyaW5nLW9ubG9hZC1odW5nLXBhZ2UucGhw
Cj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT0KLS0tIExheW91dFRlc3RzL2h0dHAvdGVzdHMvaGlzdG9yeS9yZXNvdXJjZXMv
YmFjay1kdXJpbmctb25sb2FkLWh1bmctcGFnZS5waHAJKHJldmlzaW9uIDc2NjQwKQorKysgTGF5
b3V0VGVzdHMvaHR0cC90ZXN0cy9oaXN0b3J5L3Jlc291cmNlcy9iYWNrLWR1cmluZy1vbmxvYWQt
aHVuZy1wYWdlLnBocAkod29ya2luZyBjb3B5KQpAQCAtMSwyICsxLDIgQEAKLTw/IHNsZWVwKDEw
MDApOyA/PgorPD8gc2xlZXAoNjApOyA/PgogRkFJTDogU2hvdWxkIG5ldmVyIHNlZSB0aGlzClwg
Tm8gbmV3bGluZSBhdCBlbmQgb2YgZmlsZQo=
</data>

          </attachment>
      

    </bug>

</bugzilla>