<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 02:50:03 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-12146] remove &quot;skip_env&quot; for FSTYPE=zfs</title>
                <link>https://jira.whamcloud.com/browse/LU-12146</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;Tests should not use &lt;tt&gt;skip_env&lt;/tt&gt; if they are skipped because &lt;tt&gt;FSTYPE != &quot;ldiskfs&quot;&lt;/tt&gt;.  &lt;/p&gt;

&lt;p&gt;Such tests would always be skipped when the filesystem type is ZFS, and this is not an indication of a deficient test environment.  The &lt;tt&gt;skip_env()&lt;/tt&gt; check is meant for detecting test environments that are lacking things like test programs (e.g. &lt;tt&gt;dbench&lt;/tt&gt; or &lt;tt&gt;IOR&lt;/tt&gt;) or are configured incorrectly (e.g. MDT or OST is too small, or not enough of them for basic tests).  The intent is that &lt;tt&gt;skip_env()&lt;/tt&gt; allows such tests to be skipped during developer testing, where the test environment may not have everything configured, but it should be considered an &lt;tt&gt;error()&lt;/tt&gt; if the autotest environment does not have everything installed properly in order to execute the test case.&lt;/p&gt;

&lt;p&gt;The regular &quot;&lt;tt&gt;skip&lt;/tt&gt;&quot; check is intended to skip tests when the configuration is unsuitable for the current test for whatever reason, so we don&apos;t need to mark such cases with &quot;&lt;tt&gt;skip_env&lt;/tt&gt;&quot;. &lt;/p&gt;

&lt;p&gt;It looks like several such checks are in the current tests:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;sanity.sh test 17m (ldiskfs), 17n, 24E, 51e, 57a, 57b, 60a, 77a (GSS), 77b, 77c, 77d, 77f, 77g, 77k, 100, 101a, 103a, 129, 130a (ZFS), 130b, 130c, 130d, 130e, 228a, 228b, 228c, 233a, 233b, 252, 315, 399b, 804,&lt;/li&gt;
&lt;/ul&gt;
</description>
                <environment></environment>
        <key id="55326">LU-12146</key>
            <summary>remove &quot;skip_env&quot; for FSTYPE=zfs</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="adilger">Andreas Dilger</reporter>
                        <labels>
                            <label>test_script_improvements</label>
                            <label>tests</label>
                    </labels>
                <created>Tue, 2 Apr 2019 03:34:04 +0000</created>
                <updated>Mon, 29 Jul 2019 08:27:40 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                            <comments>
                            <comment id="252165" author="adilger" created="Mon, 29 Jul 2019 08:27:40 +0000"  >&lt;p&gt;There are a bunch of other places that &lt;tt&gt;skip_env&lt;/tt&gt; is incorrectly used, in particular for &lt;tt&gt;$MDSCOUNT&lt;/tt&gt; and other places that are just variations in the test configs, and not shortcomings in the Lustre autotest environment.  I &lt;em&gt;guess&lt;/em&gt; we could force all tests to run with multiple MDTs, but I don&apos;t think that is the case today.&lt;/p&gt;

&lt;p&gt;It would be interesting to at least try one test run with &lt;tt&gt;$FAIL_ON_SKIP_ENV=true&lt;/tt&gt; and see what fails.  Ideally once these patches are run and any resulting failures are fixed, then we could enable this by default in the future?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="50057">LU-10461</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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|i00ecn:</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>