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

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>5051</bug_id>
          
          <creation_ts>2013-08-27 02:15:50 +0000</creation_ts>
          <short_desc>ERROR: Can NOT get PRAUTO, exception timed out</short_desc>
          <delta_ts>2013-10-17 14:46:36 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>BitBake</product>
          <component>bitbake</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>High</priority>
          <bug_severity>critical</bug_severity>
          <target_milestone>1.5 M5</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Jonathan Liu">net147</reporter>
          <assigned_to name="Richard Purdie">richard.purdie</assigned_to>
          <cc>corneliux.stoicescu</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>35934</commentid>
    <comment_count>0</comment_count>
    <who name="Jonathan Liu">net147</who>
    <bug_when>2013-08-27 02:15:50 +0000</bug_when>
    <thetext>After updating poky to &quot;master:4517cdbfafdc7c5fa16bb5d09ed70c8e0da6a8c8&quot;, when building an image after a while I get:
ERROR: Can NOT get PRAUTO, exception timed out
ERROR: Function failed: package_get_auto_pr

It has happened three times so far. I am using the following relevant options in my local.conf:
BB_NUMBER_THREADS = &quot;8&quot;
PARALLEL_MAKE = &quot;-j 8&quot;
PRSERV_HOST = &quot;localhost:0&quot;

Target machine is i586 Linux.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35935</commentid>
    <comment_count>1</comment_count>
    <who name="Jonathan Liu">net147</who>
    <bug_when>2013-08-27 02:25:55 +0000</bug_when>
    <thetext>The time of each run before it gave the error:
23m53.394s
2m41.952s
18m43.564s

I run bitbake with time nice -n19. I suspect it may be due to http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=bfab986ccd59636d0b0e79309f020e55481b0567.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35941</commentid>
    <comment_count>2</comment_count>
    <who name="Jonathan Liu">net147</who>
    <bug_when>2013-08-27 05:06:53 +0000</bug_when>
    <thetext>The errors disappears if I revert bfab986ccd59636d0b0e79309f020e55481b0567.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35963</commentid>
    <comment_count>3</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-08-27 23:56:04 +0000</bug_when>
    <thetext>If you swap timeout=5 to timeout=30 in that commit are things any better?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>35970</commentid>
    <comment_count>4</comment_count>
    <who name="Jonathan Liu">net147</who>
    <bug_when>2013-08-28 02:48:43 +0000</bug_when>
    <thetext>It would probably help but I have already built everything without the patch. I need a reliable method to reproduce it first.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>36011</commentid>
    <comment_count>5</comment_count>
    <who name="Jonathan Liu">net147</who>
    <bug_when>2013-08-28 22:48:27 +0000</bug_when>
    <thetext>Having timeout of 30 seems to fix it for me.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>36040</commentid>
    <comment_count>6</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-08-29 13:41:47 +0000</bug_when>
    <thetext>The performance of the PR service is drastically improved as of http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=d5e860be4c12a9d6655665af391ffd6f9351f8eb so can you see if you still have issues after this change?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>36041</commentid>
    <comment_count>7</comment_count>
    <who name="Jonathan Liu">net147</who>
    <bug_when>2013-08-29 13:48:55 +0000</bug_when>
    <thetext>I still have same error after http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=d5e860be4c12a9d6655665af391ffd6f9351f8eb with timeout of 5.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>36060</commentid>
    <comment_count>8</comment_count>
    <who name="Jonathan Liu">net147</who>
    <bug_when>2013-08-29 22:52:39 +0000</bug_when>
    <thetext>(In reply to comment #6)
&gt; The performance of the PR service is drastically improved as of
&gt; http://git.yoctoproject.org/cgit.cgi/poky/commit/
&gt; ?id=d5e860be4c12a9d6655665af391ffd6f9351f8eb so can you see if you still
&gt; have issues after this change?

It seems to be even worse now. After d5e860be4c12a9d6655665af391ffd6f9351f8eb using timeout of 30 fails with the following error (and more frequently):
ERROR: Can NOT get PRAUTO from remote PR service
ERROR: Function failed: package_get_auto_pr

build/cache/prserve.log contains:
ERROR: database table is locked: PRMAIN_nohist
NOTE: PRServer: stopping...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>36108</commentid>
    <comment_count>9</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-08-30 16:54:48 +0000</bug_when>
    <thetext>I&apos;ve pushed a change making the retry match for &quot;table is locked&quot; which it didn&apos;t previously. I&apos;ve also increased the timeout to 60s since its causing people problems. If you could see if these two patches combined, I&apos;d appreciate it, thanks!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>36130</commentid>
    <comment_count>10</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-09-01 08:04:10 +0000</bug_when>
    <thetext>I found further problem and went into this more deeply. There is now a series of patches on the bitbake mailing list which should improve the performance of the PR Server once and for all and resolve this problem, even with a 5s timeout.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>36131</commentid>
    <comment_count>11</comment_count>
    <who name="Jonathan Liu">net147</who>
    <bug_when>2013-09-01 08:51:25 +0000</bug_when>
    <thetext>It works after applying the two patches for 30 second timeout and SQLite retry fix.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>36344</commentid>
    <comment_count>12</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-09-05 15:11:56 +0000</bug_when>
    <thetext>I think the various bitbake changes to improve the PR server responsiveness have resolved this, ending with commit http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=c7b342903208cfb4cefaa0ec339c6ddfcd590acc</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>38014</commentid>
    <comment_count>13</comment_count>
    <who name="Stoicescu Cornel">corneliux.stoicescu</who>
    <bug_when>2013-10-17 14:46:36 +0000</bug_when>
    <thetext>Tested with &quot;timeout = 5&quot; and there ware no issues.

Tested on poky dora/master:faf8f8660fae26a14578738b642fdeb08bcb9d54</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>