<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:14:12 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-8052] test-framework change breaks test</title>
                <link>https://jira.whamcloud.com/browse/LU-8052</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;The commit 7151367afdb04562f016c3002f0c614004552ad6 very recently landed to master for &quot;&lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7130&quot; title=&quot;sanity.sh test 162 does not properly handle some DIR values&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7130&quot;&gt;&lt;del&gt;LU-7130&lt;/del&gt;&lt;/a&gt; test: sanity/162 doesn&apos;t handle DIR values properly&quot; breaks test in some distros.&lt;/p&gt;

&lt;p&gt;In particular it adds some uses of &apos;sed -E&apos; to the test-framework.sh&lt;br/&gt;
On sles11sp4 (and maybe other distros too) &apos;-E&apos; isn&apos;t a valid option for sed.  Trying to use it causes fatal errors.  example:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;sed: invalid option -- &apos;E&apos;
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...

  -n, --quiet, --silent
                 suppress automatic printing of pattern space
  -e script, --expression=script
                 add the script to the commands to be executed
  -f script-file, --file=script-file
                 add the contents of script-file to the commands to be executed
  --follow-symlinks
                 follow symlinks when processing in place
  -i[SUFFIX], --in-place[=SUFFIX]
                 edit files in place (makes backup if extension supplied)
  -l N, --line-length=N
                 specify the desired line-wrap length for the `l&apos; command
  --posix
                 disable all GNU extensions.
  -r, --regexp-extended
                 use extended regular expressions in the script.
  -s, --separate
                 consider files as separate rather than as a single continuous
                 long stream.
  -u, --unbuffered
                 load minimal amounts of data from the input files and flush
                 the output buffers more often
      --help     display this help and exit
      --version  output version information and exit

If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret.  All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.

E-mail bug reports to: bonzini@gnu.org .
Be sure to include the word ``sed&apos;&apos; somewhere in the ``Subject:&apos;&apos; field.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
</description>
                <environment></environment>
        <key id="36302">LU-8052</key>
            <summary>test-framework change breaks test</summary>
                <type id="1" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11303&amp;avatarType=issuetype">Bug</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="bogl">Bob Glossman</assignee>
                                    <reporter username="bogl">Bob Glossman</reporter>
                        <labels>
                    </labels>
                <created>Thu, 21 Apr 2016 16:43:30 +0000</created>
                <updated>Wed, 27 Apr 2016 15:33:30 +0000</updated>
                            <resolved>Wed, 27 Apr 2016 15:33:30 +0000</resolved>
                                                    <fixVersion>Lustre 2.9.0</fixVersion>
                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                            <comments>
                            <comment id="149699" author="bogl" created="Thu, 21 Apr 2016 16:54:29 +0000"  >&lt;p&gt;option isn&apos;t known on sles11sp4 or sles11sp3.   seems to be honored everywhere else I can find. is there some reason &apos;-E&apos; is used in this case and not &apos;-e&apos; ?&lt;/p&gt;</comment>
                            <comment id="149703" author="jgmitter" created="Thu, 21 Apr 2016 17:13:24 +0000"  >&lt;p&gt;Hi Parinay,&lt;/p&gt;

&lt;p&gt;Can you please explain why -E was used?  From what I understand -E is a BSD compatible flag for -r.  Any reason why we can&apos;t use -r instead?&lt;/p&gt;

&lt;p&gt;Thanks.&lt;br/&gt;
Joe&lt;/p&gt;</comment>
                            <comment id="149705" author="jgmitter" created="Thu, 21 Apr 2016 17:14:22 +0000"  >&lt;p&gt;Hi Bob,&lt;/p&gt;

&lt;p&gt;Could you try a test patch with -r instead of -E?&lt;/p&gt;

&lt;p&gt;Thanks.&lt;br/&gt;
Joe&lt;/p&gt;</comment>
                            <comment id="149711" author="bogl" created="Thu, 21 Apr 2016 17:23:10 +0000"  >&lt;p&gt;&lt;a href=&quot;http://review.whamcloud.com/19714&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/19714&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="149777" author="bogl" created="Thu, 21 Apr 2016 22:25:23 +0000"  >&lt;p&gt;Blocker for any test runs where testing on slles11, sp3 or sp4.&lt;br/&gt;
Right now blocking test and landing of &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8023&quot; title=&quot;build problem on master due to recent change&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8023&quot;&gt;&lt;del&gt;LU-8023&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-7957&quot; title=&quot;kernel update [SLES11 SP4 3.0.101-71]&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-7957&quot;&gt;&lt;del&gt;LU-7957&lt;/del&gt;&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="149792" author="parinay" created="Fri, 22 Apr 2016 02:29:15 +0000"  >&lt;p&gt;Bob, Joseph,&lt;br/&gt;
Apologies. &lt;br/&gt;
I didn&apos;t had sles setup to test the same and I agree &apos;-r&apos; is more correct here.  Would be careful henceforth.Thanks.&lt;/p&gt;</comment>
                            <comment id="149794" author="parinay" created="Fri, 22 Apr 2016 03:08:36 +0000"  >&lt;p&gt;From the sed GNU source for version 4.2.1 ( which is present on my test VMs)&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;289 &amp;gt;       /* Undocumented, for compatibility with BSD sed.  */
290 &amp;gt;       case &apos;E&apos;:
291 &amp;gt;       case &apos;r&apos;:
292 &amp;gt;         if (extended_regexp_flags)
293 &amp;gt;           usage(4);
294 &amp;gt;         extended_regexp_flags = REG_EXTENDED;
295 &amp;gt;         break;
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;so even if &apos;E&apos; is not present in `sed --help` , it works. Should have used &apos;r&apos;. my bad.&lt;/p&gt;</comment>
                            <comment id="149796" author="jgmitter" created="Fri, 22 Apr 2016 03:22:41 +0000"  >&lt;p&gt;Thanks for following up Parinay.  Bob has a patch in flight above for the fix, so all will be well when we can get that landed.&lt;/p&gt;</comment>
                            <comment id="150362" author="gerrit" created="Wed, 27 Apr 2016 14:48:40 +0000"  >&lt;p&gt;Oleg Drokin (oleg.drokin@intel.com) merged in patch &lt;a href=&quot;http://review.whamcloud.com/19714/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://review.whamcloud.com/19714/&lt;/a&gt;&lt;br/&gt;
Subject: &lt;a href=&quot;https://jira.whamcloud.com/browse/LU-8052&quot; title=&quot;test-framework change breaks test&quot; class=&quot;issue-link&quot; data-issue-key=&quot;LU-8052&quot;&gt;&lt;del&gt;LU-8052&lt;/del&gt;&lt;/a&gt; test: stop using unknonwn sed option&lt;br/&gt;
Project: fs/lustre-release&lt;br/&gt;
Branch: master&lt;br/&gt;
Current Patch Set: &lt;br/&gt;
Commit: 04490846ef9db8622482939a6bd1daa0714ba20e&lt;/p&gt;</comment>
                            <comment id="150368" author="jgmitter" created="Wed, 27 Apr 2016 15:33:30 +0000"  >&lt;p&gt;Landed for 2.9.0&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|hzy8u7:</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>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>