<?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>16508</bug_id>
          
          <creation_ts>2026-11-15 01:04:09 +0000</creation_ts>
          <short_desc>RRS: one hung commit stalls rrs_upgrade_history.py indefinitely; add a per-commit timeout</short_desc>
          <delta_ts>2026-11-15 01:54:42 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Recipe Reporting System (RRS)</product>
          <component>Recipe Reporting System (RRS)</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>IN PROGRESS REVIEW</bug_status>
          <resolution></resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>6.2 M2</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Tim Orling">tim.orling</reporter>
          <assigned_to name="Tim Orling">tim.orling</assigned_to>
          
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Don&apos;t know</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>107466</commentid>
    <comment_count>0</comment_count>
    <who name="Tim Orling">tim.orling</who>
    <bug_when>2026-11-15 01:04:09 +0000</bug_when>
    <thetext>rrs_upgrade_history.py analyses each commit by running
upgrade_history_internal.py through utils.run_command_interruptible(),
which waits for it with no time limit. When a commit makes the parse hang,
the whole run stalls and keeps the layer index update lock until someone
kills it. Bugs 16500 and 16504 were found this way: on a test instance,
the run sat idle on one OE-Core commit for over 7 hours.

The nightly RRS job on the test instance (rrs-update.service) has no
timeout either. A timeout around the whole run (timeout(1) or systemd)
doesn&apos;t help much: it stops the run instead of skipping the bad commit,
and in the hang the stuck process was the BitBake server started by
upgrade_history_internal.py, which a plain kill of the child leaves
behind.

Proposed fix: an optional timeout in run_command_interruptible() that
kills the command&apos;s whole process group and raises
subprocess.TimeoutExpired, and a --commit-timeout option to
rrs_upgrade_history.py (default 1 hour). With it, a commit that times out
is logged as an error and skipped.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>107467</commentid>
    <comment_count>1</comment_count>
    <who name="Tim Orling">tim.orling</who>
    <bug_when>2026-11-15 01:21:09 +0000</bug_when>
    <thetext>Patch sent to yocto-patches, under review (applies on top of the RRS series for bugs 16499-16506):
https://lore.kernel.org/all/20261115011321.58851-2-tim.orling@konsulko.com/</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>107469</commentid>
    <comment_count>2</comment_count>
    <who name="Tim Orling">tim.orling</who>
    <bug_when>2026-11-15 01:54:42 +0000</bug_when>
    <thetext>v2 sent (fixes a race in the new test; v1 is superseded):
https://lore.kernel.org/all/20261115015200.64142-2-tim.orling@konsulko.com/</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>