<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 04:19: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>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>[SERVER-28940] Make resmoke fixture setup/teardown their own testcases.</title>
                <link>https://jira.mongodb.org/browse/SERVER-28940</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;The fixture setup and teardown logs only go to logkeeper, but don&apos;t show up on the Evergreen sidebar�. So the assertions can&apos;t be extracted without figuring out the logkeeper URL from the task log.&lt;/p&gt;

&lt;p&gt;Since everything else that logs to logkeeper (i.e. test and hooks) is a testcase that shows up on the sidebar, the fixture events should get their own spots as well.&lt;/p&gt;</description>
                <environment></environment>
        <key id="376920">SERVER-28940</key>
            <summary>Make resmoke fixture setup/teardown their own testcases.</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</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="13201">Fixed</resolution>
                                        <assignee username="yves.duhem">Yves Duhem</assignee>
                                    <reporter username="robert.guo@mongodb.com">Robert Guo</reporter>
                        <labels>
                            <label>tig-qwin-eligible</label>
                            <label>tig-resmoke</label>
                    </labels>
                <created>Mon, 24 Apr 2017 15:21:25 +0000</created>
                <updated>Mon, 30 Oct 2023 23:17:15 +0000</updated>
                            <resolved>Thu, 4 Oct 2018 13:52:24 +0000</resolved>
                                    <version>3.5.6</version>
                                    <fixVersion>4.1.4</fixVersion>
                                    <component>Testing Infrastructure</component>
                                        <votes>1</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="2023489" author="xgen-internal-githook" created="Thu, 4 Oct 2018 13:51:24 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Yves Duhem&apos;, &apos;email&apos;: &apos;yves.duhem@mongodb.com&apos;, &apos;username&apos;: &apos;syev&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-28940&quot; title=&quot;Make resmoke fixture setup/teardown their own testcases.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-28940&quot;&gt;&lt;del&gt;SERVER-28940&lt;/del&gt;&lt;/a&gt; Test cases for fixture setups and teardowns&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/1e026f75dc41cca4c7293e42b5b49cb9e46d0ea3&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/1e026f75dc41cca4c7293e42b5b49cb9e46d0ea3&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2007348" author="max.hirschhorn@10gen.com" created="Wed, 19 Sep 2018 01:40:34 +0000"  >&lt;p&gt;I&apos;ve looked back at EVG-1135 and some of the Slack conversations I&apos;ve had where &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-28940&quot; title=&quot;Make resmoke fixture setup/teardown their own testcases.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-28940&quot;&gt;&lt;del&gt;SERVER-28940&lt;/del&gt;&lt;/a&gt; has explicitly come up. I&apos;m amending my earlier answer and will say that I don&apos;t think writing a log message to the task logs (even if it links to the /all logs) is a worthwhile experience for Server engineers, as it isn&apos;t much different than how the job logs urls are written to task logs by resmoke. already. The problem this ticket is aiming to resolve with MongoDB startup failures is how Server engineers aren&apos;t well-trained in when they should look at the task logs; the ideal experience is to have something for Server engineers to click on in the &quot;Test Results&quot; pane. Addressing that pain point for Server engineers should make the Build Baron tool more useful for &quot;free&quot;.&lt;/p&gt;</comment>
                            <comment id="2006562" author="robert.guo" created="Tue, 18 Sep 2018 15:23:49 +0000"  >&lt;p&gt;I had a brief offline discussion with Yves last week. My preference is to add links to the job log to the task logs and make the necessary changes to the build baron tool to parse the job logs. As we add more background hooks, there will be an increasing number of failures that show up outside of the test log of the failing test. Fixture crash stacktraces also sometimes show up earlier than when the crashes are picked up by resmoke&apos;s &lt;tt&gt;is_running()&lt;/tt&gt; check. These problems can probably be alleviated if logkeeper adds support for parallel tests, but having the BB tool handle job logs and larger logs in general seems like something we&apos;ll still want in the long run.&lt;/p&gt;</comment>
                            <comment id="2006461" author="yves.duhem" created="Tue, 18 Sep 2018 14:26:40 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=max.hirschhorn&quot; class=&quot;user-hover&quot; rel=&quot;max.hirschhorn&quot;&gt;max.hirschhorn&lt;/a&gt;, I agree that having a test for the fixture startup is a straightforward way to get these failures analyzed by the Build Baron tool.&lt;/p&gt;

&lt;p&gt;It would be more work but it is also possible to modify the Build Baron tool to extract the job URLs from the task log and perform the analysis.&lt;/p&gt;</comment>
                            <comment id="2006439" author="max.hirschhorn@10gen.com" created="Tue, 18 Sep 2018 14:15:51 +0000"  >&lt;blockquote&gt;
&lt;p&gt;It will not be as visible as having a link in the test results but having a test case for the fixture setup and teardown does not really fit in the way the resmoke code is organized and as we are doing more and more analysis on our Evergreen test results I&apos;d prefer to avoid using Evergreen tests for steps that are not strictly speaking tests.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=yves.duhem&quot; class=&quot;user-hover&quot; rel=&quot;yves.duhem&quot;&gt;yves.duhem&lt;/a&gt;, my issue with that approach is there still wouldn&apos;t be a way for the Build Baron tool to analyze the logs associated with a startup failure.&lt;/p&gt;</comment>
                            <comment id="2006424" author="yves.duhem" created="Tue, 18 Sep 2018 14:09:58 +0000"  >&lt;p&gt;The end goal being to make the job logs more easily accessible when an error occurs during a fixture setup or teardown, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=robert.guo&quot; class=&quot;user-hover&quot; rel=&quot;robert.guo&quot;&gt;robert.guo&lt;/a&gt;, &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=max.hirschhorn&quot; class=&quot;user-hover&quot; rel=&quot;max.hirschhorn&quot;&gt;max.hirschhorn&lt;/a&gt;, what do you think about adding a log line with the URL to the logs when that occurs?&lt;/p&gt;

&lt;p&gt;It will not be as visible as having a link in the test results but having a test case for the fixture setup and teardown does not really fit in the way the resmoke code is organized and as we are doing more and more analysis on our Evergreen test results I&apos;d prefer to avoid using Evergreen tests for steps that are not strictly speaking tests.&lt;/p&gt;</comment>
                            <comment id="1624017" author="robert.guo" created="Mon, 17 Jul 2017 19:37:47 +0000"  >&lt;p&gt;Based on discussion with &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=yves.duhem&quot; class=&quot;user-hover&quot; rel=&quot;yves.duhem&quot;&gt;yves.duhem&lt;/a&gt; in the code review, the logs from the fixtures won&apos;t show up in the fixture startup/teardown testcase, so this ticket is being put on hold for now.&lt;/p&gt;</comment>
                            <comment id="1556738" author="robert.guo" created="Mon, 24 Apr 2017 20:48:52 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=max.hirschhorn&quot; class=&quot;user-hover&quot; rel=&quot;max.hirschhorn&quot;&gt;max.hirschhorn&lt;/a&gt; I was thinking of the teardown phase at the end of a suite, which happens after the last testcase/hook.&lt;/p&gt;</comment>
                            <comment id="1556704" author="max.hirschhorn@10gen.com" created="Mon, 24 Apr 2017 20:31:01 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=robert.guo&quot; class=&quot;user-hover&quot; rel=&quot;robert.guo&quot;&gt;robert.guo&lt;/a&gt;, given that &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-26522&quot; title=&quot;CleanEveryN output should be written to logkeeper&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-26522&quot;&gt;&lt;del&gt;SERVER-26522&lt;/del&gt;&lt;/a&gt; made the &lt;tt&gt;CleanEveryN&lt;/tt&gt; hook into its own test case, is this really only for the initial setup of the fixtures?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="736568">SERVER-40592</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="871916">SERVER-42356</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="883471">SERVER-42622</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="is related to">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18555" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname># of Sprints</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>3.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10038"><![CDATA[Fully Compatible]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Mon, 24 Apr 2017 20:31:01 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        5 years, 18 weeks, 6 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10857" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>PM-1225</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>luke.bonanomi@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            5 years, 18 weeks, 6 days ago
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_16465" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Linked BF Score</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0.0</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>max.hirschhorn@mongodb.com</customfieldvalue>
            <customfieldvalue>robert.guo@mongodb.com</customfieldvalue>
            <customfieldvalue>yves.duhem</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|ht6apb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|htxepj:</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>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10557" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="1746">TIG 2017-07-10</customfieldvalue>
    <customfieldvalue id="2473">TIG 2018-09-24</customfieldvalue>
    <customfieldvalue id="2564">DAG 2018-10-08</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10555" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hs4a3b:</customfieldvalue>

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