<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:18:13 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>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[CDRIVER-3497] Environment setup failure in debian-package-build and rpm-package-build should be a system failure</title>
                <link>https://jira.mongodb.org/browse/CDRIVER-3497</link>
                <project id="10030" key="CDRIVER">C Driver</project>
                    <description>&lt;p&gt;If the debian-package-build/rpm-package-build tasks fail to create a chroot, that should show up as a system failure (purple) instead of a task failure (red) so it is easier to determine whether the task was broken by code changes or environment changes.&lt;/p&gt;

&lt;p&gt;The &lt;a href=&quot;https://github.com/evergreen-ci/evergreen/wiki/Project-Files#command-failure-colors&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;evergreen docs&lt;/a&gt; suggest this could be done by creating a file on failure to create a chroot environment, and having a subsequent &quot;system&quot; task check if that file exists.&lt;/p&gt;</description>
                <environment></environment>
        <key id="1104483">CDRIVER-3497</key>
            <summary>Environment setup failure in debian-package-build and rpm-package-build should be a system failure</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.mongodb.org/images/icons/priorities/minor.svg">Minor - P4</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="2">Won&apos;t Fix</resolution>
                                        <assignee username="kevin.albertson@mongodb.com">Kevin Albertson</assignee>
                                    <reporter username="kevin.albertson@mongodb.com">Kevin Albertson</reporter>
                        <labels>
                    </labels>
                <created>Sun, 19 Jan 2020 20:42:49 +0000</created>
                <updated>Tue, 28 Jan 2020 19:17:46 +0000</updated>
                            <resolved>Tue, 28 Jan 2020 19:17:46 +0000</resolved>
                                                                    <component>tests</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="2768948" author="kevin.albertson" created="Tue, 28 Jan 2020 19:17:46 +0000"  >&lt;p&gt;Since transient failures that don&apos;t require changes are rare, let&apos;s keep this as a test failure. If transient failures do become more of a concern, we could add retries within the task.&lt;/p&gt;</comment>
                            <comment id="2748084" author="roberto.sanchez" created="Tue, 21 Jan 2020 19:41:15 +0000"  >&lt;p&gt;I have had similar thoughts in the past, but I am concerned that this may mask legitimate failures.  For instance, the &lt;tt&gt;debian-package-build&lt;/tt&gt; task includes a call to &lt;tt&gt;debootstrap&lt;/tt&gt;, which prepares the build environment.  That step might fail if a package is uninstallable (this may happen as a transitory condition during a library migration or the chroot creation attempt is made after the package index is updated but before the mirror server has fully synchronized), in which case it should be considered a system failure.  On the other hand, the chroot creation step might also fail if a package we are requesting be installed in the chroot is unavailable (e.g., because the package name has changed or has been dropped from Debian).  That seems like it should be considered a proper failure; although it is not a result of a code change that was made, it requires a change to the Evergreen build helper scripts to address the failure.&lt;/p&gt;

&lt;p&gt;It is not clear how to reliably distinguish between the two conditions, as it requires grokking the output of the &lt;tt&gt;debootstrap&lt;/tt&gt; command.&lt;/p&gt;

&lt;p&gt;Similar issues are involved with the &lt;tt&gt;rpm-package-build&lt;/tt&gt; task.&lt;/p&gt;

&lt;p&gt;That seems to leave two possibilities:&lt;/p&gt;
&lt;ol&gt;
	&lt;li&gt;Leave things as they currently are and deal with occasional false positive failures of the &lt;tt&gt;rpm-package-build&lt;/tt&gt; and &lt;tt&gt;debian-package-build&lt;/tt&gt; Evergreen tasks&lt;/li&gt;
	&lt;li&gt;Make the suggested change and understand that we will be introducing the possibility of occasional false negatives, which may result in persistent brokenness of the tasks (unless we make it a point to investigate the system failures of those tasks)&lt;/li&gt;
&lt;/ol&gt;
</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hw7hrj:</customfieldvalue>

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