<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:52:24 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-19895] resmoke failures should self-document</title>
                <link>https://jira.mongodb.org/browse/SERVER-19895</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;When resmoke fails, it should print out steps to help the user debug the failure. E.g. when resmoke detects that it&apos;s run in Evergreen, it should print out the places that the user should look for symptoms.&lt;/p&gt;

&lt;p&gt;Original description:&lt;br/&gt;
At shutdown time, a fixture (Replication or Sharding) checks the return status of all the process shutdown procedures.  If any of them have returned &apos;false&apos; (which means that the process returned a non-0 exit status), it fails the test suite associated with that fixture.&lt;br/&gt;
It would be helpful if the fixture wrote a message to the log stating which process caused the suite failure.  Currently, the only way to diagnose this is to scour the logs looking for the exit status of each process; since we are looking for a line that is &lt;b&gt;not&lt;/b&gt; &quot;exited with code 0.&quot;, this is not a simple search to undertake.&lt;/p&gt;</description>
                <environment></environment>
        <key id="225296">SERVER-19895</key>
            <summary>resmoke failures should self-document</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="9">Done</resolution>
                                        <assignee username="carl.worley@mongodb.com">Raiden Worley</assignee>
                                    <reporter username="milkie@mongodb.com">Eric Milkie</reporter>
                        <labels>
                            <label>tig-qwin-eligible</label>
                            <label>tig-resmoke</label>
                    </labels>
                <created>Wed, 12 Aug 2015 17:58:44 +0000</created>
                <updated>Tue, 10 May 2022 22:44:05 +0000</updated>
                            <resolved>Fri, 22 Nov 2019 20:19:12 +0000</resolved>
                                                                    <component>Testing Infrastructure</component>
                                        <votes>0</votes>
                                    <watches>7</watches>
                                                                                                                <comments>
                            <comment id="2562642" author="xgen-internal-githook" created="Fri, 22 Nov 2019 20:16:47 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{&apos;name&apos;: &apos;Carl Worley&apos;, &apos;email&apos;: &apos;carl.worley@mongodb.com&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-19895&quot; title=&quot;resmoke failures should self-document&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-19895&quot;&gt;&lt;del&gt;SERVER-19895&lt;/del&gt;&lt;/a&gt; resmoke failures should self-document&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo/commit/6c803a670431185485786b1ac84df08cd50bca25&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo/commit/6c803a670431185485786b1ac84df08cd50bca25&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2562348" author="carl.worley" created="Fri, 22 Nov 2019 18:09:32 +0000"  >&lt;p&gt;CR: &lt;a href=&quot;https://mongodbcr.appspot.com/513670005/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mongodbcr.appspot.com/513670005/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2418248" author="robert.guo" created="Thu, 12 Sep 2019 16:56:55 +0000"  >&lt;p&gt;Excellent!&lt;/p&gt;

&lt;p&gt;I updated the ticket to say that resmoke&apos;s error handling and reporting mechanism should gather and display debugging instructions in addition to the sometimes obscure error messages.&lt;/p&gt;</comment>
                            <comment id="2418224" author="milkie" created="Thu, 12 Sep 2019 16:41:20 +0000"  >&lt;blockquote&gt;&lt;p&gt;Maybe the confusion is that when there are multiple red boxes, it isn&apos;t clear that one should look for teardown/setup failures first, then hook failures, then test failures? The teardown/setup failure box should replace the need to look for &quot;error&quot; in the task logs.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Yes, exactly!  Perhaps all we need to do is document this better &amp;#8211; this is all I need to keep in mind to help me diagnose these in the future.&lt;/p&gt;</comment>
                            <comment id="2418152" author="robert.guo" created="Thu, 12 Sep 2019 15:55:47 +0000"  >&lt;blockquote&gt;&lt;p&gt;I end up looking at a combination of all the &quot;failed&quot; test logs&lt;/p&gt;&lt;/blockquote&gt;



&lt;p&gt;The original request in this ticket was to make it easier to detect if a process exited abnormally. The solution was to add an item (&lt;tt&gt;jobx_fixture_teardown&lt;/tt&gt;) to the sidebar that will turn red if a fixture crashed. This extra red box is meant to replace searching for &quot;not &apos;exited with code 0&apos;&quot;, which I believe it does now with a much more explicit error message: &quot;An error occurred during the teardown...&quot;&lt;/p&gt;

&lt;p&gt;Maybe the confusion is that when there are multiple red boxes, it isn&apos;t clear that one should look for teardown/setup failures first, then hook failures, then test failures? The teardown/setup failure box should replace the need to look for &quot;error&quot; in the task logs.&lt;/p&gt;

&lt;p&gt;Happy to chat more if the above comment doesn&apos;t help.&lt;/p&gt;</comment>
                            <comment id="2416304" author="milkie" created="Wed, 11 Sep 2019 13:19:25 +0000"  >&lt;p&gt;But that isn&apos;t true, actually.  After clicking on the links for the red boxes, I must then try to figure out what went wrong.  The way that Evergreen divides up logs into tests is subtle, so I end up looking at a combination of all the &quot;failed&quot; test logs, and the task log, to try to figure out what the actual problem is.  This involves trying to parse the task log, and then I end up at the point where my suggestion starts.&lt;/p&gt;

&lt;p&gt;As an example, take the failure that Vlad linked above.  There are three &quot;tests&quot; that are flagged as failed, but only one of them truly shows you logs that identify the problem.&lt;/p&gt;</comment>
                            <comment id="2415385" author="robert.guo" created="Tue, 10 Sep 2019 22:04:46 +0000"  >&lt;p&gt;Thanks for the suggestion Eric. The roundabout but utilitarian answer to both of your questions is that you don&apos;t have to worry about any of it now. All failures/errors/whatevers are expressed as red boxes in the Evergreen sidebar. The thing to remember now is just to click on the link(s) for the red box(es).&lt;/p&gt;

&lt;p&gt;There are some historic reasons for the error/failure mishmash and printing the report summary 3 times. I will convert this ticket to address it.&lt;/p&gt;</comment>
                            <comment id="2414579" author="milkie" created="Tue, 10 Sep 2019 15:12:16 +0000"  >&lt;p&gt;Cool, thanks.  I think we should convert this ticket to a little cleanup in the task output for failures such as this one.&lt;br/&gt;
My issues:&lt;br/&gt;
1. The failure output is printed 3 times - is that really necessary?&lt;br/&gt;
2. The failure output says this (this is one of the three copies of this output):&lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; [2019/09/09 15:35:01.221] 524 test(s) ran in 963.35 seconds (521 succeeded, 67 were skipped, 2 failed, 1 errored)&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; [2019/09/09 15:35:01.221]     fsm_workload_tests: 524 test(s) ran in 963.31 seconds (521 succeeded, 67 were skipped, 2 failed, 1 errored)&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; [2019/09/09 15:35:01.221]         The following tests failed (with exit code):&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; [2019/09/09 15:35:01.221]             create_database:CheckReplDBHashInBackground (1 DB Exception)&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; [2019/09/09 15:35:01.221]             jstests/concurrency/fsm_workloads/create_database.js (2 UNKNOWN)&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; [2019/09/09 15:35:01.221]         The following tests had errors:&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; [2019/09/09 15:35:01.221]             job0_fixture_teardown&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;
&lt;p&gt;Can we make it so that no one has to remember what the difference between an &quot;errored&quot; test and a &quot;failed&quot; test is? (Is the difference that &quot;failed&quot; tests returned a bad status from running a program?  If that&apos;s true, how can &quot;1 DB Exception&quot; be an exit code from such a test?)  Even more confusingly, the output for job0_fixture_teardown in the task log literally says &lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; [2019/09/09 15:35:01.216] [executor:fsm_workload_test:job0] 2019-09-09T15:35:01.216+0000 job0_fixture_teardown ran in 1.52 seconds: failed.&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt; [2019/09/09 15:35:01.217] [executor:fsm_workload_test:job0] 2019-09-09T15:35:01.216+0000 The teardown of ReplicaSetFixture (Job #0) failed.&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;
&lt;p&gt;So did it fail or did it error?  Ideally, we&apos;d remove this distinction to reduce confusion.&lt;br/&gt;
I think keeping the reason for failure/error in the test logs is fine and we don&apos;t need to elevate that out into the task logs, as long as there are always test logs to look at.  Are there ever cases where the task log will say a test failed or errored and there are no corresponding test logs to look at?&lt;/p&gt;</comment>
                            <comment id="2414544" author="vlad.rachev" created="Tue, 10 Sep 2019 14:58:29 +0000"  >&lt;p&gt;Yes here&apos;s one:&#160;&lt;a href=&quot;https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_concurrency_replication_02dbec04bad4a6b138a204a29644a0524e5c3123_19_09_09_14_32_15&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_concurrency_replication_02dbec04bad4a6b138a204a29644a0524e5c3123_19_09_09_14_32_15&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In the test logs:&lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;[fsm_workload_test:job0_fixture_teardown] 2019-09-09T15:35:01.213+0000 An error occurred during the teardown of ReplicaSetFixture (Job #0): Error while stopping replica set member on port 20002: mongod on port 20002 was expected to be running, but wasn&apos;t. Process exited with code 14. - Error while stopping replica set member on port 20001: mongod on port 20001 was expected to be running, but wasn&apos;t. Process exited with code 14.&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;</comment>
                            <comment id="2414375" author="milkie" created="Tue, 10 Sep 2019 13:43:24 +0000"  >&lt;p&gt;We waited too long since Max posted his example back in January, so the log data has been purged from logkeeper.  Do you have a more recent example of this?&lt;/p&gt;</comment>
                            <comment id="2413457" author="vlad.rachev" created="Mon, 9 Sep 2019 19:58:21 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=milkie&quot; class=&quot;user-hover&quot; rel=&quot;milkie&quot;&gt;milkie&lt;/a&gt; A detailed log message is written to the &quot;test logs&quot;. That seems sufficient enough to me - would you also like that same log message to be written to the &quot;task logs&quot;, as &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; suggested? If not I will close the ticket.&lt;/p&gt;</comment>
                            <comment id="2124775" author="max.hirschhorn@10gen.com" created="Wed, 23 Jan 2019 21:30:53 +0000"  >&lt;p&gt;I believe the goal of this ticket should be to make the &lt;/p&gt;

&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;[2019/01/23 20:01:11.595] [executor:js_test:job6] 2019-01-23T20:01:11.595+0000 The teardown of ReplicaSetFixture (Job #6) failed.&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;

&lt;p&gt;log message that written to the &quot;task logs&quot; include the same level of detail as the&lt;/p&gt;

&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;[js_test:job6_fixture_teardown] 2019-01-23T20:01:11.594+0000 An error occurred during the teardown of ReplicaSetFixture (Job #6): Error while stopping replica set member on port 21501: mongod on port 21501 was expected to be running, but wasn&apos;t. Process exited with code -11.&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;

&lt;p&gt;log message that&apos;s written to the &quot;test logs&quot;.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_debug_replica_sets_terminate_primary_jscore_passthrough_ffb19c17927a5a0a07a7cd7cd7744cea80ab3e26_19_01_23_19_38_08&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_debug_replica_sets_terminate_primary_jscore_passthrough_ffb19c17927a5a0a07a7cd7cd7744cea80ab3e26_19_01_23_19_38_08&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1126500" author="mpobrien" created="Tue, 5 Jan 2016 17:03:33 +0000"  >&lt;p&gt;Writing causes of failure to stderr might also help when being run in evergreen, since log lines from stderr show up red so they are easily noticed.&lt;/p&gt;</comment>
                            <comment id="1126497" author="mpobrien" created="Tue, 5 Jan 2016 17:02:21 +0000"  >&lt;p&gt;Would also like to make job teardown messages stand out more when they fail, for example instead of:&lt;/p&gt;

&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;[executor:js_test] 2016-01-04T23:51:30.774+0000 Teardown of MasterSlaveFixture (Job #8) was not successful.&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;

&lt;p&gt;something like:&lt;/p&gt;

&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;[executor:js_test] 2016-01-04T23:51:30.774+0000 Teardown of MasterSlaveFixture (Job #8) FAILED.&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;


</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>14.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>Tue, 5 Jan 2016 17:02:21 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        4 years, 11 weeks, 5 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_17050" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Downstream Team Attention</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="16941"><![CDATA[Not Needed]]></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>steven.vannelli@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            4 years, 11 weeks, 5 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>milkie@mongodb.com</customfieldvalue>
            <customfieldvalue>xgen-internal-githook</customfieldvalue>
            <customfieldvalue>max.hirschhorn@mongodb.com</customfieldvalue>
            <customfieldvalue>mikeo@mongodb.com</customfieldvalue>
            <customfieldvalue>carl.worley@mongodb.com</customfieldvalue>
            <customfieldvalue>robert.guo@mongodb.com</customfieldvalue>
            <customfieldvalue>vlad.rachev@mongodb.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrkxrb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hvl8lj:</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="804">TIG E (01/08/16)</customfieldvalue>
    <customfieldvalue id="3390">STM 2019-11-14</customfieldvalue>
    <customfieldvalue id="3391">STM 2019-11-28</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10555" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2.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_11861" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>User Summary</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="11856"><![CDATA[Not Needed]]></customfieldvalue>

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

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