<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:13:28 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-7968] build on master taking too long, causing huge backlogs</title>
                <link>https://jira.whamcloud.com/browse/LU-7968</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;It sure looks like as of recently all builds are taking &amp;gt; 90 minutes.  I think this is due to all builds repeating server kernel builds even if they don&apos;t need to.&lt;/p&gt;

&lt;p&gt;When no kernel builds get reused, no review build is fast.  Backlogs grow quickly and empty out slowly.&lt;/p&gt;

&lt;p&gt;wondering if some recent change in master has stopped reuse of server kernel builds causing all builds to rebuild kernels and take too long.  need TEI to look at recent builds.  I&apos;m suspicious of recent landing for &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7699&quot; title=&quot;Overhaul lustre&amp;#39;s versioning&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7699&quot;&gt;&lt;del&gt;LU-7699&lt;/del&gt;&lt;/a&gt;.  worried that changes in version and rpm names prevent build from recognizing perfectly good reusable kernel builds.&lt;/p&gt;

&lt;p&gt;I know for sure backlogs have been very large lately and it&apos;s still happening.  My idea about the underlying cause is just a theory.  Need somebody in TEI who is in a position to know or find out to investigate.&lt;/p&gt;</description>
                <environment></environment>
        <key id="35635">LU-7968</key>
            <summary>build on master taking too long, causing huge backlogs</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="1" iconUrl="https://jira.whamcloud.com/images/icons/priorities/blocker.svg">Blocker</priority>
                        <status id="5" iconUrl="https://jira.whamcloud.com/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="1">Fixed</resolution>
                                        <assignee username="dmiter">Dmitry Eremin</assignee>
                                    <reporter username="bogl">Bob Glossman</reporter>
                        <labels>
                    </labels>
                <created>Mon, 28 Mar 2016 17:01:42 +0000</created>
                <updated>Wed, 1 Jun 2016 15:14:52 +0000</updated>
                            <resolved>Thu, 31 Mar 2016 19:45:46 +0000</resolved>
                                                    <fixVersion>Lustre 2.9.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                            <comments>
                            <comment id="147385" author="mdiep" created="Wed, 30 Mar 2016 22:50:43 +0000"  >&lt;p&gt;I agree with Bob that &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7699&quot; title=&quot;Overhaul lustre&amp;#39;s versioning&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7699&quot;&gt;&lt;del&gt;LU-7699&lt;/del&gt;&lt;/a&gt; remove BUILDID in lbuild might cause the caching of reusable kernel to be different everytime. Hence it rebuild kernel every time. if this is true, this will be a lustre issue, not TEI.&lt;/p&gt;</comment>
                            <comment id="147433" author="bogl" created="Thu, 31 Mar 2016 13:55:23 +0000"  >&lt;p&gt;Minh: if it is a lustre issue the breakage and the fix seems likely to be in lbuild or other build infrastructure, not in lustre code itself.  Not sure who is a proper expert to deal with such a breakage.&lt;/p&gt;</comment>
                            <comment id="147459" author="gerrit" created="Thu, 31 Mar 2016 16:16:44 +0000"  >&lt;p&gt;Dmitry Eremin (dmitry.eremin@intel.com) uploaded a new patch: &lt;a href=&quot;http://review.whamcloud.com/19262&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/19262&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7968&quot; title=&quot;build on master taking too long, causing huge backlogs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7968&quot;&gt;&lt;del&gt;LU-7968&lt;/del&gt;&lt;/a&gt; lbuild: Fix reuse signature calculation&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: 1&lt;br/&gt;
Commit: c2de7e4557841ff1045cccacafd21546f5419318&lt;/p&gt;</comment>
                            <comment id="147488" author="gerrit" created="Thu, 31 Mar 2016 19:44:25 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/19262/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/19262/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7968&quot; title=&quot;build on master taking too long, causing huge backlogs&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7968&quot;&gt;&lt;del&gt;LU-7968&lt;/del&gt;&lt;/a&gt; lbuild: Fix reuse signature calculation&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 0def2d51d9665cd83422210ae1359d62bed38521&lt;/p&gt;</comment>
                            <comment id="147489" author="dmiter" created="Thu, 31 Mar 2016 19:45:46 +0000"  >&lt;p&gt;patch landed to master.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hzy5v3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>