diff --git "a/database/tawos/tfidf/EVG_tfidf-se.csv" "b/database/tawos/tfidf/EVG_tfidf-se.csv" new file mode 100644--- /dev/null +++ "b/database/tawos/tfidf/EVG_tfidf-se.csv" @@ -0,0 +1,2825 @@ +"issuekey","created","storypoint","context","codesnippet","t_New.Feature","t_Improvement","t_Bug","t_Task","t_Build.Failure","t_Question","t_Problem.Ticket","t_Incident","t_Sub.task","c_app","c_legacy.ui","c_perf.tools","c_platform","c_ui","c_ops" +"EVG-336","06/03/2014 22:41:30",1,"Spawnhost in AWS regions besides us-east-1 ""[~david.hows] recently spent a month in NYC as a new """"exo-dev"""" for the kernel team. He proclaimed MCI as a """"Brilliant magical tool, knowledge and access to it needs to be shared widely."""" One point he identified: +spawnhost+ functionality is incredibly helpful, *except when the host is on the other side of the world from you*. Packet latency from Sydney to us-east-1 is bad and Windows RDP is especially unusable with high latency. If we roll out spawnhost functionality more widely to support staff, Dublin will feel the same pinch, but Sydney will still feel it most. *Request*: allow spawnhost users to provision instance in a alternate Amazon EC2 region. - I think you need [AMI Copy for Amazon EC2|http://aws.amazon.com/about-aws/whats-new/2013/03/12/announcing-ami-copy-for-amazon-ec2/] -- pay for transfer and storage in the new region - Initial EC2 regions supported: -- US East (Virginia) = us-east-1 -- Asia Pacific (Sydney) = ap-southeast-2 -- MAYBE: EU West (Ireland) = eu-west-1 - Add a pull-down menu on the """"spawnhost configure"""" page to select AWS region (small set we allow) - Use MCI user timezone preferences to select an EC2 region for the user? -- or make it another preference? ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-90","03/09/2015 19:54:06",2,"get rid of global locking ""its bad design and its gettin pretty irritating to users when patches time out.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-136","05/06/2015 16:45:54",1,"hostinit should use workdir ""In provisioning and setting up a host, the hostinit process should do all it's work in the specified distro working directory.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-298","05/13/2015 21:16:12",1,"Simplify util.FileExists API ""the function definition is which accepts multiple arguments then path joins them together. However, none of our code actually makes use of this multi-arg approach. We always do a filepath.Join() on the inputs before passing them to FileExists in our code. Let's change the function to behave the way we're using it."""," func FileExists(elem ...string) (bool, error) { path := filepath.Join(elem...) _, err := os.Stat(path) if err == nil { return true, nil } if os.IsNotExist(err) { return false, nil } return false, err } ",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-68","05/14/2015 21:44:08",2,"allow terminating a host directly from UI ""if """"decommissioning"""" a host isn't good enough (the host is actually stuck in a weird state that decommissioning won't get it out of) it would be useful to have the ability to just forceably terminate it right away.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-223","06/08/2015 22:08:15",2,"Add patch alert triggers ""as an extension of the alert/notify rewrite""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-497","08/19/2015 20:02:15",2,"""Terminate host ()?"" ""When clicking the trash icon on https://evergreen.mongodb.com/ui/spawn I get a thoughtful question if I am sure if I want to terminate the instance... But it doesn't tell me which instance. The message appears to supposed to have more info {code} public/static/partials/user_host_terminate.html: Terminate [[curHostData.distro._id]] host ([[curHostData.id]])? {code} But only becomes """," public/static/partials/user_host_terminate.html: Terminate [[curHostData.distro._id]] host ([[curHostData.id]])? Terminate host ()? ",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-518","08/27/2015 16:40:48",1,"Remove InsecureSkipVerify with modified go http package ""evaluate whether or not we can take out InsecureSkipVerify with the modified http package for go 1.6 ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-631","10/09/2015 21:20:41",1,"Log an event whenever a user sets priority ""Would be nice to have the option to look this up if we ever encounter a string of abuse.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-700","11/03/2015 20:58:53",2,"Add git tags in commit, if any, to waterfall page ""Is it possible to display any tags a given commit has in the waterfall page? Now that there are no BUMP commits for releases this information will be very useful to identify releases. See attached screenshot for details. Thanks, Ramón. Cc [~geert.bosch]""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-763","12/03/2015 20:29:16",2,"evergreen configuration validator should validate commands inside of functions ""e.g. if a function definition is missing a command field, it should raise an error in the validator.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-805","01/12/2016 17:13:12",1,"Disallow decommissioning static hosts ""That status doesn't make a lot of sense for static hosts - they should either be running or quarantined on the hosts page. There also appear to be some internal process(es?) that attempt to terminate hosts in this status.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-929","03/25/2016 15:07:12",1,"spawn page should give helpful error if there are no spawnable distros ""This will only affect deployments where no distro types allow user spawning. Right now on such deployments, you can set up a public key but cannot click the """"SPAWN"""" button, with no error message to indicate why.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-939","03/31/2016 23:14:59",1,"'Error setting host RDP password' message incorrectly displays error message ""I received this error message: """"\[object Object\]"""" should be the error message instead, presumably."""," Error setting host RDP password: [object Object] ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-948","04/06/2016 01:32:18",1,"Add revision order number to expansions ""This will allow users to upload artifacts with a monotonically increasing sequence number.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-992","05/04/2016 15:51:09",1,"""json.get"" and ""s3.get"" commands should automatically create outer directory if it doesn't exist yet ""for example, in : if """"src"""" doesn't exist, we should just automatically mkdir it before trying to write stand.json into it. This avoids the need for the project maintainer to have to remember to explicitly do a """"mkdir"""" somewhere before the command runs. The workaround is to add the following before the json.get: """," - command: json.get params: task: ${compare_task} variant : ${variant1} file: """"src/stand.json"""" name: """"perf"""" - command: shell.exec params: script: | mkdir -p src ",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1016","05/17/2016 22:21:48",1,"System.out/err xUnit output not displayed ""See [this build|https://evergreen.mongodb.com/task/mongo_java_driver_ubuntu_1404_test_0078a5e9b337fd76cacf38c2185c84a67ed25a5b_16_05_16_15_31_47#/log/E] Many of the test suites should have System.out content in the test report, e.g. I don't see it displayed anywhere in the UI."""," ... ",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1041","06/06/2016 18:27:33",2,"Add audit log for user-triggered events with filtering ""Would be nice to have an audit log listing who did what at what time on Evergreen. Right now if I need to restart a task I can add a note via the Build Baron plugin saying """"I restarted this task"""", but if I need to restart all failures in a build (EVG-429) I can't easily add a note to all the restarted tasks. Ideally the audit log would have some filtering mechanism (like the waterfall view has) so one could type """"restart"""" to see all the recent task restarts. I think this would be useful information for the Build Baron to have, so the """"audit log"""" is just a proposal. If a task restart (or cancellation, or priority change) automatically added a note visible via the BB plugin I think that would meet the requirements.""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1053","06/13/2016 18:55:11",1,"repo tracker should not try to fetch info on projects that are still in the process of being configured ""Creating a new project from the admin panel inserts a record into the project refs, and the next repo tracker run tries to pull commits for that project ref even when the user has not yet finished updating it with the repo owner/name/branch etc. This results in almost always getting at least 1 alert about the project being broken as it's being set up, which is pretty annoying (and confusing).""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1066","06/22/2016 04:31:31",2,"hosts page should show idle time of each host ""It shows how long the host has been up, and (if applicable) how long the current task has been running. But, there's no way to see how long an idle host has been idle, without going to a specific host's page and inspecting its event log.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3011","07/13/2016 22:01:19",8,"Add ability to zoom out on performance trend graphs ""From multiple discussions it would be nice to be able to zoom out on the trend graphs on mongo-perf and sys-perf to see longer term trends. The data could be sampled as we zoom out. ""","",0,0,0,1,0,0,0,0,0,0,0,1,0,0,0 +"EVG-9415","07/20/2016 18:50:22",0.5,"Write build system and Evergreen configuration for greenbay ""This will borrow significantly from the amboy/curator/etc projects.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9556","07/20/2016 18:55:21",1,"Define test result type and reporting format for greenbay ""Include methods for creating, aggregating, printing, writing to a file, both in human readable format and in evergreen's report.json format.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-1245","10/06/2016 20:12:57",2,"New Project should be disabled on project page for non super-users ""Project admins cannot create their own projects. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1285","10/31/2016 18:52:35",1,"Project admins cannot view disabled projects if they have no enabled projects ""Suppose I am the project admin of two projects, foo and bar. If foo is enabled and bar is disabled, I can view both foo and bar. If, however, I am just the project admin of bar, I cannot view bar.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1286","10/31/2016 20:10:25",1,"Track how many tasks a host has run ""This would enable us to easily see if hosts ever get into the pathological state of coming up, waiting, and then shutting down without running any tasks. We could log an event when this occurs. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1288","11/01/2016 15:02:42",2,"Task execution data files only appear when viewing Latest ""When viewing a previous execution of a task the files associated to that execution are not visible. When viewing the Latest, all executions are visible (this may not make sense).""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1335","11/22/2016 19:46:56",2,"Hide decommissioned hosts on Hosts page ""Can the decommissioned hosts be hidden by default on the Hosts page? Perhaps we can have a checkbox 'Show decommissioned hosts' similar to what we do for spawned? I don't think anyone needs to see those boxes on a daily basis, I never had a case where I needed to see or do anything with the decommissioned servers, they just take additional space on the page and make sorting and filtering more difficult.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1350","12/01/2016 22:05:40",1,"Document undocumented evergreen commands ""I have seen the following commands in various Evergreen config files, but none are documented on the [Project Commands|https://github.com/evergreen-ci/evergreen/wiki/Project-Commands] wiki page: * archive.targz_pack * expansions.fetch * expansions.update * git.apply_patch * keyval.inc * manifest.load * s3.get * s3Copy.copy * shell.track * shell.cleanup Could these (and any *other* available commands) please be documented? Thanks""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1386","12/19/2016 18:19:09",2,"Set RDP Password no longer working ""I can no longer use the """"Set RDP Password"""" to set passwords on the windows spawn hosts. The form appears to have been submitted successfully but the password is never changed, I have to login to the server over ssh and reset it manually""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1404","01/05/2017 18:11:28",1,"Remove HTTP verb constants in evergreen package when GCCGO version moves beyond 1.4 ""The HTTP verb constants that go added after go1.4, e.g. http.MethodPut etc, are copied into the evergreen globals.go file so that we can use them in GCCGO version 1.4. When we upgrade past this version, the constants should be removed and references to them should be replaced. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1460","01/20/2017 21:30:05",2,"use --binary in git commands ""The next chapter in the saga of the huge patch, which began in EVG-1459. The file in question, libbson-objects.inv, is a *new* binary file that is added by the patch. https://evergreen.mongodb.com/task/mongo_c_driver_releng_make_release_archive_340e610e019f404105aae8e2c1c12f8c85fc4c72_17_01_20_21_07_54"""," [2017/01/20 16:14:49.449] error: cannot apply binary patch to 'doc/libbson-objects.inv' without full index line [2017/01/20 16:14:49.449] error: doc/libbson-objects.inv: patch does not apply [2017/01/20 16:14:49.464] Command failed: Failed to apply patch: exit status 1 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1487","01/26/2017 15:53:42",1,"build_id and task_id have a race condition for patch builds ""Recent discussions and inspection gave me the impression that expansions work roughly this way (where """"roughly"""" means I'm not trying to be specific about how reserved characters are converted to dashes or underscores or whatever): * project' – key for project in evergreen * 'revision' – SHA1 of a commit in the repo for the project * 'build_variant' – entry in the 'buildvariants' part of the config.yml * 'task_name' – task name from 'tasks' part of config.yml * 'version_id' ** For commits: roughly {{""""$\{project\}\_$\{revision\}""""}} ** For patches: a unique ID * 'build_id' – roughly {{""""$\{project\}\_$\{build_variant\}\_$\{revision\}\_$\{TIMESTAMP\}""""}} * 'task_id' – roughly {{""""$\{project\}\_$\{build_variant\}\_$\{task_name\}\_$\{revision\}\_$\{TIMESTAMP\}""""}} * 'execution' – number of times a 'task_id' has executed (starting at 0) My understanding is that TIMESTAMP is the commit timestamp for commits and the submission time for patches. From this, it appears that it is possible for two patches on the same commit submitted at the same TIMESTAMP to wind up with the same 'build_id's and 'task_id's. Without considering backwards compatibility issues, it looks like for patch builds, the 'build_id' and 'task_id' should be using the 'version_id' in place of the 'revision' field. Alternatively, if 'version_id' for patches were 'project_', then 'build_id' and 'task_id' could remove the 'project' and 'revision' expansions and just use 'version_id' instead, as it would include project information and a unique identifier: * 'build_id' – roughly {{""""$\{version_id\}\_$\{build_variant\}\_$\{TIMESTAMP\}""""}} * 'task_id' – roughly {{""""$\{version_id\}\_$\{build_variant\}\_$\{task_name\}\_$\{TIMESTAMP\}""""}} It would be even more consistent, perhaps, to put timestamp after 'version_id' since that's what it's tied to, which would give you: * 'build_id' – roughly {{""""$\{version_id\}\_$\{TIMESTAMP\}\_$\{build_variant\}""""}} * 'task_id' – roughly {{""""$\{build_id\}\_$\{task_name\}""""}} TIMESTAMP could even go first, before 'version_id', which has the added value of allowing id's to sort chronologically (e.g. listing contents of an S3 bucket): * 'build_id' – roughly {{""""$\{TIMESTAMP\}\_$\{version_id\}\_$\{build_variant\}""""}} * 'task_id' – roughly {{""""$\{build_id\}\_$\{task_name\}""""}} Following that logic, you could add a new expansion: * 'expansion_id' – roughly {{""""$\{task_id\}\_$\{expansion\}""""}} Then all the unique identifier expansions would build logically and consistently on each other. That would simplify the job of users choosing an expansion for naming artifacts to S3: * Need something to reuse across tasks for a build: use just 'build_id' * Need some task output for external consumption (e.g. a release tarball): use just 'task_id' * Need to save debugging output from a particular task run: use just 'execution_id'""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1488","01/26/2017 16:45:32",1,"Add timestamp expansion ""If Evergreen provides a default expansion for the timestamp used to construct build_id, etc., then users can construct better build/task and ultimately S3 artifact identifiers than are currently provided by Evergreen itself. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1503","02/09/2017 16:45:30",1,"Document 'command_type' ""It's not mentioned on the wiki.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1520","02/22/2017 19:23:48",0,"Allow projects to specify required builders for patch builds ""It would be nice if project managers could specify in a file what builders are required when sending patch builds, so the {{evergreen}} cli could read those defaults when users don't specify them. We'd have to decide what to do when users have specified default builders in their {{.evergreen.yml}} file; probably printing a warning and honoring user's settings would be enough.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1523","02/22/2017 23:00:49",2,"handle test result test files that are too long to index ""we need an index on this field, so we should either truncate these files or figure out some other way to handle this. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1533","03/01/2017 16:37:11",2,"previously executed tasks may not be included in test history retrieval ""The [current implementation | https://github.com/evergreen-ci/evergreen/blob/master/model/task_history.go#L415] of merging old and current tasks may exclude ones if they are sorted in different ways. We should include tests with both tasks and archived tasks that cover both the normal archiving a task case, and one where the two may have different sets of test results. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1540","03/07/2017 15:50:50",2,"adjust time zones on test-history command to support user's local timezones ""We currently support inputting only UTC, which what is stored in the DB. We should come up with a good way to support users' timezones. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1560","03/10/2017 21:27:48",2,"Endpoint to report on build success rate and elapsed time within a project/variant ""For Cloud tests on Evergreen, we'd like to create custom reports that track the pass/fail rate of all tasks on a build variant and the time taken for each. As such, we'd like a REST endpoint that only requires {project} and {variant}, can take an optional {maxResults} and {sortBy}, that returns information on the last {maxResults} of builds. We need task-level detail but not test-level. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1576","03/19/2017 21:06:59",2,"s3 operations should be more robust to networking issues ""either by more retry logic if system failures continue, or preferably by pushing tasks to doing s3 operations with their own code (or curator.) ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1614","04/05/2017 19:16:11",2,"dist-race tarball execs should have the same file names as standard build ""this will make it easy to drop in or deploy race-detector enabled binaries, which isn't currently possible given that the file names aren't the same as the standard builds. However, not being able to tell based on file name if an artifact has the race detector by looking at it might make builds less hygienic or easy to produce. we could also just put symlinks in the tarball, which may or may not work more long term. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1628","04/14/2017 19:46:50",1,"get rid of global lock for task cleanup on timed out heartbeats ""The global lock is used for cleaning up hosts and tasks. This will probably require some use of atomic updates. Currently we cleanup timed out tasks and reset them. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1640","04/25/2017 01:44:08",1,"get rid of global lock for host cleanup ""this may require having atomic updates on the host status ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1650","05/01/2017 23:10:34",1,"Fix (MISSING) in runner logs ""There are a lot of (MISSING) appearing in the runner logs. Some examples: """,":~$ grep """"(MISSING)"""" /var/log/evergreen/evg_runner.log | wc 4733 182977 2870167 [evg-runner] 2017/05/01 21:59:52 [p=info]: Remote command executing: '""""-p 22 -i xxxx.pem -o StrictHostKeyChecking=no -o BatchMode=yes -o ConnectTimeout=10 -o ProxyCommand=ssh -o StrictHostKeyChecking=no -i /xxxxxx.pem -q xxxx@xxxx nc %!h(MISSING) %!p(MISSING) xxx@xxxxx echo hi""""' [evg-runner] 2017/05/01 21:47:07 [p=info]: Setup complete for host %!s(MISSING) sir-5sqg4x5k [evg-runner] 2017/05/01 21:54:50 [p=info]: Directories command: '&command.RemoteCommand{Id:""""agent_mkdir-6437555143072532165"""", CmdString:""""mkdir -m 777 -p /xxxxx"""", Stdout:(*util.CappedWriter)(0xc422b0b150), Stderr:(*util.CappedWriter)(0xc422b0b150), RemoteHostName:""""xxxxx"""", User:""""xxxx"""", Options:[]string{""""-p"""", """"22"""", """"-i"""", """"xxxx.pem"""", """"-o"""", """"StrictHostKeyChecking=no"""", """"-o"""", """"BatchMode=yes"""", """"-o"""", """"ConnectTimeout=10"""", """"-o"""", """"ProxyCommand=ssh -o StrictHostKeyChecking=no -i xxxx.pem -q xxxx@xxxxx nc %!h(MISSING) %!p(MISSING)""""}, Background:false, LoggingDisabled:false, Cmd:(*exec.Cmd)(nil)}' [evg-runner] 2017/05/01 21:44:06 [p=debug]: new instance: instance=evg_ubuntu1604-packer_20170501214405_8260689971911243266, object={i-019bc6e4aa1433fbf t1.micro us-east-1c [] {%!!(MISSING)s(int=0) pending} {pending pending} ami-602a4d76 mci disabled { } 2017-05-01T21:44:05.000Z x86_64 xen aki-919dcaf8 paravirtual %!!(MISSING)s(int=0) default e72f41bf1e7b68416a516a46293491d35a3fe7a2fc776056a9921716cd01402b [] ebs /dev/sda1 [] %!!(MISSING)s(bool=false) [{sg-15fe2e7e xxxx }] [] %!!(MISSING)s(bool=false) } [evg-runner] 2017/05/01 19:16:28 [p=error]: unable to attach tags for $s%!!(MISSING)(EXTRA string=sir-56987wng): The spot instance request ID 'sir-56987wng' does not exist (InvalidSpotInstanceRequestID.NotFound) bash /data/infrastructure_provisioning/terraform/infrastructure_teardown.sh User:root SSHKey:mci SSHOptions:[StrictHostKeyChecking=no BatchMode=yes ConnectTimeout=10] UserData:{File: Validate:} SpawnAllowed:false Expansions:[{Key:decompress Value:tar zxvf} {Key:ps Value:ps aux} {Key:kill_pid Value:kill -- -$(ps opgid= %!v(MISSING))} {Key:scons_prune_ratio Value:0.8}]} Provider:ec2 Provisioned:false ProvisionOptions: RunningTask: Pid: TaskDispatchTime:1970-01-01 00:00:00 +0000 UTC ExpirationTime:0001-01-01 00:00:00 +0000 UTC CreationTime:2017-05-01 20:02:40.275 +0000 UTC TerminationTime:1970-01-01 00:00:00 +0000 UTC LastTaskCompletedTime:0001-01-01 00:00:00 +0000 UTC LastTaskCompleted: LastCommunicationTime:0001-01-01 00:00:00 +0000 UTC Status:starting StartedBy:mci UserHost:false AgentRevision: InstanceType:m3.large Notifications:map[] UserData: LastReachabilityCheck:0001-01-01 00:00:00 +0000 UTC UnreachableSince:0001-01-01 00:00:00 +0000 UTC} [evg-runner] 2017/05/01 20:54:03 [p=info]: Uploading client binary to host %!s(MISSING) i-047143501124e7120",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1662","05/05/2017 14:11:58",2,"No overflow checking on batchtime ""It is possible to set a very large batchtime (e.g.: max int64) and overflow the internal representation. The consequence is that builds will always be scheduled.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9468","05/13/2017 20:16:48",8,"Revive Dagger Tools ""this ticket is a place holder for work on the dagger project to make the visualizer work and import some existing work""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-1691","05/19/2017 22:28:50",2,"Don't display sub-second timings on on stats graphs ""https://evergreen.mongodb.com/task_timing/mongodb-mongo-master#/project=mongodb-mongo-master&buildVariant=enterprise-rhel-62-64-bit&taskName=compile_all&requester=gitter_request&limit=500 Doing so severely skews the visual quality of the results. The spikes to high values are harder to ignore without heuristics, but rounding down times to the nearest second seems worthwhile.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1692","05/22/2017 14:14:41",2,"compile_all task failing continuously for weeks without sending notifications ""You can see the failure history here: https://evergreen.mongodb.com/task_history/mongodb-mongo-master/compile_all But this query (which I would expect to return a BFG ticket every ~3rd day or so) instead only has one ticket: https://jira.mongodb.org/issues/?jql=project%20in%20(BFG%2C%20BF)%20and%20cf%5B14277%5D%20%3D%20ubuntu1604-debug-ubsan%20and%20%22Failing%20Tasks%22%20%3D%20compile_all""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1714","06/10/2017 18:32:44",2,"go test plugin should be more flexible in its parsing ""This test shouldn't fail, and does because gccgo has a different zero time value string format, which our regex doesn't account for. https://evergreen.mongodb.com/task/Greenbay_rhel62_gccgo_test_output_2876d0bd3a8b690c1adc411d6d7b0e7534c6750e_17_06_10_17_06_01""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1717","06/12/2017 20:34:02",2,"Fetch a Paginated List of Distros: GET /distros ""EVG-880 implements only a portion of the distro model. We should enrich the APIDistro struct to implement the remainder of the model. Note also that EVG-880 assumes the distros list is not paginated, so this needs to be changed when the route is implemented.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1776","06/15/2017 16:09:07",2,"Base URL for JIRA tickets is sometimes ""undefined"" instead of ""jira.mongodb.com"" ""See https://evergreen.mongodb.com/build/mongodb_mongo_master_ubuntu1604_debug_aubsan_lite_6c0e2884a22a82d57f2cef12756fc6a7609e20c9_17_06_14_21_15_31""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1799","06/19/2017 20:27:14",1,"ETA tooltip always shows >= 1 day on patch builds ""For example, in progress tasks on https://evergreen.mongodb.com/version/594803ff2fbabe4229000a86 have a tooltip showing ETA: >= 1 day See https://evergreen.mongodb.com/patches/project/mongodb-mongo-v3.4 for more examples. The waterfall page isn't affected: https://evergreen.mongodb.com/waterfall/mongodb-mongo-v3.4""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9391","06/23/2017 21:22:18",2,"On Windows curator stat process-tree --pid <> does not return complete info ""This ticket is related to incomplete process information when querying the """"http://localhost:2285/status"""" Evergreen endpoint on Windows. As requested, I've run the following curator command on Windows with the curator build {{d7616}} commit. with output: I do not see any """"ps_info"""" data."""," $ ps PID PPID PGID WINPID TTY UID STIME COMMAND 1372 2596 1372 516 ? 197108 19:50:23 /usr/sbin/sshd 2596 1216 2596 2380 ? 197108 19:13:20 /usr/sbin/sshd 1104 1372 1104 1204 pty1 197108 19:50:24 /usr/bin/bash 860 192 860 856 pty0 197108 19:23:14 /usr/bin/bash 1216 1 1216 1216 ? 197108 19:13:20 /usr/bin/cygrunsrv 916 860 916 2472 pty0 197108 20:18:20 /usr/bin/ps 192 2596 192 2900 ? 197108 19:23:11 /usr/sbin/sshd ./curator stat process-tree --pid 2596 { """"pid"""": 2596, """"cpu"""": { """"cpu"""": """""""", """"user"""": 0, """"system"""": 0, """"idle"""": 0, """"nice"""": 0, """"iowait"""": 0, """"irq"""": 0, """"softirq"""": 0, """"steal"""": 0, """"guest"""": 0, """"guestNice"""": 0, """"stolen"""": 0 }, """"io"""": { """"readCount"""": 0, """"writeCount"""": 0, """"readBytes"""": 0, """"writeBytes"""": 0 }, """"mem"""": { """"rss"""": 20480, """"vms"""": 0, """"swap"""": 0 }, """"memExtra"""": {}, """"errors"""": [ """"Couldn't find pid:ਤ"""", """"could not get ThreadCount: could not get win32Proc: empty"""", """"could not get CommandLine: could not get win32Proc: empty"""", """"could not get Win32Proc: could not get win32Proc: empty"""" ], """"metadata"""": { """"level"""": 40, """"hostname"""": """"WIN-3DH432IBF3A"""", """"time"""": """"2017-06-23T19:55:55.9990884Z"""", """"process"""": """"C:\\data\\mci\\curator"""" } } ",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9510","06/24/2017 02:52:12",1,"curator compile only push tasks should depend on a full suite ""to avoid pushing in cases where a test has failed ""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9465","06/26/2017 19:45:10",1,"greenbay tests leave detritus in home directory ""observed from test compile operation on windows, presumably elsewhere. ""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-1818","06/27/2017 21:28:49",1,"In BF project the ""diff"" link missing ""mongo"" ""eg https://jira.mongodb.org/browse/BF-5321 points to https://github.com/mongodb/commit/932c2f345598d8e1d283e8c2bb54fd8d0e11c853 ( the link misses mongo)""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1820","06/28/2017 16:01:04",1,"static hosts should not get flagged for termination ""I have a static host that was marked as unreachable, and the monitor published a bunch of """"flagged for termination because: """" messages. Obviously the host can't be terminated though because it is static. https://evergreen.mongodb.com/host/root@ec2-54-242-216-156.compute-1.amazonaws.com""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1823","06/28/2017 19:52:18",1,"swap order of id/link/etc and summary as printed by evergreen patch ""The link and Id are the most important bits of info since they are always needed after submitting a patch. Unfortunately for large patches, they get scrolled off screen by the summary, which is not only less important, it is also redundant with the summary printed before submitting the patch. Also it seems to print several blank lines at the end, making this even worse. """," > evergreen patch Enter a description for this patch (optional): woooo .../suites/sharding_jscore_passthrough_opquery.yml | 74 +++++++++ etc/evergreen.yml | 36 +++++ jstests/core/invalid_db_name.js | 8 +- jstests/core/profile_insert.js | 3 - src/mongo/bson/bsonobj.h | 12 +- src/mongo/client/dbclient.cpp | 14 +- src/mongo/client/dbclientcursor.cpp | 18 +-- src/mongo/db/audit.h | 3 +- src/mongo/db/auth/sasl_commands.cpp | 12 +- src/mongo/db/commands.cpp | 80 +++++++--- src/mongo/db/commands.h | 176 +++++++++++++-------- src/mongo/db/commands/SConscript | 14 +- src/mongo/db/commands/apply_ops_cmd.cpp | 14 +- src/mongo/db/commands/apply_ops_cmd_common.cpp | 2 +- src/mongo/db/commands/authentication_commands.cpp | 11 +- src/mongo/db/commands/authentication_commands.h | 5 +- src/mongo/db/commands/clone.cpp | 5 +- src/mongo/db/commands/clone_collection.cpp | 14 +- src/mongo/db/commands/collection_to_capped.cpp | 28 ++-- src/mongo/db/commands/compact.cpp | 14 +- src/mongo/db/commands/conn_pool_stats.cpp | 5 +- src/mongo/db/commands/conn_pool_sync.cpp | 5 +- src/mongo/db/commands/connection_status.cpp | 5 +- src/mongo/db/commands/copydb.cpp | 14 +- src/mongo/db/commands/copydb_start_commands.cpp | 28 ++-- src/mongo/db/commands/count_cmd.cpp | 16 +- src/mongo/db/commands/cpuload.cpp | 5 +- src/mongo/db/commands/cpuprofile.cpp | 46 +++--- src/mongo/db/commands/create_indexes.cpp | 14 +- src/mongo/db/commands/current_op.cpp | 5 +- src/mongo/db/commands/dbcommands.cpp | 120 +++++++------- src/mongo/db/commands/dbhash.cpp | 14 +- src/mongo/db/commands/distinct.cpp | 16 +- src/mongo/db/commands/driverHelpers.cpp | 14 +- src/mongo/db/commands/drop_indexes.cpp | 19 ++- src/mongo/db/commands/eval.cpp | 14 +- src/mongo/db/commands/explain_cmd.cpp | 8 +- src/mongo/db/commands/fail_point_cmd.cpp | 14 +- src/mongo/db/commands/find_and_modify.cpp | 5 +- src/mongo/db/commands/find_cmd.cpp | 30 ++-- src/mongo/db/commands/fsync.cpp | 28 ++-- src/mongo/db/commands/generic.cpp | 59 +++---- src/mongo/db/commands/geo_near_cmd.cpp | 14 +- src/mongo/db/commands/get_last_error.cpp | 24 ++- src/mongo/db/commands/getmore_cmd.cpp | 8 +- src/mongo/db/commands/group_cmd.cpp | 5 +- src/mongo/db/commands/hashcmd.cpp | 14 +- src/mongo/db/commands/haystack.cpp | 14 +- src/mongo/db/commands/index_filter_commands.cpp | 3 +- src/mongo/db/commands/index_filter_commands.h | 3 +- src/mongo/db/commands/isself.cpp | 5 +- src/mongo/db/commands/kill_op.cpp | 5 +- src/mongo/db/commands/killcursors_common.cpp | 1 - src/mongo/db/commands/killcursors_common.h | 5 +- src/mongo/db/commands/list_collections.cpp | 5 +- src/mongo/db/commands/list_databases.cpp | 5 +- src/mongo/db/commands/list_indexes.cpp | 5 +- src/mongo/db/commands/lock_info.cpp | 5 +- src/mongo/db/commands/mr.cpp | 19 ++- src/mongo/db/commands/oplog_note.cpp | 5 +- src/mongo/db/commands/parallel_collection_scan.cpp | 5 +- src/mongo/db/commands/parameters.cpp | 28 ++-- src/mongo/db/commands/pipeline_command.cpp | 5 +- src/mongo/db/commands/plan_cache_commands.cpp | 3 +- src/mongo/db/commands/plan_cache_commands.h | 3 +- src/mongo/db/commands/rename_collection_cmd.cpp | 14 +- src/mongo/db/commands/repair_cursor.cpp | 5 +- src/mongo/db/commands/server_status.cpp | 5 +- .../set_feature_compatibility_version_command.cpp | 6 +- src/mongo/db/commands/shutdown.h | 6 +- src/mongo/db/commands/snapshot_management.cpp | 10 +- src/mongo/db/commands/test_commands.cpp | 29 ++-- src/mongo/db/commands/top_command.cpp | 5 +- src/mongo/db/commands/touch.cpp | 14 +- src/mongo/db/commands/user_management_commands.cpp | 100 +++++------- src/mongo/db/commands/validate.cpp | 14 +- .../db/commands/write_commands/write_commands.cpp | 36 ++--- .../write_commands/write_commands_common.cpp | 20 ++- .../write_commands/write_commands_common.h | 4 +- src/mongo/db/dbdirectclient.cpp | 21 +-- src/mongo/db/exec/stagedebug_cmd.cpp | 6 +- src/mongo/db/ftdc/ftdc_commands.cpp | 5 +- src/mongo/db/ftdc/ftdc_mongod.cpp | 23 +-- .../write_ops_document_stream_integration_test.cpp | 35 ++++ src/mongo/db/ops/write_ops_exec.cpp | 11 +- src/mongo/db/repl/master_slave.cpp | 5 +- src/mongo/db/repl/repl_set_command.h | 4 +- src/mongo/db/repl/repl_set_commands.cpp | 18 +-- src/mongo/db/repl/repl_set_request_votes.cpp | 1 - src/mongo/db/repl/replication_info.cpp | 5 +- src/mongo/db/repl/resync.cpp | 14 +- src/mongo/db/s/check_sharding_index_command.cpp | 14 +- src/mongo/db/s/cleanup_orphaned_cmd.cpp | 16 +- .../db/s/config/configsvr_add_shard_command.cpp | 5 +- .../config/configsvr_add_shard_to_zone_command.cpp | 5 +- .../configsvr_commit_chunk_migration_command.cpp | 5 +- .../config/configsvr_control_balancer_command.cpp | 5 +- .../db/s/config/configsvr_merge_chunk_command.cpp | 5 +- .../db/s/config/configsvr_move_chunk_command.cpp | 5 +- .../db/s/config/configsvr_move_primary_command.cpp | 5 +- .../configsvr_remove_shard_from_zone_command.cpp | 5 +- ...r_set_feature_compatibility_version_command.cpp | 5 +- .../config/configsvr_shard_collection_command.cpp | 5 +- .../db/s/config/configsvr_split_chunk_command.cpp | 5 +- .../configsvr_update_zone_key_range_command.cpp | 5 +- src/mongo/db/s/get_shard_version_command.cpp | 5 +- src/mongo/db/s/merge_chunks_command.cpp | 14 +- ...gration_chunk_cloner_source_legacy_commands.cpp | 10 +- ...gration_destination_manager_legacy_commands.cpp | 29 ++-- src/mongo/db/s/move_chunk_command.cpp | 5 +- src/mongo/db/s/set_shard_version_command.cpp | 14 +- src/mongo/db/s/sharding_state_command.cpp | 5 +- src/mongo/db/s/split_chunk_command.cpp | 14 +- src/mongo/db/s/split_vector_command.cpp | 14 +- src/mongo/db/s/unset_sharding_command.cpp | 5 +- src/mongo/db/service_entry_point_mongod.cpp | 9 +- .../storage/mmap_v1/journal_latency_test_cmd.cpp | 5 +- src/mongo/dbtests/directclienttests.cpp | 4 +- src/mongo/rpc/legacy_reply.cpp | 11 ++ src/mongo/rpc/legacy_request.cpp | 6 +- src/mongo/rpc/metadata.cpp | 83 ++++++---- src/mongo/rpc/metadata.h | 11 +- .../rpc/metadata/logical_time_metadata_test.cpp | 8 +- src/mongo/rpc/metadata_test.cpp | 82 +++++----- src/mongo/s/client/shard_connection.cpp | 5 +- src/mongo/s/commands/SConscript | 1 + src/mongo/s/commands/cluster_add_shard_cmd.cpp | 5 +- .../s/commands/cluster_add_shard_to_zone_cmd.cpp | 5 +- src/mongo/s/commands/cluster_apply_ops_cmd.cpp | 5 +- .../cluster_available_query_options_cmd.cpp | 5 +- src/mongo/s/commands/cluster_compact_cmd.cpp | 5 +- .../s/commands/cluster_control_balancer_cmd.cpp | 5 +- src/mongo/s/commands/cluster_count_cmd.cpp | 21 ++- src/mongo/s/commands/cluster_current_op.cpp | 14 +- src/mongo/s/commands/cluster_db_stats_cmd.cpp | 14 +- src/mongo/s/commands/cluster_drop_cmd.cpp | 5 +- src/mongo/s/commands/cluster_drop_database_cmd.cpp | 5 +- .../s/commands/cluster_enable_sharding_cmd.cpp | 14 +- src/mongo/s/commands/cluster_explain_cmd.cpp | 8 +- .../s/commands/cluster_find_and_modify_cmd.cpp | 5 +- src/mongo/s/commands/cluster_find_cmd.cpp | 5 +- .../s/commands/cluster_flush_router_config_cmd.cpp | 5 +- src/mongo/s/commands/cluster_fsync_cmd.cpp | 14 +- src/mongo/s/commands/cluster_ftdc_commands.cpp | 14 +- .../s/commands/cluster_get_last_error_cmd.cpp | 5 +- .../s/commands/cluster_get_prev_error_cmd.cpp | 14 +- src/mongo/s/commands/cluster_get_shard_map_cmd.cpp | 5 +- .../s/commands/cluster_get_shard_version_cmd.cpp | 5 +- src/mongo/s/commands/cluster_getmore_cmd.cpp | 5 +- src/mongo/s/commands/cluster_index_filter_cmd.cpp | 5 +- src/mongo/s/commands/cluster_is_db_grid_cmd.cpp | 5 +- src/mongo/s/commands/cluster_is_master_cmd.cpp | 5 +- src/mongo/s/commands/cluster_kill_op.cpp | 5 +- .../s/commands/cluster_list_databases_cmd.cpp | 5 +- src/mongo/s/commands/cluster_list_shards_cmd.cpp | 5 +- src/mongo/s/commands/cluster_map_reduce_cmd.cpp | 14 +- src/mongo/s/commands/cluster_merge_chunks_cmd.cpp | 14 +- src/mongo/s/commands/cluster_move_chunk_cmd.cpp | 14 +- src/mongo/s/commands/cluster_move_primary_cmd.cpp | 14 +- src/mongo/s/commands/cluster_netstat_cmd.cpp | 5 +- src/mongo/s/commands/cluster_pipeline_cmd.cpp | 5 +- src/mongo/s/commands/cluster_plan_cache_cmd.cpp | 6 +- src/mongo/s/commands/cluster_profile_cmd.cpp | 14 +- src/mongo/s/commands/cluster_remove_shard_cmd.cpp | 5 +- .../cluster_remove_shard_from_zone_cmd.cpp | 5 +- .../s/commands/cluster_repl_set_get_status_cmd.cpp | 14 +- src/mongo/s/commands/cluster_reset_error_cmd.cpp | 5 +- ...uster_set_feature_compatibility_version_cmd.cpp | 5 +- .../s/commands/cluster_shard_collection_cmd.cpp | 5 +- src/mongo/s/commands/cluster_shutdown_cmd.cpp | 1 - src/mongo/s/commands/cluster_split_cmd.cpp | 14 +- .../commands/cluster_update_zone_key_range_cmd.cpp | 5 +- .../commands/cluster_user_management_commands.cpp | 95 +++++------ src/mongo/s/commands/cluster_whats_my_uri_cmd.cpp | 5 +- src/mongo/s/commands/cluster_write_cmd.cpp | 21 +-- src/mongo/s/commands/commands_public.cpp | 56 +++---- src/mongo/s/commands/strategy.cpp | 40 +---- src/mongo/s/write_ops/batched_command_request.cpp | 31 +--- src/mongo/s/write_ops/batched_command_request.h | 5 +- src/mongo/s/write_ops/batched_insert_request.cpp | 5 +- src/mongo/shell/bulk_api.js | 24 +-- src/mongo/shell/collection.js | 4 +- 182 files changed, 1331 insertions(+), 1380 deletions(-) bb0b94351b auditing command use OMR 464247a137 Add sharding_jscore_passthrough_opquery suite 082605fba3 upconvert now uses document sequences 077f91713e upconvertRequest shouldn't separate data and metadata b3edb26b27 bulk_api.js should use runCommand() a340b9e614 Auth checks get access to document sequences 65ff0b9f36 don't pass cmdobj to localHostOnlyIfNoAuth() 88e825a065 ErrmsgCommandDeprecated 8391ef9095 Get errmsg out of public Command API 7c08390439 Make BasicCommand a separate type 5fe7b8bcc8 SERVER-29731 convert all direct subclasses of Command to BasicCommand 803cfc8cca runCommandDirectly This is a summary of the patch to be submitted. Continue? (y/n): y Patch successfully created. ID : 5953f7f42fbabe5e3d002018 Created : 401.02207ms ago Description : woooo Link : https://evergreen.mongodb.com/patch/5953f7f42fbabe5e3d002018 Finalized : No Summary : Base Commit : 940a6b62189bface6aec2af698e5e9c4149af258 +74 -0 buildscripts/resmokeconfig/suites/sharding_jscore_passthrough_opquery.yml +36 -0 etc/evergreen.yml +1 -7 jstests/core/invalid_db_name.js +0 -3 jstests/core/profile_insert.js +10 -2 src/mongo/bson/bsonobj.h +1 -13 src/mongo/client/dbclient.cpp +6 -12 src/mongo/client/dbclientcursor.cpp +2 -1 src/mongo/db/audit.h +4 -8 src/mongo/db/auth/sasl_commands.cpp +59 -21 src/mongo/db/commands.cpp +108 -68 src/mongo/db/commands.h +13 -1 src/mongo/db/commands/SConscript +7 -7 src/mongo/db/commands/apply_ops_cmd.cpp +1 -1 src/mongo/db/commands/apply_ops_cmd_common.cpp +4 -7 src/mongo/db/commands/authentication_commands.cpp +2 -3 src/mongo/db/commands/authentication_commands.h +2 -3 src/mongo/db/commands/clone.cpp +7 -7 src/mongo/db/commands/clone_collection.cpp +14 -14 src/mongo/db/commands/collection_to_capped.cpp +7 -7 src/mongo/db/commands/compact.cpp +2 -3 src/mongo/db/commands/conn_pool_stats.cpp +2 -3 src/mongo/db/commands/conn_pool_sync.cpp +2 -3 src/mongo/db/commands/connection_status.cpp +7 -7 src/mongo/db/commands/copydb.cpp +14 -14 src/mongo/db/commands/copydb_start_commands.cpp +7 -9 src/mongo/db/commands/count_cmd.cpp +2 -3 src/mongo/db/commands/cpuload.cpp +23 -23 src/mongo/db/commands/cpuprofile.cpp +7 -7 src/mongo/db/commands/create_indexes.cpp +2 -3 src/mongo/db/commands/current_op.cpp +56 -64 src/mongo/db/commands/dbcommands.cpp +7 -7 src/mongo/db/commands/dbhash.cpp +7 -9 src/mongo/db/commands/distinct.cpp +7 -7 src/mongo/db/commands/driverHelpers.cpp +9 -10 src/mongo/db/commands/drop_indexes.cpp +7 -7 src/mongo/db/commands/eval.cpp +4 -4 src/mongo/db/commands/explain_cmd.cpp +7 -7 src/mongo/db/commands/fail_point_cmd.cpp +2 -3 src/mongo/db/commands/find_and_modify.cpp +15 -15 src/mongo/db/commands/find_cmd.cpp +14 -14 src/mongo/db/commands/fsync.cpp +25 -34 src/mongo/db/commands/generic.cpp +7 -7 src/mongo/db/commands/geo_near_cmd.cpp +11 -13 src/mongo/db/commands/get_last_error.cpp +3 -5 src/mongo/db/commands/getmore_cmd.cpp +2 -3 src/mongo/db/commands/group_cmd.cpp +7 -7 src/mongo/db/commands/hashcmd.cpp +7 -7 src/mongo/db/commands/haystack.cpp +1 -2 src/mongo/db/commands/index_filter_commands.cpp +1 -2 src/mongo/db/commands/index_filter_commands.h +2 -3 src/mongo/db/commands/isself.cpp +2 -3 src/mongo/db/commands/kill_op.cpp +0 -1 src/mongo/db/commands/killcursors_common.cpp +2 -3 src/mongo/db/commands/killcursors_common.h +2 -3 src/mongo/db/commands/list_collections.cpp +2 -3 src/mongo/db/commands/list_databases.cpp +2 -3 src/mongo/db/commands/list_indexes.cpp +2 -3 src/mongo/db/commands/lock_info.cpp +9 -10 src/mongo/db/commands/mr.cpp +2 -3 src/mongo/db/commands/oplog_note.cpp +2 -3 src/mongo/db/commands/parallel_collection_scan.cpp +14 -14 src/mongo/db/commands/parameters.cpp +2 -3 src/mongo/db/commands/pipeline_command.cpp +1 -2 src/mongo/db/commands/plan_cache_commands.cpp +1 -2 src/mongo/db/commands/plan_cache_commands.h +7 -7 src/mongo/db/commands/rename_collection_cmd.cpp +2 -3 src/mongo/db/commands/repair_cursor.cpp +2 -3 src/mongo/db/commands/server_status.cpp +3 -3 src/mongo/db/commands/set_feature_compatibility_version_command.cpp +3 -3 src/mongo/db/commands/shutdown.h +4 -6 src/mongo/db/commands/snapshot_management.cpp +13 -16 src/mongo/db/commands/test_commands.cpp +2 -3 src/mongo/db/commands/top_command.cpp +7 -7 src/mongo/db/commands/touch.cpp +40 -60 src/mongo/db/commands/user_management_commands.cpp +7 -7 src/mongo/db/commands/validate.cpp +11 -25 src/mongo/db/commands/write_commands/write_commands.cpp +14 -6 src/mongo/db/commands/write_commands/write_commands_common.cpp +2 -2 src/mongo/db/commands/write_commands/write_commands_common.h +5 -16 src/mongo/db/dbdirectclient.cpp +2 -4 src/mongo/db/exec/stagedebug_cmd.cpp +2 -3 src/mongo/db/ftdc/ftdc_commands.cpp +6 -17 src/mongo/db/ftdc/ftdc_mongod.cpp +35 -0 src/mongo/db/ops/write_ops_document_stream_integration_test.cpp +3 -8 src/mongo/db/ops/write_ops_exec.cpp +2 -3 src/mongo/db/repl/master_slave.cpp +2 -2 src/mongo/db/repl/repl_set_command.h +1 -17 src/mongo/db/repl/repl_set_commands.cpp +0 -1 src/mongo/db/repl/repl_set_request_votes.cpp +2 -3 src/mongo/db/repl/replication_info.cpp +7 -7 src/mongo/db/repl/resync.cpp +7 -7 src/mongo/db/s/check_sharding_index_command.cpp +8 -8 src/mongo/db/s/cleanup_orphaned_cmd.cpp +2 -3 src/mongo/db/s/config/configsvr_add_shard_command.cpp +2 -3 src/mongo/db/s/config/configsvr_add_shard_to_zone_command.cpp +2 -3 src/mongo/db/s/config/configsvr_commit_chunk_migration_command.cpp +2 -3 src/mongo/db/s/config/configsvr_control_balancer_command.cpp +2 -3 src/mongo/db/s/config/configsvr_merge_chunk_command.cpp +2 -3 src/mongo/db/s/config/configsvr_move_chunk_command.cpp +2 -3 src/mongo/db/s/config/configsvr_move_primary_command.cpp +2 -3 src/mongo/db/s/config/configsvr_remove_shard_from_zone_command.cpp +2 -3 src/mongo/db/s/config/configsvr_set_feature_compatibility_version_command.cpp +2 -3 src/mongo/db/s/config/configsvr_shard_collection_command.cpp +2 -3 src/mongo/db/s/config/configsvr_split_chunk_command.cpp +2 -3 src/mongo/db/s/config/configsvr_update_zone_key_range_command.cpp +2 -3 src/mongo/db/s/get_shard_version_command.cpp +7 -7 src/mongo/db/s/merge_chunks_command.cpp +4 -6 src/mongo/db/s/migration_chunk_cloner_source_legacy_commands.cpp +13 -16 src/mongo/db/s/migration_destination_manager_legacy_commands.cpp +2 -3 src/mongo/db/s/move_chunk_command.cpp +7 -7 src/mongo/db/s/set_shard_version_command.cpp +2 -3 src/mongo/db/s/sharding_state_command.cpp +7 -7 src/mongo/db/s/split_chunk_command.cpp +7 -7 src/mongo/db/s/split_vector_command.cpp +2 -3 src/mongo/db/s/unset_sharding_command.cpp +4 -5 src/mongo/db/service_entry_point_mongod.cpp +2 -3 src/mongo/db/storage/mmap_v1/journal_latency_test_cmd.cpp +3 -1 src/mongo/dbtests/directclienttests.cpp +11 -0 src/mongo/rpc/legacy_reply.cpp +2 -4 src/mongo/rpc/legacy_request.cpp +56 -27 src/mongo/rpc/metadata.cpp +3 -8 src/mongo/rpc/metadata.h +5 -3 src/mongo/rpc/metadata/logical_time_metadata_test.cpp +43 -39 src/mongo/rpc/metadata_test.cpp +2 -3 src/mongo/s/client/shard_connection.cpp +1 -0 src/mongo/s/commands/SConscript +2 -3 src/mongo/s/commands/cluster_add_shard_cmd.cpp +2 -3 src/mongo/s/commands/cluster_add_shard_to_zone_cmd.cpp +2 -3 src/mongo/s/commands/cluster_apply_ops_cmd.cpp +2 -3 src/mongo/s/commands/cluster_available_query_options_cmd.cpp +2 -3 src/mongo/s/commands/cluster_compact_cmd.cpp +2 -3 src/mongo/s/commands/cluster_control_balancer_cmd.cpp +10 -11 src/mongo/s/commands/cluster_count_cmd.cpp +7 -7 src/mongo/s/commands/cluster_current_op.cpp +7 -7 src/mongo/s/commands/cluster_db_stats_cmd.cpp +2 -3 src/mongo/s/commands/cluster_drop_cmd.cpp +2 -3 src/mongo/s/commands/cluster_drop_database_cmd.cpp +7 -7 src/mongo/s/commands/cluster_enable_sharding_cmd.cpp +4 -4 src/mongo/s/commands/cluster_explain_cmd.cpp +2 -3 src/mongo/s/commands/cluster_find_and_modify_cmd.cpp +2 -3 src/mongo/s/commands/cluster_find_cmd.cpp +2 -3 src/mongo/s/commands/cluster_flush_router_config_cmd.cpp +7 -7 src/mongo/s/commands/cluster_fsync_cmd.cpp +7 -7 src/mongo/s/commands/cluster_ftdc_commands.cpp +2 -3 src/mongo/s/commands/cluster_get_last_error_cmd.cpp +7 -7 src/mongo/s/commands/cluster_get_prev_error_cmd.cpp +2 -3 src/mongo/s/commands/cluster_get_shard_map_cmd.cpp +2 -3 src/mongo/s/commands/cluster_get_shard_version_cmd.cpp +2 -3 src/mongo/s/commands/cluster_getmore_cmd.cpp +2 -3 src/mongo/s/commands/cluster_index_filter_cmd.cpp +2 -3 src/mongo/s/commands/cluster_is_db_grid_cmd.cpp +2 -3 src/mongo/s/commands/cluster_is_master_cmd.cpp +2 -3 src/mongo/s/commands/cluster_kill_op.cpp +2 -3 src/mongo/s/commands/cluster_list_databases_cmd.cpp +2 -3 src/mongo/s/commands/cluster_list_shards_cmd.cpp +7 -7 src/mongo/s/commands/cluster_map_reduce_cmd.cpp +7 -7 src/mongo/s/commands/cluster_merge_chunks_cmd.cpp +7 -7 src/mongo/s/commands/cluster_move_chunk_cmd.cpp +7 -7 src/mongo/s/commands/cluster_move_primary_cmd.cpp +2 -3 src/mongo/s/commands/cluster_netstat_cmd.cpp +2 -3 src/mongo/s/commands/cluster_pipeline_cmd.cpp +2 -4 src/mongo/s/commands/cluster_plan_cache_cmd.cpp +7 -7 src/mongo/s/commands/cluster_profile_cmd.cpp +2 -3 src/mongo/s/commands/cluster_remove_shard_cmd.cpp +2 -3 src/mongo/s/commands/cluster_remove_shard_from_zone_cmd.cpp +7 -7 src/mongo/s/commands/cluster_repl_set_get_status_cmd.cpp +2 -3 src/mongo/s/commands/cluster_reset_error_cmd.cpp +2 -3 src/mongo/s/commands/cluster_set_feature_compatibility_version_cmd.cpp +2 -3 src/mongo/s/commands/cluster_shard_collection_cmd.cpp +0 -1 src/mongo/s/commands/cluster_shutdown_cmd.cpp +7 -7 src/mongo/s/commands/cluster_split_cmd.cpp +2 -3 src/mongo/s/commands/cluster_update_zone_key_range_cmd.cpp +38 -57 src/mongo/s/commands/cluster_user_management_commands.cpp +2 -3 src/mongo/s/commands/cluster_whats_my_uri_cmd.cpp +6 -15 src/mongo/s/commands/cluster_write_cmd.cpp +21 -35 src/mongo/s/commands/commands_public.cpp +5 -35 src/mongo/s/commands/strategy.cpp +7 -24 src/mongo/s/write_ops/batched_command_request.cpp +3 -2 src/mongo/s/write_ops/batched_command_request.h +3 -2 src/mongo/s/write_ops/batched_insert_request.cpp +1 -23 src/mongo/shell/bulk_api.js +2 -2 src/mongo/shell/collection.js ",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3310","06/29/2017 10:43:05",8,"Annotations (relevant BF tickets) for trend graphs in evergreen perf plugin ""When triaging Microbenchmarks and sys-perf, it's difficult to get any historical info about historical ups and downs in the trend graphs. There may exist a Jira ticket, but when just looking at the trend graph, there's no marker or link to say that this jump 3 weeks ago is a known issue. A lot of time is then wasted by the build baron re-discovering things that are already known. We'd like to change the display so that, in addition to displaying change points, Build Failures are also rendered onto the trend graphs. BF tickets have 'Evergreen Project', 'Failing Buildvariants', 'Failing Tasks' and 'First Failing Revision' / 'Fix Revision' fields that can be used to link to the point in the trend graphs. When a BF and a Change Point exist for the same revision, the BF should take precedence (as this indicates that the change is known or is being worked on). ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1827","06/29/2017 20:06:22",2,"timeouts still marked as system failures ""e.g. https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_multiversion_multistorage_engine_f0110e2682e3a787df062ee3feb7637add694978_17_06_29_14_43_19/0 EVG-1608""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-1828","06/29/2017 20:41:08",1,"avoid removing task directory after timeouts ""turns out this removed files during the post task, and we shouldn't do that""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1829","06/29/2017 23:00:46",1,"HTTP error handler on some pages give non-helpful error messages ""Like on the settings page, due to the browser returning a JSON object for the error but we're trying to display it verbatim.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1838","07/01/2017 00:47:02",1,"write application logs to files and log service ""continue only writing agent lots to log service, if possible.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1839","07/01/2017 17:20:32",2,"clean up/restructure log messages ""specifically I want to use the line constructors *much* less as they're quite hard to use in a structured format. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1840","07/04/2017 02:55:03",2,"implement legacy client methods for routes required by attach plugin """""," SendTaskResults(context.Context, *task.TestResults) error SendTestLog(context.Context, *model.TestLog) (string, error) ",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1841","07/04/2017 15:07:13",1,"new client getnexttask method takes a taskID/secret ""this seems like it is in error or is confusing. ""","",0,0,0,0,0,1,0,0,0,1,0,0,0,0,0 +"EVG-1842","07/04/2017 15:18:09",1,"new client retryGet should handle nil responses ""the current implementation logs but doesn't error if the response is nil. (which I think should always be an error, or at least I believe that the response is never nil if the error is nil. It would be nice to prevent the implementation of the method handlers from needing to consider the possibility of a response being nil if they check the error. would want to update/refactor the client methods accordingly as well""","",0,0,0,0,0,1,0,0,0,1,0,0,0,0,0 +"EVG-1843","07/04/2017 18:20:11",1,"client.LogProducer's writer methods should accepet levels. ""so that we can properly filter stderr messages to error""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1844","07/04/2017 18:22:18",1,"move command package and refactor it to accept conexts ""new package should be called subprocess ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1849","07/06/2017 18:42:22",2,"Instances should fail to provision if adding tags fails ""This will prevent cases like BUILD-3424, where the reaper stopped a user's spawnhost.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1852","07/10/2017 15:38:24",1,"Hosts are not removed from DB when terminated in GCE and OpenStack ""If you spawn a host in GCE/OpenStack and then terminate it, it will still show up in the Evergreen Hosts UI because it was not removed from the DB.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1853","07/10/2017 15:42:46",1,"GCE does not accept spaces in new instance names ""If you spawn a GCE host using the default distro name """"new distro"""", GCE returns an error: Must be a match of regex '(?:[a-z](?:[-a-z0-9]{0,61}[a-z0-9])?)'. We should clean/validate the instance name in GCE before making an API call to spawn an instance.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1854","07/10/2017 16:48:03",2,"handleAPIError returns wrong error status code ""Returned JSON document claims 500 status but curl -I shows 404. Problem likely exists in handleAPIError() method in rest/route/handler.go because returned error is cast to rest.APIError instead of *rest.APIError. See: """," norman@MacBook-Pro-53:~$ curl -I https://evergreen.mongodb.com/rest/v2/hosts/asdfasdf HTTP/1.1 404 Not Found Content-Type: text/plain; charset=utf-8 X-Content-Type-Options: nosniff Date: Mon, 10 Jul 2017 15:37:02 GMT Content-Length: 19 norman@MacBook-Pro-53:~$ curl https://evergreen.mongodb.com/rest/v2/hosts/asdfasdf {""""status"""":500,""""error"""":""""host with id asdfasdf not found""""}norman@MacBook-Pro-53:~$ ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1855","07/10/2017 18:00:33",1,"OpenStack security groups are NOT optional ""The Evergreen UI indicates that security groups are an optional parameter, but the API call to create an instance will actually fail if a security group is not indicated. We need to fix the UI and also update settings validation in the provider implementation.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1856","07/10/2017 18:04:59",1,"More informative error message when spawning hosts ""If a host fails to spawn, it will not appear in the UI, but there will still be a green info message saying """"Host spawned."""" This is confusing to users who cannot tell if their host actually spawned, nor the reason it may have failed. It can fail if, for example, the distro is configured incorrectly with an image ID that does not exist. https://evergreen.mongodb.com/spawn""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1860","07/11/2017 16:10:21",2,"Clean up build API routes ""Some class names in the build abort route are misnamed, and some tests are a little messy. Ex: buildIdAbortGetHandler, AbortBuild/FindBuildById argument names""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1861","07/11/2017 16:21:57",2,"Authenticate to a vCenter server using the VMware golang library ""This ticket involves creating a client interface to the golang library similar to in the OpenStack and GCE cloud providers. At the end, we should have an authenticated client that can be used to make more API calls to the server. * Create an interface to the golang library with a mock for testing * Add credentials to *evergreen.Settings structure * Make an API call to authenticate to the server""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1862","07/11/2017 16:23:59",2,"Implement methods for reading VMware instance attributes ""These provider methods behave the same for hosts created by Evergreen and hosts that are created with the vSphere web client, so they are possible to test before we figure out how to spawn instances using the vSphere API. This involves implementing the following methods of the cloud manager interface: * GetInstanceStatus() * GetDNSName() * IsUp()""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1864","07/12/2017 16:31:33",2,"Scrolling up on the build timeline requires scrolling down ""Scenario to reproduce: 1. Visit: https://evergreen.mongodb.com/version/performance_12568fbc406678ebd98a93d121175b1f765c4766#/0 2. Attempt to scroll up on the Build Time so you can work back to the current date. It requires you to continually scroll down and then back up to trigger a load. While seemingly small this is really annoying for build barons investigating failures. Expected: When you scroll up on the build timeline it loads earlier and earlier dates without requiring a scroll down. ""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1865","07/12/2017 20:04:46",2,"Time conversion errors in API models and pagination functions ""The conversion from service level structs to API structs is incorrect. Given a time.Time field, several API models are using naive type casting to coerce these fields into APITime fields, which truncates location data and results in off-by-4-hours errors. Instead we should be using the model.NewTime method which first converts the input time to a location of UTC before populating APITime fields. Furthermore, the serialization of the time in the actual pagination function is also incorrect. Rather than format the next page's first time properly using time.Format, we currently use the .String() method which again improperly truncates the location data but also uses the wrong format. Routes affected include but are not limited to build, metrics, and hosts.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1868","07/13/2017 20:55:02",1,"Support custom machine types in Google Compute distros ""In addition to predefined machine types, Google Compute also supports custom machine types that are priced differently according to the number of vCPUs and memory used. GCE distro configuration should also support custom machine types. {panel:title=Source: [https://cloud.google.com/compute/pricing#custommachinetypepricing]} Create a custom machine type with a specific number of vCPUs and amount of memory if predefined machine types are not optimal for your workloads. Custom machine types also save you the cost of running on a larger, more expensive machine type if you don't need to use all the resources of that machine type. For example, instead of using an n1-standard-8 machine type when you just need a machine type with 6 vCPUs, create a custom machine type instance with 6 vCPUs and 22.5 GB of memory. Creating a custom machine type can save you up to 40% compared to selecting a larger machine type. {panel} ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1870","07/14/2017 21:48:51",1,"Methods in rest client should not log ""They should return errors, which the caller will log.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1876","07/15/2017 15:03:59",1,"API user and key header constants are reversed ""const ( AuthTokenCookie = """"mci-token"""" TaskSecretHeader = """"Task-Secret"""" HostHeader = """"Host-Id"""" HostSecretHeader = """"Host-Secret"""" ContentTypeHeader = """"Content-Type"""" ContentTypeValue = """"application/json"""" APIUserHeader = """"Api-Key"""" APIKeyHeader = """"Api-User"""" )""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1880","07/17/2017 21:33:58",3,"Get all revisions for a project: GET /projects//revisions/ ""Get all revisions for a project during a specific time period, which will be given as form values included in the http request. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9488","07/18/2017 15:15:48",1,"Change granularity to duration ""Change mentions of granularity to duration in the build cost reporting tool.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-1888","07/18/2017 20:14:34",1,"Add route to kill all agents ""this should go in the status server that runs in the agent""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1890","07/19/2017 22:44:52",1,"Fix setup/teardown script ordering ""The order of events is: # Copy the teardown script to the host. # Copy the setup script to the host. # Run the setup script. Some setup scripts, however, mount the working directory elsewhere, which means the setup and teardown scripts are no longer present in the distro's working directory, and then Evergreen cannot run the teardown script.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1894","07/20/2017 18:28:54",2,"Get all Tasks by Project for Cost Route: GET cost/projects//task ""Include starttime and duration when filtering for relevant tasks ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1895","07/20/2017 21:11:25",1,"Pagination broken in the hosts route ""We should fix the fact that the data Connector to properly sort the host results so that the pagination operations make sense. We'll address the parameter passing problem separately. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1900","07/24/2017 16:40:09",2,"fetch hosts route pagination broken ""When fetching a page of hosts, we are not sorting correctly""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1901","07/24/2017 22:26:28",2,"test-rest-model failure ""h2. [test-rest-model failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_rest_model_patch_752543f46b1c2a22f984c3b1ce15ff88b6314696_597639282fbabe43520018ce_17_07_24_18_15_39/0] Host: [ec2-54-224-143-176.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-9hqi78wk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~sejin.park]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-1903","07/25/2017 00:21:52",1,"patches listed in version history drawer ""The two versions at the top of the list in the screenshot link to patch tasks. Only commit tasks should be showing up there.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1904","07/26/2017 01:25:48",2,"schedule patch button can result in patch being scheduled multiple times ""we ended up in a situation with duplicate tasks being created after the first invocation errored in the middle of the operation. ""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-9493","07/26/2017 15:22:52",1,"fields message triggered panic """""," Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: fatal error: concurrent map read and map write Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: goroutine 20 [running]: Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: runtime.throw(0x158fc48, 0x21) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/runtime/panic.go:566 +0x95 fp=0xc4205fdda8 sp=0xc4205fdd88 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: runtime.mapaccess2_faststr(0x12bed00, 0xc4206d6060, 0x1555d1c, 0x8, 0x1fe07c0, 0x148f900) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/runtime/hashmap_fast.go:306 +0x52b fp=0xc4205fde08 sp=0xc4205fdda8 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/message.(*fieldMessage).Raw(0xc420436000, 0x1f9a260, 0xc420436000) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /data/mci/269e09d73d98cfec0ed8b82bd108f49e/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/message/fields.go:97 +0xb9 fp=0xc4205fde90 sp=0xc4205fde08 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.(*splunkLogger).Send(0xc4201be550, 0x1f9a0e0, 0xc4205db860) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /data/mci/269e09d73d98cfec0ed8b82bd108f49e/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send/splunk.go:59 +0x1ba fp=0xc4205fdf30 sp=0xc4205fde90 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.(*bufferedSender).backgroundWorker(0xc42031e380, 0xc4201c6f00, 0xc4201c6f60) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /data/mci/269e09d73d98cfec0ed8b82bd108f49e/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send/buffered.go:113 +0x119 fp=0xc4205fdf98 sp=0xc4205fdf30 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: runtime.goexit() Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/runtime/asm_amd64.s:2086 +0x1 fp=0xc4205fdfa0 sp=0xc4205fdf98 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: created by github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.(*bufferedSender).backgroundDispatcher Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /data/mci/269e09d73d98cfec0ed8b82bd108f49e/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send/buffered.go:65 +0xed Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: goroutine 1 [IO wait]: Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: net.runtime_pollWait(0x7f842ac5bea8, 0x72, 0x0) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/runtime/netpoll.go:160 +0x59 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: net.(*pollDesc).wait(0xc4201f1b10, 0x72, 0xc4204d18b0, 0xc420012180) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/net/fd_poll_runtime.go:73 +0x38 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: net.(*pollDesc).waitRead(0xc4201f1b10, 0x1f93920, 0xc420012180) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/net/fd_poll_runtime.go:78 +0x34 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: net.(*netFD).accept(0xc4201f1ab0, 0x0, 0x1f90e60, 0xc4207ee7e0) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/net/fd_unix.go:419 +0x238 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: net.(*TCPListener).accept(0xc4201aca08, 0x433dce, 0xc4204d1960, 0x4d108d) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/net/tcpsock_posix.go:132 +0x2e Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: net.(*TCPListener).Accept(0xc4201aca08, 0x1646388, 0xc42038c200, 0x1f988a0, 0xc420193d70) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/net/tcpsock.go:222 +0x49 Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: net/http.(*Server).Serve(0xc4204ac280, 0x1f97ae0, 0xc4201aca08, 0x0, 0x0) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /opt/go/src/net/http/server.go:2273 +0x1ce Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: github.com/evergreen-ci/evergreen/vendor/gopkg.in/tylerb/graceful%2ev1.(*Server).Serve(0xc4204b9b60, 0x1f97ae0, 0xc4201aca08, 0x5, 0x1f97ae0) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /data/mci/269e09d73d98cfec0ed8b82bd108f49e/gopath/src/github.com/evergreen-ci/evergreen/vendor/gopkg.in/tylerb/graceful.v1/graceful.go:197 +0x23c Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: github.com/evergreen-ci/evergreen/vendor/gopkg.in/tylerb/graceful%2ev1.(*Server).ListenAndServe(0xc4204b9b60, 0xc4204ac280, 0xc420499ba0) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /data/mci/269e09d73d98cfec0ed8b82bd108f49e/gopath/src/github.com/evergreen-ci/evergreen/vendor/gopkg.in/tylerb/graceful.v1/graceful.go:110 +0xae Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: github.com/evergreen-ci/evergreen/vendor/gopkg.in/tylerb/graceful%2ev1.Run(0xc4201b7090, 0x5, 0x2540be400, 0x1f8c020, 0xc420193c20) Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /data/mci/269e09d73d98cfec0ed8b82bd108f49e/gopath/src/github.com/evergreen-ci/evergreen/vendor/gopkg.in/tylerb/graceful.v1/graceful.go:78 +0x10e Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: main.main() Jul 26 14:19:49 evergreenapp-1.staging.build.10gen.cc evergreen_ui_server[9575]: /data/mci/269e09d73d98cfec0ed8b82bd108f49e/gopath/src/github.com/evergreen-ci/evergreen/service/ui_main/ui.go:100 +0xa4b ",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-1906","07/26/2017 17:10:26",1,"Reachability check ssh command doesn't use the same options as other ssh commands ""We started to add {{UserKnownHostsFile=/dev/null}} to ssh options in [this commit|https://github.com/evergreen-ci/evergreen/commit/8ee7f60f243acbb4fdc8f2131e10458c3def80a7#diff-6a305ad019927e85a72e8ffc3842a4b0R536] but it doesn't look like it applies to the reachability checks. And it causes issues sometimes.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1910","07/28/2017 17:22:34",2,"Write documentation for API v2 routes related to Version and Build Cost Reporting ""Version related routes: * EVG-1741: GET /versions/ * EVG-1746: POST /versions//abort * EVG-1747: POST /versions/version-id/restart * EVG-1735: GET /versions/version-id/builds Cost related routes: * EVG-1778: GET cost/version/ * EVG-1894: GET cost/projects//tasks with time info * EVG-1878: GET cost/distro/ with time info ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1911","07/28/2017 19:58:15",1,"push sysinfo data to logs on a regular loop in all services. ""runner and api server. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1912","07/28/2017 22:26:40",1,"Provision failed status has unreadable white font ""Due to the label css class overriding the grey color we want""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1913","07/29/2017 00:36:49",2,"set JOB_OBJECT_LIMIT_KILL_ON_JOB_CLOSE for process termination ""on windows ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1920","07/31/2017 22:42:49",2,"Provide global system task status count over time via status endpoint ""This query would potentially be extremely useful to monitor. We could alert on it (maybe) or just manually check it to gauge the effects of things like network changes, infrastructure changes, or deploys. At least # of """"system unresponsive"""" tasks in the past 30 minutes would be useful. To add to that it would be nice to override the time period, and to list all statuses, not just system unresponsive. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1921","07/31/2017 22:47:45",2,"Splunk Logging Client Creates Backpressure in Agent ""Grapes. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1923","08/01/2017 11:21:10",2,"lint failures ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_lint_1201c83d28d1e43c4baf2fe854644398d879f2f6_17_07_31_22_14_33/0] Host: [ec2-54-160-246-44.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-2vq87b3g] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *lint-agent* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-agent=fail] *lint-cli* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-cli=fail] *lint-taskrunner* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-taskrunner=fail] *lint-plugin* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin=fail] *lint-hostinit* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-hostinit=fail] *lint-plugin-builtin-keyval* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-keyval=fail] *lint-plugin-builtin-git* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-git=fail] *lint-plugin-builtin-gotest* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-gotest=fail] *lint-plugin-builtin-attach* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-attach=fail] *lint-plugin-builtin-manifest* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-manifest=fail] *lint-plugin-builtin-archive* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-archive=fail] *lint-plugin-builtin-shell* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-shell=fail] *lint-plugin-builtin-s3copy* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-s3copy=fail] *lint-plugin-builtin-expansions* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-expansions=fail] *lint-plugin-builtin-s3* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-plugin-builtin-s3=fail] *lint-notify* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-notify=fail] *lint-thirdparty* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-thirdparty=fail] *lint-scheduler* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-scheduler=fail] *lint-model* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-model=fail] *lint-validator* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-validator=fail] *lint-service* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-service=fail] *lint-monitor* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-monitor=fail] *lint-repotracker* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-repotracker=fail] *lint-cloud-providers* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-cloud-providers=fail] *lint-cloud-providers-vsphere* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-cloud-providers-vsphere=fail] *lint-rest-client* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-rest-client=fail] *lint-rest-data* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-rest-data=fail] *lint-rest-route* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-rest-route=fail] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-1924","08/01/2017 13:17:27",2,"Task links on host page point only to latest execution ""Instead of linking to the execution that ran on the given host. For example, on [the host page for host *_sir-92v86p9h_*|https://evergreen.mongodb.com/host/sir-92v86p9h], there's a link to [this task|https://evergreen.mongodb.com/task/mongodb_mongo_v3.4_enterprise_debian81_64_jsCore_auth_bca21d14a4f25d7884d1f56d2e6ff02e334c9578_17_07_27_19_10_29], which is the latest execution, and ran on *_sir-91xg5wik_*, not *_sir-92v86p9h_*. It should link to [this task|https://evergreen.mongodb.com/task/mongodb_mongo_v3.4_enterprise_debian81_64_jsCore_auth_bca21d14a4f25d7884d1f56d2e6ff02e334c9578_17_07_27_19_10_29/2] instead.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1927","08/01/2017 20:58:57",1,"Vendor Docker golang library ""Docker and Go have changed a lot since 2015. We've been using this library: github.com/fsouza/go-dockerclient We should use this fancy new official one instead: github.com/docker/docker f7d09a0a9bd626782e63e7295ca87690f26a1fb4 We also need this to configure Docker networking options: github.com/docker/go-connections 3ede32e2033de7505e6500d6c868c2b9ed9f169d The annoying thing is that when I try to import both packages as is, I get the vendoring issue that is document at [https://github.com/moby/moby/issues/28269]. A workaround I found is to remove the nested vendor dir at """"evergreen/vendor/github.com/docker/docker/vendor/github.com/docker/go-connections"""" so that imports would properly reference the dir at """"evergreen/vendor/github.com/docker/go-connections"""". Maybe there's a cleaner solution?""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1929","08/02/2017 14:57:44",1,"remove or revive Digital Ocean Host Provider ""We're using the old API for this provider, so any requests to them return """"API v1 has reached end-of-life. Please use API v2."""" https://developers.digitalocean.com/documentation/changelog/api-v1/api-v1-end-of-life/""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1937","08/02/2017 19:24:33",1,"evergreen --help prints out help message twice ""Looks like there's extra logging going on. Affects this version: """," ksuarz@celadon:~/code/mongo ♥ evergreen --help Usage: evergreen [OPTIONS] Application Options: -c, --config= path to config file (defaults to ~/.evergreen.yml) Help Options: -h, --help Show this help message Available commands: agent runs an evergreen agent cancel-patch cancel an existing patch evaluate display a project file's evaluated and expanded form export export statistics as csv or json for given options fetch fetch data associated with a task finalize-patch finalize an existing patch get-update fetch the latest version of this binary last-green return a project's most recent successful version for given variants list list available projects, tasks, or variants list-patches show existing patches patch submit a patch patch-file submit a patch using a diff file rm-module remove a module from an existing patch set-module update or add module to an existing patch test-history retrieve test history for a given project validate validate a config file version display version information [evergreen] 2017/08/02 14:21:14 [p=emergency]: Usage: evergreen [OPTIONS] Application Options: -c, --config= path to config file (defaults to ~/.evergreen.yml) Help Options: -h, --help Show this help message Available commands: agent runs an evergreen agent cancel-patch cancel an existing patch evaluate display a project file's evaluated and expanded form export export statistics as csv or json for given options fetch fetch data associated with a task finalize-patch finalize an existing patch get-update fetch the latest version of this binary last-green return a project's most recent successful version for given variants list list available projects, tasks, or variants list-patches show existing patches patch submit a patch patch-file submit a patch using a diff file rm-module remove a module from an existing patch set-module update or add module to an existing patch test-history retrieve test history for a given project validate validate a config file version display version information ksuarz@celadon:~/code/mongo ♥ evergreen version 2017-06-29 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1938","08/02/2017 20:15:55",1,"APITask's TimeTaken and ExpectedDuration fields are in nanoseconds, not milliseconds ""*Problem background:* {{APITask}} defined in rest/model/task.go has fields named {{TimeTaken}} and {{ExpectedDuration}} that are of type {{time.Duration}}. The JSON tags (""""{{time_taken_ms}}"""" & """"{{expected_duration_ms}}"""") as well as the documentation describe them to be in milliseconds, but the code does not convert the values from nanoseconds to milliseconds. 1) In {{Task}} model, the values are set in nanoseconds. - In {{func MarkEnd()}}, {{TimeTaken}} is set by doing {{t.TimeTaken = finishTime.Sub(t.StartTime)}}, which produces duration in an int64 nanosecond count. - In {{func ExpectedTaskDuration()}}, {{ExpectedDuration}} is set by: {{expDuration := time.Duration(result.ExpectedDuration) * time.Nanosecond}}. {{result.ExpectedDuration}} is expected to be in nanoseconds, and since {{time.Nanosecond}} = 1, this does not convert the value correctly. 2) In APITask, the values from Task are carried over without conversion. *Immediate Problem:* There is an inconsistency between the code and the JSON tag & documentation regarding time unit. *Long-term Problem:* Since we would like {{TimeTaken}} and {{ExpectedDuration}} to be in ms instead of ns, the code should implement conversion. Moreover, in the process of data migration, existing data should also be converted accordingly. """," TimeTaken: v.TimeTaken, ExpectedDuration: v.ExpectedDuration ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1940","08/03/2017 22:28:55",1,"Add a log viewer with rich functionality ""Currently evergreen allow to view logs as HTML or raw text. Server developers can benefit from the additional functionality when investigating build failures. Such functionality may be divided into the group that needs server support and the group that does not the latter include features: - regexp filters on the log lines - regexp search - formatting BSON objects - bookmarking - hide columns of the log (vertical filtering) - order by contents of columns of the log the former is - jump to the code line that printed the log message in github repo - connect commands that spawn multiple processes (i.e mongos -> shard -> config server -> shard) etc There is a POC of such viewer that implements - regexp filters on the log lines and - jumping to the code line that printed the log message The POC is a client side react project so it can be easily added to evergreen log view buttons as a third option.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0 +"EVG-1941","08/04/2017 00:42:24",1,"evergreen metrics endpoints panic service ""saw this in staging after playing with the metrics endpoint: {{http: panic serving 52.21.89.200:61105: interface conversion: interface {} is route.taskMetricsArgs, not *route.taskMetricsArgs}} ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1943","08/05/2017 19:50:38",1,"TestInvalidTimesAsKeyShouldError ""h2. [test-rest-route failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_rest_route_f7b33dbc7857ab39db8d8143d235e25fc96a551c_17_08_05_18_03_38/0] Host: [ec2-54-146-26-86.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-ie7r75ig] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestInvalidTimesAsKeyShouldError* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-rest-route#TestInvalidTimesAsKeyShouldError=fail] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-1944","08/07/2017 14:49:16",1,"glide.lock file has errors: upgrade testify everywhere ""Vendoring dependencies works fine using glide as of 23f6a9d8e774f597faabae8b58b8c6020b3f79ef, but errors for later versions of glide (confirmed for version 0.13.0-dev installed with brew). {panel:title=Error Message} [ERROR] Failed to set version on github.com/davecgh/go-spew to 260b7a32dd8770eb5ba41da17d125914ae064ef8: Unable to update checked out version [ERROR] Failed to set version on github.com/stretchr/objx to 260b7a32dd8770eb5ba41da17d125914ae064ef8: Unable to update checked out version [ERROR] Failed to set version on github.com/stretchr/testify to 260b7a32dd8770eb5ba41da17d125914ae064ef8: Unable to update checked out version [ERROR] Failed to set version on github.com/stretchr/objx to 260b7a32dd8770eb5ba41da17d125914ae064ef8: Unable to update checked out version {panel} Specifically, the glide.lock file uses the same commit hash for the 4 codebases above, and that commit hash does not actually exist in any of the codebases. We should find and replace those hashes with real commit hashes, and check that the lock file is compatible with newer versions of glide that catch this error.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1947","08/07/2017 21:11:54",1,"Logkeeper shouldn't make everything italic in CSS ""This makes the output harder to read.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-1948","08/08/2017 22:10:54",2,"race-proto failure ""h2. [race-proto failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_proto_21447c8c37c9f82b891a0f3c10a55a97de317e95_17_08_07_21_43_48/0] Host: [ec2-54-80-90-168.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-ghw87a4j] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-1951","08/09/2017 15:28:43",1,"prioritize tasks that have spent more time in the queue. ""to avoid the starvation case where tasks hang out in the middle of the queue.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1952","08/09/2017 16:52:56",1,"force http service to timeout large requests ""to avoid leaving request workers hanging when requests timeout. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1954","08/09/2017 20:53:52",2,"Git get_project command creates wrong directory before cloning module ""The git get_project command, before cloning a module, runs a {mkdir -p}} ({{os.MkdirAll(...)}}) command on the path where it will clone the module repository. The path used for {{mkdir}} does not match the path used to clone the module repository. The path used for {{mkdir}} is: {{conf.WorkDir/module.Prefix/module.Name/...}}. The path used to clone the module repository is: {{conf.WorkDir/Directory/module.Prefix/module.Name/}}, {{Directory}} being the directory where the project repository was cloned. This does not impact the cloning of the module repository, but it leaves an unexpected empty path (e.g. {{mongo/db/modules/enterprise/}}) in the project directory that causes a error when trying to copy the {{mongo}} binary into the project directory.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1959","08/10/2017 19:58:45",1,"A GET requests to /rest/v2/tasks/{task-id}/tests endpoint is returning 404 ""Even though there are tests for a given task, this REST endpoint returns 404. For example: This 404 error is returned in patch and mainline builds."""," {""""status"""":404,""""error"""":""""tests for task with taskId 'mongodb_mongo_master_enterprise_rhel_62_64_bit_dbg_off_sharding_MMAPv1_patch_9f2e54384d90ab0c533c6d311337d6bcc8fb5679_598ac2b3e3c331791100003b_17_08_09_08_08_28' not found""""} ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1962","08/11/2017 02:11:47",1,"increase batchtime massively for osx/zap builds ""also disable stepback for these variants. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1965","08/11/2017 21:06:07",2,"Modify Each Existing Runner Process to Check Flags Before Each Run ""Include each runner process listed in runner/registry.go as well as stopping task dispatching. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1975","08/11/2017 21:25:41",1,"Add button to admin page to restart tasks that failed/system failed during the degraded period ""Expand on the functionality for bulk restarting of tasks that exists for versions and builds today.""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-1978","08/14/2017 03:13:34",1,"services should log to standard out if no log file is configured ""(e.g. let the sytemd journal take everything, not have to log rotate on boxes) ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1979","08/14/2017 03:20:31",2,"create ""service"" subcommand to start UI or API srever ""- could create symlinks or shell wrappers in the tarball, so we could begin the merged binary transition sooner. - see if its easy to get rid of EVGHOME ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1984","08/14/2017 16:12:03",1,"Build Baron Jira plugin not working ""In the build baron plugin on a given evergreen task page, the plugin always returns """"No results found matching task or tests"""" rather than a list of related tickets.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1986","08/14/2017 18:39:56",2,"TestSubtreeCleanup ""h2. [test-subprocess failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_subprocess_55bd39c7c3cbca05713203c10b07fd269ec80ab6_17_08_14_16_33_22/0] Host: [ec2-54-227-224-67.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-a91i7sqh] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestSubtreeCleanup* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-subprocess#TestSubtreeCleanup=fail] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-1987","08/14/2017 22:42:29",1,"Agent is hitting max open files on static boxes ""Even though max open files limit is high, I see evergreen agent hitting it lsof output looks like this agent logs""","$ sudo cat /proc/16647/limits Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 64000 64000 processes Max open files 64000 64000 files Max locked memory 1048576 1048576 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 261347 261347 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us $ ps -ef | grep 16647 mci-exec 3139 16647 0 12:41 ? 00:00:00 [sh] mci-exec 3142 16647 0 12:41 ? 00:00:00 [sh] mci-exec 3144 16647 0 12:41 ? 00:00:00 [sh] mci-exec 9404 16647 0 10:10 ? 00:00:00 [sh] mci-exec 9407 16647 0 10:10 ? 00:00:00 [sh] mci-exec 9410 16647 0 10:10 ? 00:00:00 [sh] mci-exec 10857 16647 0 10:46 ? 00:00:00 [sh] mci-exec 10859 16647 0 10:46 ? 00:00:00 [sh] mci-exec 10861 16647 0 10:46 ? 00:00:00 [sh] mci-exec 11010 16647 0 11:28 ? 00:00:00 [sh] mci-exec 11012 16647 0 11:28 ? 00:00:00 [sh] mci-exec 11015 16647 0 11:28 ? 00:00:00 [sh] mci-exec 11698 16647 0 18:41 ? 00:00:00 [sh] mci-exec 11704 16647 0 18:41 ? 00:00:04 [sh] mci-exec 16647 1 56 Aug13 ? 14:02:00 /data/mci/evergreen agent --api_server=https://evergreen.mongodb.com --host_id=ubuntu1604-ppc-3.pic.build.10gen.cc --host_secret=xxxxxxxxxxxxxxxxx --log_prefix=/data/mci/agent mci-exec 18854 16647 0 17:29 ? 00:00:00 [sh] mci-exec 18860 16647 0 17:29 ? 00:00:00 [sh] mci-exec 19959 16647 0 13:39 ? 00:00:00 [sh] mci-exec 19964 16647 0 13:39 ? 00:00:08 [sh] mci-exec 19968 16647 0 13:39 ? 00:00:00 [sh] mci-exec 20095 16647 0 07:37 ? 00:00:00 [sh] mci-exec 20096 16647 0 07:37 ? 00:00:00 [sh] mci-exec 20098 16647 0 07:37 ? 00:00:00 [sh] mci-exec 20408 16647 0 08:24 ? 00:00:00 [sh] mci-exec 20410 16647 0 08:24 ? 00:00:00 [sh] mci-exec 20412 16647 0 08:24 ? 00:00:00 [sh] mci-exec 23931 16647 0 17:19 ? 00:00:00 [sh] mci-exec 23939 16647 0 17:19 ? 00:00:00 [sh] mci-exec 23948 16647 0 12:11 ? 00:00:00 [sh] mci-exec 23952 16647 0 12:11 ? 00:00:00 [sh] mci-exec 23956 16647 0 12:11 ? 00:00:00 [sh] mci-exec 25007 16647 0 12:57 ? 00:00:00 [sh] mci-exec 25011 16647 0 12:57 ? 00:00:00 [sh] mci-exec 25013 16647 0 12:57 ? 00:00:00 [sh] mci-exec 25687 16647 0 16:57 ? 00:00:00 [sh] mci-exec 25692 16647 0 16:57 ? 00:00:00 [sh] mci-exec 27358 16647 0 08:52 ? 00:00:00 [sh] mci-exec 27360 16647 0 08:52 ? 00:00:01 [sh] mci-exec 27362 16647 0 08:52 ? 00:00:00 [sh] mci-exec 28300 16647 0 16:58 ? 00:00:00 [sh] mci-exec 28306 16647 0 16:58 ? 00:00:00 [sh] mci-exec 28692 16647 0 08:28 ? 00:00:00 [sh] mci-exec 28694 16647 0 08:28 ? 00:00:00 [sh] mci-exec 28697 16647 0 08:28 ? 00:00:00 [sh] mci-exec 29280 16647 0 09:36 ? 00:00:00 [sh] mci-exec 29282 16647 0 09:36 ? 00:00:00 [sh] mci-exec 29285 16647 0 09:36 ? 00:00:00 [sh] mci-exec 31626 16647 0 08:29 ? 00:00:00 [sh] mci-exec 31628 16647 0 08:29 ? 00:00:00 [sh] mci-exec 31632 16647 0 08:29 ? 00:00:00 [sh] mci-exec 32726 16647 0 08:30 ? 00:00:00 [sh] mci-exec 32728 16647 0 08:30 ? 00:00:00 [sh] mci-exec 32731 16647 0 08:30 ? 00:00:00 [sh] mci-exec 33826 16647 0 17:45 ? 00:00:00 [sh] mci-exec 33832 16647 0 17:45 ? 00:00:00 [sh] mci-exec 33836 16647 0 18:09 ? 00:00:00 [sh] mci-exec 33846 16647 0 18:09 ? 00:00:00 [sh] mci-exec 36753 16647 0 11:49 ? 00:00:00 [sh] mci-exec 36757 16647 0 11:49 ? 00:00:00 [sh] mci-exec 36759 16647 0 11:49 ? 00:00:00 [sh] mci-exec 36804 16647 0 07:46 ? 00:00:00 [sh] mci-exec 36806 16647 0 07:46 ? 00:00:00 [sh] mci-exec 36808 16647 0 07:46 ? 00:00:00 [sh] mci-exec 37101 16647 0 10:24 ? 00:00:00 [sh] mci-exec 37104 16647 0 10:24 ? 00:00:00 [sh] mci-exec 37106 16647 0 10:24 ? 00:00:00 [sh] mci-exec 37231 16647 0 07:47 ? 00:00:00 [sh] mci-exec 37233 16647 0 07:47 ? 00:00:00 [sh] mci-exec 37236 16647 0 07:47 ? 00:00:00 [sh] mci-exec 40357 16647 0 10:58 ? 00:00:00 [sh] mci-exec 40360 16647 0 10:58 ? 00:00:01 [sh] mci-exec 40362 16647 0 10:58 ? 00:00:00 [sh] $ sudo lsof | grep 16647 | wc 3904183 42881522 398226910evergreen 16647 16661 mci-exec 8121u sock 0,8 0t0 139932354 protocol: TCP evergreen 16647 16661 mci-exec 8122u sock 0,8 0t0 139936364 protocol: TCP evergreen 16647 16661 mci-exec 8123u sock 0,8 0t0 139951587 protocol: TCP evergreen 16647 16661 mci-exec 8124u sock 0,8 0t0 139935422 protocol: TCP evergreen 16647 16661 mci-exec 8125u sock 0,8 0t0 139958379 protocol: TCP evergreen 16647 16661 mci-exec 8126u sock 0,8 0t0 139944428 protocol: TCP evergreen 16647 16661 mci-exec 8127u sock 0,8 0t0 139951657 protocol: TCP evergreen 16647 16661 mci-exec 8128u sock 0,8 0t0 139936395 protocol: TCP evergreen 16647 16661 mci-exec 8129u sock 0,8 0t0 139948536 protocol: TCP evergreen 16647 16661 mci-exec 8130u sock 0,8 0t0 139918209 protocol: TCP evergreen 16647 16661 mci-exec 8131u sock 0,8 0t0 139951665 protocol: TCP evergreen 16647 16661 mci-exec 8132u sock 0,8 0t0 139942495 protocol: TCP evergreen 16647 16661 mci-exec 8133u sock 0,8 0t0 139946359 protocol: TCP evergreen 16647 16661 mci-exec 8134u sock 0,8 0t0 139959383 protocol: TCP evergreen 16647 16661 mci-exec 8135u sock 0,8 0t0 139946360 protocol: TCP evergreen 16647 16661 mci-exec 8136u sock 0,8 0t0 139951626 protocol: TCP evergreen 16647 16661 mci-exec 8137u sock 0,8 0t0 139951694 protocol: TCP[evg-agent] 2017/08/14 21:40:36 [p=notice]: json: unsupported value: NaN [evg-agent] 2017/08/14 21:40:36 [p=debug]: [evg-agent] 2017/08/14 21:40:36 [p=notice]: json: unsupported value: NaN [evg-agent] 2017/08/14 21:40:36 [p=notice]: Post https://evergreen.mongodb.com/api/2/task/cloud_automation_profiling_ubuntu16_power_LinuxTestGroup18_1edf3a6027fad776944a7dc45cb9f99645dcbafb_17_08_14_20_30_24/process_info: dial tcp: lookup evergreen.mongodb.com on 8.8.8.8:53: dial udp 8.8.8.8:53: socket: too many open files [evg-agent] 2017/08/14 21:40:36 [p=notice]: Post https://evergreen.mongodb.com/api/2/task/cloud_automation_profiling_ubuntu16_power_LinuxTestGroup18_1edf3a6027fad776944a7dc45cb9f99645dcbafb_17_08_14_20_30_24/process_info: dial tcp: lookup evergreen.mongodb.com on 8.8.8.8:53: dial udp 8.8.8.8:53: socket: too many open files [evg-agent] 2017/08/14 21:40:36 [p=notice]: Post https://evergreen.mongodb.com/api/2/task/cloud_automation_profiling_ubuntu16_power_LinuxTestGroup18_1edf3a6027fad776944a7dc45cb9f99645dcbafb_17_08_14_20_30_24/process_info: dial tcp: lookup evergreen.mongodb.com on 8.8.8.8:53: dial udp 8.8.8.8:53: socket: too many open files [evg-agent] 2017/08/14 21:40:37 [p=notice]: Post https://evergreen.mongodb.com/api/2/task/cloud_automation_profiling_ubuntu16_power_LinuxTestGroup18_1edf3a6027fad776944a7dc45cb9f99645dcbafb_17_08_14_20_30_24/process_info: dial tcp: lookup evergreen.mongodb.com on 8.8.8.8:53: dial udp 8.8.8.8:53: socket: too many open files [evg-agent] 2017/08/14 21:40:38 [p=notice]: json: unsupported value: NaN",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1988","08/14/2017 23:49:05",2,"Junit errors must include system-out field ""The JUnit parser should include {{}} from the test as well as the error. For example, when you click the """"HTML"""" or """"Raw"""" for the failing test here: https://evergreen.mongodb.com/task/mms_int_INT_JAVA_MMS_027f21ea449448e16c29d4f8ffd8d5559badbc0b_17_08_14_14_21_29 You see only the {{}} in https://evergreen.mongodb.com/test_log/mms_int_INT_JAVA_MMS_027f21ea449448e16c29d4f8ffd8d5559badbc0b_17_08_14_14_21_29/0/com.xgen.svc.mms.api.res.ApiUsersResourceIntTests.testDeleteUser not the {{}} Appending the {{}} to the error output would be greatly useful. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1991","08/16/2017 15:19:24",2,"Can't spawn hosts with a new key from the UI ""Saved keys work, and you can spawn with a new key from the CLI""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1997","08/18/2017 17:16:34",2,"Allow authenticated users to reconfigure other people's patches ""Every so often we have patches for WiredTiger drops or custom builds that need to have a variant or two added for testing or delivery purposes. When this happens, if the original author of the patch is not around we need an admin to do it. I think it should be ok for users to reconfigure other people's patches.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-1999","08/21/2017 21:07:35",1,"Avoid removing task directory before the post-tasks run. ""I noticed that when a task gets aborted, the agent removes the task directory before the post-tasks run so if something in post-tasks tries to use a file or folder in the task directory, it will logically fail and the task will be marked as failed instead of aborted. Example - https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_aggregation_WT_ese_27c4847e65a0162897ad72a3a39636ac7bd3cf67_17_08_14_21_52_45 It's not clear that this task was aborted though because of EVG-55, I just happen to know that the entire build was indeed aborted.""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-2002","08/22/2017 17:23:26",2,"improve cancelation of runners ""use more contexts""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2003","08/22/2017 20:49:43",2,"log recent task statuses ""like /api/status/recent_tasks but to the log. in the runner. some reasonable task status ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2005","08/24/2017 15:22:40",1,"add ability to abort build while unscheduling ""We already have this feature for versions; it would be nice to have it for builds as well.""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2009","08/25/2017 16:52:42",2,"test-proto failure "" h2. [test-proto failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_proto_115cd9f9e9a6328579240810dc85839e2fbfb28e_17_08_25_00_27_39/0] Host: [ec2-54-161-255-88.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-4av87v5h] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2014","08/25/2017 22:05:32",2,"Task history endpoint needs to do limits last in its query "" {code:json} [ { """"$match"""" : { """"branch"""" : """"mongodb-mongo-master"""", """"r"""" : """"gitter_request"""", """"$or"""" : [ { """"details.timed_out"""" : { """"$ne"""" : true }, """"details.type"""" : { """"$ne"""" : """"system"""" }, """"status"""" : { """"$in"""" : [ """"failed"""" ] } } ], """"test_results.test_file"""" : { """"$in"""" : [ """"jstests/sharding/config_version_rollback.js"""" ] }, """"start_time"""" : { """"$gte"""" : ISODate(""""2017-08-01T00:00:00Z"""") }, } }, { """"$limit"""" : 10 }, { """"$project"""" : { """"status"""" : 1, """"test_results"""" : 1, """"start_time"""" : 1, """"details"""" : 1, """"display_name"""" : 1, """"build_variant"""" : 1, """"execution"""" : 1, """"order"""" : 1, """"old_task_id"""" : 1, """"branch"""" : 1, """"gitspec"""" : 1, """"_id"""" : 1 } }, { """"$unwind"""" : """"$test_results"""" }, { """"$match"""" : { """"test_results.status"""" : { """"$in"""" : [ """"fail"""" ] }, """"test_results.test_file"""" : { """"$in"""" : [ """"jstests/sharding/config_version_rollback.js"""" ] } } }, { """"$sort"""" : { """"order"""" : -1, """"test_results.test_file"""" : -1 } }, { """"$project"""" : { """"lid"""" : """"$test_results.log_id"""", """"tdt"""" : """"$details.type"""", """"test_status"""" : """"$test_results.status"""", """"task_status"""" : """"$status"""", """"st"""" : """"$test_results.start"""", """"et"""" : """"$test_results.end"""", """"to"""" : """"$details.timed_out"""", """"tid"""" : """"$_id"""", """"r"""" : """"$gitspec"""", """"p"""" : """"$branch"""", """"tn"""" : """"$display_name"""", """"ex"""" : """"$execution.execution"""", """"url"""" : """"$test_results.url"""", """"tf"""" : """"$test_results.test_file"""", """"otid"""" : """"$old_task_id"""", """"url_r"""" : """"$test_results.url_raw"""", """"bv"""" : """"$build_variant"""" } } ] {code} """," [ { """"$match"""" : { """"branch"""" : """"mongodb-mongo-master"""", """"r"""" : """"gitter_request"""", """"$or"""" : [ { """"details.timed_out"""" : { """"$ne"""" : true }, """"details.type"""" : { """"$ne"""" : """"system"""" }, """"status"""" : { """"$in"""" : [ """"failed"""" ] } } ], """"test_results.test_file"""" : { """"$in"""" : [ """"jstests/sharding/config_version_rollback.js"""" ] }, """"start_time"""" : { """"$gte"""" : ISODate(""""2017-08-01T00:00:00Z"""") }, } }, { """"$limit"""" : 10 }, { """"$project"""" : { """"status"""" : 1, """"test_results"""" : 1, """"start_time"""" : 1, """"details"""" : 1, """"display_name"""" : 1, """"build_variant"""" : 1, """"execution"""" : 1, """"order"""" : 1, """"old_task_id"""" : 1, """"branch"""" : 1, """"gitspec"""" : 1, """"_id"""" : 1 } }, { """"$unwind"""" : """"$test_results"""" }, { """"$match"""" : { """"test_results.status"""" : { """"$in"""" : [ """"fail"""" ] }, """"test_results.test_file"""" : { """"$in"""" : [ """"jstests/sharding/config_version_rollback.js"""" ] } } }, { """"$sort"""" : { """"order"""" : -1, """"test_results.test_file"""" : -1 } }, { """"$project"""" : { """"lid"""" : """"$test_results.log_id"""", """"tdt"""" : """"$details.type"""", """"test_status"""" : """"$test_results.status"""", """"task_status"""" : """"$status"""", """"st"""" : """"$test_results.start"""", """"et"""" : """"$test_results.end"""", """"to"""" : """"$details.timed_out"""", """"tid"""" : """"$_id"""", """"r"""" : """"$gitspec"""", """"p"""" : """"$branch"""", """"tn"""" : """"$display_name"""", """"ex"""" : """"$execution.execution"""", """"url"""" : """"$test_results.url"""", """"tf"""" : """"$test_results.test_file"""", """"otid"""" : """"$old_task_id"""", """"url_r"""" : """"$test_results.url_raw"""", """"bv"""" : """"$build_variant"""" } } ] ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2186","08/28/2017 16:07:13",1,"On Windows a GET request to Evergreen /status endpoint consistently returns after > 40 seconds. ""As part of the buildscripts/collect_resource_info.py script to collect system resource usage info, we make a GET request to the /status Evergreen endpoint every 5 seconds. We expect this call to return immediately, however, based on our testing on Windows, it shows the request consistently takes over 40 seconds to return. Here is an example: https://evergreen.mongodb.com/task/mongodb_mongo_master_windows_64_2k8_debug_off_replica_sets_initsync_static_jscore_passthrough_MMAPv1_patch_5dcaad5f137eebc1915c0fc7b5078da4aa86f915_59a0b8b8c9ec440568014edd_17_08_25_23_54_46#/log/S In the {{System Resource Info - Execution 0}} link I've added a {{duration}} field to each document returned. This measures the time in seconds between sending the GET request and receiving the response.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2015","08/28/2017 17:26:31",2,"/tasks//tests endpoint does not form previous page correctly ""When querying for the previous page, we do a pipeline like this, which does not return the document that we want to start on within the results (in this case we started on TestGetDNSNameAPICall) This returns the following document (the exact results of the previous query) { """"line_num"""" : 1, """"exit_code"""" : 0, """"log_id"""" : """"598be3eb9dbe3244ba0000ab"""", """"test_file"""" : """"TestConfigureAPICall"""", """"start"""" : 1502340075, """"end"""" : 1502340075, """"status"""" : """"pass"""" } However this gets filtered out by this block of code, so we never create the previous page """," [ { """"$match"""" : { """"_id"""" : """"mci_rhel62_gccgo_test_cloud_providers_openstack_cea29ff7ceb60a2b4ed7e52223be5a213ec6588c_17_08_09_22_12_28"""" } }, { """"$unwind"""" : """"$test_results"""" }, { """"$project"""" : { """"line_num"""" : """"$test_results.line_num"""", """"exit_code"""" : """"$test_results.exit_code"""", """"url"""" : """"$test_results.url"""", """"_id"""" : 0, """"log_id"""" : """"$test_results.log_id"""", """"test_file"""" : """"$test_results.test_file"""", """"url_raw"""" : """"$test_results.url_raw"""", """"start"""" : """"$test_results.start"""", """"end"""" : """"$test_results.end"""", """"status"""" : """"$test_results.status"""" } }, { """"$match"""" : { """"test_file"""" : { """"$lte"""" : """"TestGetDNSNameAPICall"""" } } }, { """"$sort"""" : { """"test_file"""" : 1 } }, { """"$limit"""" : 1 } ] if testFilename != """""""" { found := false for _, t := range res { if t.TestFile == testFilename { found = true break } } if !found { grip.Info(testFilename) return []task.TestResult{}, &rest.APIError{ StatusCode: http.StatusNotFound, Message: fmt.Sprintf(""""test with filename %s not found"""", testFilename), } } } ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2018","08/28/2017 21:27:13",1,"lint-proto "" h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_lint_c7175f35bd1976630705b06f8cdad85b46ed4735_17_08_28_13_45_50/0] Host: [ec2-54-145-89-248.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-fvn869bh] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *lint-proto* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-proto=fail] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-9612","08/28/2017 22:13:54",2,"describe periodic job for cost reporting collection ""might involve application with mongodb backed amboy queue. ""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9651","08/28/2017 22:26:58",1,"build system and test helpers for anser ""e.g. port the makefile""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2019","08/29/2017 00:05:15",1,"Test Timeouts showing up as System Failures ""Test timeouts seem to still be showing up as purple after the changes [this commit|https://github.com/evergreen-ci/evergreen/commit/83b35bf8ccf358a0774ff32ff52943abb04cd689] (EVG-1872, EVG-1608) https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_replica_sets_WT_ese_cee116558d7771b520c0fd4dd239c0a987dcc2ec_17_08_28_15_41_52 It's happening mostly with the the {{initial_sync_with_write_load.js}} test and seems to have started around August 23rd on RHEL 6 (but I haven't looked at enough data points to confirm this)""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2024","08/30/2017 16:21:07",1,"isprod flag in Evergreen settings file doesn't work ""The UI server is always setting it to true""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2027","08/31/2017 16:16:59",2,"Version errors (and probably warnings) don't display in UI ""On https://evergreen.mongodb.com/version/sys_perf_9a41a9d7cb22c29986fc3d66bb0a284c0b7c6c50#/0 the errors are supposed to display under the count of errors, but don't for some reason""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-9584","09/06/2017 20:54:59",1,"TestSingleWorkerSuite ""h2. [race-pool failed on race-detector|https://evergreen.mongodb.com/task/amboy_race_detector_race_pool_91247c9ebc9bd4e33d44e920b3e44363777435ef_17_08_11_16_08_36/0] Host: [ec2-54-197-120-146.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-43bi5jyg] Project: [amboy|https://evergreen.mongodb.com/waterfall/amboy] *TestSingleWorkerSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/amboy/race-pool#TestSingleWorkerSuite=fail] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,0,0,0,1,0,0 +"EVG-2032","09/08/2017 18:36:51",1,"test-rest-client failure ""h2. [test-rest-client failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_rest_client_f645d805a3830c2a5ea747bb2a682d7e72e2f3bf_17_09_08_15_45_52/0] Host: [ec2-54-211-227-89.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-x96r4qnj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2033","09/08/2017 19:05:44",2,"rest/v2/ endpoint for tasks by status in a recent time period ""default to 30m""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2034","09/08/2017 19:07:10",1,"remove shell script shims from evergreen deploy toolchain ""our deployed environments no longer depend upon them, so we should clean up the indirection. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2036","09/08/2017 21:57:10",2,"race-proto failure ""h2. [race-proto failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_proto_779d1fd69cb92952c1d5364b0050d7e5512a139a_17_09_08_19_59_14/0] Host: [ec2-54-198-104-119.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-v3sg7mmk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2038","09/09/2017 03:14:00",2,"evergreen web service should host api and ui routes ""we can have a single service listen on more than one port for now and later remove one of the ports. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2041","09/11/2017 14:50:39",2,"s3 command takes longer in new agent ""For example, [test-alerts took 20 seconds|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_alerts_cfbbe9b69bf097768e136a70abc6ad6dd62a7311_17_09_08_21_08_15] to run with the old agent but [2 minutes 22 seconds|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_alerts_7677ed72f6b91917629f50c40ae142b6c29346e3_17_09_09_02_54_17] to run with the new agent. The increase comes from the s3 puts: """," [2017/09/11 09:41:02.783] Script execution complete. [2017/09/11 09:41:02.783] Finished 'shell.exec' in """"run-make"""" in 31.006304265s [2017/09/11 09:41:02.783] Finished running task commands in 39.265331464s. [2017/09/11 09:41:02.831] Finished 'gotest.parse_files' in 45.061582ms [2017/09/11 09:41:03.381] retrying after error during putting to s3 bucket: [2017/09/11 09:41:08.409] retrying after error during putting to s3 bucket: [2017/09/11 09:41:13.642] retrying after error during putting to s3 bucket: [2017/09/11 09:41:24.391] retrying after error during putting to s3 bucket: [2017/09/11 09:41:47.258] retrying after error during putting to s3 bucket: [2017/09/11 09:41:47.258] Finished 's3.put' in 44.427181114s [2017/09/11 09:41:47.270] retrying after error during putting to s3 bucket: [2017/09/11 09:41:52.286] retrying after error during putting to s3 bucket: [2017/09/11 09:42:01.637] retrying after error during putting to s3 bucket: [2017/09/11 09:42:21.089] retrying after error during putting to s3 bucket: [2017/09/11 09:42:46.105] retrying after error during putting to s3 bucket: [2017/09/11 09:42:46.105] Finished 's3.put' in 58.846715583s ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9675","09/11/2017 23:19:10",2,"create model for aggregated/summation of bcr data ""potentially directly from the database, rather than against the API to avoid credentials issues. ""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2049","09/11/2017 23:40:48",2,"select a default project if specified project name does not exist ""sites must default to *some* project. if the config file specifies a """"wrong"""" project, then we should pick the first project (or something similar.) ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2067","09/12/2017 20:00:36",1,"Messages written to the task logs don't have leading whitespace preserved ""I suspect the new Evergreen agent is doing something like calling {{strings.Trim()}} or {{strings.TrimSpace()}} instead of {{strings.TrimRight()}}. https://evergreen.mongodb.com/task_log_raw/mongodb_mongo_master_enterprise_rhel_62_64_bit_aggregation_33cb4a950c5de3c1c783b25ecf0fd4454cce844a_17_09_12_17_37_00/0?type=T&text=true https://evergreen.mongodb.com/task_log_raw/mongodb_mongo_master_enterprise_rhel_62_64_bit_aggregation_c31e309846609b4309a72868db7eafc189f839ca_17_09_01_21_51_14/0?type=T&text=true"""," [2017/09/12 18:20:49.294] [resmoke] 2017-09-12T18:20:49.288+0000 YAML configuration of suite aggregation [2017/09/12 18:20:49.294] test_kind: js_test [2017/09/12 18:20:49.294] selector: [2017/09/12 18:20:49.294] roots: [2017/09/12 18:20:49.294] - jstests/aggregation/*.js [2017/09/12 18:20:49.294] - jstests/aggregation/bugs/*.js [2017/09/12 18:20:49.294] - jstests/aggregation/expressions/*.js [2017/09/12 18:20:49.294] - jstests/aggregation/sources/*/*.js [2017/09/12 18:20:49.294] - jstests/aggregation/variables/*.js [2017/09/01 23:22:05.730] [resmoke] 2017-09-01T23:22:05.729+0000 YAML configuration of suite aggregation [2017/09/01 23:22:05.731] test_kind: js_test [2017/09/01 23:22:05.731] selector: [2017/09/01 23:22:05.731] roots: [2017/09/01 23:22:05.731] - jstests/aggregation/*.js [2017/09/01 23:22:05.731] - jstests/aggregation/bugs/*.js [2017/09/01 23:22:05.731] - jstests/aggregation/expressions/*.js [2017/09/01 23:22:05.731] - jstests/aggregation/sources/*/*.js [2017/09/01 23:22:05.731] - jstests/aggregation/variables/*.js ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2070","09/12/2017 22:36:30",1,"Intermittent s3.put failures for optional uploads ""In the sqlproxy project, we have been observing occasional s3.put failures for files marked as optional. See [here|https://evergreen.mongodb.com/task/sqlproxy_single_variant__os_single_variant~debian81_sign_0ffa9f806c9f9f07cdf653799d0e86b5821519fd_17_09_11_20_02_29] for an example. [~adinoyi.omuya] took a look at the recent changes, and noted this: it looks like taking the attach file logic out of the retry loop made it so that when a local file doesn't exist, an s3.put operation now fails: see https://github.com/evergreen-ci/evergreen/blob/master/command/s3_put.go#L261 (what retry logic used to do)""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2071","09/13/2017 00:08:26",1,"TestCommandTestSuite, TestShellExec ""h2. [test-proto failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_proto_a4f9cf75b2e2d9e51faba4d900730d82857e00d9_17_09_12_21_31_20/0] Host: [ec2-54-211-4-223.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-9vcg7kjh] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestCommandTestSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-proto#TestCommandTestSuite=fail] *TestShellExec* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-proto#TestShellExec=fail] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2073","09/13/2017 12:53:34",2,"add s390/POWER/ARM tests that use cross compiled binaries ""support for this *mostly* exists in the form of dist-test, but there's some CI changes that we'd need to make to make this a reality. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2074","09/13/2017 13:57:58",2,"New Evergreen agent isn't performing task timeouts ""I noticed on the Evergreen waterfall page that there were fuzzer tasks taking 4 hours to run, but were considered """"failures"""" rather """"timeouts"""". https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_debian71_64_jstestfuzz_sharded_WT_27471dc703ea0144ce4419d0bb59a4d092877d24_17_09_12_18_06_18 https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_windows_64_2k8_jstestfuzz_concurrent_replication_c5e038cb5e25cfdd4037534d34ce0d4e11f5c1ec_17_09_12_21_40_29 The """"jstestfuzz*"""" Evergreen tasks [set their {{exec_timeout_secs}} to 4 hours|https://github.com/mongodb/mongo/blob/27471dc703ea0144ce4419d0bb59a4d092877d24/etc/evergreen.yml#L138] and [set their {{timeout_secs}} to 30 minutes|https://github.com/mongodb/mongo/blob/27471dc703ea0144ce4419d0bb59a4d092877d24/etc/evergreen.yml#L131]. # It doesn't appear that the idle timeout is being triggered after 30 minutes of not seeing resmoke.py write anything to its stdout pipe. # It doesn't appear that the """"timeout"""" section of the Evergreen project configuration file is being executed."""," [2017/09/12 22:37:01.924] [resmoke] 2017-09-12T22:37:01.923+0000 YAML configuration of suite jstestfuzz_replication ... [2017/09/12 22:39:07.482] [executor:js_test:job0] 2017-09-12T22:39:07.480+0000 Writing output of 72f2-mdb_c5e0-ent_42ab-qa_a6ce-1505255760149-02 to https://logkeeper.mongodb.org/build/014c4377fbee859bfe80696908dfdc6d/test/59b8620b904130379d01d545. [2017/09/13 02:34:44.612] Task completed - FAILURE. [2017/09/12 21:41:16.253] [resmoke] 2017-09-12T21:41:16.177+0000 YAML configuration of suite jstestfuzz_sharded ... [2017/09/12 21:55:56.708] [executor:js_test:job0] 2017-09-12T21:55:56.708+0000 Writing output of 72f2-mdb_2747-ent_42ab-qa_a6ce-1505252399046-084 to https://logkeeper.mongodb.org/build/59d45a90ad759db6b43d9785fcd774ca/test/59b857ec54f248607807fce0. [2017/09/13 01:39:40.751] Task completed - FAILURE. ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2076","09/13/2017 21:00:46",1,"evergreen patch should link to tasks when -f is given ""Currently, when you run an evergreen patch with the finalize option it gives you a link to the patch. Once you click on the link you are taken to a page which says: Which is not what you really want if you are giving the --finalize flag. It should instead just link you directly to the tasks status page."""," Tasks for this patch have already been scheduled. Modifying the configuration will update the patch to include additional tasks and variants. View Existing Tasks… ",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2083","09/15/2017 14:09:52",1,"TestDirectoryCleanup ""h2. [test-agent failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_agent_28483b573e858d2164715f948b82c831bb86e2e9_17_09_14_23_01_10/0] Host: [ec2-54-224-201-86.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-fy7g4nkg] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestDirectoryCleanup* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-agent#TestDirectoryCleanup=fail] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2084","09/15/2017 15:59:50",1,"TestFetchEBSPricing, TestEBSPriceCaching ""h2. [test-cloud-providers-ec2 failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_cloud_providers_ec2_cd6d70d2c248a96b3fa1f2a21ba025d536af5b16_17_09_15_13_41_22/0] Host: [ec2-54-158-120-3.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-1fg86i1h] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestFetchEBSPricing* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-cloud-providers-ec2#TestFetchEBSPricing=fail] *TestEBSPriceCaching* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-cloud-providers-ec2#TestEBSPriceCaching=fail] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2085","09/15/2017 19:03:47",2,"TestCommandTestSuite ""h2. [race-agent failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_agent_ce89b33b74493e60b49a3b85720f9c0e8b5ed397_17_09_15_15_01_53/0] Host: [ec2-54-158-79-112.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-q79r7sth] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestCommandTestSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestCommandTestSuite=fail] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2086","09/15/2017 19:29:35",1,"hang_analyzer doesn't appear to run in Windows ""Test suite timed out after running for ~6hrs https://evergreen.mongodb.com/task/mongodb_mongo_master_windows_64_2k8_debug_sharding_patch_fe125855b6b3e8feb9d7d666338a7f2d29d301ad_59b9960ce3c3316a9e024b4a_17_09_13_20_33_28/0 There appears to be on output for hang analyzer and there was also no evidence that an attempt was made.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2088","09/15/2017 20:42:53",1,"shell.exec should fail if directory does not exist ""I have the following in an EVG config: {{post: - command: shell.exec params: working_dir: mms/server script: | ... }} Some tasks however don't have the folder {{mms/server}}. As such they fail to run this post task and they hang for 15m before EVG shuts them down. We should see some error output and the next post task should run. See https://evergreen.mongodb.com/task/mms_unit_js_GITHUB_PR_START_3c19e4f2cf774c9c2dab6506cca89a7a45a286cd_17_09_15_17_55_02""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2091","09/15/2017 23:16:21",2,"Host list is very slow ""https://evergreen.mongodb.com/hosts is very slow to load and respond when searching""","",0,0,0,0,0,0,1,0,0,0,1,0,0,0,0 +"EVG-2092","09/18/2017 15:26:01",2,"Command timeout is being set after command finishes and is sometimes not set ""The original symptom of this problem is that the sys-perf project has purple instead of red tasks. The db has json.send in run test (step 4.2 of 6) as the last command run, but in fact steps 5, 6.1, and 6.2 succeeded. Step 6.3 failed. Here is an example from the Evergreen self-tests. Setting command timeout, which also sets the current command, should happen immediately after we log """"Running command %v (step..."""" and before we run the command. There may be a race between startIdleTimeoutWatch() and checkIn(), since startIdleTimeoutWatch() calls checkIn(). startIdleTimeoutWatch() sends on the same channel it's listening on, which could conceivably cause unpredictable behavior. Since checkIn() uses a non-blocking send, a deadlock could cause it not to set tc.currentCommand. """," [2017/09/16 15:03:31.938] Finished 'shell.exec' in """"run-make"""" in 4m48.034997766s [2017/09/16 15:03:31.938] Command timeout set to 2h0m0s ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2094","09/18/2017 16:02:14",1,"remove legacy logger and loggingwriter ""which will let us get rid of our last slogger dependency. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2095","09/18/2017 16:02:51",1,"avoid global mutable string variables in the global.go file ""there are a few, we should avoid this ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2098","09/18/2017 16:48:17",2,"Pushing to a GitHub pull request should unschedule older patch builds ""(for that pull request, of the automatically configured kind.) Maybe also only if they've not been modified. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2099","09/18/2017 19:15:20",1,"Address race detector failures in agent tests ""h2. [coverage failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_coverage_61502934324cd17f6db77e5294fb91f37a94fd78_17_09_16_18_54_13/0] Host: [ec2-54-198-34-242.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-ig7r634j] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2100","09/18/2017 20:39:33",1,"New Evergreen agent appears not to normalize Windows CRLF line endings ""There's an extra blank line after each line of output from {{wmic}}. https://evergreen.mongodb.com/task_log_raw/mongodb_mongo_master_windows_64_2k8_debug_aggregation_WT_e49cbf575a9f8a867280d0a21c3da622700dc3f5_17_09_18_16_55_14/0?type=S&text=true"""," [2017/09/18 18:04:32.450] Running wmic process list /format:list; wmic os get /format:list [2017/09/18 18:04:32.593] [2017/09/18 18:04:32.593] [2017/09/18 18:04:32.593] CommandLine= [2017/09/18 18:04:32.593] CSName=WIN-H67KGNQHGVV [2017/09/18 18:04:32.593] Description=System Idle Process [2017/09/18 18:04:32.593] ExecutablePath= [2017/09/18 18:04:32.593] ExecutionState= [2017/09/18 18:04:32.593] Handle=0 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2103","09/19/2017 20:46:38",2,"Add endpoint for host statistics ""This came out of a post-mortem of EVG-1990. This endpoint should provide host statistics so that the status page can alert for incidents of this type.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9400","09/19/2017 21:05:11",1,"It's possible for grip to panic when trying to send a long message ""At around 10 pm last night, the taskrunner kept hitting panics when trying to log a large error string related to starting agents: From what I could see from splunk, it was trying to start agents on about 100 hosts (though it's possible only a fraction of those errored). I tried to reproduce this with grip logging 50000 lines to stdout but was unsuccessful"""," journal error: write unixgram @->/run/systemd/journal/socket: write: message too long panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x986bbf] goroutine 28 [running]: panic(0x14167a0, 0xc420012090) /opt/go/src/runtime/panic.go:500 +0x1a1 log.(*Logger).Output(0x0, 0x2, 0xc43227eb40, 0x60, 0x0, 0x0) /opt/go/src/log/log.go:147 +0x6f log.(*Logger).Printf(0x0, 0xc43227e5a0, 0x60, 0x0, 0x0, 0x0) /opt/go/src/log/log.go:173 +0x7e github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.(*nativeLogger).Send(0xc42028e760, 0x2206de0, 0xc429824310) /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send/native.go:123 +0x11a github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.ErrorHandlerFromSender.func1(0x21f7520, 0xc421ff99a0, 0x2206ea0, 0xc429824070) /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send/error_handler.go:32 +0x7f github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.(*Base).ErrorHandler(0xc4201b00f0, 0x21f7520, 0xc421ff99a0, 0x2206ea0, 0xc429824070) /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send/base.go:115 +0x95 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.(*systemdJournal).Send(0xc42028e780, 0x2206ea0, 0xc429824070) /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send/systemd.go:60 +0x14a github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.(*multiSender).Send(0xc42027e5a0, 0x2206ea0, 0xc429824070) /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send/multi.go:127 +0xb2 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/logging.(*Grip).Error(0xc4200133a0, 0x144cd60, 0xc430d83110) /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/logging/general.go:85 +0x66 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip.Error(0x144cd60, 0xc430d83110) /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/loggers.go:97 +0x4c github.com/evergreen-ci/evergreen/taskrunner.(*Runner).Run(0x224db20, 0x7f75831fca60, 0xc42001adc0, 0xc42006a700, 0xc4201900d0, 0x2) /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/taskrunner/runner.go:50 +0x965 github.com/evergreen-ci/evergreen/cli.runnerBackgroundWorker(0x7f75831fca60, 0xc42001adc0, 0x2201760, 0x224db20, 0xc42006a700, 0x1bf08eb000, 0xc42028e910) /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/cli/runner.go:204 +0x2e7 created by github.com/evergreen-ci/evergreen/cli.startRunners /data/mci/126f28333fbc9152cb4171e0127c6f87/gopath/src/github.com/evergreen-ci/evergreen/cli/runner.go:156 +0x301 ",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2104","09/19/2017 21:29:30",1,"display Build URL in evergreen patch summary only for finalized patches ""For unfinalized submitted patches, the Build URL simply links to a page with the text """"not found"""" and so isn't useful. Putting the Build URL next to the Configure [patch] URL makes it harder to click on them.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2105","09/20/2017 17:21:13",2,"Logkeeper inserts test and global logs with wrong start time ""A [commit|https://github.com/evergreen-ci/logkeeper/commit/4d1eecad89a349fcadf765690cbdc877fee99d57#diff-100d281dce5be5551efb680a8617d493] to fix lint errors changed this function: to this: In the changed example, Go's zero value for time, January 1, year 1, is always returned, because earliest starts at this zero value, and no time can be earlier than this. This function sets the value of the started field in the log document. There is a 365 day TTL index on this field, so the documents were successfully inserted and then deleted by MongoDB, since the value in the started field was older than 365 days."""," func earliestLogTime(logs []LogLine) *time.Time { var earliest *time.Time earliest = nil for _, v := range logs { if earliest == nil || v.Time().Before(*earliest) { t := v.Time() earliest = &t } } return earliest } func earliestLogTime(logs []LogLine) *time.Time { var earliest time.Time for _, v := range logs { if v.Time().Before(earliest) { earliest = v.Time() } } return &earliest } ",0,0,1,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2107","09/20/2017 18:33:15",1,"notification banner should be dismissable ""and remember that i dismissed it in localStorage or a cookie or something""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2109","09/21/2017 17:24:09",1,"EVG does not give a useful error message when aws_key/aws_secret are blank ""This came up as part of the timezone project, where an evergreen project was created to publish a timelib build artifact to the s3 bucket downloads.mongodb.org. A sample patch build is below, where the s3.put task appears to complete successfully yet the files do not get pushed: https://evergreen.mongodb.com/task/mongodb_olsen_timezones_linux_64_compile_patch_20f042bac80a25384ed877ea032f84cdd694a1da_59c2a736e3c33124a8001a2f_17_09_20_17_37_46""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2110","09/21/2017 17:26:43",1,"Agent panics on zSeries when getting error response from api server ""We've seen this problem across all the zSeries boxes (rhel6/7, sles11/12, ubuntu1604) in the past few days. Agent panics from time to time and the last line in logs is error response from api server like this As [~brian.samek] suggested, I run the agent in the foreground to get more details and I see this runtime error now This is from a rhel67-z box.""","[evergreen.agent] 2017/09/21 16:09:36 [p=warning]: error response from api server: Post https://evergreen.mongodb.com/api/2/task/mongodb_mongo_master_enterprise_rhel_67_s390x_sharding_jscore_op_query_passthrough_WT_55586df431096badb7a8dc56b2281cd590e183d3_17_09_18_13_57_53/process_info: dial tcp: lookup evergreen.mongodb.com on 64.6.64.6:53: dial udp 64.6.64.6:53: i/o timeout (attempt 1 of 10)[evergreen.agent] 2017/09/21 16:09:36 [p=warning]: error response from api server: Post https://evergreen.mongodb.com/api/2/task/mongodb_mongo_master_enterprise_rhel_67_s390x_sharding_jscore_op_query_passthrough_WT_55586df431096badb7a8dc56b2281cd590e183d3_17_09_18_13_57_53/process_info: dial tcp: lookup evergreen.mongodb.com on 64.6.64.6:53: dial udp 64.6.64.6:53: i/o timeout (attempt 1 of 10) panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x11b77e] goroutine 56 [running]: panic(0x1258540, 0xc420010090) /opt/go/src/runtime/panic.go:500 +0x408 github.com/evergreen-ci/evergreen/rest/client.(*communicatorImpl).retryRequest(0xc420333ae0, 0x3fffd40d740, 0xc42046cac0, 0x153fb06, 0x4, 0xc420e0f6b0, 0xa2, 0x15419ce, 0x6, 0xc420bb8990, ...) /data/mci/c9b32294cf542d53df8b15c2621d3680/gopath/src/github.com/evergreen-ci/evergreen/rest/client/request.go:152 +0x62e github.com/evergreen-ci/evergreen/rest/client.(*communicatorImpl).SendProcessInfo(0xc420333ae0, 0x3fffd40d740, 0xc42046cac0, 0xc420088000, 0x90, 0xc42026b360, 0x20, 0x0, 0xc4204cc200, 0x1a, ...) /data/mci/c9b32294cf542d53df8b15c2621d3680/gopath/src/github.com/evergreen-ci/evergreen/rest/client/methods.go:580 +0x1b8 github.com/evergreen-ci/evergreen/agent.(*metricsCollector).processInfoCollector(0xc42046cb80, 0x3fffd40d740, 0xc42046cac0, 0x12a05f200, 0x2540be400, 0x1e) /data/mci/c9b32294cf542d53df8b15c2621d3680/gopath/src/github.com/evergreen-ci/evergreen/agent/metrics.go:73 +0x2b4 created by github.com/evergreen-ci/evergreen/agent.(*metricsCollector).start /data/mci/c9b32294cf542d53df8b15c2621d3680/gopath/src/github.com/evergreen-ci/evergreen/agent/metrics.go:44 +0x122",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2111","09/21/2017 18:03:43",2,"command timeout appears to not work ""In a task that was run the command did not timeout after two hours of idle output. The command only timed out after the task hit the 6 hour task timeout. +Expected Result:+ After the command did not log any lines to evergreen for 2 hours, the command would be terminated. Task: https://evergreen.mongodb.com/task/mongodb_mongo_master_windows_64_2k8_debug_auth_48cdb7d69246339e097bf23ec0e6b9187a3f9221_17_09_21_06_03_29/0 Log File: https://evergreen.mongodb.com/task_log_raw/mongodb_mongo_master_windows_64_2k8_debug_auth_48cdb7d69246339e097bf23ec0e6b9187a3f9221_17_09_21_06_03_29/0?type=T&text=true +Selected log lines:+ References https://jira.mongodb.org/browse/BF-6631"""," [2017/09/21 02:55:53.180] Task logger initialized (agent revision: f42fecc5d6f4cbb89a3dd3deb12ed2572e0ca835). [2017/09/21 02:55:53.389] Starting task mongodb_mongo_master_windows_64_2k8_debug_auth_48cdb7d69246339e097bf23ec0e6b9187a3f9221_17_09_21_06_03_29, execution 0. ...Trimmed... [2017/09/21 03:26:15.936] [executor:js_test:job0] 2017-09-21T07:26:15.936+0000 cluster_ip_whitelist.js ran in 38.85 seconds. [2017/09/21 03:26:36.145] [executor:js_test:job2] 2017-09-21T07:26:36.144+0000 copyauth_between_shards.js ran in 172.68 seconds. [2017/09/21 08:55:53.389] Running task-timeout commands. [2017/09/21 08:55:53.389] Running command 's3.get' in """"fetch debugsymbols archive"""" (step 1 of 3) ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2112","09/22/2017 17:00:37",1,"Upgrade angular version to 1.6.6 ""current version is 1.3.9""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2113","09/22/2017 17:52:39",2,"golang: Single test failure marks all other tests with same name as failed ""See: https://evergreen.mongodb.com/task/stitch_cloud_prod_linux_64_tests_without_cloud_c217911122ce24c6446811aa3da471378e9741b0_17_09_22_16_39_58 The {{TestStageMetrics}} test only failed for our twilio service but other services that use the same name passed but are marked as failed.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2114","09/22/2017 21:49:06",1,"lint failure ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_lint_1ac5afb5168e9d565fb732bfaeae96d5925da84d_17_09_21_19_38_19/0] Host: [ec2-54-205-80-112.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-4ybi5agj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2115","09/25/2017 21:47:29",2,"add terminate spawnhost route to new api and refactor cli accordingly ""the spawnhost termination route is only in the UI server because it depends on the settings object (which rest/v2 doesn't have access to.) we should make sure that we have enough ways to populate routes that we can get access to this if we need to. I think we should wait to do this until later when the settings object is loadable from the database, and we have moved to a middleware-based security model (I think this will be true when we start using gimlet and have an anser-like Environment concept). ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2116","09/26/2017 14:22:04",1,"Recent tasks rest v2 endpoint returns null tasks in verbose mode ""https://evergreen.mongodb.com/rest/v2/status/recent_tasks?minutes=15 works, but https://evergreen.mongodb.com/rest/v2/status/recent_tasks?minutes=15&verbose=true does not.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2117","09/26/2017 17:14:29",2,"Some tasks have incomplete system logs ""I've noticed that some tasks have incomplete system logs like no ps, df output. It's inconsistent though, same task can be ok on one commit and miss system logs on the other. I also don't see a correlation between this problem and a task being green or red.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2118","09/26/2017 18:40:15",1,"s3.put times out after many hours without any diagnostic information ""toolchain-builder tasks are timing out while running +Task+ https://evergreen.mongodb.com/task/toolchain_builder_debian71_compile_8bee304eec313fd501bc673c13321446a4154653_17_09_20_16_03_07 +Task Logs:+: +Agent Logs+ This is also occuring on other tasks: https://evergreen.mongodb.com/task/toolchain_builder_debian81_compile_8bee304eec313fd501bc673c13321446a4154653_17_09_20_16_03_07 https://evergreen.mongodb.com/task/toolchain_builder_rhel62_compile_8bee304eec313fd501bc673c13321446a4154653_17_09_20_16_03_07"""," [2017/09/25 13:26:17.983] Running command 's3.put' (step 6 of 6) [2017/09/25 17:06:52.322] Task completed - FAILURE. [2017/09/25 17:06:52.324] Running post-task commands. [2017/09/25 13:26:17.841] Finished 'shell.exec' in 2h19m24.572941823s [2017/09/25 13:26:17.841] Current command set to '' () [2017/09/25 17:06:52.322] Hit exec timeout [2017/09/25 17:06:52.324] Preparing script... [2017/09/25 17:06:52.324] Executing script with : set -o errexit ",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2123","09/27/2017 16:18:28",1,"Unable to spawn hosts and currently spawned hosts are not showing ""When I go to to spawn a host I have an empty public key in the dropdown and see this message: {quote} You cannot spawn a host because there are no spawnable distros. {quote} I have a spawned host currently running from this morning, but it doesn't show up on the spawn host page: ec2-54-81-41-251.compute-1.amazonaws.com""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2124","09/27/2017 19:06:34",1,"setupReadyHosts runs only a handful of times per hour at peak load ""Overnight setupReadyHosts runs every 20 seconds, but during the day it can take more than 30 minutes between runs. This is presumably causing delays in spawnhost creation. It can also cause hosts to be reaped by Evergreen because they are not set up quickly enough.""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-2126","09/27/2017 20:55:01",2,"zombie task invasion ""https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_jstestfuzz_sharded_session_WT_patch_7765cbafc5ab73262ce8d233c2410194b6bba1d7_59cbeaf4e3c3312ab20012c2_17_09_27_18_16_41""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-2128","09/28/2017 12:45:15",1,"use standard library contexts, and remove legacy contexts ""this also means we can remove gorilla contexts""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2129","09/28/2017 14:26:52",1,"lint failure ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_lint_5574d71c7305785f9574b167f99e5bce6ed4494e_17_09_27_21_16_12/0] Host: [ec2-54-224-255-41.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-krkg4hik] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2130","09/28/2017 14:41:35",1,"json.send command is failing ""A number of the tests are failing due to system failures with a 'System Timed out' status. For example, one of the task logs contains: """," [2017/09/27 23:16:22.466] Running command 'json.send' in """"run test"""" (step 4.2 of 6) [2017/09/28 01:06:36.677] Task completed - FAILURE. ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2132","09/29/2017 12:27:20",2,"Evergreen overdelivering notifications ""Since the recent change to simplify the logic around notification delivery it looks like we're generating notifications in cases where we should not be. Looking at this query: https://jira.mongodb.org/issues/?jql=project%20%3D%20BFG%20AND%20text%20~%20%22%5C%22multiversion_auth%20on%20~%20ASAN%20Enterprise%20SSL%20Ubuntu%2016.04%20DEBUG%20(downgrade_replset.js)%5C%22%22 All of these notifications are for the same task, same test, same buildvariant and different commits. Given that the logic is supposed to send only one notification every 48 hours for such a combination, the fact that we are sending upwards of 10 per day seems like a bug.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2134","09/29/2017 20:41:29",2,"Accessing resources that can be filtered via direct URL is broken ""When I want to view certain distros on the hosts page by opening a direct URL like https://evergreen.mongodb.com/hosts#/filter/rhel70-small, I get redirected to https://evergreen.mongodb.com/hosts#!/filter/#%2Ffilter%2Frhel70-small page that loads all the hosts. It applies to all the distros, not just rhel70-small. I normally jump to those urls from https://evergreen.mongodb.com/task_queue where each distro has """"view hosts"""" shortcut. Same problem occurs when trying to jump from a scheduled task to the task queue it's in by clicking the """"Nth in queue"""" link on the task's page. For example, URL it's taking me to is https://evergreen.mongodb.com/task_queue#/#mongodb_mongo_master_ubuntu1604_debug_ubsan_tool_e977f79fb37f7c6608bcfa7df81932b302285a57_17_09_29_13_40_59 and I get redirected https://evergreen.mongodb.com/task_queue/#!#%2F%23mongodb_mongo_master_ubuntu1604_debug_ubsan_tool_e977f79fb37f7c6608bcfa7df81932b302285a57_17_09_29_13_40_59 and it loads the entire page without taking me to the exact task like it used. P.S. I had hard time coming up with the ticket summary, feel free to change to something that makes sense. ""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2137","09/30/2017 12:52:31",2,"slow provisioning should use AWS started time not created_time ""created_time is subject to fluctuations in runner throughput and inter-runner interaction, and being too aggressive here can lead to hosts getting terminated too soon. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2139","09/30/2017 13:03:37",2,"subprocess.RemoteCommand's wait may not work. ""We observe commands hitting the time out and then, when we call """"kill"""" on the command (to prevent zombie ssh sessions,) we report that the command is not running, and then when trying to reproduce commands we find that commands that take ~minutes in evergreen take 10s of seconds manually. RemoteCommand isn't (well?) tested (we don't have a suitable integration environment, it's difficult to mock this component. It may make sense to replace it, or replace its internals, entirely. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2144","10/02/2017 14:45:20",1,"Evergreen smoke test ""This smoke test will run as part of our test suite in Evergreen. It will: # Start the runner and the web service. # Start a container for the agent. # Insert some data into the database. # Run a project config containing a minimal example of each command.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2145","10/02/2017 14:45:35",2,"Fix time picker on admin settings page ""It was removed in EVG-2123""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2146","10/02/2017 17:41:07",1,"Evergreen /task_history page modifies window.location.hash in a way that makes URL non-copyable from location bar ""Clicking the {{server8070.js}} link on [this task page|https://evergreen.mongodb.com/task/mongodb_mongo_master_rollback_3dot4_rhel_62_replica_sets_ac9d5702568845898659dfee662ce05320ce13e7_17_10_02_13_37_58] links to https://evergreen.mongodb.com/task_history/mongodb-mongo-master/replica_sets?revision=ac9d5702568845898659dfee662ce05320ce13e7#server8070.js=fail; however, after the page loads the {{window.location.hash}} is modified to be """"\!#server8070.js=fail"""" and is interpreted as highlighting cases where the {{\!#server8070.js}} test failed upon reload.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2149","10/02/2017 19:18:34",1,"test-cli failure ""h2. [test-cli failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_cli_70b94443c8afabb6f2bcf3c27b8882e895dadb05_17_10_02_17_54_19/0] Host: [ec2-54-81-214-176.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-3gi87mng] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2150","10/02/2017 19:20:01",1,"TestS3CopyPluginExecution ""h2. [test-command failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_command_70b94443c8afabb6f2bcf3c27b8882e895dadb05_17_10_02_17_54_19/0] Host: [ec2-54-166-203-175.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-jfir4mvj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestS3CopyPluginExecution* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-command#TestS3CopyPluginExecution=fail] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2151","10/02/2017 19:21:04",1,"TestSetupReadyHosts ""h2. [test-hostinit failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_hostinit_70b94443c8afabb6f2bcf3c27b8882e895dadb05_17_10_02_17_54_19/0] Host: [ec2-54-80-104-127.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-fwkg4yek] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestSetupReadyHosts* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-hostinit#TestSetupReadyHosts=fail] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2152","10/02/2017 22:26:21",2,"Hang analyzer no longer runs for hanged tasks/missing hang analyzer output ""While trying to diagnose BF-5821, I noticed that the hanged tasks were missing their hang analyzer output in the task log: https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1604_debug_asan_multiversion_multistorage_engine_4f5ec27ba25abb13e554721d65aa1c91100bca5e_17_09_29_22_38_23. I also noticed that the hang analyzer only ran for 57 microseconds, which seems like far too few microseconds let alone seconds to actually analyze the hang.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2154","10/03/2017 15:03:56",1,"lint failure ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_lint_c660df7721c3a2cd04d29ce3126bf9fe5d4035aa_17_09_28_14_50_08/0] Host: [ec2-54-198-160-83.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-995847nh] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2155","10/03/2017 16:25:27",2,"Evergreen should be more robust to disabled projects ""* The next_task endpoint should not return tasks for projects which are missing or disabled * The scheduler shouldn't enqueue tasks from missing or disabled projects""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2159","10/03/2017 19:57:25",1,"Add debug build to Evergreen Makefile ""Update Makefile to add a debug build option that will * leave debug symbols (remove """"-w"""" from ldflags) * Disable inlining and optimisations: (Add to go build: -gcflags """"-N -l"""") for debugging with GDB.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2161","10/03/2017 22:16:18",1,"change notify email presentation type ""make them actually text emails; remove the <@ from the subject line; etc. (these are the internal emails""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2162","10/03/2017 22:30:04",1,"Agent still cleaning up .ssh directory on Windows ""https://evergreen.mongodb.com/host/sir-2rm87wfh problem running taskrunner: problem starting agent on host sir-2rm87wfh: error prepping remote host sir-2rm87wfh: error creating directories on remote machine: Warning: Permanently added 'ec2-54-166-21-78.compute-1.amazonaws.com,54.166.21.78' (RSA) to the list of known hosts. Permission denied (publickey,gssapi-keyex,gssapi-with-mic). : exit status 255 problem starting agent on host sir-rbfg6yvh: error prepping remote host sir-rbfg6yvh: error creating directories on remote machine: ssh: connect to host ec2-54-162-206-86.compute-1.amazonaws.com port 22: Connection timed out : exit status 255 problem starting agent on host sir-p5ir6d2k: error prepping remote host sir-p5ir6d2k: error creating directories on remote machine: ssh: connect to host ec2-54-166-129-183.compute-1.amazonaws.com port 22: Connection timed out : exit status 255""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2164","10/03/2017 22:58:34",1,"Rename distro.Distro.Id's JSON field name from '_id' ""Change '_id' to a more appropriate name.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2165","10/03/2017 23:06:43",1,"""raw"" logs aren't working properly ""e.g. https://evergreen.mongodb.com/test_log/59d3d30b2a60ed21b400070e?raw=1 Renders like this: !image-2017-10-03-18-02-45-006.png|thumbnail! It looks like the response headers have Content-type: text/html, but it should be text/plain.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2167","10/04/2017 04:05:22",2,"application environment accessors ""wrap existing settings options anser/sink style""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2169","10/04/2017 13:03:46",2,"Agent was unable to kill running process ""2 tasks within a patch build timed out. I don't believe that either should have hit the time limit.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2171","10/04/2017 19:56:26",1,"Please reduce the default tag expiration time for hosts from 90 days to 10 days ""90 days seems to be too much in excess for host expiration and would like to reduce it to a more reasonable number.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2174","10/04/2017 21:27:07",2,"Correctly handle scenarios where EC2 cancels spot requests ""The spot instance request ID 'sir-rbfg6yvh' does not exist (InvalidSpotInstanceRequestID.NotFound) github.com/evergreen-ci/evergreen/cloud/providers/ec2.(*EC2SpotManager).describeSpotRequest /data/mci/3c3159ed41cb07b22be02ed0dd51e90f/gopath/src/github.com/evergreen-ci/evergreen/cloud/providers/ec2/ec2spot.go:373 github.com/evergreen-ci/evergreen/cloud/providers/ec2.(*EC2SpotManager).GetInstanceStatus /data/mci/3c3159ed41cb07b22be02ed0dd51e90f/gopath/src/github.com/evergreen-ci/evergreen/cloud/providers/ec2/ec2spot.go:161 github.com/evergreen-ci/evergreen/cloud.(*CloudHost).GetInstanceStatus /data/mci/3c3159ed41cb07b22be02ed0dd51e90f/gopath/src/github.com/evergreen-ci/evergreen/cloud/cloud.go:191 github.com/evergreen-ci/evergreen/monitor.checkHostReachability /data/mci/3c3159ed41cb07b22be02ed0dd51e90f/gopath/src/github.com/evergreen-ci/evergreen/monitor/host_monitoring.go:97 github.com/evergreen-ci/evergreen/monitor.monitorReachability.func1 /data/mci/3c3159ed41cb07b22be02ed0dd51e90f/gopath/src/github.com/evergreen-ci/evergreen/monitor/host_monitoring.go:58 runtime.goexit /opt/go/src/runtime/asm_amd64.s:2086 failed to get spot request info for sir-rbfg6yvh github.com/evergreen-ci/evergreen/cloud/providers/ec2.(*EC2SpotManager).GetInstanceStatus /data/mci/3c3159ed41cb07b22be02ed0dd51e90f/gopath/src/github.com/evergreen-ci/evergreen/cloud/providers/ec2/ec2spot.go:163 github.com/evergreen-ci/evergreen/cloud.(*CloudHost).GetInstanceStatus /data/mci/3c3159ed41cb07b22be02ed0dd51e90f/gopath/src/github.com/evergreen-ci/evergreen/cloud/cloud.go:191 github.com/evergreen-ci/evergreen/monitor.checkHostReachability /data/mci/3c3159ed41cb07b22be02ed0dd51e90f/gopath/src/github.com/evergreen-ci/evergreen/monitor/host_monitoring.go:97 github.com/evergreen-ci/evergreen/monitor.monitorReachability.func1 /data/mci/3c3159ed41cb07b22be02ed0dd51e90f/gopath/src/github.com/evergreen-ci/evergreen/monitor/host_monitoring.go:58 runtime.goexit /opt/go/src/runtime/asm_amd64.s:2086 ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2177","10/05/2017 14:00:48",2,"migrate periodic background jobs to amboy services internally ""this is mostly to just reduce the nubmber of random one-off background threads, and to help us build confidence in amboy within evergreen. I'm mostly thinking about the data collection threads that log recent task statuses to splunk along with application and system statistics collection ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2188","10/09/2017 03:55:10",2,"gopsutil doesn't collect io_counters on OS X ""{quote} * Collect system resource usage data for all supported host types (e.g. ZaP and Intel; Windows, Solaris, Linux and Darwin) * Collect CPU, IO, and Memory usage for all processes spawned by a task, stored on a per-process level, (for tasks that spawn many processes). ** The parent process ID of each process spawned by the task will also be included in this information. {quote} The """"writeBytes"""" field for all processes on OS X is being reported as 0, so I don't think the work for collecting this metric happened. There was an idea of taking the code for the automation agent and upstreaming it to {{gopsutil}}. http://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_osx_1010_debug_aggregation_WT_155db509a8e376211095cec062f7aa5be1b7707e_17_10_08_00_36_06/metrics/process?start_at=%222006-01-02T15:04:05.000Z%22""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2189","10/09/2017 04:20:21",2,"gopsutil doesn't collect cpu_times on Windows ""{quote} * Collect system resource usage data for all supported host types (e.g. ZaP and Intel; Windows, Solaris, Linux and Darwin) * Collect CPU, IO, and Memory usage for all processes spawned by a task, stored on a per-process level, (for tasks that spawn many processes). ** The parent process ID of each process spawned by the task will also be included in this information. {quote} The """"cpu"""" field for all processes on Windows is being reported as an object containing all 0's, so I don't think the work for collecting this metric happened. There was an idea of taking the code for the automation agent and upstreaming it to {{gopsutil}}. http://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_windows_64_2k8_debug_sharding_WT_155db509a8e376211095cec062f7aa5be1b7707e_17_10_08_00_36_06/metrics/process?start_at=%222006-01-02T15:04:05.000Z%22""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2193","10/10/2017 14:44:44",1,"Evergreen isn't respecting timeout_secs as part of command settings ""The {{concurrency*}} tasks run a JavaScript test that runs other JavaScript tests. Since resmoke.py won't produce output until the outer JavaScript test finishes, we've increased the {{timeout_secs}} setting to what we'd ordinarily use for the entire task. For example, [the """"idle timeout"""" for the {{concurrency_sharded_with_stepdowns_and_balancer_WT}} is set to 6 hours|https://github.com/mongodb/mongo/blob/f74896d9aae90d0b31eeb06f37f59ca386c03570/etc/evergreen.yml#L3603]. {code:yaml} - <<: *task_template name: concurrency_sharded_with_stepdowns_and_balancer_WT commands: - func: """"do setup"""" - func: """"run tests"""" timeout_secs: 21600 # 6 hour timeout for each test vars: resmoke_args: --suites=concurrency_sharded_with_stepdowns_and_balancer --storageEngine=wiredTiger {code} However, the Evergreen tasks are timing after running for 2 hours without resmoke.py producing any output. {quote} 2h 5m 7s Started on Oct 10, 2017 1:07:21 am Finished on Oct 10, 2017 3:12:29 am https://evergreen.mongodb.com/task/mongodb_mongo_master_windows_64_2k8_debug_concurrency_sharded_with_stepdowns_and_balancer_WT_63a1ed132fce92bca57845879f4bb25e44c92874_17_10_10_00_23_21 {quote} The [task timing for the {{concurrency_sharded_with_stepdowns_and_balancer_WT}} task|https://evergreen.mongodb.com/task_timing/mongodb-mongo-master#/project=mongodb-mongo-master&buildVariant=windows-64-2k8-debug&taskName=concurrency_sharded_with_stepdowns_and_balancer_WT&requester=gitter_request&limit=100&onlySuccessful=false] shows that it started to time out after the deploy from Oct 5th that includes the changes from EVG-2152. [~sam.kleinman] and I did some debugging Oct 9th together and identified a line in {{agent/command.go}} that was always setting the command's timeout to {{defaultIdleTimeout}} (= 2 hours); however, even with [Sam's changes|https://github.com/evergreen-ci/evergreen/commit/886d894ef477d37afccda47cff3d1b5ee7fb5e35], the {{timeout_secs}} still appears to not be getting respected. h6. Agent logs The """"agent logs"""" show that the Evergreen agent is incorrectly setting the command timeout to 2 hours. """," - <<: *task_template name: concurrency_sharded_with_stepdowns_and_balancer_WT commands: - func: """"do setup"""" - func: """"run tests"""" timeout_secs: 21600 # 6 hour timeout for each test vars: resmoke_args: --suites=concurrency_sharded_with_stepdowns_and_balancer --storageEngine=wiredTiger [2017/10/10 01:08:26.116] Current command set to ''shell.exec' in """"run tests""""' (test) [2017/10/10 01:08:26.116] Set command timeout for ''shell.exec' in """"run tests""""' (test) to 2h0m0s ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2195","10/10/2017 18:18:50",2,"'evergreen test-history' returning old data ""Running this command: Gives me the following results: I would have expected some of the more recent failures (like any of these: BF-5239) to show up in this command. It seems like either I'm inputting the wrong command here (and there's a sort which isn't listed in the --help?) or that this command is sorting the wrong way?"""," evergreen test-history -p mongodb-mongo-master --test jstests/gle/gle_sharded_wc.js --limit 10 Start Time Duration(ms) Variant Task Name Test File URL Tue Jul 15 19:04:44 2014 40s rhel70 gle_auth jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53c57215d2a60f29980002b0/test/53c57b4cd2a60f2f640001e7/ Tue Jul 15 18:34:06 2014 2m0s rhel70 gle_auth_write_cmd jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53c57394d2a60f2a6500081f/test/53c5741ed2a60f2aad000af6/ Tue Jul 15 19:31:45 2014 5m7s ubuntu1404 gle_auth_write_cmd jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53c56fe6d2a60f26f900093a/test/53c581a1d2a60f32b80001b3/ Tue Jul 15 19:31:43 2014 46s rhel70 gle_auth jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53c58104d2a60f3256000176/test/53c5819fd2a60f32b90001aa/ Fri Jun 20 23:05:38 2014 10m28s osx-108 gle_auth_write_cmd jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53a4b6ded2a60f3587000870/test/53a4be42d2a60f3a3b000300/ Fri Jun 20 23:34:28 2014 10m27s osx-108 gle_auth jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53a4bd9cd2a60f3983000a1d/test/53a4c504d2a60f3b820006c7/ Fri Jun 20 23:45:53 2014 10m26s linux-64 gle_auth jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53a4c050d2a60f3a0e00086a/test/53a4c7b2d2a60f3be0000d4e/ Fri Jun 20 23:45:58 2014 10m26s linux-64 gle_auth_write_cmd jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53a4c056d2a60f3a3b000800/test/53a4c7b6d2a60f3c9000026b/ Sat Jun 21 00:09:56 2014 10m25s ubuntu1404 gle_auth_write_cmd jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53a4c5f6d2a60f3b620009b4/test/53a4cd53d2a60f3dc4000cce/ Sat Jun 21 01:23:28 2014 10m25s ubuntu1404 gle_auth jstests/gle/gle_sharded_wc.js http://buildlogs.mongodb.org/build/53a4d733d2a60f42a20004b6/test/53a4de90d2a60f46eb0003b8/ ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2196","10/10/2017 19:29:56",1,"test-agent failure ""h2. [test-agent failed on windows|https://evergreen.mongodb.com/task/mci_windows_test_agent_d57aa60195b8cfb0e03a19a7f0430cdd639db8aa_17_10_10_15_44_43/0] Host: [ec2-54-197-96-19.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-se5i7mpg] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2197","10/10/2017 19:31:27",1,"race-agent failure ""h2. [race-agent failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_agent_d57aa60195b8cfb0e03a19a7f0430cdd639db8aa_17_10_10_15_44_43/0] Host: [ec2-54-166-157-83.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-zs1g5kkj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2201","10/11/2017 08:58:06",1,"add alert for underwater distro schedule ""log alert if expected runtime for a distro at maxhosts is more than day (more than a week for statics?) ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2204","10/11/2017 18:55:33",1,"lint failure ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_lint_ca6ea0c0879d9ac5489e094e67d8fe6daad6803b_17_10_11_14_47_30/0] Host: [ec2-54-205-214-155.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-btai4dwj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2206","10/11/2017 21:53:48",1,"Taskrunner should log when it is dispatching an agent to an uncommunicative host ""[Currently|https://github.com/evergreen-ci/evergreen/blob/85790be675d892f39a74d66b2204f67aad053fa7/taskrunner/task_runner.go#L44], we do not make a distinction between three cases: # Hosts which have never had an agent running. # Agents which have aborted gracefully (because, for example, we have upgraded Evergreen). # Agents which have not checked in in greater than MaxLCTInterval. In the third case we should log that this has happened, as it indicates that an agent may have exited due to an unexpected error or panic.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2208","10/12/2017 16:38:37",1,"race-agent failure ""h2. [race-agent failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_agent_69487ae236457d78fd37f604464f442eb2766c27_17_10_12_14_19_23/0] Host: [ec2-54-161-145-173.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-y9mg7vrj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2209","10/13/2017 16:35:30",1,"race-agent failures ""h2. [race-agent failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_agent_27f512e14a34247d213456c605bb547f06467879_17_10_13_04_12_42/0] Host: [ec2-54-205-148-172.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-kmdi744h] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestAgentIntegrationSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentIntegrationSuite=fail] *TestAgentIntegrationSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentIntegrationSuite=fail] *TestAgentIntegrationSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentIntegrationSuite=fail] *TestAgentIntegrationSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentIntegrationSuite=fail] *TestRunTask* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestRunTask=fail] *TestRunTask* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestRunTask=fail] *TestRunTask* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestRunTask=fail] *TestRunTask* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestRunTask=fail] *TestAgentIntegrationSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentIntegrationSuite=fail] *TestRunTask* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestRunTask=fail] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2214","10/15/2017 19:48:53",1,"Runners should log when they finish running ""We alert if a runner has not run in the last 10 minutes based on logging that each runner does when it starts. We should also log when each runner process finishes so that we can detect stalls or panics in the middle of an agent run. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2218","10/18/2017 18:21:41",1,"Make trend view the default view for performance patch builds (sys-perf and microbenchmarks) ""Can we make the trend view the default for patch builds in the perf plugin? The trend view makes it easier to see if the change due to the patch is significant or not based on historical data. ""","",0,0,0,1,0,0,0,0,0,0,0,1,0,0,0 +"EVG-2228","10/19/2017 22:39:27",1,"Can't decommission hosts from hosts page ""Clicking the button appears to noop.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2230","10/20/2017 16:46:12",2,"Agent should heartbeat before starting the heartbeat ticker ""Otherwise, it will not heartbeat during tasks that take less than 30 seconds. If it runs many of these in a row, it may never heartbeat.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2232","10/20/2017 21:28:43",1,"Populate git hash field in BF and BFG jira projects ""I added a """"Git Hash"""" field to the BF and BFG projects - can we make sure this gets populated with the git hash ID when a ticket gets generated? cc [~max.hirschhorn] [~david.daly] Would it be best to use the short or long git hash ID?""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2239","10/24/2017 17:03:44",2,"TestEnvironmentSuite, TestLoadingConfig ""h2. [test-evergreen failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_evergreen_20af791587220d4de3e5e52d7191808d8ed82716_17_10_24_14_12_33/0] Host: [ec2-54-204-104-120.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-f3k845tk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestEnvironmentSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-evergreen#TestEnvironmentSuite=fail] *TestLoadingConfig* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-evergreen#TestLoadingConfig=fail] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2240","10/24/2017 17:04:01",2,"TestSetupReadyHosts ""h2. [test-hostinit failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_hostinit_20af791587220d4de3e5e52d7191808d8ed82716_17_10_24_14_12_33/0] Host: [ec2-54-161-232-14.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-xmdr743k] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestSetupReadyHosts* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-hostinit#TestSetupReadyHosts=fail] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2241","10/24/2017 17:05:25",2,"TestParserOnRealTests ""{color:red}colored text{color}h2. [test-command failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_command_20af791587220d4de3e5e52d7191808d8ed82716_17_10_24_14_12_33/0] Host: [ec2-54-204-66-74.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-vj9r43bj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestParserOnRealTests* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-command#TestParserOnRealTests=fail] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2265","10/25/2017 16:48:34",2,"add direct-to-slack logger for Alert/Emergency messages ""we'll need to get bot credentials""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2258","10/25/2017 18:50:05",1,"Nil pointer when viewing first execution of a 1 execution task "" """," net/http.(*conn).serve.func1(0xc4204c6960) /usr/local/Cellar/go/1.9.1/libexec/src/net/http/server.go:1697 +0xd0 panic(0x519a2a0, 0x619e930) /usr/local/Cellar/go/1.9.1/libexec/src/runtime/panic.go:491 +0x283 github.com/evergreen-ci/evergreen/service.(*UIServer).taskPage(0xc420428900, 0x68b2950, 0xc42000e070, 0xc4203fc000) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/service/task.go:171 +0x4ba github.com/evergreen-ci/evergreen/service.(*UIServer).(github.com/evergreen-ci/evergreen/service.taskPage)-fm(0x68b2950, 0xc42000e070, 0xc4203fc000) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/service/ui.go:147 +0x48 github.com/evergreen-ci/evergreen/service.(*UIServer).loadCtx.func1(0x68b2950, 0xc42000e070, 0xc420ba3400) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/service/middleware.go:234 +0x1b5 net/http.HandlerFunc.ServeHTTP(0xc4201d17c0, 0x68b2950, 0xc42000e070, 0xc420ba3400) /usr/local/Cellar/go/1.9.1/libexec/src/net/http/server.go:1918 +0x44 github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux.(*Router).ServeHTTP(0xc4202dc050, 0x68b2950, 0xc42000e070, 0xc420ba3400) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux/mux.go:114 +0xdc github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.Wrap.func1(0x68b2950, 0xc42000e070, 0xc420ba3200, 0xc420c932a0) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:46 +0x4d github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP(0xc4206c4440, 0x68b2950, 0xc42000e070, 0xc420ba3200, 0xc420c932a0) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:29 +0x4e github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP(0x6166a20, 0xc4206c4440, 0xc4206c44c0, 0x68b2950, 0xc42000e070, 0xc420ba3200) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 +0xa5 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm(0x68b2950, 0xc42000e070, 0xc420ba3200) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 +0x60 github.com/evergreen-ci/evergreen/service.UserMiddleware.func1(0x68b2950, 0xc42000e070, 0xc420ba3000, 0xc420c92f80) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/service/middleware.go:399 +0x224 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP(0xc4206c43a0, 0x68b2950, 0xc42000e070, 0xc420ba3000, 0xc420c92f80) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:29 +0x4e github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP(0x6166a20, 0xc4206c43a0, 0xc4206c44a0, 0x68b2950, 0xc42000e070, 0xc420ba3000) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 +0xa5 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm(0x68b2950, 0xc42000e070, 0xc420ba3000) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 +0x60 github.com/evergreen-ci/evergreen/service.(*Logger).ServeHTTP(0xc420564040, 0x68b2950, 0xc42000e070, 0xc420ba3000, 0xc420c92f20) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/service/middleware.go:451 +0x3d5 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP(0x615f2a0, 0xc420564040, 0xc4206c4480, 0x68b2950, 0xc42000e070, 0xc420ba3000) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 +0xa5 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm(0x68b2950, 0xc42000e070, 0xc420ba3000) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 +0x60 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(*Static).ServeHTTP(0xc4205d2480, 0x68b2950, 0xc42000e070, 0xc420ba3000, 0xc420c92f00) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/static.go:53 +0x6f2 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP(0x615fd20, 0xc4205d2480, 0xc4206c4460, 0x68b2950, 0xc42000e070, 0xc420ba3000) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 +0xa5 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(*Negroni).ServeHTTP(0xc4205d2450, 0x616d0e0, 0xc420ba4e00, 0xc420ba3000) /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:86 +0xf5 net/http.serverHandler.ServeHTTP(0xc420a2a000, 0x616d0e0, 0xc420ba4e00, 0xc420ba3000) /usr/local/Cellar/go/1.9.1/libexec/src/net/http/server.go:2619 +0xb4 net/http.(*conn).serve(0xc4204c6960, 0x616df60, 0xc420409a40) /usr/local/Cellar/go/1.9.1/libexec/src/net/http/server.go:1801 +0x71d created by net/http.(*Server).Serve /usr/local/Cellar/go/1.9.1/libexec/src/net/http/server.go:2720 +0x288 ",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2260","10/25/2017 20:59:02",1,"avoid running second mkdir if there is no setup script ""in taskrunner/host_gateway.go""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2262","10/25/2017 22:50:55",1,"lint-cli, lint-model-task, lint-taskrunner ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_lint_ebf6771fae3f87e6f859fe300ca63d5b903209d5_17_10_24_21_47_56/0] Host: [ec2-54-204-243-118.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-x9y84pbk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *lint-cli* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-cli=fail] *lint-model-task* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-model-task=fail] *lint-taskrunner* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/lint#lint-taskrunner=fail] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2266","10/26/2017 18:18:14",2,"Evergreen spawned host failed to load task artifacts ""I spawned a Windows hosts from the this task (twice) and selected to load the artifacts. The host came up without the artifacts: """," $ ls -R /data /data: db mci tmp /data/db: /data/mci: /data/tmp: ",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-2268","10/26/2017 18:47:06",1,"terminate idle linux ephemeral hosts more quickly ""given secondly billing, and the fact that starting hosts is now much quicker, keeping idle hosts around for longer doesn't feel particularly useful.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2275","10/27/2017 02:51:11",1,"Teardown fails to trigger teardown of DSI cluster ""I don't know how to prove this one way or the other - but this is an example of a machine that was torn down but the DSI infrastructure was not torn down: https://evergreen.mongodb.com/host/i-02a8b54c1e6d5fffa [~david.daly] If this is in fact an Evergreen issue then we need to move this over to Evergreen. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2278","10/28/2017 15:54:11",2,"audit and cleanup evergreen service/runner application process ""to avoid interactions with other processes: - loggers should be setup first and have teardown last (maybe move them into the environment.) - potentially wait for some period of time for the local queue to drain. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9367","10/30/2017 19:36:56",1,"amboy/anser should use mongodb's mgo fork ""so that we can support change streams ""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2286","11/01/2017 02:48:55",1,"Cleanup util/spawn/remote packages ""There's a bunch of dead code that misses the linter's because it's public, this ticket is a cleanup bucket. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2291","11/01/2017 19:23:41",1,"task runner should add an event to the hosts event log when it deploys a new agent ""including the hash""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9513","11/02/2017 15:49:16",1,"Curator process and system resource monitoring should not require AWS credentials ""We are using curator just for system and process resource monitoring. When started on a non-Evergreen launched node, the following message shows up in stdout: """," [curator] 2017/11/02 14:54:30 [p=warning]: Couldn't parse AWS credentials file ",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9331","11/02/2017 15:51:45",1,"Curator warings/errors should be logged to stderr ""See MAKE-290 for how a warning gets generated. When a warning is produced it ends up in stdout/JSON file, it should go to stderr.""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9542","11/02/2017 15:53:54",2,"Curator --file option should handle existing file better ""Logging the ouput of curator with the --file option will overwrite an existing file. It should append to it. Perhaps another option could control this behavior.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9544","11/02/2017 15:57:02",2,"Capability to monitor all processes on Windows ""Curator has the capability ot monitor all processes on Linux using For Windows this cannot be done. It would be better having a new option to monitor all processes, perhaps {{curator stat process --all-pid}}."""," curator stat process-tree --pid 1 ",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2297","11/02/2017 20:32:25",1,"race-agent failures ""h2. [race-agent failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_agent_8d1cd0f9dbb7a744edbb9cdc1a379f8cf59a85db_17_11_02_18_25_58/0] Host: [ec2-54-221-151-108.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-wm9r7w3h] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestAgentSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentSuite=fail] *TestAgentEndTaskShouldExit* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentEndTaskShouldExit=fail] *TestAgentSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentSuite=fail] *TestAgentEndTaskShouldExit* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentEndTaskShouldExit=fail] *TestAgentSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentSuite=fail] *TestAgentEndTaskShouldExit* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentEndTaskShouldExit=fail] *TestAgentSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentSuite=fail] *TestAgentEndTaskShouldExit* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentEndTaskShouldExit=fail] *TestAgentSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentSuite=fail] *TestAgentEndTaskShouldExit* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-agent#TestAgentEndTaskShouldExit=fail] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2298","11/02/2017 20:56:00",1,"Some spawn hosts are not provisioning ""Debian and Amazon spawnhosts, and possibly others, are failing to provision. setup.sh is correctly being placed in the user's home directory. However, Evergreen attempts to run the setup script in _root's_ home directory. This presumably only affects spawnhosts because running the setup script uses a different code path for build hosts.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2300","11/03/2017 16:57:06",2,"monitor should flag hosts that encounter system failures more than 3 times ""we should definitely flag/report these? potentially also be able to turn it off so we don't end up terminating hosts too often when there's a bad commit afoot. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2303","11/03/2017 19:35:54",1,"race-scheduler failure ""h2. [race-scheduler failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_scheduler_59a6190a0c5afed01051cd42e547adbc1d16994d_17_11_03_17_57_13/0] Host: [ec2-54-227-88-100.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-4gsr6vqh] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-9439","11/04/2017 22:29:33",2,"amboy queue backed grip.Sender implementation ""let's put this in a new repo in the evergreen-ci org, as its reasonably general use. the idea is that we want a sender that wraps a queue and sends messages as possible but gets us out of needing to use the buffered sender (which centers on a capped buffer used in combination with a message batching type,) and is not suitable for some use cases. ""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9579","11/04/2017 22:33:24",1,"add ability for jobs to be local-queue only ""versions set to -1 or something on the job type document""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9507","11/06/2017 15:43:26",1,"remove level setting options from logger interface ""just set levels via the sender ""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2307","11/06/2017 18:37:44",1,"race-rest-data failures ""h2. [race-rest-data failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_rest_data_dbecd8bb7a03f60240497048299bebfa701130ae_17_11_06_17_30_06/0] Host: [ec2-54-146-155-98.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-tp386iij] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestMockConnectorSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-rest-data#TestMockConnectorSuite=fail] *TestMockConnectorSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-rest-data#TestMockConnectorSuite=fail] *TestMockConnectorSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-rest-data#TestMockConnectorSuite=fail] *TestMockConnectorSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-rest-data#TestMockConnectorSuite=fail] *TestMockConnectorSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/race-rest-data#TestMockConnectorSuite=fail] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-9653","11/06/2017 21:59:33",1,"remote ordered queue may serialize migrations ""maybe the queue implementation is too naive or the dependencies are too strict. ""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2311","11/07/2017 01:06:55",2,"Panic in monitor when running teardown script on hosts ""Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: RemoteCommand(teardown-i-09abec83f62eae9cc-6037277636045730342) killing process 2575 Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: panic: runtime error: invalid memory address or nil pointer dereference Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x76dce9] Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: goroutine 991 [running]: Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: panic(0x15a5ba0, 0xc420012080) Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: /opt/go/src/runtime/panic.go:500 +0x1a1 Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: github.com/evergreen-ci/evergreen/monitor.runHostTeardown(0x246b0a0, 0xc420244f40, 0xc4afe97ab8, 0xc43e4ec570, 0xc4bb136630, 0xc42a764cf0) Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: /data/mci/9641710e6fdec15649cd1d40233e0409/gopath/src/github.com/evergreen-ci/evergreen/monitor/hosts.go:206 +0x289 Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: github.com/evergreen-ci/evergreen/monitor.terminateHost(0x246b0a0, 0xc420244f40, 0xc4afe97ab8, 0xc420234000, 0x180001, 0x0) Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: /data/mci/9641710e6fdec15649cd1d40233e0409/gopath/src/github.com/evergreen-ci/evergreen/monitor/hosts.go:177 +0x3b3 Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: github.com/evergreen-ci/evergreen/monitor.terminateHosts.func1.1(0xc4b78a6c00, 0x615c4d) Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: /data/mci/9641710e6fdec15649cd1d40233e0409/gopath/src/github.com/evergreen-ci/evergreen/monitor/hosts.go:120 +0x48 Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: github.com/evergreen-ci/evergreen/util.RunFunctionWithTimeout.func1(0xc43326b440, 0xc43e4ec540) Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: /data/mci/9641710e6fdec15649cd1d40233e0409/gopath/src/github.com/evergreen-ci/evergreen/util/func.go:24 +0x27 Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: created by github.com/evergreen-ci/evergreen/util.RunFunctionWithTimeout Nov 07 00:56:03 evergreenapp-2.build.10gen.cc evergreen[2346]: /data/mci/9641710e6fdec15649cd1d40233e0409/gopath/src/github.com/evergreen-ci/evergreen/util/func.go:25 +0x7c""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2314","11/07/2017 17:13:27",1,"TestAgentIntegrationSuite ""h2. [test-agent failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_agent_e1bfc1f450e177ecbe3d52134c264550806c8dca_17_11_07_15_53_24/0] Host: [ec2-54-90-171-120.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-wqyg55qg] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] *TestAgentIntegrationSuite* - [Logs|] | [History|https://evergreen.mongodb.com/task_history/mci/test-agent#TestAgentIntegrationSuite=fail] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2316","11/07/2017 20:10:06",1,"fuzz start of runner tasksb ""so that there isn't a big hit when the runner restarts""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2317","11/08/2017 14:32:57",1,"Missing Test Summary from Previous Test Executions ""There seems to have been a behavior change in restarting tasks introduced in the past week where the sidebar stops showing information for previous executions. I was able to reproduce this behavior in my patch builds and when manually restarting a task on mainline mongodb-master. I've attached screenshots of a patch build that I ran last week with a before and after comparison. The side bar showed information on the 4th and 5th executions from last week. But when I restarted the task again with a 6th execution just now, test information on the 5th execution (and all other executions) disappeared.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2321","11/09/2017 15:19:52",2,"Remove legacy taskfind methods ""* Remove """"NoMerge"""" methods * FindOne and FindOneOld should not merge by default * Remove the test results field from the task struct * Create a test results method""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2324","11/10/2017 00:17:06",1,"Tag EBS volumes ""Can we apply the same tags to EBS volumes that we do to EC2 instances? It's very helpful for spending analysis to have tags on AWS entities that Evergreen manages, such as EC2 instances, which Evergreen launches and terminates directly. The EBS volumes attached to those instances are only used for the launched EC2 instances, but have no tags, so can't be accounted for as easily for billing-wise.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2325","11/10/2017 15:47:21",1,"Log teardown script output ""The sys-perf project has been leaking resources recently. It appears that the teardown script isn't being called. For instance, see this [host|https://evergreen.mongodb.com/host/i-0dc091d289bd98e76]. When the host was terminated, it says the teardown script ran successfully, but there is no output from the teardown script, and it ran suspiciously fast. For reference, here's a [host|https://evergreen.mongodb.com/host/i-0d622c42b5addd18e] from last week that was successfully torn down. This failure is causing us to leak resources, which in turn causes us to hit AWS limits on our sys-perf account, which in turn leads to purple tasks. We're having to do a lot of cleanup by hand to keep things working. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9648","11/13/2017 16:15:19",2,"reduce exported surface area of amboy/queue package ""also merge in the driver package.""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2330","11/13/2017 16:51:30",1,"Evergreen CLI should not log debug messages """""," $ evergreen get-update [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='attach.results' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='attach.xunit_results' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='gotest.parse_files' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='json.get' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='s3Copy.copy' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='json.send' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='keyval.inc' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='shell.exec' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='setup.initial' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='archive.targz_pack' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='archive.targz_unpack' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='expansions.update' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='git.apply_patch' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='json.get_history' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='s3.put' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='shell.cleanup' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='shell.track' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='expansions.fetch_vars' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='git.get_project' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='manifest.load' message='registering command'] [evergreen] 2017/11/13 11:47:36 [p=debug]: [command='s3.get' message='registering command'] Binary is already up to date at revision 2017-09-14 - not updating. ",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2332","11/13/2017 19:04:12",1,"Cannot apply patch that deletes binary file ""I deleted some files, including a binary file called """"paper\-100k.pdf"""", and submitted the change for a patch test with """"evergreen patch \-\- \-\-binary"""": https://evergreen.mongodb.com/task/mongo_c_driver_releng_link_with_cmake_mac_patch_760dbf8f60306dd4775c1690d3f1936b03431efe_5a09d242c9ec446c07006e6e_17_11_13_17_11_30 It logs: ... and proceeds to test the unpatched source."""," [2017/11/13 12:27:03.680] git reset --hard '760dbf8f60306dd4775c1690d3f1936b03431efe' [2017/11/13 12:27:03.759] git apply --check --whitespace=fix '/var/folders/9t/3_c20f0d03b063ys2_vyvk_c0000gm/T/mcipatch_093536943' [2017/11/13 12:27:03.822] error: patch failed: src/snappy-1.1.3/testdata/paper-100k.pdf:1 [2017/11/13 12:27:03.822] error: src/snappy-1.1.3/testdata/paper-100k.pdf: patch does not apply [2017/11/13 12:27:03.840] mongoc HEAD is now at 760dbf8 CDRIVER-2331 implement delete_one/many [2017/11/13 12:27:03.840] cd mongoc; git reset --hard 760dbf8f60306dd4775c1690d3f1936b03431efe [2017/11/13 12:27:03.840] HEAD is now at 760dbf8 CDRIVER-2331 implement delete_one/many [2017/11/13 12:27:03.840] Command failed: Failed to apply patch: exit status 1 [2017/11/13 12:27:03.840] Running command 'git.apply_patch' in """"fetch source"""" (step 1.2 of 5) [2017/11/13 12:27:03.840] git.apply_patch is deprecated. Patches are applied in git.get_project. ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9395","11/14/2017 15:11:35",1,"ConvertToComposer does not set log level on a fieldMessage on calls after the first ""We are logging startHosts success messages at Error but should be logging them at Info. https://github.com/evergreen-ci/evergreen/blob/master/hostinit/runner.go#L84 has the side effect of setting the message type to Error even though it doesn't log, so when the next line runs, it logs at the Error level even though it should lot at Info. I think this is because fieldMessage.setup() sets the metadata field to &Base only if it is not already set https://github.com/mongodb/grip/blob/master/message/fields.go#L117. As a result, ConvertToComposer, which is called by all *When methods even if they noop, only sets the level of a fieldMessage the first time it runs.""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2335","11/14/2017 18:29:05",1,"Hosts that fail to provision do not have logs to explain why ""E.g., https://evergreen.mongodb.com/host/sir-82qr4fyk""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2341","11/15/2017 23:27:41",1,"run longer tasks first ""all other things being equal, this should shorten makespan""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2342","11/16/2017 16:35:37",2,"remove unreachable static hosts from host pool ""seems reasonable to quarantine unreachable hosts to prevent putting pressure on the taskrunner until we can increase the taskrunner capacity.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2343","11/16/2017 16:57:03",2,"unschedule tasks older than a threshold ""to avoid forcing the scheduler to continually reconsider tasks that are underwater? we should define an underwater threshold, but one or two weeks is probably correct. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2355","11/17/2017 21:44:27",1,"logkeeper app logging improvements ""- slack - panic handlers""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2349","11/19/2017 22:42:24",1,"reduce taskrunner alert frequency. ""- alert only if a host fails 5 times in a row. - provide more context about an alert (provider/distro) ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2350","11/20/2017 14:04:09",2,"expand scope of host event log ""- queries/helpers to support: last n host events in order (by kind). - query to support: events (in order) in the last time period. - add event logs connectivity issues. - add event logs taskrunner errors. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2352","11/20/2017 16:15:35",1,"task_lifecycle.go incorrectly calculates that build is ""finished"" when 1 task remains ""I observed via the v2 build endpoint that when a build still has 1 task remaining, it believes that all tasks are complete and therefore calculates the finished time, make span, etc. This might be effecting the experience in the UI but is definitely confusing api users. The suspect line of code is here: https://github.com/evergreen-ci/evergreen/blob/9dd90b01cda9824688c287408a680901db0d60a1/model/task_lifecycle.go#L459 ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2354","11/20/2017 21:53:29",2,"Tooltips + filtering not working on history page ""As an example, if you look at this page: https://evergreen.mongodb.com/task_history/mongodb-mongo-master/noPassthrough_WT#/backup_restore_stop_start.js=fail&buildVariants= Hovering over failing tasks does not show the failing tests in the tooltip. In addition, the filter on the right side of the page no longer works. While not a blocker, this is still a pretty bad one for us.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2359","11/28/2017 19:50:49",1,"Misconfigured (?) alerts can cause API server to panic ""{ """"action"""":""""aborted"""", """"duration"""":99758786, """"metadata"""":{ """"level"""":80, """"hostname"""":""""evergreenapp-3.build.10gen.cc"""", """"time"""":""""2017-11-28T19:06:30.279939625Z"""", """"process"""":""""/srv/evergreen/current/clients/linux_amd64/evergreen"""", """"pid"""":23697 }, """"panic"""":""""invalid memory address or nil pointer dereference"""", """"path"""":""""/api/2/task/mms_e2e_local_with_daemon_E2E_Local_ATM_GSSAPI_Auth_39af01bba94eb8e94d772555ee352baf2bfe88b0_17_11_28_15_38_10/end"""", """"request"""":317538, """"span"""":""""99.759063ms"""", """"stack"""":{ """"message"""":""""[runtime/asm_amd64.s:510] """", """"frames"""":[ { """"function"""":""""runtime.call64"""", """"file"""":""""/usr/lib/go/src/runtime/asm_amd64.s"""", """"line"""":510 }, { """"function"""":""""runtime.gopanic"""", """"file"""":""""/usr/lib/go/src/runtime/panic.go"""", """"line"""":491 }, { """"function"""":""""runtime.panicmem"""", """"file"""":""""/usr/lib/go/src/runtime/panic.go"""", """"line"""":63 }, { """"function"""":""""runtime.sigpanic"""", """"file"""":""""/usr/lib/go/src/runtime/signal_unix.go"""", """"line"""":367 }, { """"function"""":""""github.com/evergreen-ci/evergreen/alerts.TaskFailTransition.ShouldExecute"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/alerts/project_triggers.go"""", """"line"""":157 }, { """"function"""":""""github.com/evergreen-ci/evergreen/alerts.(*TaskFailTransition).ShouldExecute"""", """"file"""":""""\u003cautogenerated\u003e"""", """"line"""":1 }, { """"function"""":""""github.com/evergreen-ci/evergreen/alerts.getActiveTaskFailureTriggers"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/alerts/alerts_activation.go"""", """"line"""":159 }, { """"function"""":""""github.com/evergreen-ci/evergreen/alerts.RunTaskFailureTriggers"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/alerts/alerts_activation.go"""", """"line"""":57 }, { """"function"""":""""github.com/evergreen-ci/evergreen/service.(*APIServer).EndTask"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/service/api_task.go"""", """"line"""":174 }, { """"function"""":""""github.com/evergreen-ci/evergreen/service.(*APIServer).EndTask-fm"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/service/api.go"""", """"line"""":768 }, { """"function"""":""""github.com/evergreen-ci/evergreen/service.(*APIServer).checkHost.func1"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/service/api.go"""", """"line"""":259 }, { """"function"""":""""github.com/evergreen-ci/evergreen/service.(*APIServer).checkTask.func1"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/service/api.go"""", """"line"""":170 }, { """"function"""":""""net/http.HandlerFunc.ServeHTTP"""", """"file"""":""""/usr/lib/go/src/net/http/server.go"""", """"line"""":1918 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux.(*Router).ServeHTTP"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux/mux.go"""", """"line"""":114 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.Wrap.func1"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go"""", """"line"""":46 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go"""", """"line"""":29 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go"""", """"line"""":38 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go"""", """"line"""":38 }, { """"function"""":""""github.com/evergreen-ci/evergreen/service.UserMiddleware.func1"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/service/middleware.go"""", """"line"""":399 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go"""", """"line"""":29 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go"""", """"line"""":38 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go"""", """"line"""":38 }, { """"function"""":""""github.com/evergreen-ci/evergreen/service.(*RecoveryLogger).ServeHTTP"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/service/middleware.go"""", """"line"""":472 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go"""", """"line"""":38 }, { """"function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(*Negroni).ServeHTTP"""", """"file"""":""""/home/tychoish/goprojects/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go"""", """"line"""":86 }, { """"function"""":""""net/http.serverHandler.ServeHTTP"""", """"file"""":""""/usr/lib/go/src/net/http/server.go"""", """"line"""":2619 }, { """"function"""":""""net/http.(*conn).serve"""", """"file"""":""""/usr/lib/go/src/net/http/server.go"""", """"line"""":1801 }, { """"function"""":""""runtime.goexit"""", """"file"""":""""/usr/lib/go/src/runtime/asm_amd64.s"""", """"line"""":2337 } ], """"time"""":""""2017-11-28T19:06:30.279914551Z"""" } }""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2360","11/28/2017 20:48:25",2,"JUnit parser omits errors in tests ""When the JUnit was parsed from https://evergreen.mongodb.com/task/mms_unit_java_UNIT_JAVA_MMS_patch_b13b9850dc1d66bb326b41c893b416446bcaaada_5a1db5ece3c3315c910004c4_17_11_28_19_15_56 - the error in {{com.xgen.svc.mms.svc.deployment.DeploymentDiffSvcUnitTests}} was not found. See attached XML file. If a JUnit file has {{errors>0}} in the {{}} block, then EVG must mark the test as failed and include the text from the {{}} element for the reason.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2362","11/29/2017 16:00:32",1,"Add parameter to expansions.update to ignore missing file ""The command {{expansions.update}} is used to update the expansion macros based on YML file. Sometimes this is done conditionally that the YML file may or may not be created. In this case the update fails, Perhaps a param could be added to suppress the error if the YML {{file}} does not exist. This is the case where it would be useful to have: {code} """"copy EC2 artifacts"""": - command: shell.exec params: shell: bash working_dir: src script: | if [ -z """"${ec2_artifacts}"""" ]; then exit 0 fi ... - command: expansions.update params: file: src/${aws_ec2_yml} {code} The function {{""""copy EC2 artifacts""""}} is invoked, but only should continue under certain conditions. Maybe an alternate method is to exit the function early, but I do not know how that can be done in {{evergreen.yml}} Resulting output: """," """"copy EC2 artifacts"""": - command: shell.exec params: shell: bash working_dir: src script: | if [ -z """"${ec2_artifacts}"""" ]; then exit 0 fi ... - command: expansions.update params: file: src/${aws_ec2_yml} [2017/11/29 10:13:09.130] Running command 'expansions.update' in """"copy EC2 artifacts"""" (step 2.2 of 33) [2017/11/29 10:13:09.130] Updating expansions with keys from file: src/ [2017/11/29 10:13:09.130] Command failed: read /data/mci/bbdeae674b4db3eb5d4989b897658e52/src: is a directory ",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9403","12/01/2017 16:01:52",1,"configure socket timeout in anserdb interface ""might make sense to also set this by default in the migration app to something reasonable? ""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9353","12/01/2017 16:02:46",2,"rate limiting pool smoke test suite ""- expand coverage - improve logging (anecdotally it appears to not be working""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2387","12/04/2017 16:47:29",2,"Look into why JIRA tickets were created for ops alerts over the weekend ""The two alerts: Host: sles12-z-2.maristisv.build.10gen.cc Distro: suse12-zseries-test jira_error ---------------- jira authentication error: Auth at JIRA instance failed (HTTP(S) request). Post /rest/auth/1/session: unsupported protocol scheme and Host: sles12-z-1.maristisv.build.10gen.cc Distro: suse12-zseries-build jira_error ---------------- jira authentication error: Auth at JIRA instance failed (HTTP(S) request). Post /rest/auth/1/session: unsupported protocol scheme""","",0,0,0,0,0,0,0,1,0,1,0,0,0,0,0 +"EVG-2389","12/06/2017 20:46:49",2,"Expansions update caused files to not be found after deploy ""See https://evergreen.mongodb.com/task/sqlproxy_full_matrix__os_full_matrix~windows_mongodb_version~latest_mongodb_topology~standalone_tdvt_patch_9a4997e9cd86d24ef206b8c0b29e5ccc6340b567_5a285085c9ec4467ae0000b9_17_12_06_20_18_14/0#/%23%257B%2522compare%2522%253A%255B%257B%2522hash%2522%253A%25229a4997e9cd86d24ef206b8c0b29e5ccc6340b567%2522%257D%255D%257D#%257B%2522compare%2522%253A%255B%257B%2522hash%2522%253A%25229a4997e9cd86d24ef206b8c0b29e5ccc6340b567%2522%257D%255D%257D""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2398","12/11/2017 17:44:49",1,"Logkeeper logs some messages at too high a level ""We should investigate and change them to the appropriate levels""","",0,0,1,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2400","12/11/2017 21:12:44",2,"update vendored migration tools ""- revendor amboy and anser - update migrations entry point to use new application structure - add new command for command line? - import any local changes to the migration utility ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2401","12/11/2017 23:19:10",2,"simple.exec command ""no shell just: - working directory, - envvar - args that we run shlex split on.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2402","12/11/2017 23:56:12",2,"add flag to files structure for filtering download ""- the default should be to download the file. - name: """"ignore_for_reproduction"""" ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2404","12/11/2017 23:59:12",2,"new attach.resources command ""- should work like attach.results, - allow file globbing, - use existing attach artifacts results. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2407","12/13/2017 17:15:05",1,"archive.targz_unpack cannot find file ""{{ls}} confirms the file is present, and yet: I don't see any cases of anyone actually using this command, so it's possible it's been broken for a while, but no one has noticed, or I may be using it incorrectly. I noticed this when I was trying to use the command in EVG-2377. We should probably add it to the smoke test when it's fixed."""," Command failed: error opening tar file archive.tgz for reading: open archive.tgz: no such file or directory ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9545","12/13/2017 17:58:40",1,"Add githash to curator version ""Print the githash as part of the curator version when {{--version}} is specified.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2408","12/13/2017 18:19:37",2,"Extend Rest v2 API to include patch alias ""Extend patches to include """"Alias"""". The __github alias indicates use of github pull request testing.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9678","12/13/2017 20:55:01",2,"grip.message.CollectAllProcesses() is slow on OS X 10.12 ""CollectAllProcesses() can take ~32 seconds to get list of running processes. See https://evergreen.mongodb.com/task/mci_osx_test_command_ac87c5d1aed2ec4a80f93b992e5c3e53c11427d2_17_12_12_17_01_28 Log from test on My computer: rsamuels  ⋯  github.com  evergreen-ci  evergreen  make test-command RUN_TEST=""""TestShellExecuteCommand/TestCancellingContextShouldCancelCommand"""" RUN_COUNT=50 go test -ldflags=""""-w -s -X=github.com/evergreen-ci/evergreen.BuildRevision=a82e9e00278d27efcea7b509e3663798bbd4939c"""" -c -o bin/test.command ./command EVGHOME=/Users/rsamuels/go/src/github.com/evergreen-ci/evergreen SETTINGS_OVERRIDE=/Users/rsamuels/mongo/creds.yml ./bin/test.command -test.v -test.run='TestShellExecuteCommand/TestCancellingContextShouldCancelCommand' -test.count='50' -test.timeout=10m 2>&1 | tee bin/output.command.test === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (30.61s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (30.60s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (31.17s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (31.17s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (31.23s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (31.22s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (31.87s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (31.87s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (32.11s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (32.11s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (31.22s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (31.22s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (32.12s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (32.12s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (31.69s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (31.69s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (31.83s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (31.83s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (30.88s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (30.87s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (31.98s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (31.98s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (31.78s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (31.77s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (31.94s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (31.94s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (32.67s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (32.66s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (32.44s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (32.44s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (33.81s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (33.80s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (34.15s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (34.15s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand --- PASS: TestShellExecuteCommand (34.45s) --- PASS: TestShellExecuteCommand/TestCancellingContextShouldCancelCommand (34.45s) === RUN TestShellExecuteCommand === RUN TestShellExecuteCommand/TestCancellingContextShouldCancelCommand panic: test timed out after 10m0s""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9376","12/13/2017 22:21:16",1,"Time from ""curator stat"" on Windows is incorrect ""The time reported by curator for {{stat}} is incorrect, and always the same on Windows: """," """"metadata"""":{""""level"""":40,""""time"""":""""0001-01-01T00:00:00Z""""} ",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2410","12/13/2017 23:05:07",1,"Smoke test failing due to address already in use "" https://evergreen.mongodb.com/task_log_raw/mci_ubuntu1604_smoke_test_783f92be62e7d0877d86e2d0bc80f498b853b328_17_12_13_22_42_43/1?type=T&text=true"""," [2017/12/13 17:59:26.704] [web.service] 2017/12/13 22:59:26 [p=trace]: listen tcp :8080: bind: address already in use [2017/12/13 17:59:26.704] [web.service] 2017/12/13 22:59:26 [p=trace]: listen tcp :9090: bind: address already in use ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9341","12/14/2017 22:26:51",2,"Curator cannot write to an existing file ""I am using the following command. When issuing it a second time (after the file has been closed (system rebooted), it fails to write to the file and provides the result to stdout. Resulting output: """," ./curator stat system --file system.json [curator.stats]2017/12/14 17:24:15 logging error: write system.json: bad file descriptor ",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2417","12/14/2017 22:53:12",2,"new manifests should populate the branch field ""they use the project rather than the project_ref. in service/api_plugin_manifest.go""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2423","12/18/2017 15:21:24",2,"Smoke test should load data itself instead of doing it in bash in self-tests.yml ""This will also allow us to generate the agent secret dynamically.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2451","12/19/2017 20:16:10",2,"improve handling of logging errors ""particularly around the deco-host alert""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2436","12/20/2017 14:48:04",1,"Large display tasks have some visual issues ""https://evergreen-staging.corp.mongodb.com/task/mci_race_detector_display_lint_patch_0cc8e73995b8c9ea86632b8cb97de262b76c502e_5a3999f59dbe32091a00000a_17_12_19_23_00_25""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2438","12/20/2017 16:19:16",5,"Improved performance chart analysis by controlling y axis range and scale ""In order to make it easier to for engineers to analyze charts, it would be helpful to be able to toggle the y-axis to control: 1. Linear vs Logarithmic scale 2. Origin (0) based vs Zoomed in Acceptance Criteria: 1. Ability to toggle linear vs logarithmic on performance chart page that will update all charts 2. Ability to toggle Origin vs Zoomed In for y-axis starting off point 3. Preference are maintained for the duration of the session 4. Default is Linear, Zoomed 5. Toggle should float so you can access it anywhere (regardless of scrolling)""","",0,1,0,0,0,0,0,0,0,0,1,1,0,0,0 +"EVG-2439","12/20/2017 16:31:10",2,"Queries in model/scheduler_stats.go should skip display tasks ""These queries rely on task metadata (like scheduled and started) that are not set for display tasks.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2440","12/20/2017 16:38:12",2,"Finishing a display task causes visual bug for its box ""https://evergreen.mongodb.com/task/mci_race_detector_display_lint_bff5658ca3ec9e21b1e84b63bc909d3c0ad924e8_17_12_20_16_29_50 { """"id"""" : """"mci_race_detector_dist_bff5658ca3ec9e21b1e84b63bc909d3c0ad924e8_17_12_20_16_29_50"""", """"d"""" : """"dist"""", """"s"""" : """"failed"""", """"ed"""" : { """"status"""" : """"failed"""", """"type"""" : """"test"""", """"desc"""" : """"'shell.exec' in \""""run-make\"""""""" }, """"st"""" : ISODate(""""2017-12-20T16:33:50.946Z""""), """"tt"""" : NumberLong(""""60353534749""""), """"a"""" : true },""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2444","12/20/2017 19:48:31",1,"Specify --index in git apply for patch builds ""This would allow us to be able to apply patches from the {{.gitmodules}} file. See an example build here where we currently do not do this and fail a patch because of it https://evergreen.mongodb.com/task/stitch_ios_sdk_linux_64_run_tests_patch_aebe6ea5306136c6a284ddc6bfd7bcb0968fbfb1_5a39c1dfe3c33112c4001acc_17_12_20_01_50_23.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2446","12/21/2017 03:07:13",1,"fix and reenable underwater task pruning ""we turned it off with a feature flag, because the query is backwards. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2447","12/21/2017 15:31:01",1,"Remove size field from distro mount points ""We do not use this field, and it is not supported by aws-sdk-go. After EVG-2416, we should remove this field from the UI.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2450","12/24/2017 02:21:52",2,"make subprocess.Command implementations private ""it looks like we mostly use the literal constructors, which we'll need to replace. additionally the ssh and scp implementations can be refactored and simplified given the use of the CommandContext constructor. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2453","12/27/2017 16:07:06",1,"Sorting by time taken on Evergreen task page doesn't sort correctly ""For example, see https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_osx_1010_mmapv1_jstestfuzz_replication_resync_3949ed24bfe7e936384120a785c1e6ad627bc1bd_17_12_13_03_41_35/0. !Screen Shot 2017-12-27 at 10.52.42 AM.png|thumbnail! In https://evergreen.mongodb.com/task/mongodb_mongo_v3.6_enterprise_osx_1010_mmapv1_replica_sets_initsync_jscore_passthrough_b5cdf38ac7a01e4abd519d8a8019c47cfaf8b7e0_17_12_18_21_19_09/0, {{views_all_commands.js}} ran for 23 minutes, but appears towards the bottom. !Screen Shot 2017-12-27 at 10.55.49 AM.png|thumbnail!""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2456","12/27/2017 21:33:04",2,"Something set a task to priority to < 0 ""This caused the task to show status """"Blacklisted"""". Since this is not possible to set with the UI, something set this task to have a negative priority. Setting the priority via the UI to non-negative fixed this particular task, but we should figure out what set this priority. https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_sharding_jscore_passthrough_WT_patch_43b1a2984a4c7b9d1fbc9e4d0d6596c6f626ffda_5a43de53e3c33137e1004d18_17_12_27_17_55_10""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2457","12/28/2017 19:56:43",1,"scripts/all_configs.go is broken "" Most likely because evergreen/cli was removed in https://github.com/evergreen-ci/evergreen/commit/01ee03317c369b5663637be7dda2891bd3c7fc2b""","$ go build scripts/all_configs.go scripts/all_configs.go:21:2: cannot find package """"github.com/evergreen-ci/evergreen/cli"""" in any of: ....",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-2461","12/29/2017 16:31:07",1,"Add degraded mode flag to prevent CLI from updating ""For cases where we know the CLI is known to be broken.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2462","12/29/2017 19:21:15",1,"smoke-test-endpoints failure ""h2. [smoke-test-endpoints failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_smoke_test_endpoints_0e61f0b474edc2ba483df93a1b3985786163c2ba_17_12_29_18_17_15/0] Host: [ec2-54-92-156-27.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-8d587wmh] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2463","12/29/2017 20:51:53",2,"Task page continuously requests the task logs ""When on a task page, the full task logs are requested and downloaded every few seconds by the browser. This happens even after the task has ended and the logs no longer change.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2464","01/01/2018 21:12:38",2,"Automatically retry jobs that fail due to host termination ""I've investigated several test failures that turned out to be due to a host termination - for example BF-7103. It would reduce the amount of noise in the Evergreen test results if jobs that fail due to a host being terminated were automatically retried.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2473","01/02/2018 17:18:45",1,"call repotracker function in webhook handler for push events ""- in amboy job""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2474","01/02/2018 17:19:43",2,"test-cloud failure ""h2. [race-cloud failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_cloud_ca50b345db53a9eaae5f55f56e9d564d8a25a0f5_18_01_02_16_53_00/0] Host: [ec2-54-221-22-58.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-apci7chh] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2480","01/03/2018 16:07:31",1,"Rename simple.exec to subprocess.exec ""Subprocess.exec has been implemented but under another name. Since it is not yet used, we can simply rename it in the commands package.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2482","01/03/2018 16:10:07",2,"Define generate.tasks model ""Define the model that describes the JSON document which will be passed to the generate.tasks command.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2485","01/03/2018 16:14:38",2,"Create task_group model ""This model will be used to parse the evergreen configuration file.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2486","01/03/2018 16:15:29",2,"Make changes to task model for task_group ""Add any task_group metadata that we will need to hold onto.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2487","01/03/2018 16:16:24",2,"Add last_task_group field to host model ""Add a previous_task_group field. Do not change running_task, as this is used to determine if a host can be assigned a task.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2489","01/03/2018 16:18:43",2,"Design interface for next task discovery ""This is to support 3 other tickets: Implement a mock for next task discovery. Implement discovering the next task for a task_group. Implement discovering the next task for tasks not in task groups.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2490","01/03/2018 16:23:00",2,"Implement task removal from queue ""We need to support removing a task from the middle of the queue, and determine when we will need to do this.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2491","01/03/2018 16:24:35",1,"Implement mock for next task discovery ""Implement the interface for testing.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2493","01/03/2018 16:29:30",2,"Implement next task discovery for tasks not in task groups ""Tasks not in a task_group are in a task_group of 1.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2494","01/03/2018 16:31:56",2,"Modify agent GetNextTask logic to take into account task groups ""The agent needs to handle the additional data it will receive, i.e., setup and teardown logic.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2496","01/03/2018 16:33:48",2,"Add task_group setup/teardown test logic to agent ""This setup/teardown runs before and after each task in a task_group. Certain commands, like attach.artifacts, should be illegal here.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2497","01/03/2018 16:34:29",2,"Add timeout handler for task_group ""This will run if a task in a task group times out. If it does not exist the top-level timeout handler will run.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2498","01/03/2018 16:35:16",2,"Change pre/post to use task_group setup/teardown handlers ""The implementation for this is that tasks not in a task_group are in a task_group of 1. The difference is that their setup and teardown is in fact pre and post.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2505","01/03/2018 17:41:46",1,"Able to edit patch alias name to be blank ""# Create a patch alias # Save it # Delete the alias name field # Save again What should happen: Save fails with an error messages. What actually happens: Save succeeds.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2507","01/03/2018 21:22:32",1,"Don't step back lint tasks ""since they take a long time and it's not that important""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2509","01/03/2018 22:58:12",1,"left nav on jscore very slow to load ""See for example: https://evergreen.mongodb.com/task/mongodb_mongo_v3.6_enterprise_rhel_62_64_bit_jsCore_a6a3056ce0833e969665380e0eca7ed2aca42742_18_01_03_21_21_01 Any jscore passthrough is similarly impacted. Takes about 23.49s to load the left nav. This nav is essential for identifying when a test started failing.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2514","01/04/2018 21:02:29",2,"Lobster line numbers should always be visible ""Since line numbers are needed for bookmarking, They should always stay on the left side of the page no matter how far you scroll to the right.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2533","01/05/2018 16:49:20",1,"hostinit should log errors at a higher level "" if ready, err := init.IsHostReady(&h); !ready { m := message.Fields{ """"GUID"""": init.GUID, """"message"""": """"host not ready for setup"""", """"hostid"""": h.Id, """"DNS"""": h.Host, """"runner"""": RunnerName, } if err != nil { m[""""error""""] = err.Error() } grip.Info(m) continue }""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2538","01/05/2018 20:26:09",1,"UI server panics if you try to view a task execution that doesn't exist ""https://evergreen-staging.corp.mongodb.com/task/mci_race_detector_race_hostinit_959673cc5c242f1a5669171a353f8dc4bb1b9058_18_01_04_19_33_08/5 (switched to a staging link to we panic prod by clicking this)""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2544","01/08/2018 16:28:48",1,"test-command failure ""h2. [test-command failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_command_055bf72a82de7ae4e0551bc097a524ccd6cc654a_18_01_08_15_39_50/0] Host: [ec2-54-144-148-137.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-mchr7t9j] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2545","01/08/2018 17:24:47",2,"Expansions for Patches created by Github Pull Requests ""github_pr_number github_org github_repo github_author""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2546","01/08/2018 18:26:52",1,"test-cloud failure ""h2. [test-cloud failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_cloud_0ecf2db50c3df64e0db5e1ccab40e016d5ff2ecc_18_01_08_17_20_28/0] Host: [ec2-54-196-16-165.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-fm3r4jrh] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2548","01/08/2018 22:07:42",2,"Write additional integration tests for new ec2 host provider ""There is currently one for spot, but not for on-demand. There may also be an opportunity to improve the spot integration test, and to add integration tests for features other than spawn.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2549","01/08/2018 22:16:28",1,"race-cloud failure ""h2. [race-cloud failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_cloud_adac48ce22826cb6a33202d38184a3f3566e6bff_18_01_08_21_01_25/0] Host: [ec2-54-211-48-14.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-46ni524k] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2551","01/09/2018 14:44:12",1,"test-command failure ""h2. [test-command failed on windows|https://evergreen.mongodb.com/task/mci_windows_test_command_adac48ce22826cb6a33202d38184a3f3566e6bff_18_01_08_21_01_25/0] Host: [ec2-54-147-219-159.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-mvci6gwj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2554","01/09/2018 15:29:26",2,"Display task in which all execution tasks are green is red ""https://evergreen.mongodb.com/task/mci_race_detector_display_lint_1d9ce86c998861e2980ea0f8cf72e950e62fee46_18_01_09_14_15_14""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2557","01/09/2018 15:50:40",1,"Display tasks should list number of execution tasks they contain ""It's not obvious in the screenshot that the lint task contains 38 tasks, of which only 37 have run. It would be nice to add the number to the """"This task contains:"""" line, like """"This task contains 38 tasks:"""".""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2559","01/09/2018 16:47:24",1,"lint-spawn failure ""h2. [lint-spawn failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_lint_spawn_1d9ce86c998861e2980ea0f8cf72e950e62fee46_18_01_09_14_15_14/0] Host: [ec2-54-205-156-199.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-cg686e1h] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2563","01/10/2018 15:22:13",2,"lobster search malfunctions for 1-hit searches ""If you type in a search in lobster for a search string that only has one hit, you cannot subsequently redo the search. That is, after typing the search string and clicking """"Find"""", and then scrolling the window around, you cannot then click on """"Next"""" or """"Previous"""" (or even """"Find"""") and have the window re-center on the search term again. Instead, you must edit the search string and search for something else, and then put the original search term back in and search again. Ideally, clicking on """"Find"""" would re-do the search. I've also on occasion managed to gum up the searcher such that the viewport on the webpage is no longer updated. That is, when I scroll the web page, the only text visible is the original text in the viewport, and the rest of the webpage is blank. I'm not sure what would cause this or how to diagnose the problem (I ended up reloading the entire page to fix it.).""","",0,0,1,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2565","01/10/2018 17:14:34",2,"Add Ability to Approve External Pull Request Patches ""WiredTiger would like the ability for an authorized internal user to approve patches from the community for running in evergreen.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9349","01/10/2018 18:48:29",2,"message.WrapStack type ""that can wrap a composer (or similar.) ""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-9458","01/10/2018 18:49:29",2,"make conditional logging a composer feature. ""rather than a property of the journaling level.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2566","01/10/2018 18:58:54",1,"Github PR Testing Degraded Mode should not prevent status updates for running patches. ""Github status API updates should have their own degraded mode flag.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2568","01/10/2018 20:55:07",1,"Add flag to allow individual projects to use Github webhooks to track pushes, instead of repotracker polling ""We currently poll GitHub for new commits. This is becoming unsustainable. We currently use more than 80% of our hourly GitHub wait limit. We should allow projects to opt in to using webhooks. The repotracker runner should exclude projects with this flag enabled.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2569","01/10/2018 20:55:52",1,"Increase infrequent runner interval to 3 minutes ""This is currently set at 2 minutes. The infrequent runners are alerts, notify, and repotracker. We need to reduce this interval because the repotracker is getting close to using up our GitHub rate limit. We hope to fix this by moving projects to EVG-2568.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2581","01/11/2018 15:02:03",1,"Provide additional data dumps for perf visualization development ""In order for Ruslan to get a representative set of data to validate his changes, we need to get him some additional workloads. Here are the ones that are unique and currently generate bugs: Sys Perf Core Workloads: https://evergreen.mongodb.com/task/sys_perf_linux_3_node_replSet_core_workloads_WT_852ff9f97b6b92f5c3a88d0e070fe9c0f90ef175_17_11_30_16_44_10 Mongo Perf: https://evergreen.mongodb.com/task/performance_linux_mmap_standalone_insert_37cb7ea09393e88662e3139bd20fa29e59f2a1a3_18_01_11_00_01_36""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2575","01/11/2018 15:15:40",1,"race-agent failure ""h2. [race-agent failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_agent_0bbb82ca2a64b921cf851aefdd213dbe6e401f7b_18_01_10_22_53_43/0] Host: [ec2-54-163-164-130.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-1ji8764j] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2585","01/12/2018 21:29:37",1,"Host reachability check should not return error if context is canceled ""error: error checking if host sir-z6fr7rxh is reachable: reachability command encountered error for sir-z6fr7rxh: signal: killed extended: signal: killed github.com/evergreen-ci/evergreen/subprocess.(*remoteCmd).Run /Users/brian/go/src/github.com/evergreen-ci/evergreen/subprocess/remote_command.go:66 github.com/evergreen-ci/evergreen/hostutil.CheckSSHResponse /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostutil/host_status.go:61 github.com/evergreen-ci/evergreen/cloud.(*ec2SpotManager).IsSSHReachable /Users/brian/go/src/github.com/evergreen-ci/evergreen/cloud/ec2_spot.go:174 github.com/evergreen-ci/evergreen/cloud.(*CloudHost).IsSSHReachable /Users/brian/go/src/github.com/evergreen-ci/evergreen/cloud/cloud_host.go:45 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:367 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:223 runtime.goexit /usr/local/Cellar/go/1.9.2/libexec/src/runtime/asm_amd64.s:2337 reachability command encountered error for sir-z6fr7rxh github.com/evergreen-ci/evergreen/hostutil.CheckSSHResponse /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostutil/host_status.go:71 github.com/evergreen-ci/evergreen/cloud.(*ec2SpotManager).IsSSHReachable /Users/brian/go/src/github.com/evergreen-ci/evergreen/cloud/ec2_spot.go:174 github.com/evergreen-ci/evergreen/cloud.(*CloudHost).IsSSHReachable /Users/brian/go/src/github.com/evergreen-ci/evergreen/cloud/cloud_host.go:45 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:367 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:223 runtime.goexit /usr/local/Cellar/go/1.9.2/libexec/src/runtime/asm_amd64.s:2337 github.com/evergreen-ci/evergreen/cloud.(*ec2SpotManager).IsSSHReachable /Users/brian/go/src/github.com/evergreen-ci/evergreen/cloud/ec2_spot.go:182 github.com/evergreen-ci/evergreen/cloud.(*CloudHost).IsSSHReachable /Users/brian/go/src/github.com/evergreen-ci/evergreen/cloud/cloud_host.go:45 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:367 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:223 runtime.goexit /usr/local/Cellar/go/1.9.2/libexec/src/runtime/asm_amd64.s:2337 error checking if host sir-z6fr7rxh is reachable github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:369 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /Users/brian/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:223 runtime.goexit /usr/local/Cellar/go/1.9.2/libexec/src/runtime/asm_amd64.s:2337 ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2586","01/12/2018 21:58:51",1,"GitHub PR testing does not appear to unschedule patches after PR is merged ""https://github.com/evergreen-ci/evergreen/pull/577""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2589","01/12/2018 22:41:37",2,"Add way to see intersection of filters, rather than union in lobster ""Currently if you have one filter active and then add another, the set of log lines returned grows - you see logs that match *any* of your active filters. It'd be nice to add a toggle so that you could only see lines that match *all* of your active filters.""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2590","01/16/2018 14:07:32",1,"Log manual host status changes in the event log ""I think just add usernames to log ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2592","01/16/2018 15:44:36",1,"Increase number of system failures required to quarantine hosts from 3 to 6 ""Per in-person conversation.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2593","01/16/2018 17:23:24",1,"test-cloud failure ""h2. [test-cloud failed on osx|https://evergreen.mongodb.com/task/mci_osx_test_cloud_2ee67df2bf21df26b8529b12ebd700c14bd39564_18_01_12_21_50_43/0] Host: [macos-1012-46.macstadium.build.10gen.cc|https://evergreen.mongodb.com/host/macos-1012-46.macstadium.build.10gen.cc] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2594","01/16/2018 17:25:58",1,"test-agent failure ""h2. [test-agent failed on osx|https://evergreen.mongodb.com/task/mci_osx_test_agent_2ee67df2bf21df26b8529b12ebd700c14bd39564_18_01_12_21_50_43/0] Host: [macos-1012-30.macstadium.build.10gen.cc|https://evergreen.mongodb.com/host/macos-1012-30.macstadium.build.10gen.cc] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2596","01/16/2018 19:28:04",0,"Clean up Evergreen CLI update routes/data structures ""Don't do this before EVG-2461 has been deployed to production for around a month. Evergreen users need enough time to update to new version, with the new api. # Remove json metadata from evergreen.ClientConfig and it's substructures # Remove """"/update/"""" route (as.getUpdate) from service/api.go""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2597","01/16/2018 22:02:52",1,"Unscheduled task not in queue shows itself as 1st in queue on task page ""https://evergreen.mongodb.com/task/bson_ruby_tests_special_os__special_os~rhel55_32_latest_stable_rubies~ruby_2.4.2_test_4233ec5714033dffd901b3e9dc6645aa95b2705a_18_01_16_10_00_28""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2599","01/17/2018 11:08:07",2,"Dates displayed in the performance waterfall as the run time dates. ""The new date functionality displays the run rather than the commit date. As a result, the date labels can be out of order (although the order of commits is still correct). ""","",0,0,1,0,0,0,0,0,0,0,1,1,0,0,0 +"EVG-2601","01/17/2018 15:33:02",2,"Patch alias does not support display tasks ""- You can select part of a display task with an alias - Selecting all tasks in a display task with an alias does not select the display task""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2602","01/17/2018 15:40:45",2,"Project aliases should use own collection ""We have code in project_aliases.go to do this already.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2604","01/17/2018 17:58:58",1,"Spawn hosts have bad behavior when provisioning fails ""There are two problematic cases: 1. If a spawn host fails to provision, it will simply disappear from the user's page. 2. If the binary fails to fetch artifacts, the user will still receive the spawn host with missing artifacts. Hosts fail to provision 3-5% of the time. However, with build hosts, if a host fails, we simply start another one. For spawn hosts we either do not give the user a spawn host or we give them one in a bad state. We should fix this. We could, for example, not give the user a spawn host until we are sure it is in a good state, and keep the UI element in the in progress state until then, even if we need to throw away a host that failed to provision.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2612","01/18/2018 19:43:45",1,"Taskrunner puts agent on host even though setup script failed to run ""https://evergreen.mongodb.com/host/sir-f4d86fzg""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2613","01/19/2018 14:22:47",2,"Add individual task execution data support in the REST v2 API ""Current Behavior: When requesting task data via the /tasks or /build/xyz/tasks endpoint - only the latest task execution is provided. Requested Behavior: When requesting task data via the /tasks or /build/xyz/tasks endpoint - either all task executions are provided or by default only the latest is provided with some option to get the whole list. This is necessary when trying to analyze historical results from New Relic and other data ingestion frameworks.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2617","01/19/2018 16:07:15",2,"Lobster mis-colors sharded passthroughs and mongos ""All primaries are given the same color, regardless of which shard/configsvr they're from. Ex: https://logkeeper.mongodb.org/lobster/build/657b16b8eac8676156b6eb494e1fac5a/test/5a610b6fbe07c42d9b0ce29b?bookmarks=0%2C24011""","",0,0,1,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2618","01/19/2018 20:03:07",1,"The Lobster ""Details"" toolbar dropdown should be hidden by default ""In my workflow I find that I rarely use the tools exposed in the details drop down but have to click """"Hide Details"""" every time I launch as it is overlays log content.""","",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2622","01/22/2018 14:26:38",1,"Attached artifacts not associating links to task ""The evergreen command {{attach.artifacts}} is not displaying the associated artifacts. This is because the artifacts are not being associated to task (in the DB).""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2623","01/22/2018 14:31:48",2,"Task history page doesn't highlight boxes that match test filter ""The task history page used to make the boxes larger and a different color if they matched the test filter. This isn't happening anymore and the changes from EVG-2354 don't seem to have addressed this. https://evergreen.mongodb.com/task_history/mongodb-mongo-master/sharding_last_stable_mongos_and_mixed_shards?revision=42c264630fa1e7d5924c291a9eeac6522d70f31e#/coll_epoch_test1.js=fail""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2624","01/22/2018 14:43:06",1,"Sorting test results by ""sequence"" causes them to display in reverse execution order ""Sorting test results by """"sequence"""" previously would sort with the first test executed by resmoke.py job #0, to the second test executed by resmoke.py job #0, ..., to the first test executed by resmoke.py job #1, etc. The test results are currently being displayed as the last test executed by resmoke.py's last job, etc. https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_sharding_last_stable_mongos_and_mixed_shards_42c264630fa1e7d5924c291a9eeac6522d70f31e_18_01_20_02_50_28#/sort=Sequence I suspect this is fallout from the changes from [1f09198|https://github.com/evergreen-ci/evergreen/commit/1f09198b40a03f62233ea382ff8836cc7d4dc359] as part of EVG-2453, where potentially sorting by the empty string previously wouldn't respect {{reverse=true}}. I suspect it is sufficient to change [the {{reverse=true}} line|https://github.com/evergreen-ci/evergreen/blob/3a9201a2c06f318cdffb068c02569a8c12c855ee/public/static/js/task.js#L343] to {{reverse=false}} in order to restore the old behavior.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2634","01/23/2018 21:21:05",1,"New Cloud spot provider panics ""https://gist.github.com/bsamek/c46c94a89c76629cf97bc6d116d95816""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9514","01/24/2018 18:34:38",2,"add time to amboy.Job ""for """"created"""" """"start after"""" time. implementation entirely in Base. pushed up to interchange. ""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2637","01/24/2018 20:10:20",1,"Errors are logged for unreachable hosts """""," { [-] DNS: ec2-34-228-199-71.compute-1.amazonaws.com GUID: dcc82768226ef6154894e2bada42fe6b distro: rhel62-test error: error checking if host sir-teqr6fnh is reachable: reachability command encountered error for sir-teqr6fnh: exit status 255 extended: exit status 255 github.com/evergreen-ci/evergreen/subprocess.(*remoteCmd).Run /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/subprocess/remote_command.go:66 github.com/evergreen-ci/evergreen/hostutil.CheckSSHResponse /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostutil/host_status.go:61 github.com/evergreen-ci/evergreen/cloud.(*ec2SpotManager).IsSSHReachable /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/cloud/ec2_spot.go:174 github.com/evergreen-ci/evergreen/cloud.(*CloudHost).IsSSHReachable /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/cloud/cloud_host.go:45 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:369 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:225 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 reachability command encountered error for sir-teqr6fnh github.com/evergreen-ci/evergreen/hostutil.CheckSSHResponse /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostutil/host_status.go:75 github.com/evergreen-ci/evergreen/cloud.(*ec2SpotManager).IsSSHReachable /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/cloud/ec2_spot.go:174 github.com/evergreen-ci/evergreen/cloud.(*CloudHost).IsSSHReachable /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/cloud/cloud_host.go:45 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:369 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:225 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 github.com/evergreen-ci/evergreen/cloud.(*ec2SpotManager).IsSSHReachable /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/cloud/ec2_spot.go:182 github.com/evergreen-ci/evergreen/cloud.(*CloudHost).IsSSHReachable /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/cloud/cloud_host.go:45 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:369 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:225 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 error checking if host sir-teqr6fnh is reachable github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:371 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /data/mci/3214f7994cffca2c1967cb2d129fd831/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:225 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 hostid: sir-teqr6fnh message: host not ready for setup metadata: { [+] } runner: hostinit } ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2639","01/25/2018 16:10:52",1,"Do not run reachability checks over SSH for EC2 hosts ""We should verify that the reachability check is not essential for dynamic hosts to receive a new agent. If getting/starting an agent after first launch and after agents exit does not depend on the reachability check, and if dynamic hosts will be reaped if they are idle, then we may be able to restrict reachability checks for static hosts. This will prevent us from reaping dynamic hosts due to ephemeral networking problems.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2641","01/26/2018 16:21:35",2,"Evergreen claims Github PR patches completed in negative times "" “31 succeeded, 1 failed, 7 other in -2562047h47m16.854775808s” Steps: 1. Rerun failing task in a github PR patch 2. push another change. I noticed that ubuntu1604 had several unfinished/unstarted tasks at this time, so the update for the evergreen context never should have been posted.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2642","01/26/2018 16:22:01",1,"js-test failure "" h2. [js-test failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_js_test_f03f3cc35188c90c9bcbb8d086664023907acbf4_18_01_26_14_19_31/0] Host: [ec2-34-228-162-89.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-9t187bbj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,0,1,0,0,0,0 +"EVG-2644","01/26/2018 17:18:24",1,"Use VPCs in cloud tests ""Switch to using VPC in cloud integration test and switch instance type to t2.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2651","01/28/2018 22:06:42",2,"Display tasks do not show color for previous execution in patches, task history drawer ""https://evergreen.mongodb.com/version/5a6e487ce3c3314e5c002a39 https://evergreen.mongodb.com/task/mci_race_detector_display_lint_caa84e43680cee15e7d6014f6a14eb6484c19ec6_18_01_26_22_18_28""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2653","01/29/2018 14:53:18",1,"dist-test failure ""h2. [dist-test failed on ubuntu1604-arm64|https://evergreen.mongodb.com/task/mci_ubuntu1604_arm64_dist_test_3ae4e4d120b090ad4e258863c72e207f501acdd3_18_01_29_03_14_42/1] Host: [ec2-107-21-12-112.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-6x6g574h] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2667","01/29/2018 18:30:17",1,"Commit including a binary on GitHub fails to apply in patch ""We are beta testing the new GitHub PR to EVG patch feature, and I pushed a binary commit to an existing PR. Unfortunately, every task that checks out our source fails with: {{{+ git apply --stat /tmp/mcipatch_282431706 [2018/01/29 13:25:47.622] + git apply --binary --whitespace=fix --index [2018/01/29 13:25:47.629] :18: new blank line at EOF. [2018/01/29 13:25:47.629] + [2018/01/29 13:25:47.629] error: cannot apply binary patch to 'onprem-setup-setup-onprem_FAILURE.png' without full index line [2018/01/29 13:25:47.630] error: onprem-setup-setup-onprem_FAILURE.png: patch does not apply}} See https://evergreen.mongodb.com/version/5a6f6485c9ec447e020004f2""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2669","01/29/2018 19:19:38",1,"test-cloud failure ""h2. [test-cloud failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_cloud_bcc0a55519c7a7d47898afdc344e71dd2aaf39fc_18_01_29_18_57_11/0] Host: [ec2-52-91-111-249.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-zt6r7qdk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2670","01/29/2018 20:27:50",2,"Allow users to reconfigure tasks for patch builds created through GitHub PR testing ""Dependency: For Performance team, this would be useful if we can trigger sys-perf patch build (head of master) from a PR to 10gen/dsi. In sys-perf, we have quite a few tasks and some of them run for a long time. We would like to add a couple smoke test tasks, like ycsb_short and mongoshell_short, and configure those to always be triggered automatically when one posts a PR. But, if I know that my patch is in fact related to the initialsync_logkeeper_WT task, then I should be able to go into the patch build page and schedule that task in addition to the automatically scheduled ones. It should also be possible for a reviewer to do so. (Basically, any MongoDB Inc engineer.) I'm torn on the question whether it should be allowed to unschedule the automatically added ones. A possible answer is that it should be allowed to do so in evergreen, but if a repo is configured to require certain tests to pass, then failing to run said tests would of course block ability to merge the PR.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2673","01/30/2018 15:37:40",1,"prevent evergreen from running empty updatealls ""or try at least ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2675","01/30/2018 15:39:58",1,"distro page should deco hosts option has incorrect query form ""Fix issue introduced in EVG-1128""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2676","01/30/2018 15:43:27",1,"clean up middleware ""we have dropped support for pre-go1.7 which means we can remove some code and do some clean up""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2677","01/30/2018 15:43:28",1,"Log ""X-Cluster-Client-Ip"" header of API calls to Evergreen ""This came out of a discussion with [~cristopher.stauffer]. He had a script running against Evergreen but wasn't sure where it was running. There may be other cases where we would like the IP address of a host making API calls against Evergreen. The load balancer inserts this IP address as the """"X-Cluster-Client-Ip"""". We should include this IP address in the Splunk logs.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2690","01/30/2018 17:04:04",1,"cli host terminate ""panic: terminate flag redefined: h"" "" """," [gabriel@earthshaker mongo]$ cli host terminate i-07b2f0164fd56f35f terminate flag redefined: h panic: terminate flag redefined: h goroutine 1 [running]: flag.(*FlagSet).Var(0xc4200764e0, 0x2b95a60, 0xc42012412f, 0x1cfa546, 0x1, 0x1cfde89, 0x9) /opt/go1.8/go/src/flag/flag.go:793 +0x420 flag.(*FlagSet).BoolVar(0xc4200764e0, 0xc42012412f, 0x1cfa546, 0x1, 0x4d0000, 0x1cfde89, 0x9) /opt/go1.8/go/src/flag/flag.go:566 +0x70 flag.(*FlagSet).Bool(0xc4200764e0, 0x1cfa546, 0x1, 0x0, 0x1cfde89, 0x9, 0x1) /opt/go1.8/go/src/flag/flag.go:579 +0x7f github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.BoolFlag.Apply.func1(0x1cfa546, 0x1) /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli/flag.go:283 +0xa7 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.eachName(0x1cfa540, 0x7, 0xc4204f2a70) /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli/flag.go:63 +0xb5 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.BoolFlag.Apply(0x1cfa540, 0x7, 0x1cfde89, 0x9, 0x0, 0x0, 0x0, 0x0, 0xc4200764e0) /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli/flag.go:284 +0x101 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.(*BoolFlag).Apply(0xc42020d640, 0xc4200764e0) :21 +0x66 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.flagSet(0x1cfe0d2, 0x9, 0xc420133b40, 0x2, 0x2, 0xc420133b40) /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli/flag.go:54 +0x7d github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.Command.Run(0x1cfe0d2, 0x9, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1d34652, 0x1c, 0x0, ...) /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli/command.go:89 +0xd6 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.(*App).RunAsSubcommand(0xc42009a180, 0xc4200de280, 0x0, 0x0) /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli/app.go:356 +0xa1f github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.Command.startApp(0x1cf5fa4, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1d53564, 0x26, 0x0, ...) /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli/command.go:273 +0x81b github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.Command.Run(0x1cf5fa4, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1d53564, 0x26, 0x0, ...) /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli/command.go:74 +0x142c github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli.(*App).Run(0xc42009a000, 0xc420010240, 0x4, 0x4, 0x0, 0x0) /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/cli/app.go:236 +0x5d6 main.main() /data/mci/ab7e25a7975a6f98a3e0a2d103064034/gopath/src/github.com/evergreen-ci/evergreen/main/evergreen.go:28 +0x53 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2691","01/30/2018 18:46:35",1,"periodically check to activate tasks if batchtime elapses ""I think we need to: - refactor out the code that checks to see if tasks need to be activated and run it in its own loop, reasonably regularly, every minute or two.) - could do this with a very well formed amboy job. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2693","01/31/2018 14:58:45",2,"Finish Time is earlier than Start Time for a task ""For the given task, the finish time is before the start time. Additionally, the time taken field appears to have suffered from some rollover miscalculation and the UI does not display the time values. https://evergreen.mongodb.com/api/rest/v2/tasks/mms_int_INT_JAVA_ATM_patch_5ea54aa42725ca59ac8952f55d54a6e41edf7c69_5a70f937e3c3317d9b001fae_18_01_30_23_01_12""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2697","01/31/2018 15:09:32",1,"Allow tasks to log their post group ""I'm adding this as a placeholder for determining how/if we should log post group commands.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2698","01/31/2018 15:31:18",2,"Highlighted text in lobster moves when scrolling ""When you highlight text in lobster, then scroll, the highlighted selection changes.""","",0,0,1,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2699","01/31/2018 16:57:45",1,"Agent tests are panicking on Windows ""{{{""""message"""":""""hit panic; adding error"""",""""metadata"""":{""""level"""":90,""""hostname"""":""""WIN-LMHFULM2L27"""",""""time"""":""""2018-01-31T16:40:08.8624204Z"""",""""process"""":""""C:\\data\\mci\\95573c9ad530edf932b8b7f41c654bc2\\gopath\\src\\github.com\\evergreen-ci\\evergreen\\bin\\test.agent"""",""""pid"""":5740},""""operation"""":""""running task"""",""""panic"""":""""runtime error: invalid memory address or nil pointer dereference"""",""""stack"""":{""""context"""":{""""message"""":"""""""",""""metadata"""":{""""time"""":""""0001-01-01T00:00:00Z""""}},""""frames"""":[{""""function"""":""""github.com/evergreen-ci/evergreen/agent.(*Agent).runTask.func1"""",""""file"""":""""C:/data/mci/95573c9ad530edf932b8b7f41c654bc2/gopath/src/github.com/evergreen-ci/evergreen/agent/agent.go"""",""""line"""":170},{""""function"""":""""runtime.call32"""",""""file"""":""""c:/go1.8/go/src/runtime/asm_amd64.s"""",""""line"""":514},{""""function"""":""""runtime.gopanic"""",""""file"""":""""c:/go1.8/go/src/runtime/panic.go"""",""""line"""":489},{""""function"""":""""runtime.panicmem"""",""""file"""":""""c:/go1.8/go/src/runtime/panic.go"""",""""line"""":63},{""""function"""":""""runtime.sigpanic"""",""""file"""":""""c:/go1.8/go/src/runtime/signal_windows.go"""",""""line"""":161},{""""function"""":""""github.com/evergreen-ci/evergreen/agent.(*Agent).runPostTaskCommands"""",""""file"""":""""C:/data/mci/95573c9ad530edf932b8b7f41c654bc2/gopath/src/github.com/evergreen-ci/evergreen/agent/agent.go"""",""""line"""":319},{""""function"""":""""github.com/evergreen-ci/evergreen/agent.(*Agent).finishTask"""",""""file"""":""""C:/data/mci/95573c9ad530edf932b8b7f41c654bc2/gopath/src/github.com/evergreen-ci/evergreen/agent/agent.go"""",""""line"""":274},{""""function"""":""""github.com/evergreen-ci/evergreen/agent.(*Agent).runTask"""",""""file"""":""""C:/data/mci/95573c9ad530edf932b8b7f41c654bc2/gopath/src/github.com/evergreen-ci/evergreen/agent/agent.go"""",""""line"""":213},{""""function"""":""""github.com/evergreen-ci/evergreen/agent.(*Agent).loop"""",""""file"""":""""C:/data/mci/95573c9ad530edf932b8b7f41c654bc2/gopath/src/github.com/evergreen-ci/evergreen/agent/agent.go"""",""""line"""":118},{""""function"""":""""github.com/evergreen-ci/evergreen/agent.(*AgentSuite).TestAgentEndTaskShouldExit"""",""""file"""":""""C:/data/mci/95573c9ad530edf932b8b7f41c654bc2/gopath/src/github.com/evergreen-ci/evergreen/agent/agent_test.go"""",""""line"""":111},{""""function"""":""""runtime.call32"""",""""file"""":""""c:/go1.8/go/src/runtime/asm_amd64.s"""",""""line"""":514},{""""function"""":""""reflect.Value.call"""",""""file"""":""""c:/go1.8/go/src/reflect/value.go"""",""""line"""":434},{""""function"""":""""reflect.Value.Call"""",""""file"""":""""c:/go1.8/go/src/reflect/value.go"""",""""line"""":302},{""""function"""":""""github.com/evergreen-ci/evergreen/vendor/github.com/stretchr/testify/suite.Run.func2"""",""""file"""":""""C:/data/mci/95573c9ad530edf932b8b7f41c654bc2/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/stretchr/testify/suite/suite.go"""",""""line"""":102},{""""function"""":""""testing.tRunner"""",""""file"""":""""c:/go1.8/go/src/testing/testing.go"""",""""line"""":657},{""""function"""":""""runtime.goexit"""",""""file"""":""""c:/go1.8/go/src/runtime/asm_amd64.s"""",""""line"""":2197}]}}}}""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2703","01/31/2018 19:31:02",1,"smoke-test-task failure ""h2. [smoke-test-task failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_smoke_test_task_e3402f013c5d431442436be3fb303b6a497c98f2_18_01_31_16_44_37/0] Host: [ec2-54-91-92-164.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-1mar75nh] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2704","01/31/2018 20:59:28",1,"Ignore shouldExit if next task is in the same task group as previous ""This potentially should only apply to a task group with 1 host.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9593","02/01/2018 22:47:37",1,"lint failure ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/amboy_race_detector_lint_06ba2f6774cb462f34131a041e60dafcedfccff8_18_02_01_18_21_25/0] Host: [ec2-34-227-59-90.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-jkyg6qth] Project: [amboy|https://evergreen.mongodb.com/waterfall/amboy] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,0,0,0,1,0,0 +"EVG-2706","02/02/2018 15:08:33",1,"Attach.artifacts always logs that it attaches 1 file ""https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_jsCore_patch_06b9e9ebf9778293b8425093ada0aa1eb83b594e_5a623652e3c331768300087f_18_01_19_18_18_06""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2708","02/02/2018 17:18:47",1,"UnscheduleStaleUnderwaterTasks may blacklist old tasks recently scheduled by users ""Max scheduled https://evergreen.mongodb.com/task/mongodb_mongo_master_windows_64_2k8_ssl_noPassthrough_WT_77fbada9b93dfa474d41216baa19f556e75bc8ca_17_11_10_22_58_32, and it was blacklisted, potentially by UnscheduleStaleUnderwaterTasks, because this function only takes into account the task's create time. This means that users who wish to schedule tasks older than two weeks must also reset their priority. We could potentially fix this by filtering out tasks with a non-empty """"activated_by"""" field.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2710","02/03/2018 20:34:24",1,"Add link to host page in decommissioned host jira description ""For example in a ticket associated with host ubuntu1604-ppc-3.pic.build.10gen.cc, it would be useful to include a link to https://evergreen.mongodb.com/host/ubuntu1604-ppc-3.pic.build.10gen.cc for quickly seeing what the host has been doing and to adjust its status. Less obviously useful, and a separate request, but still perhaps worth doing, if it's easy, would be making the distro text in the description a link to the distro page (""""ubuntu1604-power8-test"""" could link to https://evergreen.mongodb.com/distros##ubuntu1604-power8-test)""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2711","02/03/2018 20:56:13",0,"Uptime in decommissioned host jira text shows strangely formatted incorrect time ""For example, one ticket shows """"2562047h47m16.854775807s"""" for ubuntu1604-ppc-3.pic.build.10gen.cc. It would be nice if it could 1) use correct uptime (the host has been up for """"1 day, 1 hour and 2 minutes"""" right now, 2) not show so much precision for the seconds, and 3) include days, not just hours, so something like """"1d1h2m30s"""" or something similar. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2714","02/05/2018 14:16:57",1,"lobster is no longer usable in Firefox ""It used to look just like Chrome's rendering, but now it looks all wrong; the buttons are spaced incorrectly, the font is the wrong size, and the """"details"""" are always missing -- the pane vanishes immediately after you click """"Show Details"""".""","",0,0,1,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2715","02/05/2018 14:50:43",1,"colapse ""task_scheduled"" events in event-log UI ""we run the scheduler often and it probably ends up obscuring lots of useful data. ""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2717","02/05/2018 15:54:43",1,"remove patch.Intent type from the amboy job for patch intent creation ""You can't (easily) roundtrip a struct that has an field with an interface type, so if (when?) we ever move patchIntentProcessors to using the remote queue, we end up with a sticky situation. It's not critical, but we should do this soon. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2718","02/05/2018 16:40:07",1,"Monitor attempted to terminate intent host ""Feb 05 16:31:34 evergreenapp-2.build.10gen.cc evergreen[23088]: [message='Error cleaning up hosts' runner='monitor']: error terminating host: error terminating host evg-rhel62-small-20180205161616-1618972814792567608: error terminating host evg-rhel62-small-20180205161616-1618972814792567608: after 10 retries, operation failed: InvalidInstanceID.Malformed: Invalid id: """"evg-rhel62-small-20180205161616-1618972814792567608"""" (expecting """"i-..."""")""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2719","02/05/2018 18:15:25",2,"Investigate whether we should apply patches with --whitespace=fix ""We found a case where the patch process fixing whitespace locally on the Evergreen host caused our linting task to miss whitespace errors that otherwise would have kept the code from being merged into master. What happens is that then the code can be merged, but the next person to open a PR off of that base will cause our linting task to fail because the whitespace issues won't have been fixed. It would be better for the patch process to not fix whitespace so that we can catch it on our own in our lint tasks. Re: https://mongodb.slack.com/archives/C0V896UV8/p1517849650000072 Example: https://evergreen.mongodb.com/task/mms_unit_js_UNIT_JS_LINT_patch_2d46f5d9caf3d38537766f163377eeb840dbcb82_5a720430e3c3317d9b004258_18_01_31_18_00_17""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2720","02/05/2018 18:48:16",1,"avoid static host decomissioning loops ""- don't decommission static hosts for consistent system failures - move from 6 consecutive failures back to 3 - continue to decomission for taskrunner errors ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2722","02/05/2018 21:52:25",1,"Display Task Behaviour around Execution tasks is wrong ""It's currently possible to 1. Create a patch with a single execution task of a display task 2. Create a tag which only contains part of an execution tag, that only activates the tagged tasks. If a tag includes 1 or more execution tasks from a display the task, every task from the display task should be included. In all other situations, execution tasks should be invisible to the user. (including aliases task regexes, and task requests from the command line.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9594","02/07/2018 17:02:43",2,"test-rest failure ""h2. [test-rest failed on ubuntu1604|https://evergreen.mongodb.com/task/amboy_ubuntu1604_test_rest_8f3592813cce537dd0fba0b61ecb3e85a3d0b38d_18_02_06_01_24_26/0] Host: [ec2-34-228-185-201.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-9j2843pg] Project: [amboy|https://evergreen.mongodb.com/waterfall/amboy] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,0,0,0,1,0,0 +"EVG-9345","02/07/2018 17:28:21",2,"store more concise errors in jobs, log more in pools ""- log errors in the pools so we can see when/where things go wrong. - avoid pushing stack traces in job documents""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2731","02/07/2018 19:48:16",1,"manifest override for ""always fetch latest"" ""be able to specify modules with """"always fetch latest"""" semantics to avoid the manifest pinning for things like the fuzzer/sysperf/etc.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2732","02/07/2018 19:48:18",2,"test_history REST endpoint does not return successful tasks info ""When retrieving task information from the {{/rest/v1/projects//test_history}} endpoint. The results do not contain successful tasks when {{taskStatuses}} includes """"success"""". Some additional tests showed a related issue: while timeout results are returned when {{taskStatuses='timeout'}} they are not returned when {{taskStatuses='timeout,failed'}}. Only the failed tasks results are returned.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2733","02/07/2018 20:43:23",2,"Improve logkeeper logging ""There were a few changes made to logkeeper logging so we could send logs to splunk that turned out to make it more difficult to troubleshoot load related issues. IIRC, we stopped logging good requests and only log errors. Right now, logs look like this: What would help us is: * Have access logs (http method, path, status) for all requests * Log client ip (I believe it's available as one of the header fields) * Log some details for 'Internal Server Error' Perhaps we can split access logs and logkeeper logs and don't send some of them to splunk?""","Feb 7 20:10:26 logkeeperapp-0 logkeeper[25019]: [logkeeper] 2018/02/07 20:10:26 [p=error]: [error='inserting test with id ObjectIdHex(""""5a7b5d3290413061bb015a89"""") took 1.387978ms' requestID='0'] Feb 7 20:10:26 logkeeperapp-0 logkeeper[25019]: [logkeeper] 2018/02/07 20:10:26 [p=error]: [error='inserting test with id ObjectIdHex(""""5a7b5d3290413061bb015a8a"""") took 1.554176ms' requestID='0'] Feb 7 20:10:26 logkeeperapp-0 logkeeper[25019]: [logkeeper] 2018/02/07 20:10:26 [p=error]: [error='finding build with id df420f183a2766fccd7a8f5f5c04621a took 1.172723ms' requestID='0'] Feb 7 20:10:26 logkeeperapp-0 logkeeper[25019]: [logkeeper] 2018/02/07 20:10:26 [p=error]: [error='inserting test with id ObjectIdHex(""""5a7b5d3290413061bb015a8b"""") took 2.16831ms' requestID='0'] Feb 7 20:10:26 logkeeperapp-0 logkeeper[25019]: [logkeeper] 2018/02/07 20:10:26 [p=error]: [error='finding build with id 9ec113d71c4efb9f8c96a1a004e2f7ba took 1.215577ms' requestID='0'] Feb 7 20:10:26 logkeeperapp-0 logkeeper[25019]: [logkeeper] 2018/02/07 20:10:26 [p=error]: [error='inserting test with id ObjectIdHex(""""5a7b5d3290413061bb015a8c"""") took 1.290326ms' requestID='0'] Feb 7 20:10:26 logkeeperapp-0 logkeeper[25019]: [logkeeper] 2018/02/07 20:10:26 [p=error]: [error='finding build with id 0b06d371fe4ba134e28e2984658c2fa5 took 1.263711ms' requestID='0']",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-2734","02/07/2018 21:01:06",1,"Evergreen cannot apply mailbox-style patches which create new files, and moves them in a later commit ""Maybe a bug maybe user error, although I don't think I did anything interesting with git here. https://evergreen.mongodb.com/build/dsi_linux_runner_patch_c48251e93c6b82523444f689e276a1c1e9252487_5a7b67c7c9ec4420de328f67_18_02_07_20_55_35 From this PR: https://github.com/10gen/dsi/pull/20 Filing in case it's interesting - I'm gonna try working around it in the mean-time.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2737","02/07/2018 23:15:02",2,"ensure isolation during task creation ""- derive date for version create time from github rather than system time - sort tasks and builds before insertion so that we're always inserting in the same order ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2738","02/08/2018 14:44:14",1,"smoke-test-task failure ""h2. [smoke-test-task failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_smoke_test_task_66dd4be6aba9503f99316e5045378019eca86543_18_02_07_19_54_28/0] Host: [ec2-34-226-193-185.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-xghg6pxj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2739","02/08/2018 15:40:30",1,"Create Report for Expected Duration versus Actual Duration ""auto log to splunk/etc. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2742","02/08/2018 19:41:41",1,"avoid creating tickets for successive build failures ""we're not decoing these hosts, but we are creating tickets, we shouldn't. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2743","02/08/2018 19:56:00",1,"remove cost reporting go routine in task end ""make it an amboy job!""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2745","02/09/2018 14:56:35",2,"Command attach.artifacts should not error if the file is missing ""The behavior of {{attach.artifacts}} should either have an option to ignore missing files or not error if a file is missing from the {{files}} param.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9574","02/09/2018 18:32:36",1,"Add flag to only print failed tests on greenbay run ""Currently the output is a bit too noisy for large projects. I really only care about failed tests.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2753","02/10/2018 17:52:20",2,"Combine Host Reachability and LastCommunication Time Values into ""LastContactTime"" ""or similar, there's no meaningful difference between these values at the moment, but the monitor/hostinit/taskrunner handle them differently. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2755","02/12/2018 01:41:46",1,"remove ""generic-linux-distors"" from self-tests.yml ""differences in configuration between machines lead to build failures that are not needed. pool sizes should be large enough on 16.04""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2756","02/12/2018 02:26:30",1,"deprecate and warn support for tasks that run on more than one distro ""In the medium term we would like to remove the ability to specify more than one distro. Historically it was useful in using static hosts and dynamic hosts in related pools, but that's not been a reality of our deployment recently. At the same time the logic to support allowing tasks to appear in more than one task queue makes task dispatching and scheduling much more complicated than it might be. In the future we can add a layer inbetween distros, which describe host configurations, and the distros which represent queues, using some sort of pooling or grouping system, which will provide more flexibility as it will be an application wide configuration, and not specific to task definitions. This deprecation and warning is the first step in this process.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2764","02/12/2018 16:14:11",1,"Move all documentation from repo into wiki ""./plugin/builtin/buildbaron/README.md ./plugin/builtin/perfdash/README.md ./service/REST_README.md ./docs/using-degraded-mode.rst ./rest/how_to.rst ./rest/usage.rst""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2767","02/12/2018 19:07:56",2,"Restart Task in UI doesn't close restart window/can spawn duplicate tasks ""1. clicking yes doesn't close the window. 2. The user can click Yes multiple times and have it create multiple tasks.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-9590","02/12/2018 19:15:31",1,"lint failure ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/amboy_race_detector_lint_d2da6d14e40c46ce82dc497c01301d6da8302010_18_02_12_16_06_14/0] Host: [ec2-34-229-19-196.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-jc986kpj] Project: [amboy|https://evergreen.mongodb.com/waterfall/amboy] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,0,0,0,1,0,0 +"EVG-2772","02/12/2018 23:37:47",2,"set content-length header in agent post requests ""so we can log better in the API server ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2773","02/13/2018 02:02:20",1,"make sure repotracker catchup jobs respect the github api limit ""in the case that the queue gets backed up, we don't want to blow through limit when we start working the queue. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2774","02/13/2018 14:02:09",1,"log local queue stats on web servers ""also drop local job listing in queue report""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2775","02/13/2018 14:46:11",2,"Lobster given undefined url for all logs view ""From the """"job logs"""": https://logkeeper.mongodb.org/build/63b3fc51e56a2e15bc96d26685c0e020 If you click """"Complete logs for all"""" you get: https://logkeeper.mongodb.org/lobster/build/63b3fc51e56a2e15bc96d26685c0e020/test/undefined?bookmarks=0%2C11018 Which has """"undefined"""" as the test id. It should say """"all"""" instead of """"test/undefined"""": https://logkeeper.mongodb.org/lobster/build/63b3fc51e56a2e15bc96d26685c0e020/all?bookmarks=0%2C11018""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2779","02/13/2018 16:45:49",1,"tune runner parallelism ""in the post reachability-check world, we should tune things up a bit: - reexamine threads running taskrunner (as more of the retry waiting for a host to get ready is happening here) - more threads running host provisioning in hostinit (because this ends up retrying) - terminate hosts loop in the monitor. - timeout for host termination operation - timing of the interval for hostinit/taskrunner/monitor""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2782","02/13/2018 19:39:38",1,"Passing --large to the patch command doesn't enable large patches ""because NewRequestReader has a 16MB limit. We should remove --large, or make a bigger reader.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2783","02/13/2018 20:19:34",1,"Panic in GetDNSName """""," { [{github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/recovery.LogStackTraceAndContinue /data/mci/f04cd0c71429b9ef0145c7465a42925a/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/recovery/recovery.go 70} {runtime.call32 /opt/go1.8/go/src/runtime/asm_amd64.s 514} {runtime.gopanic /opt/go1.8/go/src/runtime/panic.go 489} {runtime.panicmem /opt/go1.8/go/src/runtime/panic.go 63} {runtime.sigpanic /opt/go1.8/go/src/runtime/signal_unix.go 290} {github.com/evergreen-ci/evergreen/cloud.(*ec2Manager).GetDNSName /data/mci/f04cd0c71429b9ef0145c7465a42925a/gopath/src/github.com/evergreen-ci/evergreen/cloud/ec2.go 660} {github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /data/mci/f04cd0c71429b9ef0145c7465a42925a/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go 346} {github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /data/mci/f04cd0c71429b9ef0145c7465a42925a/gopath/src/github.com/evergreen-ci/evergreen/hostinit/setup.go 218} {runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s 2197}]} ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2786","02/13/2018 22:31:28",1,"Fix Lint Errors in rest/model "" The BuildFromService /ToService functions are copying the send.SlackOptions object from evergreen/SlackConfig. This means it's copying a mutex, and generating a mutex error. I can't reproduce this in evergreen, but both Brian and I can repro locally."""," rest/model/admin.go:1047::error: function call copies lock value: github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.SlackOptions contains sync.RWMutex (vet) rest/model/admin.go:1061::error: assignment copies lock value to options: github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/grip/send.SlackOptions contains sync.RWMutex (vet) ",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-9526","02/14/2018 11:35:36",2,"improve string format of stack traces ""particularly for panics that we log to splunk""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2789","02/14/2018 14:05:14",1,"Panic in agent when enforcing callback timeouts ""{{https://evergreen.mongodb.com/host/sir-5v887hak}}""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2794","02/14/2018 21:19:20",1,"Panic when running CLI commands that communicate with API with invalid key ""Johns-MacBook-Pro-2:evergreen johnliu$ ./evergreen host list --all runtime error: invalid memory address or nil pointer dereference""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2796","02/15/2018 15:03:36",2,"git checkout fails if the mongo diff is empty ""https://evergreen.mongodb.com/task/sys_perf_3.2_linux_standalone_compile_patch_ba20ef3dc5e82459f9c7ddbce4a055b3d32aab74_5a856c25e3c331600b270c14_18_02_15_11_21_56 * This is a common use case in performance, most of our diffs are against the modules * This has happens from time to time, please consider adding a unit test for protecting this use case""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2797","02/15/2018 16:54:53",2,"Fix zero dates in versions ""Perf depends on valid create_time in versions, so we should go back and correct these.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2798","02/15/2018 18:41:35",0,"add TTL index on task event log ""this log only has data for tasks, including system metrics data. ttl to six months ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2799","02/16/2018 01:12:08",2,"report on host idle time upon termination. ""just as we do for task-end-stats, we can and should collect host-termination-stats when we terminate a host. long term, stats may include: - total up time, - total idle time. - time for tasks, - cost of host, - number of tasks run - ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2800","02/16/2018 03:31:30",1,"remove excess monitor logging ""it logs a lot, and very little of it is useful. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2801","02/16/2018 14:24:38",2,"time out tasks when heartbeats expire in amboy job ""there is only one task flagging function in the monitor which times out/ends tasks when the heartbeats expire. We should move this functionality into an amboy job, and remove it and it's complicated machinery from the monitor""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2802","02/16/2018 14:26:17",2,"move cloud status change detection ""there is one """"hostMonitoringFunction"""" with the sole function of detecting when hosts are terminated externally (e.g. spot-host-termination) we should move this functionality out of the monitor and into an independent amboy job. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2815","02/20/2018 20:09:44",2,"`go test` failure shown when negative time printed ""`go test` sometimes mistakenly prints out a negative time. We recently got this output in our output: We use the command `gotest.parse_files` to display which test cases succeed or fail for a given task. For the above test case, it showed this as a failure and therefore reported the task as a failure even though `go test` exited successfully. I assume this is due to the parsing logic doesn't expect a negative run time for a test. Evergreen task: https://evergreen.mongodb.com/task/mongo_go_driver_tests__version~3.4_os~osx_test_standalone_noauth_nossl_patch_c0d49e37272a4a5a31ac5ce84e453d5c9a31415e_5a8c71e3e3c331479c35c023_18_02_20_19_07_34 Log file: https://evergreen.mongodb.com/test_log/5a8c79022fbabe102183dd6a?raw=1"""," --- PASS: TestHeartbeatInterval/mongodb://localhost/?heartbeatIntervalMS=10 (-0.00s) ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2816","02/20/2018 20:45:35",2,"Don't Make Patches with no Build Variants or Tasks ""Like this one: https://evergreen-staging.corp.mongodb.com/version/5a8522cb9dbe327d22aec3c5""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2823","02/21/2018 19:30:42",1,"avoid negative values for cost ""validate time range to make sure its positive. wrap the logic of CostForDuration""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2826","02/21/2018 21:42:36",1,"The `get-update` command fails due to version mismatch ""When running the {{evergreen.exe get-update}} command on Windows I am getting the following error: My current version is: If I run the file, which {{evergreen get-update}} downloaded I get this version: """," E:\workspace\mongo>evergreen get-update A new version is available. Run 'evergreen get-update' to fetch it. Update to version 2018-02-09 found at https://evergreen.mongodb.com/clients/windows_amd64/evergreen Fetching update from https://evergreen.mongodb.com/clients/windows_amd64/evergreen Upgraded binary downloaded to C:\Users\kaloi\AppData\Local\Temp\257184635 - verifying [evergreen] 2018/02/21 16:35:51 [p=emergency]: Update failed - expected new binary to have version 2018-02-09, but got 2017-06-29 instead E:\workspace\mongo>evergreen --version evergreen version 2018-01-31 E:\workspace\mongo>C:\Users\kaloi\AppData\Local\Temp\257184635 version 2017-06-29 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9661","02/22/2018 16:12:27",2,"driver should have an ID() and this should be propogated to the locker ""so that the """"owner"""" in a job reflects (somehow) the id of the machine/instance that is running it""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2828","02/22/2018 16:31:18",1,"use continue on error semantics when canceling stale patches from PRs ""e.g. when you close requests or push new builds just so things don't straggle. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2829","02/22/2018 16:55:31",1,"race-rest-client failure ""h2. [race-rest-client failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_rest_client_272f89c1db8467057a17bdb13eca2099dd6b0a7a_18_02_22_14_57_58/1] Host: [ec2-54-87-242-248.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-76v87v8j] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-9684","02/23/2018 14:26:34",1,"add annotate method for message composer. ""have method that we can use to add arbitrary (quasi structured data) to any message composer. We'll mostly add it to the base type, but may override (particularly for fieldsMessage) in some implementations. The main use case, initially would be to be able to use existing messages but also write logging helpers that add request ids for better traceability in request logging. ""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2836","02/23/2018 15:24:29",1,"Inactive display task has odd UI color ""CC [~john.liu]""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2837","02/23/2018 16:02:56",2,"Timeout / error when getting history of the failures ""```https://evergreen.mongodb.com/rest/v1/projects/mongodb-mongo-master/test_history?sort=latest&tasks=sharding_auth&tests=jstests%2Fsharding%2Fconvert_to_and_from_sharded.js&taskStatuses=failed&limit=1``` returns """"The service is temporarily unavailable. Please try again later."""" error ""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-2841","02/23/2018 18:34:34",1,"Agents that get 409s for task secrets should get another task, not exit ""Two hosts https://evergreen.mongodb.com/host/sir-xbpr7eek and https://evergreen.mongodb.com/host/sir-sfqr542j, got the same task from the next task endpoint. The latter got 409s, the agent exited, and then the host was reaped. Instead the latter should instead stop task execution and get another task. However, we may need to make a distinction between a 409 because the host secret is wrong (in which case getting a new agent is the right thing to do) versus if the task secret is wrong (in which case the agent should ask for another task).""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2850","02/26/2018 18:44:07",2,"enterprise module patch not always being applied. ""I have some work that has changes in both the community and enterprise repos. I noticed that I was getting inconsistent results patch-building the them. Sometimes it appeared that while the enterprise module was added, the patch on it was not applied. https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_compile_patch_9c65faa1ea24b92d86f846abd38909b4ef2fe5bc_5a90936be3c33134821ce592_18_02_23_22_19_55##%257B%2522compare%2522%253A%255B%257B%2522hash%2522%253A%25229c65faa1ea24b92d86f846abd38909b4ef2fe5bc%2522%257D%252C%257B%2522hash%2522%253A%25229c65faa1ea24b92d86f846abd38909b4ef2fe5bc%2522%257D%255D%257D In this patch-build, on the first execution the enterprise patch was not applied and the compile failed, then later when I rescheduled it, the enterprise patch was applied and the compile succeeded.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2853","02/26/2018 22:22:47",1,"API V1 Task History fails to return correct results for various inputs ""Example: https://evergreen.mongodb.com/rest/v1/tasks/compile/history?project=mongodb-mongo-master What am I doing wrong?""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2854","02/26/2018 22:35:37",2,"Support aliases for groups of distros ""Users might have a task that can run on any Linux, for example. We should provide a way of specifying groups of distros which allows tasks to run on whichever queue they are at the head of first.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2856","02/27/2018 16:47:04",1,"Show more task/version history drawer commit text ""Problem: Often I want to see the commit summaries to figure out which commits between a test passes and failing might be related to the issue I'm seeing. Currently, I hover over each commit to see the full text, which is slow and cumbersome. Proposed Solution: Could we add allow allow the commit side bar to take up more side space to it can display the complete commit summaries and then users could or change the size as they need? ""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2858","02/27/2018 18:02:20",1,"When creating a new distro certain validators never return true ""https://github.com/evergreen-ci/evergreen/blob/master/public/static/js/distros.js#L374 When creating a new distro the settings key is not defined so the validators linked above throw 'is_vpc' is not defined essentially crashing the validation of the form. When this happens you are unable to click Save Configuration and thus cannot make a new distro. Note that copying an existing distro works as expected.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2875","02/27/2018 18:47:07",2,"Add flag to patch/patch-file CLI commands to apply default subscriptions to patch ""Patch creation route should be modified to creation subscriptions at this time""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2879","02/27/2018 18:50:19",2,"Use github <-> crowd mapping to associate Github PR patches with the actual user that created it ""Refactor patch intents to use Github UID number""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2897","02/27/2018 19:06:40",2,"Document commands missing in wiki ""https://github.com/evergreen-ci/evergreen/wiki/Project-Commands""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2898","02/27/2018 19:50:14",1,"Fetching Patched Project Configurations can Fail for Github PR Requests ""Fetching patch projects uses the Github diffs, instead reaching out the pulls ref.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2899","02/27/2018 22:17:55",1,"Error when using ""Decommission hosts of this distro for this update"" checkbox in Distros UI ""error unmarshaling request: json: cannot unmarshal object into Go struct field Distro.user_data of type string""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2902","02/28/2018 18:32:58",1,"test-rest-client failure ""h2. [test-rest-client failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_rest_client_b0b8a79ff37ba3d0e654ba4726b05b7dcd3aed52_18_02_28_18_26_31/0] Host: [ec2-34-228-145-51.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-xsi84qrk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2903","02/28/2018 19:55:02",1,"Copying project copies git history ""This is a hard one to describe - I copied one project to another, carefully not hitting the save button until the fields were all updated. The new project and old project have nothing to do with each other (they don't share repos). They do share admins. As soon as I hit save, it popped up an error message saying it couldn't find the base commit, so I entered the latest one from the new project repo branch. The waterfall page shows all the history from the old project with weird 404 errors when I click on the github links pointing to commit hashes from the old project but under the new project's repo. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2907","02/28/2018 22:06:38",1,"Panic when retrieving config "" error: error retrieving admin settings: error populating section alerts: error retrieving section alerts: reflect: call of reflect.Value.Type on zero Value extended: error populating section alerts: error retrieving section alerts: reflect: call of reflect.Value.Type on zero Value github.com/evergreen-ci/evergreen.GetConfig /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/config.go:935 github.com/evergreen-ci/evergreen/service.(*APIServer).NextTask /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/service/api_task.go:438 github.com/evergreen-ci/evergreen/service.(*APIServer).NextTask-fm /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/service/api.go:771 github.com/evergreen-ci/evergreen/service.(*APIServer).checkHost.func1 /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/service/api.go:256 net/http.HandlerFunc.ServeHTTP /opt/go1.8/go/src/net/http/server.go:1942 github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux.(*Router).ServeHTTP /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux/mux.go:114 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.Wrap.func1 /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:46 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:29 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/service.UserMiddleware.func1 /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/service/middleware.go:401 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:29 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/service.(*RecoveryLogger).ServeHTTP /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/service/middleware.go:478 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(*Negroni).ServeHTTP /data/mci/60739af262bc9d09b433b1c3b884b7cb/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:86""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2909","03/01/2018 12:16:18",1,"json/tag and json/commit apis return different data for the same params ""For some reason, json/commit api does not return data for some versions. These two calls should be equivalent, however they doesn't: This works: https://evergreen.mongodb.com/plugin/json/tag/performance-3.6/3.6.1-Baseline/linux-mmap-repl/misc/perf This doesn't: https://evergreen.mongodb.com/plugin/json/commit/performance-3.6/025d4f4fe61efd1fb6f0005be20cb45a004093d1/linux-mmap-repl/misc/perf The bug affects several pages of evergreen. At least performance discovery and task page (the page with trend charts). Going to use json/tag api for perf discovery right now, because it's critical. CC: [~john.liu], [~sam.kleinman], [~jim.oleary]""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2910","03/01/2018 15:01:37",1,"Private project variables are deleted on page save ""Repro steps: 1. Make a private project variable. Save the page. 2. Make another project variable, either private or not. Save the page. What happens: The private variable from the first step will be set to the empty string in the database.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2911","03/01/2018 21:18:25",2,"smoke test fails if a commit is pushed to github during the test ""h2. [smoke-test-task failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_smoke_test_task_8906dca1975e308582f4604169998a715767f314_18_03_01_21_05_07/1] Host: [ec2-54-221-34-35.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-4axr4ezk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~richard.samuels]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2913","03/02/2018 15:13:11",2,"Code refactoring for REST V1 API: waterfall versions ""The waterfall versions API, which was written for perf. discovery, should be moved to rest api v2, which requires code refactoring and unit test writing.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2919","03/05/2018 15:55:19",2,"Test results exceeds maximum document size on grid page ""https://evergreen.mongodb.com/grid/mongodb-mongo-master: """," Error fetching builds: Total size of documents in testresults matching { $match: { $and: [ { task_id: { $eq: """"mongodb_mongo_master_linux_64_repeated_execution_jsCore_1cf874bd73ebb13f753840bb6eea63207076c438_18_03_04_23_25_57"""" } }, {} ] } } exceeds maximum document size ",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2984","03/05/2018 18:07:51",2,"Runner hangs indefinitely during deploys ""The runner has hung during several recent deploys, and we had to kill -9 it to continue the deploy. We should figure out why it is hanging.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2921","03/05/2018 21:15:19",2,"s3.put with local_files_include_filter to non-existent bucket does not fail task ""in the following task: https://evergreen.mongodb.com/task/cloud_automation_master_builddebian12deb_Automation_Agent_Generic_25348cb36b8d3bd3a0938fe6d1a73b0adeedddec_18_03_05_17_22_04 We are trying to upload files (with a filter, so that we can't use the optional as described in the docs - https://github.com/evergreen-ci/evergreen/wiki/Project-Commands#s3put) to a non existent s3 bucket. Since we know the bucket doesn't exist, we expected the task to fail. Files failed to upload (as expected) but the task was not marked as failed.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2922","03/05/2018 21:37:47",2,"Cleanup UpdateBuildAndVersionStatusForTask Database interactions ""The bit of code makes a large number of unnecessary db fetches ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2924","03/06/2018 15:07:10",2,"Display tasks square is grey after completion ""https://evergreen.mongodb.com/build/mci_race_detector_patch_3214a9f6e5553b626192ce15de72fd486398fbdb_5a99959f2a60ed0765bd4d58_18_03_02_18_19_17""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2925","03/06/2018 15:15:50",1,"Small number of EC2 errors logged ""At around 10 am today error: error checking DNS name for host sir-r64847zh: spot instance does not yet have an instanceId extended: spot instance does not yet have an instanceId github.com/evergreen-ci/evergreen/cloud.(*ec2Manager).GetDNSName /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/cloud/ec2.go:667 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:358 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:220 runtime.goexit /usr/local/Cellar/go/1.9.2/libexec/src/runtime/asm_amd64.s:2337 github.com/evergreen-ci/evergreen/cloud.(*ec2Manager).GetDNSName /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/cloud/ec2.go:667 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:358 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:220 runtime.goexit /usr/local/Cellar/go/1.9.2/libexec/src/runtime/asm_amd64.s:2337 error checking DNS name for host sir-r64847zh github.com/evergreen-ci/evergreen/hostinit.(*HostInit).IsHostReady /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:360 github.com/evergreen-ci/evergreen/hostinit.(*HostInit).setupReadyHosts.func1 /Users/johnliu/go/src/github.com/evergreen-ci/evergreen/hostinit/setup.go:220 runtime.goexit /usr/local/Cellar/go/1.9.2/libexec/src/runtime/asm_amd64.s:2337 ""","",0,0,0,0,0,0,0,1,0,1,0,0,0,0,0 +"EVG-2926","03/06/2018 15:53:20",2,"Enforce requirement for all projects to specify a branch ""Projects can omit branch, and parts of evergreen assume master. This breaks PR testing.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9364","03/06/2018 20:40:58",2,"Investigate Blockages with Amboy Remote Queues ""Amboy queues are occasionally getting blocked as in MCI-2772. This is especially true on hard restarts of Evergreen.""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2929","03/06/2018 21:13:52",1,"Attach generate.tasks json files as artifacts ""This will help a user debug their generated tasks and provide more visibility.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2934","03/07/2018 13:58:14",1,"Cannot use a macro expansion in s3.put optional parameter ""The following is not valid: The {{optional}} parameter cannot use a macro expansion."""," - command: s3.put params: optional: ${is_patch|false} aws_key: ${aws_key} aws_secret: ${aws_secret} local_file: src/distsrc.${ext|tgz} remote_file: ${project}/${build_variant}/${revision}/sources/mongo-src-${build_id}.${ext|tgz} bucket: mciuploads permissions: public-read content_type: ${content_type|application/x-gzip} display_name: Source tarball # We only need to upload the source tarball from one of the build variants # because it should be the same everywhere, so just use linux-64/windows-64-2k8. build_variants: [ linux-64, windows-64-2k8-ssl ] ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2936","03/07/2018 15:43:42",1,"Remove dead code for form data in submitPatch in api_patch.go ""I added a logging statement so we can verify in Splunk that the code is never hit.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9555","03/08/2018 14:23:30",2,"support autodetection of distribution ""the {{artifacts}} subcommand currently detects what architecture we are on, but not the distribution (when run on linux). There are presently a number of varied approaches to doing this in drivers-specific code paths, most notably in the [download-mongodb.sh|https://github.com/mongodb-labs/drivers-evergreen-tools/blob/master/.evergreen/download-mongodb.sh#L8-L42] script used by most drivers running on evergreen. If this were handled by curator, we could _completely_ drop the {{download-mongodb.sh}} script. ""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-2939","03/08/2018 14:46:53",1,"reduce frequency of process tree collection ""we currently collect proc tree info in the agent every 5 seconds for the first minute before dropping to once every 10 seconds. We should remove the special casing of the first period. We might also consider dropping this to once every 15 seconds to reduce the data volume. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2940","03/08/2018 15:20:28",1,"pass -i to go build to cache dependencies ""also improve the clean target to clean GOPATH/pkg/""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2945","03/08/2018 20:21:50",1,"numnewreporevisionstofetch not respected for new projects ""Instead of downloading 10 revisions for new projects (""""numnewreporevisionstofetch"""") Evergreen downloads 500 (""""maxreporevisionstosearch"""").""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2947","03/08/2018 22:54:00",2,"Task failed but failure output was not logged ""https://evergreen.mongodb.com/task/mci_ubuntu1604_js_test_ff04b3c3a109e85b980a6430d64258345aaaebbd_18_03_08_21_59_10/0 should have 08 03 2018 17:41:28.366:INFO [karma]: Karma v2.0.0 server started at http://0.0.0.0:9876/ 08 03 2018 17:41:28.370:INFO [launcher]: Launching browser PhantomJS with unlimited concurrency 08 03 2018 17:41:28.375:INFO [launcher]: Starting browser PhantomJS 08 03 2018 17:41:29.240:INFO [PhantomJS 2.1.1 (Mac OS X 0.0.0)]: Connected on socket DcdSb01aM2ON7l7aAAAA with id 21142958 PhantomJS 2.1.1 (Mac OS X 0.0.0) ERROR { """"message"""": """"SyntaxError: Expected an identifier but found 'url' instead\nat js/services/rest.js:358:0"""", """"str"""": """"SyntaxError: Expected an identifier but found 'url' instead\nat js/services/rest.js:358:0"""" } make: *** [js-test] Error 1""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2949","03/09/2018 14:42:19",2,"When many commits are pushed at once, run the latest one ""I pushed a batch of commits, but it chose to run one of the earlier ones, rather than the top of the stack.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2966","03/12/2018 17:34:46",2,"Cache versions in task groups in scheduler ""Large numbers of task groups in the queue can potentially slow the scheduler, since there will be n*log n calls to EarlierInTaskGroup per task group, where n is the number of tasks in the task group in the queue. EarlierInTaskGroup queries for a version and unmarshalls its yaml.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2978","03/14/2018 19:27:13",1,"Using aliases is overly verbose ""When I upload a patch using an alias, it logs every task it's going to run. This doesn't happen when not using an alias, and floods my terminal with unuseful noise. vs """," > evergreen patch -p mongodb-mongo-master -f -d """"without alias"""" jstests/noPassthrough/readConcern_atClusterTime.js | 10 ++++++++++ src/mongo/db/read_concern.cpp | 16 ++++++++++------ 2 files changed, 20 insertions(+), 6 deletions(-) d8cf907cef SERVER-33798 Fail atClusterTime reads at times newer than the current cluster time This is a summary of the patch to be submitted. Continue? (y/n): y Patch successfully created. ID : 5aa976c62fbabe4336f81f3f Created : 2018-03-14 19:23:50.671 +0000 UTC Description : without alias Build : https://evergreen.mongodb.com/version/5aa976c62fbabe4336f81f3f Finalized : Yes > evergreen patch -p mongodb-mongo-master -f -a required -d """"with alias"""" jstests/noPassthrough/readConcern_atClusterTime.js | 10 ++++++++++ src/mongo/db/read_concern.cpp | 16 ++++++++++------ 2 files changed, 20 insertions(+), 6 deletions(-) d8cf907cef SERVER-33798 Fail atClusterTime reads at times newer than the current cluster time This is a summary of the patch to be submitted. Continue? (y/n): y activated tasks on 5 variants... tasks for variant enterprise-windows-64-2k8: audit jsCore dbtest jstestfuzz_replication sharding_auth_audit jsCore_decimal external_auth compile_benchmarks ese jstestfuzz_sharded ssl sslSpecial jsCore_ese jstestfuzz_concurrent_replication compile compile_all jsCore_auth burn_in_tests benchmarks_orphaned aggregation_fuzzer jstestfuzz auth_audit snmp replica_sets_auth sasl sharding_ese jstestfuzz_concurrent replica_sets_ese sharding_auth jstestfuzz_concurrent_sharded tasks for variant linux-64-debug: sharding_jscore_op_query_passthrough bulk_gle_passthrough dbtest concurrency_simultaneous change_streams aggregation_sharded_collections_passthrough read_only write_concern_majority_passthrough replica_sets_auth sharding_jscore_passthrough slow1 parallel_compatibility concurrency_sharded_with_stepdowns integration_tests_standalone aggregation jsCore_compatibility concurrency_sharded_with_stepdowns_and_balancer jsonSchema aggregation_read_concern_majority_passthrough integration_tests_sharded causally_consistent_jscore_passthrough compile_all mongosTest replica_sets_initsync_static_jscore_passthrough concurrency change_streams_mongos_passthrough causally_consistent_jscore_passthrough_auth replica_sets_jscore_passthrough replica_sets_initsync_jscore_passthrough concurrency_replication noPassthrough change_streams_sharded_collections_passthrough sharding integration_tests_replset failpoints_auth retryable_writes_jscore_passthrough aggregation_facet_unwind_passthrough disk_wiredtiger read_only_sharded compile jsCore_auth concurrency_sharded retryable_writes_jscore_stepdown_passthrough sharding_auth replica_sets_kill_secondaries_jscore_passthrough concurrency_sharded_causal_consistency noPassthroughWithMongod tool read_concern_linearizable_passthrough read_concern_majority_passthrough replica_sets session_jscore_passthrough sharded_causally_consistent_jscore_passthrough sharding_jscore_passthrough_wire_ops jsCore_decimal auth sharded_collections_jscore_passthrough aggregation_mongos_passthrough failpoints aggregation_one_shard_sharded_collections concurrency_sharded_causal_consistency_and_balancer jsCore parallel aggregation_auth serial_run tasks for variant enterprise-ubuntu1604-clang-3.8-libcxx: compile compile_all tasks for variant ubuntu1604-debug-aubsan-lite: jsCore compile_all compile watchdog_wiredtiger dbtest tasks for variant enterprise-rhel-62-64-bit: noPassthroughWithMongod concurrency_sharded_with_stepdowns aggregation aggregation_auth mongosTest package gle_auth_basics_passthrough_write_cmd sharded_collections_jscore_passthrough jstestfuzz_concurrent_replication sharding_gle_auth_basics_passthrough slow1 sharding_jscore_passthrough_wire_ops jstestfuzz bulk_gle_passthrough concurrency_sharded_with_stepdowns_and_balancer sharding_op_query sharding_ese read_only_sharded sharding_csrs_continuous_config_stepdown aggregation_fuzzer aggregation_one_shard_sharded_collections concurrency_sharded_causal_consistency_and_balancer rollback_fuzzer jstestfuzz_concurrent_sharded multiversion sharded_causally_consistent_jscore_passthrough change_streams_secondary_reads concurrency write_concern_majority_passthrough retryable_writes_jscore_passthrough gle_auth_basics_passthrough jstestfuzz_sharded multiversion_auth sharding_last_stable_mongos_and_mixed_shards read_concern_linearizable_passthrough concurrency_replication auth compile jstestfuzz_sharded_continuous_stepdown read_only aggregation_ese replica_sets_initsync_static_jscore_passthrough jsCore_decimal concurrency_sharded jstestfuzz_concurrent_sharded_continuous_stepdown dbtest jstestfuzz_concurrent_sharded_causal_consistency aggregation_mongos_passthrough gle_auth_write_cmd replica_sets_jscore_passthrough sharding tool aggregation_sharded_collections_passthrough ese rlp compile_all update_fuzzer jstestfuzz_replication jsCore_ese aggregation_facet_unwind_passthrough change_streams_mongos_passthrough sharding_jscore_op_query_passthrough jsCore integration_tests_standalone ssl jstestfuzz_sharded_causal_consistency audit change_streams concurrency_sharded_causal_consistency integration_tests_replset jsCore_op_query serial_run multiversion_multistorage_engine parallel sslSpecial jstestfuzz_sharded_session read_concern_majority_passthrough sharding_jscore_passthrough jstestfuzz_concurrent burn_in_tests lint compile_benchmarks benchmarks_orphaned retryable_writes_jscore_stepdown_passthrough aggregation_read_concern_majority_passthrough failpoints_auth replica_sets_auth sharding_auth_audit replica_sets_initsync_jscore_passthrough noPassthrough parallel_compatibility replica_sets_ese causally_consistent_jscore_passthrough jstestfuzz_replication_initsync jsonSchema session_jscore_passthrough change_streams_sharded_collections_passthrough concurrency_simultaneous failpoints gle_auth replica_sets snmp disk_wiredtiger jsCore_minimum_batch_size idl_tests jstestfuzz_concurrent_replication_session integration_tests_sharded sasl sharding_gle_auth_basics_passthrough_write_cmd replica_sets_kill_secondaries_jscore_passthrough jstestfuzz_replication_session jstestfuzz_concurrent_sharded_session auth_audit causally_consistent_jscore_passthrough_auth jsCore_auth sharding_auth update_fuzzer_replication jsCore_compatibility Patch successfully created. ID : 5aa976db2fbabe4336f81f44 Created : 2018-03-14 19:24:11.539 +0000 UTC Description : with alias Build : https://evergreen.mongodb.com/version/5aa976db2fbabe4336f81f44 Finalized : Yes ",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-2979","03/14/2018 22:01:20",1,"race-service failure ""h2. [race-service failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_service_3083938e219bb79558affa23445b04be49554e85_18_03_14_20_00_18/0] Host: [ec2-52-201-88-193.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-85kr56vg] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2980","03/14/2018 23:43:49",1,"Waterfall needs a color for system-* statuses ""https://evergreen.mongodb.com/task/mci_race_detector_display_lint_3083938e219bb79558affa23445b04be49554e85_18_03_14_20_00_18""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2981","03/15/2018 10:31:38",1,"Perf. discovery - ratio value representation and normalization ""Currently, ratio vaulue is calculated as Sa / Sb, where Sa and Sb are speeds of 'compare from/to' revisions. This approach produces abnormal values distribution. For example, ratio 1/3 is closer to 1 than ratio 3/1. To fix this issue we could use different approaches: * apply log function: log(Sa / Sb). In this case log(1/3) = -log(3/1) and also log(1/1) = 0 (I think it fits the best for charts, for example trend chart) * or modify existing function, so we could keep percentages: (sign(Sa / Sb) * max(Sa. Sb) / min(Sa, Sb) -1. For example for 3 / 1 it will give 2 (or 200%), for 1 /3 it will give -2 (or -200%), for 1 / 1 it will give 0(%). Both approaches will produce normal distribution with peak near 0.""","",0,0,1,0,0,0,0,0,0,0,0,1,0,0,0 +"EVG-2986","03/15/2018 15:39:28",2,"test-util failure ""h2. [test-util failed on windows|https://evergreen.mongodb.com/task/mci_windows_test_util_32b7ae3e8f4ab2da14c7ecfb333eb300dd772bd7_18_03_15_15_06_09/0] Host: [ec2-54-221-3-232.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-3iai7f5g] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~richard.samuels]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2991","03/16/2018 14:09:59",1,"Links in Event log to JIRA use a hostname of ""undefined"" ""See: https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_windows_64_2k8_aggregation_fuzzer_54dc55063a25fdcae65356c2515e55768181dc80_18_03_15_22_10_50#/log/EV Under the event: Mar 15, 2018 7:08:50 pmCreated Jira Alert BFG-57288. BFG-57288 links to: https://undefined/browse/BFG-57288""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-2995","03/18/2018 19:23:16",2,"race-service failure ""h2. [race-service failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_service_c109c8d2ecaf550a05223cbcaaae5d96d4f158c7_18_03_16_15_28_32/1] Host: [ec2-35-173-204-177.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-aj985ajk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~richard.samuels]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-2996","03/19/2018 14:07:03",2,"Add support for read preference to Evergreen settings ""During a primary failover, we received this error We set write concern in the Evergreen settings but not read preference. We could set read preference to primaryPreferred to avoid this error."""," error retrieving section from DB: error retrieving section service_flags: no reachable servers ",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3004","03/19/2018 19:21:19",1,"error: no dispatchable task found in the queue """""," error: no dispatchable task found in the queue extended: no dispatchable task found in the queue github.com/evergreen-ci/evergreen/service.assignNextAvailableTask /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/api_task.go:304 github.com/evergreen-ci/evergreen/service.(*APIServer).NextTask /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/api_task.go:516 github.com/evergreen-ci/evergreen/service.(*APIServer).NextTask-fm /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/api.go:688 github.com/evergreen-ci/evergreen/service.(*APIServer).checkHost.func1 /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/api.go:186 net/http.HandlerFunc.ServeHTTP /opt/go1.8/go/src/net/http/server.go:1942 github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux.(*Router).ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux/mux.go:114 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.Wrap.func1 /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:46 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:29 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/service.UserMiddleware.func1 /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/middleware.go:402 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:29 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/service.(*RecoveryLogger).ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/middleware.go:479 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(*Negroni).ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:86 net/http.serverHandler.ServeHTTP /opt/go1.8/go/src/net/http/server.go:2568 net/http.(*conn).serve /opt/go1.8/go/src/net/http/server.go:1825 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 github.com/evergreen-ci/evergreen/service.(*APIServer).NextTask /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/api_task.go:518 github.com/evergreen-ci/evergreen/service.(*APIServer).NextTask-fm /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/api.go:688 github.com/evergreen-ci/evergreen/service.(*APIServer).checkHost.func1 /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/api.go:186 net/http.HandlerFunc.ServeHTTP /opt/go1.8/go/src/net/http/server.go:1942 github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux.(*Router).ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/gorilla/mux/mux.go:114 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.Wrap.func1 /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:46 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:29 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/service.UserMiddleware.func1 /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/middleware.go:402 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.HandlerFunc.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:29 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(middleware).ServeHTTP-fm /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/service.(*RecoveryLogger).ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/service/middleware.go:479 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.middleware.ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:38 github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni.(*Negroni).ServeHTTP /data/mci/902a7d0a69432902700828156aeeb289/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/urfave/negroni/negroni.go:86 net/http.serverHandler.ServeHTTP /opt/go1.8/go/src/net/http/server.go:2568 net/http.(*conn).serve /opt/go1.8/go/src/net/http/server.go:1825 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3005","03/19/2018 20:14:20",2,"teardown_group did not run in task group ""Test results should be visible here https://evergreen.mongodb.com/task/mci_race_detector_display_lint_patch_ddf48e044c307e3f8734279be95f2d9d7134410f_5ab00b2e2a60ed6c7b037ac7_18_03_19_19_10_39.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3006","03/19/2018 20:18:54",1,"Add query parameter to retrieve test results for any task execution in REST API v2 ""The {{/tasks//tests}} endpoint returns the test results for the latest execution. A query parameter should be added to be able to request the results for a specific execution.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3007","03/19/2018 20:26:25",1,"Include project id in the task resource of the REST API v2 ""In the rest API v2, the task resource returned from the {{/tasks/}} endpoint should contain the {{project_id}}.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3010","03/20/2018 14:24:34",2,"CLI list aliases command does not list tags """""," ~ evergreen list --aliases -p mci __github ^ubuntu1604$ ^test-.* __github ^windows$ ^test-.* __github .* smoke.* smoke .* test ^ubuntu1604$ ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3014","03/20/2018 18:06:30",2,"Ability to have patch-only variants ""The opposite of {{patchable: false}} to have variants that will only run if specifically patched against.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3015","03/20/2018 18:15:38",2,"Github PR testing erroring with 404 not founds from Github and not creating patch documents ""See [here|https://mongodb.splunkcloud.com/en-US/app/search/search?q=search%20source%3Dhttp%3Aevergreen%20%22patch-intent-processor-github-d3628430-2c68-11e8-9d11-9b2e5bd22849%22&display.page.search.mode=verbose&dispatch.sample_ratio=1&earliest=-24h%40h&latest=now&sid=1521569644.1325457] for an example of such a failure. Github is returning 404 not found on the commits url, in the case of [this|https://github.com/evergreen-ci/evergreen/pull/899] PR the URL was https://api.github.com/repos/evergreen-ci/evergreen/pulls/899/commits. We're not sure if this is a Github issue, but it seems to be associated with increase of 502 errors for github. Possibilities: 1. Retry 2. small delay before initial request 3. -Creating patch documents anyway?-""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3020","03/21/2018 17:43:25",1,"EC2 price caching should retry ""To avoid test failures like https://evergreen.mongodb.com/task/mci_ubuntu1604_test_cloud_patch_e8acfa358074c70be806067e192335f4142f5ab4_5ab289e82a60ed6c7b2a6519_18_03_21_16_35_53""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3024","03/21/2018 20:30:26",2,"schedule tasks that have generate.tasks commands ahead of tasks that don't ""these tasks, in effect, have dependencies, but the scheduler won't necessarily put them at the head of the line, which will increase time-to-completion metrics. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3026","03/22/2018 17:10:20",1,"reduce interface service for http client pool ""maybe maintain more than one pool. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3027","03/22/2018 17:11:12",1,"pass contexts through validator. ""remove some/all github context.TODO cases ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3028","03/22/2018 18:56:12",1,"lint failure ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_display_lint_54f99531f11ad4784886294cfa45ff01fde0d154_18_03_22_17_51_02/0] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~richard.samuels]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3031","03/23/2018 14:41:40",2,"task restarts in dispatching state lead to stuck hosts. ""I think we should just monitor for tasks that have been dispatched for more than ~2 minutes that haven't been restarted and if they're stuck in that state, we should undispatch them, and force the hosts to retry the next-task process. This happened to [this host|https://evergreen.mongodb.com/host/sir-xmpi7gvj], and [this task|https://evergreen.mongodb.com/task/mci_race_detector_lint_model_alert_patch_54f99531f11ad4784886294cfa45ff01fde0d154_5ab3fd192fbabe3354bd9d23_18_03_22_18_59_38/0] which was restarted quickly by pull request testing, which probably has tighter timings that this aspect of the system can tolerate. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3033","03/23/2018 19:30:26",1,"race-util failure "" h2. [race-util failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_util_eed9d34f04f673ba3e5b0b399754a6739bcb1f13_18_03_23_17_35_32/0] Host: [ec2-18-232-114-219.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-1e3g54sg] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3034","03/26/2018 22:07:52",1,"incremental improvements to all config options. ""- in the admin command not the deploy command - have the ability to exclude deactivated projects""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3035","03/26/2018 22:10:43",1,"Organize UI code ""so that adding a new test file doesn't require listing it in karma.conf.js""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3036","03/27/2018 15:51:45",1,"lint failure ""h2. [lint failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_display_lint_5fa703014758d18a7fb7474cb88d50910061c861_18_03_26_18_03_02/0] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~richard.samuels]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3037","03/27/2018 16:35:14",2,"remove notify runner. ""I don't believe that the runner as such is being used, but several runners use the {{notify.NotifyAdmins}} function to send error messages, but otherwise this package is entirely unused. I think we can provide a more reasonable interface for """"sending admin email"""" and remove most of this legacy code now. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3038","03/27/2018 18:12:33",1,"Project page should not have .evergreen.yml as ghost text ""This implies that is the default, but there is no default""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3041","03/28/2018 16:36:06",1,"Have DescribeSpotInstanceRequests handle errors where spot instance doesn't exist anymore ""Don't retry for these args: { [-] DryRun: null Filters: null SpotInstanceRequestIds: [ [+] ] } client: *cloud.awsClientImpl error: InvalidSpotInstanceRequestID.NotFound: The spot instance request ID 'sir-gv6g5dvg' does not exist status code: 400, request id: ae7051ba-ecef-47e6-8880-f9c61f1b9d5e message: error running DescribeSpotInstanceRequests metadata: { [+] ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3049","03/29/2018 18:31:00",1,"smoke-test-task failure ""h2. [smoke-test-task failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_smoke_test_task_patch_19955d487142d8a07cf9954d5c59b97ec66b7a2a_5abd13b3c9ec445137470d67_18_03_29_16_26_27/0] Host: [ec2-54-91-51-128.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-ijwr6jwk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3050","03/29/2018 19:42:01",1,"move repotracker jobs to remote queue ""as a safer, step towards using the local queues less, let's move all local queue operations related to the repotracker to the remote queue. this will involve flattening some nested jobs in patch intent processing. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3051","03/29/2018 19:42:51",2,"move stats collection jobs to the remote queue ""more delicately, we should see if we can merge host-idle and task-start into a single job, to reduce the overhead. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3055","03/30/2018 16:19:12",1,"move project activation code out of repotracker ""it doesn't depend on any repotracker functionality, and should probably live in the models package. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8818","03/30/2018 18:02:36",1,"test-queue failure ""h2. [test-queue failed on ubuntu1604|https://evergreen.mongodb.com/task/amboy_ubuntu1604_test_queue_96e18b98692c7576a3cce6b9b4281898e7ff558b_18_03_29_22_01_31/0] Host: [ec2-54-158-142-207.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-yfcg7kfh] Project: [amboy|https://evergreen.mongodb.com/waterfall/amboy] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,0,0,0,1,0,0 +"EVG-5518","03/30/2018 18:28:00",1,"'Compare' delta calculations seem wrong for latency tests ""The delta calculations are actually correct but with small numbers, rounding is used and the scale is misleading. Precision makes a huge difference when numbers are as tiny as these. Look at the example below: (0.003 - 0.002) / 0.002 = 0.5 (0.0034 - 0.0017) / 0.0017 = 1 \|(0.002 - 0.003)\| / 0.002 = .334 \|(0.0017 - 0.0034)\| / 0.0017 = 0.5 When I first looked at the graph below, I thought the calculations were wrong (since they are rounded and the rounded numbers' deltas are very different from the more precise numbers' delta that is used the actual calculation). I then zoomed in and realized the imprecision of the displayed numbers was causing my confusion.""","",0,0,1,0,0,0,0,0,0,0,0,1,0,0,0 +"EVG-3061","03/30/2018 18:54:06",1,"Remove legacy event unmarshaller ""Cannot be done until October 2018 Pipe the following into the mongo shell; if it returns nothing it is safe to do this ticket:: Search the repo for """"//TODO: EVG-3061"""" to find code blocks to remove"""," use mci rs.slaveOk() db.task_event_log.find({r_id: {$exists: true}, """"data.r_type"""": {$exists: true}}).limit(1) ",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3063","03/30/2018 20:25:53",1,"nil pointer exception in build route """""," runtime/asm_amd64.s:515 [action='aborted' duration='81.643382ms' panic='runtime error: invalid memory address or nil pointer dereference' path='/build/mongodb_mongo_master_osx_108_db7b5a93e9bdfee1826a91b94a9f8b904be89813_14_02_13_03_03_10' request='3108' span='81.643569ms'] ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3068","04/02/2018 20:18:43",1,"rest v2 metrics endpoint 400 ""http://evergreen.mongodb.com/api/rest/v2/tasks/dsi_linux_runner_lint_python_scripts_823c7fd3d5881c2ebfe615e088512002593fde5d_18_04_02_16_04_17/metrics/system """," { status: 400, error: """"problem parsing time from '' (parsing time """""""" as """"""""2006-01-02T15:04:05.000Z"""""""": cannot parse """""""" as """""""""""")"""" } ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3069","04/02/2018 22:43:10",1,"getEBSCost calls getInstanceInfo with spot instance request id """""," { """"_id"""" : """"host-termination-job.sir-wf9g6zhj"""", """"job"""" : { """"metadata"""" : { """"errors"""" : [ """"error fetching ebs cost: error getting instance info: id appears to be a spot instance request ID, not a host ID (sir-wf9g6zhj)"""" ] } } } ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8667","04/03/2018 02:19:40",2,"configurable email message type ""sufficent functionality to replace notify package in evergreen, needs configurable subjects and other features the current smtp settings don't permit. ""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3074","04/03/2018 17:02:13",1,"Better handle monitor flagging the same host for termination twice ""problem saving new job host-termination-job.sir-t9ng7mkk.2018-04-03.16-00-00: E11000 duplicate key error collection: amboy.evg.service.jobs index: _id_ dup key: { : """"host-termination-job.sir-t9ng7mkk.2018-04-03.16-00-00"""" }""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8783","04/03/2018 21:58:52",1,"Allow sending slack messages to users in Grip ""The slack sender currently only allows sending messages to channels.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3087","04/03/2018 22:01:10",2,"Convert existing Github PR Status API code to use event driven notifications ""Also, after finalizing a version, also create a subscription to the outcome of that version""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3088","04/03/2018 22:08:03",2,"Write migration or script to populate Github <-> Crowd mapping ""*carefully* iterate the users in the org, and populate their github uid numbers (see model/user.GithubUser) -Given that we employ ~1000 people, throttle this operation over a couple of hours so we avoid exhausting our API limits.- [Dashboard|https://mongodb.splunkcloud.com/en-US/app/search/evergreen_github_monitoring] shows we don't drop below 4k anymore, so don't worry about throttling""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8828","04/03/2018 22:12:22",1,"test-queue failure ""h2. [test-queue failed on ubuntu1604|https://evergreen.mongodb.com/task/amboy_ubuntu1604_test_queue_3b410354187d914a8dca37ba4f95ec767b8b836c_18_04_03_21_04_27/0] Host: [ec2-107-22-74-78.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-yksr59xj] Project: [amboy|https://evergreen.mongodb.com/waterfall/amboy] ~BF Ticket Generated by [~sam.kleinman]~ ""","",0,0,0,0,1,0,0,0,0,0,0,0,1,0,0 +"EVG-3089","04/03/2018 22:18:22",2,"Add build-break subscriptions ""Automatically create subscriptions on the outcome trigger to repotracker created versions based on the project's build-break notification configuration. Search """"build-break"""" in design document for details""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3090","04/03/2018 22:22:55",2,"Add implicit patch subscriptions ""Create subscriptions to patches automatically based on the user's patch settings.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3091","04/03/2018 22:29:58",0,"Increase Github status API timeout ""increasing to 60s due to recent timeouts.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3094","04/04/2018 18:14:53",2,"Entire task group should be able to depend on a task outside the task group ""If a single task in a task group depends on a task outside the task group, this task may not be scheduled with the rest of the task group. We should support task group-level dependencies for the case where a user wishes a task group not to run until some task outside of the group runs.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3095","04/04/2018 19:23:33",1,"write migration function+generator for perf data migrations ""the JS we used in the shell to do this is, we should also have a mode that does this, but sets from/to project and leaves variant alone. """," var copy_baseline = function(tag, project, from_variant, to_variant){ var from_query = {tag: tag, project_id: project, variant: from_variant}; var to_query = {tag: tag, project_id: project, variant: to_variant}; var docs = db.json.find(from_query).toArray(); docs.forEach(function(d){ delete d._id; d.variant = to_variant db.json.insert(d); }); } ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3099","04/04/2018 22:09:39",1,"Link to first execution of a display task 404s ""This URL https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_display_unittests!_patch_d1b3c0a0a4dd31e1d1b37ed21cf00a92e59f276e_5ac52230e3c3314977acedf2_18_04_04_19_07_23/0##%257B%2522compare%2522%253A%255B%257B%2522hash%2522%253A%2522d1b3c0a0a4dd31e1d1b37ed21cf00a92e59f276e%2522%257D%255D%257D links to this URL https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_compile_unittests_patch_d1b3c0a0a4dd31e1d1b37ed21cf00a92e59f276e_5ac52230e3c3314977acedf2_18_04_04_19_07_23_0 for compile_unittests, which 404s. I believe the task execution number is being passed incorrectly to the URL by the UI code.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3101","04/05/2018 14:16:22",1,"Type must be on-demand or spot error """""," type must be on-demand or spot github.com/evergreen-ci/evergreen/cloud.(*ec2Manager).GetInstanceStatus /data/mci/779275dd6bf73b6695674a625ae2db8d/gopath/src/github.com/evergreen-ci/evergreen/cloud/ec2.go:456 github.com/evergreen-ci/evergreen/cloud.(*CloudHost).GetInstanceStatus /data/mci/779275dd6bf73b6695674a625ae2db8d/gopath/src/github.com/evergreen-ci/evergreen/cloud/cloud_host.go:53 github.com/evergreen-ci/evergreen/units.(*hostTerminationJob).Run /data/mci/779275dd6bf73b6695674a625ae2db8d/gopath/src/github.com/evergreen-ci/evergreen/units/host_termination.go:127 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool.runJob /data/mci/779275dd6bf73b6695674a625ae2db8d/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool/helpers.go:23 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool.worker /data/mci/779275dd6bf73b6695674a625ae2db8d/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool/helpers.go:61 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool.(*localWorkers).Start.func1 /data/mci/779275dd6bf73b6695674a625ae2db8d/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool/local.go:84 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3102","04/05/2018 15:23:11",1,"UI shows an undefined error in certain host status changes ""Two cases this has been observed in: - When trying to change a static host to `decommissioned` - When trying to update the status with an invalid status""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3103","04/05/2018 16:40:34",2,"Github PRs pushed in close succession result in unscheduled tasks in most recent patch ""https://evergreen.mongodb.com/version/5ac4e71ac9ec446bd998d117 was the most recent commit, but we had to manually schedule windows. The previous commit, https://evergreen.mongodb.com/version/5ac4e788c9ec446bd998d66e, worked fine. Note that both had the same patch time.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3104","04/05/2018 19:55:07",1,"Panic in repotracker ""https://mongodb.slack.com/archives/C866SR2LR/p1522954349000579""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3105","04/05/2018 20:01:23",1,"No reservation found for instance id ""https://mongodb.slack.com/archives/C866SR2LR/p1522954408000535""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3107","04/06/2018 00:48:34",1,"avoid terminating slow hosts that have provisioned ""currently we have an absolute cutoff for a host to go from started->running a task, and it leasds to some frustrating cases where we successfully provision hosts that then get killed before the host gets an agent. We should: - when flagging slow provisioning hosts for termination we should make sure that they're actually not-yet-provisioned. - have the timer reset when the host gets provisioned so """"waiting for agent"""" is tracked separately rather than having a single timeout for everything. - right now the """"is this host idle and should be terminated"""" is in 2 files and at 3-4 functions/statements, that should be centralized. It would be great if this could be expressed in a way that could be queried for from mongodb rather than filtered at the application level. - for better traceability, we should log a reason for flagging a host for termination in the event log or at least in splunk when we terminate it. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3111","04/06/2018 14:03:31",1,"Panic in host termination job ""pool/helpers.go:36 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 units/host_termination.go:85 pool/helpers.go:23 pool/helpers.go:61 pool/local.go:84 runtime/asm_amd64.s:2197""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3113","04/06/2018 18:04:44",2,"Pagination of /rest/v2/tasks//tests isn't compatible with running tests multiple times ""In the {{mongodb\-mongo\-*}} Evergreen projects we run test suites using resmoke.py with {{\-\-repeat=10}} on [the Linux Repeated Execution builder|https://evergreen.mongodb.com/task/mongodb_mongo_master_linux_64_repeated_execution_jsCore_4644d79d8cc42f2dd343fbab2f1d54fe80e2e2ea_18_03_01_15_02_40]. This causes the {{report.json}} we upload to Evergreen to have the same JavaScript test mentioned multiple times. Attempting to use pagination to iterate over the test results leads to (1) certain results being returned multiple times, and more noticably (2) an infinite loop. I think the {{/rest/v2/tasks//tests}} endpoint should be changed to either (a) ignore the {{limit}} parameter and return all executions of a test in its response, or (b) paginate using a unique value - for example, the _id of the document in the {{mci.tests}} collection. """," Fetching test results https://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_linux_64_repeated_execution_jsCore_4644d79d8cc42f2dd343fbab2f1d54fe80e2e2ea_18_03_01_15_02_40/tests?limit=1000 Fetching test results https://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_linux_64_repeated_execution_jsCore_4644d79d8cc42f2dd343fbab2f1d54fe80e2e2ea_18_03_01_15_02_40/tests?limit=1000&start_at=collection_info_cache_race%3AValidateCollections Fetching test results https://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_linux_64_repeated_execution_jsCore_4644d79d8cc42f2dd343fbab2f1d54fe80e2e2ea_18_03_01_15_02_40/tests?limit=1000&start_at=drop_index%3AValidateCollections ... Fetching test results https://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_linux_64_repeated_execution_jsCore_4644d79d8cc42f2dd343fbab2f1d54fe80e2e2ea_18_03_01_15_02_40/tests?limit=1000&start_at=pull_or%3AValidateCollections Fetching test results https://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_linux_64_repeated_execution_jsCore_4644d79d8cc42f2dd343fbab2f1d54fe80e2e2ea_18_03_01_15_02_40/tests?limit=1000&start_at=sort10%3AValidateCollections Fetching test results https://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_linux_64_repeated_execution_jsCore_4644d79d8cc42f2dd343fbab2f1d54fe80e2e2ea_18_03_01_15_02_40/tests?limit=481&start_at=update_multi5%3AValidateCollections Fetching test results https://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_linux_64_repeated_execution_jsCore_4644d79d8cc42f2dd343fbab2f1d54fe80e2e2ea_18_03_01_15_02_40/tests?limit=3&start_at=write_result%3AValidateCollections Skipping https://evergreen.mongodb.com/api/rest/v2/tasks/mongodb_mongo_master_linux_64_repeated_execution_jsCore_4644d79d8cc42f2dd343fbab2f1d54fe80e2e2ea_18_03_01_15_02_40/tests?limit=3&start_at=write_result%3AValidateCollections because we'd otherwise infinite loop ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3117","04/09/2018 21:11:39",2,"Unable to run anser from a directory outside the clients directory if EVGHOME is unset ""john.liu@evergreenapp-1:/srv/evergreen/current/clients/linux_amd64$ ./evergreen service deploy anser --id admin_map_restructure --dry-run --url $DB [evergreen] 2018/04/09 19:58:57 [p=info]: creating new remote job queue with 32 workers [evergreen] 2018/04/09 19:58:57 [p=info]: job server running [evergreen] 2018/04/09 19:58:57 [p=error]: EVGHOME is unset [evergreen] 2018/04/09 19:58:57 [p=warning]: client directory 'clients' does not exist, creating empty directory and continuing with caution [evergreen] 2018/04/09 19:58:57 [p=error]: mkdir clients: permission denied [evergreen] 2018/04/09 19:58:57 [p=emergency]: problem configuring application environment: problem finding client binaries: lstat clients: no such file or directory""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3120","04/10/2018 02:02:14",1,"ValidateHost should always validate host secret ""https://github.com/evergreen-ci/evergreen/blob/9c9ad23589805c8a7c8c6b327f014b341156d4a3/model/validate.go#L71-L74""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3122","04/10/2018 16:52:23",1,"Finalizing a patch from the CLI fails if display task and task group are both present """""," (venv) [jonathan@CAP-JA mongo]$ evergreen patch -y -d """"Min task_group config #4"""" -v linux-64 -t """"task1,task2!,task3,task4"""" -f Unexpected reply from server (500 Internal Server Error): error processing patch: patch has no build variants or tasks (venv) [jonathan@CAP-JA mongo]$ evergreen patch -y -d """"Min task_group config #4"""" -v linux-64 -t """"task1,task2!,task3,task4"""" Patch successfully created. ID : 5accd87bc9ec44776407faf6 Created : 2018-04-10 15:30:04.421 +0000 UTC Description : Min task_group config #4 Build : https://evergreen.mongodb.com/patch/5accd87bc9ec44776407faf6 Finalized : No ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3123","04/10/2018 17:10:18",1,"Allow admins to add a reason when quarantining a host ""When I quarantine a host it should prompt to add a reason which should be free form text. This allows for someone else to go back to troubleshoot these hosts and they can see a clear reason why the host was manually quarantined. This message should be displayed in the event log under the """"Additional Details""""""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3137","04/10/2018 21:53:48",2,"Tasks with same task group but different build are out of order in queue ""https://evergreen.mongodb.com/build/mongodb_mongo_master_enterprise_windows_64_2k8_openssl_patch_d1b3c0a0a4dd31e1d1b37ed21cf00a92e59f276e_5acd1fe6c9ec443f0213179b_18_04_10_20_35_51""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3128","04/11/2018 15:46:29",2,"add flag to disable distro without removing it. ""effect should be: - do not generate new schedules for it. - do not start new hosts for it. - disable spawning. should be ok to let existing hosts run and work through the existing queue. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3129","04/11/2018 15:47:30",2,"admin rest route to clear a schedule for a specific distro ""should be able to clear a persisted schedule, effectively preventing new tasks from being dispatched on that distro (until the scheduler runs again.) ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3133","04/11/2018 16:23:29",1,"Windows task restarts itself after completion ""This task ran to completion on windows, then restarted and ran again, 9 times. It even finished uploading artifacts before restarting (though the upload portion is missing from the log). The uploading of artifacts is a """"post"""", so the task finished successfully. https://evergreen.mongodb.com/task/mongo_odbc_driver_win32_build_patch_a1013a7e247e05e347a03e04bdf146140bb4f720_5ace13f6e3c3311b1673eb37_18_04_11_13_56_37""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3134","04/11/2018 17:05:50",1,"remove configuration MergeToggle configuration ""(doesn't make sense any more.) ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9227","04/12/2018 16:18:43",1,"Grip SMTP sender not sending correctly formatted RCPT command/not handling STARTTLS command ""Grip does this: {code} addr := target.String() if err = o.client.Rcpt(addr); err != nil { {code} So addr is formatted like a RFC 5322, but the RFC says it should just be the (""""mailbox and domain"""" (that is addr.Address) See quote from [here|https://tools.ietf.org/html/rfc5321] """," addr := target.String() if err = o.client.Rcpt(addr); err != nil { The second step in the procedure is the RCPT command. This step of the procedure can be repeated any number of times. RCPT TO: [ SP ] The first or only argument to this command includes a forward-path (normally a mailbox and domain, always surrounded by """"<"""" and """">"""" brackets) identifying one recipient. ",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3136","04/12/2018 17:46:23",1,"Add more retries to the host provisioning step ""We're seeing problems with some hosts taking a bit longer than usual to start the ssh service so we run into provisioning problems (like https://evergreen.mongodb.com/host/sir-tbs87y1g). It looks like ssh becomes available within the minute after we stop retrying, so adding more retries would help. We'll also look into ways to make ssh start faster.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3140","04/13/2018 14:40:19",1,"Add Newer/Older buttons at bottom of patches list ""When searching through a list of patches for a specific patch run, my typical UX flow is to scan each entry from top to bottom to see if the one I want is on that page. If it's not, I have to scroll back to the top to click the """"Older"""" button to get to the next page. It would be useful to have the newer/older links additionally displayed at the bottom to avoid this inconvenience.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3141","04/13/2018 18:04:11",1,"lobster next/prev does not notice changes in search term ""If you start a search in lobster by typing a search term and then clicking Find, and then you change (edit) the search term, the Prev and Next buttons continue the former search, instead of searching for the new term.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3143","04/15/2018 21:44:54",2,"Add Evergreen command to serialize all expansions into a YAML file ""One of the reasons that the Server team's {{etc/evergreen.yml}} project configuration file makes so much use of embedded {{shell.exec}} scripts is because the string substitution for expansions is syntactically convenient. There are many advantages (esp. around testability) to moving these embedded scripts out of the Evergreen project configuration but we'd like to be able to avoid a bunch of options processing boilerplate in Python when we'd go to convert them. Having an Evergreen command able to generate the YAML file so all the of the scripts could take the same command line inputs was an idea that came up between [~david.bradford] and myself as a way to address this.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3145","04/16/2018 16:31:31",2,"Error restarting PyMongo build ""Clicking """"restart build"""" here fails: https://evergreen.mongodb.com/version/mongo_python_driver_04de1697cb1f1d877023942f7ce620415ee08b60 Furthermore there's no error message, only """"undefined"""". I hypothesize that Evergreen times out restarting a build with 1449 tasks, and there's a second bug that prevents it from displaying an informative error.""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-3148","04/17/2018 14:26:30",1,"Intra-task group dependencies should be a validation warning ""Tasks will not run serially if some tasks have dependencies while others do not, since the scheduler must run to schedule a task whose dependencies have just become satisfied.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3150","04/17/2018 17:49:51",1,"Function names are not validated ""The following will pass {{evergreen validate}}: """," ... - func: """"no function defined"""" ... ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3158","04/17/2018 22:47:47",1,"Make it possible for project admins to blacklist tasks/builds/versions for their projects ""Prior to EVG-913 this was possible by any authenticated user but is now something that can only be done by Evergreen admins.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3159","04/18/2018 15:05:50",1,"test-agent failure ""h2. [test-agent failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_agent_0ed622d13a7b0861c70f7a2e7942c8e6f5285521_18_04_17_21_32_26/0] Host: [ec2-54-86-109-55.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-d9vg5qhj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3161","04/18/2018 15:46:08",1,"Display task shows date of ""Dec 31, 0000"" ""https://evergreen.mongodb.com/task/mci_ubuntu1604_display_lint_9cc8da404f24023cd24e6a5e727cd37ed91565ec_18_04_18_14_41_08""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3162","04/18/2018 16:28:01",2,"Duplicated/missing patch aliases in the UI ""The workloads project had two {{.* .*}} GitHub patch aliases. The Evergreen project was missing its {{test.*}} alias.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3171","04/19/2018 16:35:43",1,"Waterfall - collapsed view for search ""Perf team wants to improve UX of waterfall when working with build variants that have different schedule. For example for sys-perf project 'Linux 3-Shard Cluster' variant executed on weekly basis and an performance engineer have to scroll several pages to see the run results. As a good starting point it would be nice to have the same collapsed view when using search with variant name. Currently, the search doesn't show collapsed results, because it executed on UI. This happens because search works on client side only. In order to implement new behavior we should send search term to backend and also modify DB query to use it. Acceptance criteria: * Users have similar UX (collapsed view) when looking at all results (currently done) and when looking at search results (todo)""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3174","04/19/2018 17:59:49",1,"Display tasks with multiple executions do not have previous_executions when requested via api ""Example: https://evergreen.mongodb.com/api/rest/v2/builds/mci_race_detector_041f5d87b3d9609bef48a4a21e32606242e8638b_18_04_17_20_01_00/tasks?fetch_all_executions=1 Expected: In the above case where execution=1 for the latest run, there should be a previous_executions element with execution=0 data. Actual: previous_executions is missing""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3178","04/19/2018 21:15:58",1,"create host provisioning background job ""with timeouts, and a sustainable periodicity. this is half of the hostinit process. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3179","04/19/2018 21:33:56",2,"Link icons in HTML logs inoperative ""The """"link"""" icons at the beginning of each line of the HTML logs seem to not be working. Example: https://evergreen.mongodb.com/task/dot_net_driver_tests__version~2.6_os~windows_64_topology~replicaset_auth~auth_ssl~nossl_test_patch_b6a9c2675a5eeb887e8103b262e8f25d5a564d00_5ad8df43e3c33109168f2959_18_04_19_18_26_12 Possibly related to the following error message: """"Refused to execute script from 'https://evergreen.mongodb.com/static/js/jquery.js' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled."""" Visiting """"https://evergreen.mongodb.com/static/js/jquery.js"""" yields a 404 page.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3184","04/20/2018 16:47:23",2,"move host creation to background job ""this is the component that calls start-hosts in the cloud APIs""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3186","04/20/2018 16:48:42",2,"run background job creation operation on multiple systems ""but maybe not every system, use an environment variable to flag this on some systems. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3189","04/20/2018 19:36:18",1,"make smoke-start-server fails locally on OS X """""," [web.service] 2018/04/20 14:33:14 [p=trace]: [evergreen] 2018/04/20 14:33:14 [p=emergency]: problem configuring application environment: Failed to setup email logger: dial tcp [::1]:25: connect: connection refused ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3191","04/20/2018 21:07:05",1,"Intermittent TestAbort failures in test-agent ""h2. [test-agent failed on ubuntu1604|https://evergreen.mongodb.com/task/mci_ubuntu1604_test_agent_patch_662c9afe7d4298a40dfe3ce43d1521699f76edd8_5ada419ac9ec441366fe38c8_18_04_20_19_38_06/0] Host: [ec2-18-232-166-76.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-a8ar77rk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3204","04/23/2018 19:56:07",2,"Build Failure Links for Performance Discovery ""Given a revision/patch is selected that contains tests with associated open Build Failures When I scroll down the page Then I see a list of BF's listed in a """"Failures"""" column that are open and that were created after the reference point (baseline tag, patch id, or revision) Given a revision/patch is selected that contains tests with associated open Build Failures When I click on a Build Failure Link Then I'm taken to that build failure in JIRA""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0 +"EVG-3252","04/24/2018 22:21:33",2,"Windows task restarted, likely due to agent panic """""," [2018/04/24 15:13:57.794] Task logger initialized (agent revision: 854f0bcf9c94208871ddbf3616d545071dfd0bfc). [2018/04/24 15:13:58.050] Starting task mongodb_mongo_master_windows_64_2k8_ssl_powercycle_fcv3.6_patch_fc8096229e6ba7745431f77ec985eb65ee0541af_5adf7a02e3c33152d0e8bdca_18_04_24_18_40_36, execution 0. [2018/04/24 15:13:58.174] Running pre-task commands. [2018/04/24 15:13:58.501] Running command 'shell.exec' in """"kill processes"""" (step 1 of 5) [2018/04/24 15:13:58.606] Running command 'shell.exec' in """"cleanup environment"""" (step 2 of 5) [2018/04/24 15:13:58.638] rm -rf src /data/db/* mongo-diskstats* mongo-*.tgz ~/.aws ~/.boto venv ... [2018/04/24 15:48:09.783] 2018-04-24 19:47:39,841 INFO System was last booted 2018-04-24 19:44:52.000000, up 167 seconds [2018/04/24 15:48:09.783] 2018-04-24 19:47:39,841 INFO Operations to perform ['crash_server'] [2018/04/24 15:48:09.783] Connection reset by 10.122.1.15 port 22 [2018/04/24 15:53:39.027] Task logger initialized (agent revision: 854f0bcf9c94208871ddbf3616d545071dfd0bfc). [2018/04/24 15:53:39.261] Starting task mongodb_mongo_master_windows_64_2k8_ssl_powercycle_fcv3.6_patch_fc8096229e6ba7745431f77ec985eb65ee0541af_5adf7a02e3c33152d0e8bdca_18_04_24_18_40_36, execution 0. [2018/04/24 15:53:39.387] Running pre-task commands. [2018/04/24 15:53:39.673] Running command 'shell.exec' in """"kill processes"""" (step 1 of 5) [2018/04/24 15:53:39.848] Running command 'shell.exec' in """"cleanup environment"""" (step 2 of 5) [2018/04/24 15:53:39.888] rm -rf src /data/db/* mongo-diskstats* mongo-*.tgz ~/.aws ~/.boto venv ... [2018/04/24 16:21:01.837] 2018-04-24 20:20:32,608 INFO Operations to perform ['crash_server'] [2018/04/24 16:21:01.837] Connection reset by 10.122.15.99 port 22 [2018/04/24 16:26:38.510] Task logger initialized (agent revision: 854f0bcf9c94208871ddbf3616d545071dfd0bfc). [2018/04/24 16:26:38.736] Starting task mongodb_mongo_master_windows_64_2k8_ssl_powercycle_fcv3.6_patch_fc8096229e6ba7745431f77ec985eb65ee0541af_5adf7a02e3c33152d0e8bdca_18_04_24_18_40_36, execution 0. [2018/04/24 16:26:38.827] Running pre-task commands. [2018/04/24 16:26:39.081] Running command 'shell.exec' in """"kill processes"""" (step 1 of 5) [2018/04/24 16:26:39.408] Running command 'shell.exec' in """"cleanup environment"""" (step 2 of 5) [2018/04/24 16:26:39.461] rm -rf src /data/db/* mongo-diskstats* mongo-*.tgz ~/.aws ~/.boto venv ... [2018/04/24 16:47:37.378] 2018-04-24 20:47:04,755 INFO System was last booted 2018-04-24 20:44:24.000000, up 160 seconds [2018/04/24 16:47:37.378] 2018-04-24 20:47:04,755 INFO Operations to perform ['crash_server'] [2018/04/24 16:47:37.378] Connection reset by 10.122.0.170 port 22 [2018/04/24 16:53:08.819] Task logger initialized (agent revision: 854f0bcf9c94208871ddbf3616d545071dfd0bfc). [2018/04/24 16:53:09.347] Starting task mongodb_mongo_master_windows_64_2k8_ssl_powercycle_fcv3.6_patch_fc8096229e6ba7745431f77ec985eb65ee0541af_5adf7a02e3c33152d0e8bdca_18_04_24_18_40_36, execution 0. [2018/04/24 16:53:09.451] Running pre-task commands. [2018/04/24 16:53:09.748] Running command 'shell.exec' in """"kill processes"""" (step 1 of 5) [2018/04/24 16:53:10.106] Running command 'shell.exec' in """"cleanup environment"""" (step 2 of 5) [2018/04/24 16:53:10.153] rm -rf src /data/db/* mongo-diskstats* mongo-*.tgz ~/.aws ~/.boto venv ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3253","04/24/2018 23:45:49",1,"REST /v1/tasks/task_id endpoint broken for split tasks ""In particular the test_results object is empty. I use this for a script that shows me all failing tests across all tasks in a patch build.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3261","04/25/2018 15:17:13",1,"Validate that execution tasks in a display task are not named display_* ""This may cause task IDs to collide.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3262","04/25/2018 15:41:41",1,"Evergreen /build page should show wall-clock time for display tasks listed in the ""Tasks"" sidebar ""For example, the {{sharding}} task reports that it takes 1h25m but that is the cumulative time and not the wall-clock time after it has been subdivided into {{sharding_1}}, {{sharding_2}}, etc. I'd like to be able to use the """"Tasks"""" sidebar to identify the long-running Evergreen tasks so I think displaying the wall-clock time instead of the cumulative time would be more helpful. [https://evergreen.mongodb.com/build/mongodb_mongo_master_enterprise_rhel_62_64_bit_db80e9fbd16df2ef3b357bad4c4c7d9212e57dcf_18_04_25_09_28_08] [https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_display_sharding_db80e9fbd16df2ef3b357bad4c4c7d9212e57dcf_18_04_25_09_28_08]""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3263","04/25/2018 15:44:14",2,"Evergreen /build page should provide some way to expand display tasks in the ""Tasks"" sidebar into their constituent execution tasks ""The table below the """"This task contains 16 execution tasks"""" section that's shown on [this task page|https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_display_sharding_db80e9fbd16df2ef3b357bad4c4c7d9212e57dcf_18_04_25_09_28_08] would be beneficial to be able to visualize inline on the /build page in the """"Tasks"""" sidebar as a way to compare across Evergreen tasks how long the execution units take to run.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3265","04/25/2018 16:53:16",1,"Panic in ec2 host provider ""https://github.com/evergreen-ci/evergreen/blob/fede5eb386db11f5911149464c9f8d9dbbbdba28/cloud/ec2.go#L616 stack pool/helpers.go:36 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 cloud/ec2.go:616 hostinit/setup.go:121 hostinit/setup.go:277 hostinit/wrapper.go:64 units/provisioning_setup_host.go:78 pool/helpers.go:23 pool/helpers.go:61 pool/local.go:84 runtime/asm_amd64.s:2197""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3266","04/25/2018 16:58:04",1,"Display ""Files"" section for failed execution tasks on the display task's /task page ""This request came out of a Slack conversation [~milkie] would wishes to avoid needing to click through to the execution task when he wants to view the artifacts associated with the particular task failure. https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_display_replica_sets_auth_patch_b57eee5a295ede1fd67299dc9990c272c1f66ea3_5ae08618e3c33152d0fc8b41_18_04_25_13_44_15""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3267","04/25/2018 17:05:49",1,"Reduce API calls in collect-task-end-data and collect-host-idle-data jobs ""getEC2Cost seems to make an unnecessary call to GetInstanceInfo. This causes us to exceed our API limits when > 1000 tasks finish in < 10 minutes. I think the data we need from this API call can be cached and we may be able to drastically reduce the API calls we make for these jobs.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3269","04/25/2018 21:10:23",1,"Log total queue length in a stats job ""For the historical dashboard, which currently has a graph with no data.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3270","04/25/2018 21:43:40",1,"SetupHost should not attempt to set up a host if another job is there first ""We saw a case where the queues were backed up, and many provisioning-setup-host jobs attempted to run on a single host, causing it to become decommissioned while it was running a task. It's also conceivable this could happen if a job has not finished by the time the job creation job runs.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3273","04/26/2018 15:47:55",1,"Run create host more, setup host less ""In this commit https://github.com/evergreen-ci/evergreen/commit/e4da95da76f03a2611e0226e966ec29b738e9ca4 we throttled hostinit on the theory that it is the cause of us hitting AWS API limits. However, from Splunk graphs from a period where we started 300 new hosts in 10 minutes, it's clear that the biggest user of the API is setup host. Since we pay up front for a minute, and since it may take that long for hosts to spawn, we should run setup host at the same rate that we run create host. See link to graph in comment.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3277","04/27/2018 16:15:56",1,"Error when restarting display task led to multiple restarts and some tasks with no task logs ""When I had click the restart button for https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_display_sharding_auth_patch_7cd83e5486cfb3383c2e4e5671ae9602be297547_5ae2b03c2fbabe28b01ee4db_18_04_27_05_08_24, there was some error that was reported (no screenshot, sorry). Refreshing the page shows that the task had actually restarted but clicking through to the execution tasks showed that the task had effectively been restarted multiple times. https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_display_sharding_auth_patch_7cd83e5486cfb3383c2e4e5671ae9602be297547_5ae2b03c2fbabe28b01ee4db_18_04_27_05_08_24/3 is marked as """"System unresponsive"""" because some tasks (e.g. https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_sharding_auth_19_patch_7cd83e5486cfb3383c2e4e5671ae9602be297547_5ae2b03c2fbabe28b01ee4db_18_04_27_05_08_24/3) are saying that they are running when in fact [the host|https://evergreen.mongodb.com/host/sir-wn2r7dhg] has been terminated already.""","",0,0,0,0,0,0,1,0,0,0,1,0,0,0,0 +"EVG-3278","04/27/2018 16:21:08",1,"Goroutine leak in agent ""goroutine 146625 [chan send, 1370 minutes]: github.com/evergreen-ci/evergreen/agent.(*Agent).runCommands.func2.1(0xc42084d380, 0xc420edc7c0) /data/mci/2c983fd2b509e3982e50ec453047eecc/gopath/src/github.com/evergreen-ci/evergreen/agent/command.go:87 +0x160 github.com/evergreen-ci/evergreen/agent.(*Agent).runCommands.func2(0xc42084d380, 0xc420edc7c0, 0x29438e0, 0xc420ffa0c0, 0xc4203862a0, 0xc420adc9a0) /data/mci/2c983fd2b509e3982e50ec453047eecc/gopath/src/github.com/evergreen-ci/evergreen/agent/command.go:91 +0xf2 created by github.com/evergreen-ci/evergreen/agent.(*Agent).runCommands /data/mci/2c983fd2b509e3982e50ec453047eecc/gopath/src/github.com/evergreen-ci/evergreen/agent/command.go:91 +0x6e2""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3279","04/27/2018 16:55:54",1,"Task page from a task in a display_group needs a navigation back to the display_group ""When navigating from a display_group to a task there is no link on the task page back to the display group.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3280","04/27/2018 21:31:24",1,"race-agent failure ""h2. [race-agent failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_agent_df2949c03cd3c2af3af4f7c968ecaf8147095f1a_18_04_27_15_21_34/0] Host: [ec2-54-152-68-147.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-anmi6qtk] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~richard.samuels]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3281","04/27/2018 22:34:00",1,"Populate 'Failing Tests' field in BFG/BF tickets with failing tests ""See summary.""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3282","04/28/2018 06:41:30",1,"Cannot save project that has PR testing enabled ""The https://evergreen.mongodb.com/projects##stitch-cloud-prod project cannot be saved right now because the stitch-cloud-qa project also tracks master as it should but it does not have PR testing due to the restriction. The error I get saving on stitch-cloud-prod is """"Couldn't save project: Cannot enable PR Testing in this repo, must disable in 'stitch-cloud-prod' first""""""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3283","04/28/2018 19:32:43",1,"Add files links to REST V2 /tasks/{task_id} endpoint for exec tasks in a display task ""https://evergreen.mongodb.com/rest/v1/tasks/mongodb_mongo_master_enterprise_rhel_62_64_bit_coverage_display_unittests!_5891912b5622eed300b11b05cd3269be580e086c_18_04_27_11_55_41 reports \{{""""files"""": null}}.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3284","04/30/2018 04:14:58",1,"Add pprof endpoint to agent ""In EVG-3276, in order to get the stack trace for a running agent, we had to attach to its stdout and then send it SIGQUIT. We currently have pprof on the runner and web service. It should also be exposed on the agent.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3286","04/30/2018 17:00:35",2,"Add support for force terminating multiple hosts ""EVG-68 added support for terminating one.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3290","04/30/2018 23:18:17",1,"fetchDiffFromGithub should retry ""We hit this error: """," failed to fetch diff from github: Expected 200 OK, got 404 Not Found patch document should have 1 patch, found 0 ",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3291","04/30/2018 23:23:30",2,"Host termination UI ran teardown script in infinite loop ""I terminated the host in the DB to stop it. https://evergreen.mongodb.com/host/sir-bi2g7aph""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3296","05/01/2018 15:07:11",1,"Tasks restart job panics at the end log statement ""pool/helpers.go:36 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 units/tasks_restart.go:70 pool/helpers.go:23 pool/helpers.go:61 pool/local.go:84 runtime/asm_amd64.s:2197""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3300","05/02/2018 03:13:53",1,"UpdateRunningTask should check host health ""[UpdateRunningTask|https://github.com/evergreen-ci/evergreen/blob/eca5f65b497c2b4325b6a71fe24d85ffde3a5629/model/host/host.go#L406] may attempt to assign a task to a host that has been decommissioned or terminated, because iterating over the queue can take some time, and while this is happening the host may change state. Before assigning a task to a host, we should check host health once more, like the beginning of [NextTask|https://github.com/evergreen-ci/evergreen/blob/eca5f65b497c2b4325b6a71fe24d85ffde3a5629/service/api_task.go#L366] does.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3301","05/02/2018 03:23:59",2,"Cache expected task durations between scheduler runs ""Cache the results of [GetExpectedDurations|https://github.com/evergreen-ci/evergreen/blob/eca5f65b497c2b4325b6a71fe24d85ffde3a5629/scheduler/task_duration_estimator.go#L15] between scheduler runs. Also, ensure this query is covered by an index.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3303","05/02/2018 15:16:51",1,"Eradicate IsNil from auth.User interface ""In rest/route/authenticator.go, the return values from GetUser need to be nil checked. This lets us remove the IsNil method.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3309","05/02/2018 20:18:51",1,"BFG tickets are not being created for some Evergreen failures ""This was first reported to me by [~esha.maharishi]. [Here|https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1604_debug_asan_sharding_ese_c50a57061af31f92c1c6aab09b1417ab127fed0c_18_04_25_19_45_49] is an example of a task that did not generate a BFG ticket. It's been failing on every commit, but only now has someone noticed the failure. I'm unsure if every one of those failures are missing a BFG, or if it's just some of them. After speaking with [~robert.guo], I'm marking this as P1 because it's crunch time for the 4.0 release and we need clear visibility as to what is failing. It would be nice if we could run an analysis of * all the failures in Evergreen * all the tickets created in the BFG project for the past 7 days or so, so we can correlate them and see what percentage of Evergreen failures are missing a BFG ticket. If the percentage is low, we can drop the priority.""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-3313","05/03/2018 18:13:32",1,"An offline server shown as running ""I see https://evergreen.mongodb.com/host/sles12-z-3.maristisv.build.10gen.cc is in running state and claiming that Last Reachability Check ran a few seconds ago, but we know that it's down right now and not reachable.""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-3316","05/04/2018 14:55:19",1,"Search is not being updated after changing case sensitive toggle ""Go here: https://logkeeper.mongodb.org/lobster/build/6851102e2debb777c24bf4cc37f82461/test/5aebe84a54f24812c008f808?bookmarks=0%2C19723 Type """"numberLong"""" in the Search bar and click Find twice. (should be at hit 2 of 891) Now change the search to """"numberLong("""" and turn on Case Sensitive search, then click Next. The browser will hang as the search script never returns.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3318","05/04/2018 17:46:19",1,"Some task history queries do not return results ""https://evergreen.mongodb.com/task_history/mongodb-mongo-master/unittests?revision=11d837751b0da2cf7948ee17e2f6438f38c93693#/decorable_test=fail""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3319","05/04/2018 18:13:19",1,"Escape Jira reserved characters in build baron plugin ""[https://confluence.atlassian.com/jiracoreserver073/search-syntax-for-text-fields-861257223.html]   [https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_67_s390x_display_unittests!_11d837751b0da2cf7948ee17e2f6438f38c93693_18_05_04_03_57_22] ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8940","05/04/2018 18:16:12",1,"Grip email sender cannot be long lived due to socket timeouts ""Must open a connection per send""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3320","05/04/2018 21:58:53",1,"Task in task group incorrectly has build_id set to it's task id. ""Task mongodb_mongo_master_enterprise_rhel_62_64_bit_compile_patch_3d9ad8270139723593781ba980dd07c5c230b085_5aecb3f4e3c331265f754822_18_05_04_19_27_50 has a build id that is the same as it's task id""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3324","05/04/2018 23:45:38",1,"Fold IsDispatchable into FindNextTask ""If a task is not dispatchable, we iterate over the queue again in FindNextTask.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3330","05/07/2018 18:45:48",1,"fetch_all_executions tasks endpoint can be slow ""This takes 8-10 seconds. [https://evergreen.mongodb.com/api/rest/v2/builds/mongodb_mongo_v3.6_enterprise_rhel_72_s390x_7715621883aee73cbf5c162db6d04578ba353f60_18_05_07_11_04_31/tasks?fetch_all_executions=1] [~cristopher.stauffer] is using this endpoint in a script, so it should be faster than this.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3334","05/08/2018 22:32:47",1,"coverage failure ""h2. [coverage failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_coverage_53781eaad5d372a2e3c90845e29c136320391afc_18_05_08_18_23_55/0] Host: [ec2-107-22-128-18.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-gveg435h] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~brian.samek]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3335","05/09/2018 14:45:40",1,"Panic when retrieving banner in UI route ""unable to retrieve admin settings: error populating section alerts: error retrieving section alerts: reflect: call of reflect.Value.Type on zero Value""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3337","05/09/2018 19:03:13",2,"Have to hit back button twice to get back to Evergreen from Lobster. ""# Go here: [https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_integration_tests_replset_07ae6a93bf517643adcf4098e369f49e28f0bf99_18_05_09_16_47_46] # Click HTML next to any test # It takes 2 clicks of the back button to get back to evergreen, I'd expect it to only take one.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3346","05/10/2018 20:06:07",2,"Reduce calls to DescribeSpotPriceHistory ""We occasionally exceed our AWS API limits. The two most frequent calls are DescribeInstances, which EVG-3251 moved to a batch call, and DescribeSpotPriceHistory, which this ticket is meant to address. We call this function in two places, in describeHourlySpotPriceHistory, which is called by the task end and host idle jobs, and by getLatestLowestSpotCostForInstance, which is called each time we spawn an ec2 host with type auto, to determine if we should spawn an on-demand or a spot host. I believe we should do two things: # Query Splunk for the logging in describeHourlySpotPriceHistory and getLatestLowestSpotCostForInstance to determine if one of these functions represents the bulk of the calls to DescribeSpotPriceHistory. They may both be used heavily, since the former is called each time we spawn a host, and the latter each time a task ends. # Figure out how to cache these data. (The two cases use different parameters, but I think this is only because getLatestLowestSpotCostForInstance passes a future date to only get the latest price, so we can make the calls identical). It might make sense to cache these data. We can use their granularity to determine our caching strategy, or use 1-minute granularity, since it's unlikely we care to make finer distinctions than that.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3347","05/10/2018 20:29:24",2,"Hosts that have transitioned to running after agent deploy failures do not retry ""We quarantine a host if StartAgentOnHost fails at least 10 times. However, we do this with an aggregation on the event log, which means that we will still believe that the put job has failed 10 times if the host has been quarantined for some time and has just been set to running. We should ensure that newly running hosts get all 10 attempts. *We should also create a ticket.*""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3348","05/11/2018 13:28:03",0,"Perf tools - number normalizations ""There are different types of numbers could be found on perf tools pages - some of them are usual, however there are also very big and very small numbers, which require some extra space to display. Moreover, currently, small numbers could be truncated to 0, which makes the number useless. Goal: all numbers should be easily readable, comparable and informative.  In order to improve this we should use number normalization, which I think should work like this: * Consider the first three (TBD) non-zero (TBD) digits to be significant. * Drop the rest part of the value * Use short notation where possible, like k or M (TBD)  ""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0 +"EVG-8573","05/12/2018 18:03:52",2,"create evergreen project for gimlet ""- include threshold (95% ?) for coverage - add pull-request testing - single task""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3356","05/12/2018 20:01:56",1,"use gimlet helpers for reading/writing to request data ""remove similar functions from the util package""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3363","05/13/2018 22:28:50",1,"Panic: nil cloud manager in setupHost() ""[https://github.com/evergreen-ci/evergreen/blob/bd044573930dcf571d8ec43a10670d38295c34a3/hostinit/setup.go?utf8=%E2%9C%93#L122]   pool/helpers.go:36 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 cloud/ec2.go:621 hostinit/setup.go:122 hostinit/setup.go:278 hostinit/wrapper.go:64 units/provisioning_setup_host.go:78 pool/helpers.go:23 pool/helpers.go:61 pool/local.go:84 runtime/asm_amd64.s:2197   5/11/18 10:28PM EST from a Slack alert""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3364","05/14/2018 16:44:16",1,"Do not disable PR testing when disabling a project ""Instead, check if the project is disabled when determining whether or not to create a patch build from a github webhook. We shouldn't change any project data when disabling a project other than the disabled field.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3365","05/14/2018 19:22:09",1,"Lint Generate tasks is linting vendored projects ""See here: [https://evergreen.mongodb.com/task/mci_ubuntu1604_display_lint_patch_47d843b228453688b321f23ce50948dec658f936_5af9d04f2fbabe33902316b7_18_05_14_18_07_30]   [lint-vendor-github.com-mongodb-grip-send|https://evergreen.mongodb.com/task/mci_ubuntu1604_lint_vendor_github.com_mongodb_grip_send_patch_47d843b228453688b321f23ce50948dec658f936_5af9d04f2fbabe33902316b7_18_05_14_18_07_30] is unexpected""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3366","05/14/2018 21:08:07",1,"No longer able to view all logs unless you know the url ""You can't get to [https://logkeeper.mongodb.org/build/657a8889982a404882c60eb73acff101/all?raw=1] or [https://logkeeper.mongodb.org/build/657a8889982a404882c60eb73acff101/all?html=1] from lobster""","",0,0,1,0,0,0,0,0,0,0,1,0,0,1,0 +"EVG-3369","05/16/2018 14:36:47",1,"BB plugin not able to do searches ""After [https://github.com/evergreen-ci/evergreen/commit/825cbc94aee285a77e21900086a33671f26ff214,] the BB plugin reported that searching Jira failed.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3373","05/17/2018 15:56:50",1,"delegate all mux dependency on gimlet ""* impacts agent status server, * pprof * mostly need to use gimlet.GetVars rather than mux.Vars""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3379","05/18/2018 19:22:33",1,"imrpove CSRF. ""It should be implemented as a negorni middleware, and we should be able to attach to (some?) UI routes but not others. This is important for being able to combine/reduce our services and simplify our load balancing configuration. I think that we currently have it turned off. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3382","05/18/2018 20:29:36",1,"GitHub status API is updated for builds but not for patches ""e.g, https://evergreen.mongodb.com/build/mci_ubuntu1604_patch_6935cf29e9d5141e16a83924f886f6b46ad5d3f1_5aff23a0c9ec44191d68cb50_18_05_18_19_04_01""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3385","05/18/2018 21:53:26",1,"Restarting tasks in a Pull Request patch leads to a Github Status with no ""Details"" link for ""evergreen"" context ""https://github.com/10gen/mms/pull/14229 There was an individual task that failed on the first run (https://evergreen.mongodb.com/task/mms_int_INT_JAVA_BRS_36_patch_4c58337b9ba0f80de594910678a76c908015ae52_5aff0f59c9ec44191d660fbe_18_05_18_17_37_31/0) and passed when it was re-run, but it appears that the top-level """"evergreen"""" task hasn't had its state updated to match, and there's no """"details"""" link for me to look closer""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3386","05/18/2018 22:25:38",1,"Show tooltip of test full name on hover ""Test names can be very long. An example is [fuzzer test|https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_jstestfuzz_replication_initsync_0a4f7b1ebf173984883d6e018ae88350015dfeb3_18_05_16_19_19_11/0]. It's hard to see the full name of the failed test right now.""","",1,0,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3388","05/18/2018 23:23:09",1,"EC2 panic ""pool/helpers.go:67 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 cloud/ec2.go:685 hostinit/setup.go:77 hostinit/setup.go:233 hostinit/wrapper.go:49 units/provisioning_setup_host.go:78 pool/helpers.go:23 pool/helpers.go:32 pool/helpers.go:87 runtime/asm_amd64.s:2197""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3389","05/19/2018 23:18:13",1,"s3Copy.copy command should accept a permissions argument ""It currently always copies with public-read permissions, which is surprising, given the behavior of s3.put, which accepts a permissions argument. If possible, it should copy with the same permissions as the source file, if a permissions argument is not provided.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3390","05/19/2018 23:22:53",1,"Run fewer iterations on the race variants ""We have moved multithreading out of many packages and into amboy. We run enough tests that occasionally we exceed our GitHub API limits. We should only run the race detector on packages that use multithreading.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9002","05/21/2018 16:05:08",0,"Github Status API Sender sets wrong field for URLs ""Should set TargetURL, not URL""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3392","05/21/2018 16:35:35",1,"Structured logging for all events ""Most events in model/event are just strings that are logged, let's give them a common structure    ""","message.WrapError(err, message.Fields{ """"resource_type"""": event.ResourceType, """"message"""": """"error logging event"""", """"source"""": """"event-log-fail"""", } ",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3396","05/22/2018 16:17:27",2,"Group setup did not run before restart of patch build task in task group ""Executions 2, 3, and 4 of this task were system failures, because the directory was missing https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_ubuntu1604_64_compile_all_patch_6ab1592260c9b21d802aa65a11d268c0a97b11a7_5b042b95e3c3310342a53aab_18_05_22_14_46_14.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3402","05/23/2018 14:13:05",1,"race-service failure "" h2. [race-service failed on race-detector|https://evergreen.mongodb.com/task/mci_race_detector_race_service_503d660cd7293890a15999c2e8a898cdabeab151_18_05_22_21_41_11/0] Host: [ec2-54-152-99-180.compute-1.amazonaws.com|https://evergreen.mongodb.com/host/sir-an2i4pxj] Project: [mci|https://evergreen.mongodb.com/waterfall/mci] ~BF Ticket Generated by [~john.liu]~ ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3403","05/23/2018 14:16:40",2,"BB plugin fallback search is not returning expected results ""[https://evergreen.mongodb.com/task/mci_race_detector_race_agent_503d660cd7293890a15999c2e8a898cdabeab151_18_05_22_21_41_11]   should have found https://jira.mongodb.org/browse/EVG-3395 at least but did not""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3407","05/23/2018 19:23:06",1,"Investigate how it's possible for TaskTransitionToFailure alert records to have an empty task id ""It's possible that porting this to Event driven notifications fixed this weirdness, but we should still have a look. Grep codebase for """"EVG-3407"""" to find relevant area""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3408","05/23/2018 19:25:24",2,"Remove legacy notifications ""Grep codebase for EVG-3408 The _entire_ alerts package will be removable at this point.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3410","05/23/2018 20:15:43",2,"Restrict delivery method configuration ""Creating tickets in a JIRA project and EVG webhooks should be restricted to the project admin page only. Comments should remain available to users""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3412","05/23/2018 20:41:54",2,"Move mongodb-specific jira constants to configuration options ""in alerts/jira.go and ui_plugin_build_baron_tickets.go""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8353","05/23/2018 21:13:15",1,"Panic in slack sender when using slackMessage ""Slack sender is indexing into Attachments on error, but can't do this when message.Slack is used.   pool/rate_limiting_average.go:145 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:28 send/slack.go:95 logger/job_single.go:52 pool/helpers.go:23 pool/rate_limiting_average.go:181 pool/rate_limiting_average.go:166 runtime/asm_amd64.s:2197""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3417","05/24/2018 15:53:17",1,"""updating status for incomplete build"" error in logs ""from model/trigger/build.go""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3424","05/24/2018 20:36:19",8,"Support starting containers in scheduler ""# Add a maximum containers field to the distro document. # The scheduler, when inserting a host document for a distro that has maximum containers set, should set the containers fields in the host document. # After inserting host documents for containers, the scheduler should also insert host documents for parents.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3427","05/24/2018 20:40:02",1,"Refactor notification triggers to be an interface ""And remove circular dependency of trigger function <-> fetching subscriptions""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3429","05/25/2018 16:17:30",1,"Failing tests in created jira tickets show most (all?) tests ""{quote} @John Liu, there are a lot more """"Failing Tests"""" populated in https://jira.mongodb.org/browse/BF-9314 than I would have expected, considering only that 1 test failed https://mongodb.slack.com/archives/C0V896UV8/p1527261366000109 {quote}""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3430","05/25/2018 16:38:59",2,"Spawn host with data files did not have all data files ""It only included the source directory: {{source-mongodb-mongo-v4.0-e87f98}}. Note, I have since moved more data files there (I have a script that copies the pieces I need out of {{/data/mci}}).""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-3431","05/25/2018 18:04:07",1,"Github Status API messages not being posted for external patches ""This PR: [https://github.com/mongodb/mongoid/pull/4499] Created this build: [https://evergreen.mongodb.com/version/5b0733ffc9ec4405c1abefbb]   Despite the build succeeding, evergreen check status in PR still shows """"Pending - preparing to run tasks"""".""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8482","05/25/2018 18:57:00",1,"Panics when sending slack alerts ""pool/rate_limiting_average.go:145 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:28 send/slack.go:95 logger/job_single.go:52 pool/helpers.go:23 pool/rate_limiting_average.go:181 pool/rate_limiting_average.go:166 runtime/asm_amd64.s:2197""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3432","05/25/2018 20:52:58",1,"Unable to create BF tickets in EVG from plugin ""error filing ticket: error creating JIRA ticket: HTTP request returned unexpected status `400 `: \{""""errorMessages"""":[],""""errors"""":{""""customfield_15756"""":""""Field 'customfield_15756' cannot be set. It is not on the appropriate screen, or unknown.""""}}""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3433","05/29/2018 15:55:35",1,"Make s3.put output full s3 url ""In the s3.put post-task command, the output is of the form: Putting src/ec2_artifacts.tgz into path mongodb-mongo-master/enterprise-rhel-62-64-bit/2e6989e2744726f66289aca955cbc661539b6814/remote_ec2/remote_ec2_artifacts-mongodb_mongo_master_enterprise_rhel_62_64_bit_sharding_op_query_1_2e6989e2744726f66289aca955cbc661539b6814_18_05_28_04_25_48-0.tgz in s3 bucket mciuploads I've gotten feedback that it would be more useful to concatenate these together to be the actual bucket url, rather than having the user do that manually.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3435","05/29/2018 19:53:57",1,"Fix Lobster Lint & Build ""I've recently added lobster into Evergreen as it's own project, but we need to get the build and lint working. Don't do this manually, do configure your editor of choice to do it for you automatically.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3438","05/30/2018 16:44:05",2,"Create a top level Perf change point page ""Should be accessible like perf discovery. * The page will be the starting point for the performance build baron. * This ticket is to just create the web page. * Should be under the plugins drop down.""","",0,0,0,1,0,0,0,0,0,0,1,1,0,0,0 +"EVG-3440","05/30/2018 16:54:13",1,"Update List of Changepoints to use list with BF removed ""Build on EVG-3439 to display the updated list of changepoints from new endpoint. No other changes needed. ""","",1,0,0,0,0,0,0,0,0,0,1,1,0,0,0 +"EVG-3443","05/30/2018 20:40:05",1,"Allow github patch definitions to use tags ""Currently this is only implemented for patch aliases.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3445","05/30/2018 21:59:12",2,"s3Copy.copy and s3.put should log when they noop ""in a number of cases, s3.copy doesn't do anything and the desired behavior is to continue without erroring. However, the current behavior only logs this activities in the agent log and not the task log. We should clarify and provide a higher-level report of what the s3.copy command did in the task logs that includes things like: - number of files copied - file(s) skipped because they didn't exist - file(s) skipped because their target existed. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3561","05/31/2018 15:18:16",5,"Update the Build Baron plugin to allow user feedback ""This should include adding the buttons for collecting feedback on ticket suggestions.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3447","05/31/2018 18:50:31",1,"Use activated time in task latency stats ""Currently, the task latency stats are incorrect when tasks are activated by batch time or by users. We should take this into account. The current graphs have very long task latencies, but this is because tasks have been activated long after they are created.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3448","06/01/2018 15:47:05",1,"Log provision failures in host provision job ""so that failure volume can be easily graphed in splunk""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3449","06/01/2018 16:19:23",1,"Generate tasks retries on invalid payloads and doesn't output an error message ""Example here: [https://evergreen.mongodb.com/task/lobster_ubuntu1604_generate_tasks_patch_1d067be3f946b69fba9400902da52e972984b580_5b10e2b80305b914de9bad59_18_06_01_06_08_03/1|https://evergreen.mongodb.com/task/lobster_ubuntu1604_generate_tasks_patch_1d067be3f946b69fba9400902da52e972984b580_5b10e2b80305b914de9bad59_18_06_01_06_08_03/0] [Splunk error|https://mongodb.splunkcloud.com/en-US/app/search/search?q=search%20source%3D%22http%3Aevergreen%22%20lobster_ubuntu1604_generate_tasks_patch_1d067be3f946b69fba9400902da52e972984b580_5b10e2b80305b914de9bad59_18_06_01_06_08_03%7C%20spath%20error%20%7C%20search%20error%3D%22error%20reading%20project%20yaml%3A%20project%20errors%3A%20%0A%09lint-src-actions%3A%20nothing%20named%20%27lint-src-actions%27%0A%09lint-src-components-about%3A%20nothing%20named%20%27lint-src-components-about%27%0A%09lint-src-components-app%3A%20nothing%20named%20%27lint-src-components-app%27%0A%09lint-src-components-connectedfetch%3A%20nothing%20named%20%27lint-src-components-connectedfetch%27%0A%09lint-src-components-fetch%3A%20nothing%20named%20%27lint-src-components-fetch%27%0A%09lint-src-components-logview%3A%20nothing%20named%20%27lint-src-components-logview%27%0A%09lint-src-components-notfound%3A%20nothing%20named%20%27lint-src-components-notfound%27%0A%09lint-src-stores%3A%20nothing%20named%20%27lint-src-stores%27%0A%09lint-server%3A%20nothing%20named%20%27lint-server%27%0A%09lint-src%3A%20nothing%20named%20%27lint-src%27%0A%09lint-.%3A%20nothing%20named%20%27lint-.%27%22&display.page.search.mode=verbose&dispatch.sample_ratio=1&earliest=1527865792.000&latest=1527865792.001&sid=1527868105.13768078]""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3455","06/01/2018 22:03:32",2,"Successful patch issued a failure notification to a user. ""A user got a notification saying """"Evergreen patch 5b118ede2a60ed326b9a4e8f in 'mms' has failed!"""", but the patch succeeded. `db.event_log.find(\{r_id: """"5b118ede2a60ed326b9a4e8f""""})` shows that the corresponding patch and version failed and succeeded with in the span of a minute. There is likely a bug in the task lifecycle/event logging that is causing this.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3459","06/04/2018 15:47:33",1,"Investigate Slack sender errors ""We were hitting several panics in the slack grip sender (see MAKE-410). We need to look into why these errors were happening in the first place. Logging shows no errors since then, but we can probably look deeper into the notifications collection to confirm that.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3462","06/04/2018 19:42:04",2,"Docker provider panics on a log line if no mix/max port are set in distro ""Stack trace: """," pool/helpers.go:67 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 cloud/docker.go:113 units/provisioning_create_host.go:113 units/provisioning_create_host.go:82 pool/helpers.go:23 pool/helpers.go:32 pool/helpers.go:87 runtime/asm_amd64.s:2197 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3464","06/05/2018 14:45:27",1,"V1 API returning empty task set unexpectedly ""Given this task page: https://evergreen.mongodb.com/task/mongodb_mongo_master_debian92_concurrency_replication_causal_consistency_27b080da5ab09b324514a62ab38a3e6463e0d1c1_18_06_04_21_57_34/0 I'm hitting this end point to collect 'recent failure date': https://evergreen.mongodb.com/rest/v1/tasks/concurrency_replication_causal_consistency/history?project_id=mongodb-mongo-master But that endpoint is returning the Tasks key as null. The task and project_id values seem to be correct. Any idea what's going on? Note that whatever the problem is here (might totally be my fault!), we are under-scoring test failures because we're seeing all failures as """"failing zero of zero recent executions"""".""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-3470","06/05/2018 22:08:41",2,"Baseline comparison disappears when assign thread level ""On a task page, when assigning a thread level after clicking """"All"""" the comparison disappears. There is no way to do choose a comparison for assigned thread levels, only for """"All or """"Max"""".    ""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3542","06/06/2018 22:50:31",2,"Evergreen is attempting to copy the binary in multiple threads simultaneously ""When spawning via https://evergreen.mongodb.com/spawn, the hosts go through a provisioning stage and then disappear.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3483","06/07/2018 17:02:58",1,"When creating new SSH public key in spawn hosts, should not let you ""save the key"" without entering a name ""When spawning a spawn host if you select """"new key..."""" enter your key then check """"save key"""" you can then hit spawn without entering a name. It should instead force you to enter a name if you have checked save key""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3485","06/07/2018 18:26:19",1,"Assess gitRef in Lobster ""gitRef is in the lobster codebase in many places, but it seems like this path is never git, so none of those code paths are being hit. We should assess what this was for, and either get it working, or remove it.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0 +"EVG-3487","06/07/2018 21:41:56",2,"It's not possible to patch a project that doesn't have a config yaml committed to its repo ""Even if the patch adds the yaml""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3488","06/07/2018 23:04:31",1,"Admin restart tasks should be able to restart setup-failed tasks ""Currently there are checkboxes only for red and purple tasks.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3493","06/08/2018 18:41:25",2,"Add a way to delete all existing subscriptions on notifications page ""Also, for deleting individual notifications, it seems like we should display more than just the selector type, since the user can't determine what task/build/version it refers to without clicking.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3494","06/08/2018 18:49:05",1,"Setting priority on a display task doesn't set priority on its execution tasks ""Example: [https://evergreen.mongodb.com/task/mci_ubuntu1604_display_lint_patch_09b809283c45bd044d42451d873afa90e83807c2_5b1abfdd0305b93cbb59168c_18_06_08_17_41_50] Display task was set to priority 55, but execution tasks had no priority in UI and were deep in the queues""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3500","06/09/2018 16:46:27",1,"Remove existing gotest output before running test in Evergreen self-tests ""Otherwise, subsequent tasks in a task group may appear to fail due to an earlier failure. See https://evergreen.mongodb.com/task/mci_ubuntu1604_display_lint_patch_78fe3206570729465d3df6f87209fe93d0dc41d1_5b1bdee42a60ed67bab381f6_18_06_09_14_06_29.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3501","06/11/2018 15:32:06",2,"Ensure that we handle changing parent IDs in child documents ""A parent intent document may have a different ID than the ultimate host document. We should ensure that children can keep track of their parents across this change.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3502","06/11/2018 15:49:59",1,"Log mark end details ""Each minute we log an aggregate of task end statuses. We should also log MarkEnd, so that we can analyze this data by project or task.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3504","06/11/2018 17:00:18",1,"BB plugin search still doesn't escape things correctly ""Error searching jira for ticket: HTTP request returned unexpected status `400 `, (project in (BF, WT, SERVER, BFG)) and ( text~""""capped\:CheckReplOplogs"""" or text~""""indexv\:CheckReplOplogs"""" ) order by updatedDate desc""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3505","06/11/2018 20:06:41",2,"Case-insensitive Lobster search is actually case sensitive ""In master load [http://localhost:3000/lobster/build/4191390ec6c7ee9bdea4e45f9cc94d31/test/5af32dbbf84ae86d1e01e964?bookmarks=0%2C1129] Search """"integration_Test"""". This should match, because it's case insensitive by default, but has no matches. The hilighter works as expected. Toggling the case sensitive toggle under Hide Details makes it work, until the search is rerun.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3510","06/13/2018 21:41:32",2,"Remove Deprecated React Methods from Lobster ""componentWillReceiveProps from Fetch component""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3512","06/14/2018 14:47:03",2,"Individual names in ""Files"" section for display tasks. ""See EVG-3266""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3524","06/14/2018 20:47:32",2,"Display pool mapping info in distro UI ""Users may wish to see, in the distro UI, information from the pool mapping.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3525","06/14/2018 20:51:54",2,"Restrict parent hosts from spawning, running agents ""If a distro is a container pool, it should not be useable for tasks or spawnable by users. One approach is to add a checkbox to the distro UI which sets a field which prevents the distro from being spawned in tasks. Then we add validation that only those distros may be saved in the pool mapping in the admin collection. In addition, we should not start agents on these hosts.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5532","06/18/2018 18:05:46",1,"add failure timestamp to BFG template ""I frequently find it helpful to know the push time for a commit that triggered a build with a failure, in order to correlate it to a timeline in my head of when things were pushed and when failures occurred. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3536","06/18/2018 18:45:50",1,"Restarting failed tasks appears to hang ""When restarting a small number of failed tasks (31) in a version, this hangs for almost a minute.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3538","06/18/2018 18:48:56",2,"ZSeries and ARM tests are failing immediately ""Here's a task: [https://evergreen.mongodb.com/task/mci_ubuntu1604_arm64_xc_subprocess_2c36b9184a7ca6556eb1a77655cd0336ef08246e_18_06_18_16_03_54/0#/log/T] And its log: https://evergreen.mongodb.com/task_log_raw/mci_ubuntu1604_arm64_xc_subprocess_2c36b9184a7ca6556eb1a77655cd0336ef08246e_18_06_18_16_03_54/0?type=T""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3545","06/19/2018 20:15:34",2,"Validate slack usernames at settings save ""Similarly to how we validate github usernames, let's validate slack user names.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3636","06/19/2018 22:09:55",2,"Discrepancies between tasks status on a buildvariant view and task view. ""I was looking at the rhel71-ppc queue and found that tasks that are scheduled and have # in the queue show up as unscheduled on the buildvariant view. For example, everything but green says unscheduled - https://evergreen.mongodb.com/build/mongodb_mongo_master_enterprise_rhel_71_ppc64le_6d8b7f90fe0ae5251bfab98279d22ef705fae603_18_05_13_18_49_43 while this task https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_71_ppc64le_concurrency_replication_6d8b7f90fe0ae5251bfab98279d22ef705fae603_18_05_13_18_49_43 is scheduled This build is opposite - https://evergreen.mongodb.com/build/mongodb_mongo_master_enterprise_rhel_71_ppc64le_d12afa4fdda9c6b113e7be3b4d67d757b07b50b5_18_05_14_13_46_06 Push task for it says scheduled on that view but the task view says not scheduled https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_71_ppc64le_push_d12afa4fdda9c6b113e7be3b4d67d757b07b50b5_18_05_14_13_46_06 And some unscheduled tasks on https://evergreen.mongodb.com/build/mongodb_mongo_master_enterprise_rhel_71_ppc64le_9482d5a32e100ce7f939ea5789b1862fc98e9924_18_05_14_22_56_00 are actually successfully completed https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_71_ppc64le_gle_auth_basics_passthrough_9482d5a32e100ce7f939ea5789b1862fc98e9924_18_05_14_22_56_00 I see the same situation on other """"large queue"""" distros like Enterprise Ubuntu 16.04 s390x and Enterprise SLES 12 s390x One example is here - https://evergreen.mongodb.com/build/mongodb_mongo_master_enterprise_suse12_s390x_9482d5a32e100ce7f939ea5789b1862fc98e9924_18_05_14_22_56_00 and another here - https://evergreen.mongodb.com/build/mongodb_mongo_master_enterprise_ubuntu1604_s390x_cf339b8a8d8708e8b28747fe0cafee7cc79fe9a6_18_05_16_00_03_26 (compile task is scheduled but shows up as not scheduled on that view) If it's a UI problem, it's annoying but less critical than if this is a bug with the way old tasks are being unscheduled. I see tasks about a month old still in the queue while we should we unscheduling ones older than 1 (2?) week.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3549","06/19/2018 23:45:14",2,"Speed up task_queue page ""The task_queue page takes about 40 seconds to load.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3550","06/20/2018 21:35:45",2,"Add validation in distro model to ensure that container pools specify a valid distro ""Ensure that for each distro with a ContainerPool key, that ContainerPool specifies a valid parent distro (which cannot have its own ContainerPool key).""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3551","06/21/2018 14:26:49",1,"task history page for compiles not working ""https://evergreen.mongodb.com/task_history/mongodb-mongo-master/compile is returning blank?""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3555","06/21/2018 15:39:38",1,"Panic in scheduler ""Stack trace at revision c30ae459ada04bddf27a878c80354386249b9de2 """," pool/helpers.go:67 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 scheduler/wrapper.go:38 units/scheduler.go:76 pool/helpers.go:23 pool/helpers.go:32 pool/helpers.go:87 runtime/asm_amd64.s:2197 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3562","06/25/2018 14:35:40",2,"No notifications for 100% consistent OS X openssl unittests failures ""https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_osx_1010_openssl_unittests_d520be0814492c262515cf0a5d62a127ace70dce_18_06_22_16_32_29 https://jira.mongodb.org/issues/?filter=24306&jql=%22Failing%20Buildvariants%22%20%3D%20enterprise-osx-1010-openssl%20and%20%22Failing%20Tasks%22%20%3D%20%22unittests!%22%20""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3566","06/25/2018 20:04:57",2,"Updating 'Default VPC Subnet Id' in distros settings page has no effect ""The {{Default VPC Subnet Id}} setting was originally set to subnet B in the VPC. Trying to update this to another subnet has no effect. Requests continue to be launched in Subnet B.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3587","06/27/2018 20:18:26",1,"Change the current signal processing page to display multiple lists ""The lists / views we wish to display are: * *warnings*: system failures, post run checks and threshold failures from evergreen (see EVG-3586 for more detail). * *unprocessed change points*: this is the current list (done in EVG-3440 and EVG-3439). * *processed change points*: the contents of the *perf.processed_change_points* collection.""","",0,1,0,0,0,0,0,0,0,0,1,1,0,0,0 +"EVG-3588","06/27/2018 20:44:08",1,"Running migrations should not run other amboy jobs ""john.liu@evergreenapp-1:/srv/evergreen/current/clients/linux_amd64$ ./evergreen service deploy anser spawnhost-expiration-preference --conf /etc/mci_settings.yml [evergreen] 2018/06/27 19:41:36 [p=info]: creating new remote job queue with 4 workers [evergreen] 2018/06/27 19:41:36 [p=info]: job server running [evergreen] 2018/06/27 19:41:36 [p=info]: job server running [evergreen] 2018/06/27 19:41:36 [p=info]: starting queue job server for remote queue [evergreen] 2018/06/27 19:41:36 [p=error]: [api_name='DescribeSpotPriceHistory' args='{   AvailabilityZone: """"us-east-1b"""",   EndTime: 2018-06-27 20:41:35.898 +0000 UTC,   InstanceTypes: [""""c3.4xlarge""""],   ProductDescriptions: [""""Windows""""],   StartTime: 2018-06-27 13:07:14 +0000 UTC }' client='*cloud.awsClientImpl' message='AWS API call']: RequestCanceled: request context canceled caused by: context canceled""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3589","06/27/2018 20:54:05",8,"Update the display and grouping of items in the signal processing lists ""Each list should only contain the items for the project being viewed (that is 'https://evergreen.mongodb.com/signal-processing/sys-perf' should only display sys-perf master, 'https://evergreen.mongodb.com/signal-processing/sys-perf-4.0' should display change points from sys-perf-4.0). Since the project is implicit depending on the plugin page, it should no longer be necessary to display it. (EVG-3737) The lists contain warnings, or change points (processed or unprocessed EVG-5147) grouped by revision. Each line item in this list contains further component change points or warnings. Line items are displayed: * revision in the first (left most) column. * hazard value in the second column. * create time in the third column. * one per revision per line item * sorted by max hazard value and create time. A grouped line item is a list of component items: * sort by internal hazard value by default. * it should be possible to view the component items as a sub-list . * it should be possible to sort by internal properties (variant/ task / test in this sub list)""","",0,1,0,0,0,0,0,0,0,0,0,1,0,0,0 +"EVG-3593","06/28/2018 14:58:53",1,"rest v2 routes that require authentication 404 with correct api token ""https://evergreen.mongodb.com/api/rest/v2/builds/mongodb_mongo_master_linux_64_duroff_mmapv1_9482d5a32e100ce7f939ea5789b1862fc98e9924_18_05_14_22_56_00/tasks""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3594","06/28/2018 16:26:49",1,"Degraded mode should not mark events as processed. ""This risks swallowing BFGs""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3597","06/28/2018 19:17:07",1,"move queries to the models package from service ""{{getVersionHistory}} and {{getHostData}} in the service package should really be in the models package (and arguably the entire {{models.go}} should be elsewhere, but maybe it makes sense to hold off until we move things to a restv2 style situation.)""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3600","06/28/2018 21:09:42",2,"Dynamic tasks must support depends_on for static ones ""Repro: This [dynamic task|https://evergreen.mongodb.com/task/mms_e2e_local_new_e2e_Local_ATM_Import_Automation_patch_14b2d0c90a023dbd4501b62e1d9b1e0861d548ca_5b353ea9e3c3315d3eca92d1_18_06_28_20_01_46] was generated from [this patch|https://evergreen.mongodb.com/version/5b353ea9e3c3315d3eca92d1]. You can see that it doesn't activate the requisite static tasks IVY_DEPENDENCIES and NPM_DEPENDENCIES (and the UI doesn't render the dependencies correctly in the task page) ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8463","06/29/2018 14:31:08",2,"jobs stay locked after they stop running ""either because of early returns, db errors in unlocking, or panics the jobs stay locked (and then run later after a restart)""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3604","06/29/2018 17:27:31",1,"keys CLI operations do not work "" After removing file validation: """," $ evergreen keys list command line configuration path is not specified NAME: evergreen keys list - list all public keys for the current user USAGE: evergreen keys list [arguments...] command line configuration path is not specified $ ./clients/darwin_amd64/evergreen keys list Public keys stored in Evergreen: Name: '%!s(model.APIString=0xc4201b6e80)', Key: '%!s(model.APIString=0xc4201b6e90)' Name: '%!s(model.APIString=0xc4201b6ea0)', Key: '%!s(model.APIString=0xc4201b6eb0)' ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3605","06/29/2018 19:38:26",2,"Lobster not scrolling horizontally when searching ""[https://logkeeper.mongodb.org/lobster/build/5fd863fe3a97fef224b4ee0f4efd2d14/test/5a300a7cbe07c47ae7144c94#bookmarks=0%2C2295] Search for """"connection attempt""""""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3606","06/30/2018 00:13:46",2,"Tasks in group ran in wrong order ""This task group should run the tasks in order: https://github.com/mongodb/mongo/blob/821f9f69916da51f97e001b1c45dff6e49533f81/etc/evergreen.yml#L6891-L6896 However, here it didn't happen that way: https://evergreen.mongodb.com/build/mongodb_mongo_master_embedded_sdk_iphonesimulator_10.2_14730a1d7515716a420603c2bfd6c48874791242_18_06_28_23_23_53 The embedded_sdk_s3_put task did not run immediately after embedded_sdk_install_dev as required.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3607","06/30/2018 01:26:07",2,"Single machine task groups should admit/imply explicit dependencies ""The mobile project needs to be able to run several steps on the same machine in sequence. Additionally, we need to use task group for this, so that other builders can depend on the results of particular tasks within the group. However, if one task fails, the subsequent tasks still execute, which is not what we want. Additionally, in the GUI, selecting one task to execute for a patch doesn't auto-select any of the others, even though they are dependencies. We need a way to declare dependencies.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3608","07/01/2018 22:07:05",2,"Improve Waterfall performance ""If we change the waterfall to download the waterfall data (window.serverData) asynchronously, instead of embedding it into the page via templates, we can cut the waterfall load/render time in half.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-8417","07/02/2018 20:34:54",1,"Gimlet's panic handler should write errors using rest.APIError ""The front end expects errors to have the structure defined by the the rest.APIError struct, but when a restv2 route panics, the """"error"""" field is unset""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3611","07/02/2018 22:37:29",2,"Pre-populate variables, including user data for spawn host UI ""Would it be practical to populate project expansions for these as well? We should probably do this if we can, so users can pass secrets.""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3612","07/03/2018 16:07:03",1,"Always send evergreen build results from a commit to the committer ""Evergreen, for every build done upon commit, should send the results to the committer. There have been many failures lately due to mutually affecting commits being committed in too close a timeframe for either pre-commit builds to include the other; or just simply poor test coverage pre-commit because the committer didn't expect the changes to be so widely affecting. More immediate feedback would be very helpful because it can take a while for the resulting BFGs to be sorted out, triaged to the correct team, the severity determined, assigned and inspected. Especially when the system experiences a lot of failures. We have more developers these days, so the probability of conflicting changes is much higher than it used to be. A more immediate turnaround by notifying the committer ASAP will keep the build greener for everyone -- and give less work to Build Barons, who, once they notice the severity, usually have to manually ping offending committers or revert simple mistakes themselves.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3613","07/03/2018 18:14:29",2,"Investigate double notifications ""I received two notifications for 5b3bad480305b9400b342cc5, the first one failed, the second one succeeded. All tasks in this patch succeeded.   This is possibly a dupe of EVG-3455""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3616","07/03/2018 23:14:10",2,"BFGs created for display tasks do not include failed tests information ""The BFG tickets created when a display task fails do not include the section containing the test names and links to the logs and history.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8483","07/04/2018 09:14:03",2,"AbortableRunner.Abort doesn't call Queue.Complete() ""First of all, thanks a lot for an awesome library. It is strange, but Amboy is the only local queue for Go that has all needed features.   Problem — if you call `AbortableRunner.Abort` and then query queue stat, stat is not correct. In my case job is still running. As far I see, AbortableRunner doesn't call `Queue.Complete()`   And workaround not easy because implementation of `Queue.Complete()` in case of `priorityLocalQueue` is not reliable — counter is simply decrementing, so, anyone can easily break stats if call  `Queue.Complete` several times. So, in my code I wrap it to check is `buildJob.Status().Completed`.""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3617","07/05/2018 13:28:09",1,"Task page for display tasks always show task status and link to latest execution ""They should instead show the task status and link to the execution selected for the display task. https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_windows_64_2k8_wtdevelop_display_replica_sets_auth_b76457d9aa0188e1d2369851506b9d4d927024cb_18_07_03_02_07_37/0""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3620","07/06/2018 17:53:17",2,"remove rest.APIError in favor of gimlet.ErrorResponse ""this should, I think, involve a more serious refactor of how errors get passed to the API code. It's currently the case that the rest/data package and some areas of the model (generated tasks) return API errors which I think is wrong (and we wouldn't want to have the models package depend on gimlet.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3621","07/06/2018 17:54:13",1,"Set content-length header in requests to crowd ""Scarecrowd's WSGI can't handle chunked encoding, which go sets by default if ContentLength isn't set.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3623","07/06/2018 19:52:46",2,"Estimated time to start exposed in API ""I would like to have some way of judging how much progress a task has made, and when it is likely to start executing, using the API. Presently there is a field called position in queue that is exposed in evergreen UI. This field can be tracked on a per task basis to see if the task is making progress toward being built, and to roughly estimate when it will start building, assuming a steady load on the system. The API does not expose this field and doesn't provide any data as far as I can tell to perform similar estimation.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3630","07/06/2018 23:55:33",1,"Wrong raw link on lobster ""The raw link button points to the all log messages of the job, which is useful in some cases, but a user would expect the raw link to the specific test. Here's an example. https://logkeeper.mongodb.org/lobster/build/888d60ec4c67a6e88a62271495561bc6/test/5b365c4af84ae86783002eba#bookmarks=0%2C3996""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3631","07/08/2018 17:19:51",1,"add deploy management configuration to CLI config file ""I want to be able to add direct connection operations to EVG app servers in the evergreen CLI, and to do this we would want to have some configuration in the cli config file that would let us store this information. perhaps eventually we can make the evergreen CLI itself manage the build/deployment cycle for the evergreen application, but for now a section in the CLI config file to store the locations of the app servers (to start) will make it possible to add administrative options to manage the service from the cli. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8626","07/08/2018 18:54:48",1,"add abortable pool features to rate limiting pool ""to support terminating notification jobs (for example). ""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3632","07/09/2018 14:17:30",1,"log reporting queries to splunk ""use amboy's reporting package to log more data in the amboystatus jobs.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3633","07/09/2018 14:22:21",1,"switch all existing production amboy pools to use the abortable pool. ""we might want to wait until the notification pools can be backed by an abortable pool, because they use a rate limiting pool (MAKE-427), or we can move the other two worker pools to be abortable first. The work to expose the management interface is separate. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3634","07/09/2018 14:23:41",2,"reorganize app server administration port ""expose the abortable pool management interface (depends on EVG-3633), add a prefix for the pprof endpoints, ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3635","07/09/2018 15:12:22",2,"Static hosts removed from a distro config are still in the pool ""We've removed 2 servers from ubuntu1604-arm64-large on 5/21: ubuntu1604-arm64-1.linaro.build.10gen.cc ubuntu1604-arm64-8.linaro.build.10gen.cc The server were in quarantined status prior to that and remained in the pool in the same state even after we removed them. Today, 7/09, I set them to the running state to let evergreen do its thing and properly decommission them, but it started to run tasks on them instead. Things that need to be fixed: * Evergreen should decommission hosts that are removed from the distro config when there are no tasks running on them, even if they are in a quarantined state. * Evergreen should not run tasks on hosts that are not part of any distros * If a host is removed from the distro config and set to the running state, evergreen should decommission it.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3640","07/09/2018 20:37:42",2,"Retrieve project via version id via API ""Travis PR statuses link to Evergreen version URLs. As far as I can tell there's no way to figure out, given a version, what project this version is in.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3641","07/09/2018 21:53:12",2,"Access task results by display task Id in the API ""As an Evergreen user, I'd like to access task metadata and test results of a display task by its id. Currently the API only gives access to execution tasks.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3646","07/10/2018 19:25:16",1,"Ability to subscribe to failures of a specific test ""CC [~spencer]""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3649","07/10/2018 19:35:59",2,"Build break notifications should notify when the first task regresses, not when version is done ""Currently build break notifications will almost never get sent because versions almost never completely finish""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3651","07/11/2018 20:20:43",2,"Must HTML Entities encode some characters in JIRA markup in BF/BFG tickets ""[~matthew.saltz] pointed out that some BF and BFG tickets have broken links/JIRA markup. For example: https://jira.mongodb.org/browse/BF-9901?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel I believe the cause is that an ! is included in the """"text"""" portion of the link. Examples: Broken JIRA markup: [unittests! failed on * Enterprise Windows 2008R2 compile_all|https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_windows_64_2k8_compile_all_display_unittests!_a7f2cf99a1ab6548eff63d3eddafab1134fe6b84_18_07_10_17_50_03/0] Working JIRA markup: [unittests (no exclamation) failed on * Enterprise Windows 2008R2 compile_all|https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_windows_64_2k8_compile_all_display_unittests!_a7f2cf99a1ab6548eff63d3eddafab1134fe6b84_18_07_10_17_50_03/0] ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3654","07/12/2018 18:01:03",2,"Project admins should be able to opt in all committers to build break notifications ""By default, turning on build break notifications should only notify users who have opted into them. However, project admins should have the option to opt in all users to build break notifications for that project. This is to support differing use cases for server (users can opt in) and cloud (everyone should get build break notifications, and it shouldn't require individual user action to get them).""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3656","07/12/2018 19:56:19",2,"Cannot create JIRA tickets because of unset Issue type ""(this only affects event driven notifications, not the existing BFG logic)""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3663","07/13/2018 16:45:49",2,"Some hosts stuck indefinitely being prepped for agents ""This occurred after the outage yesterday where AWS was terminating spot hosts Example host: sir-4zei5ghk. These hosts were terminated in AWS, but Evergreen continued in a loop attempting to prep them. From the host page they appeared to be running a task, but the task they appeared to be running, from the task page, was purple. I decommissioned all of the hosts (~ 80 of them) in the UI and then terminated them in the DB.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3664","07/13/2018 16:46:39",1,"scheduler should insert host intent documents in a bulk operation ""currently there's a forloop around insert one. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3674","07/19/2018 16:39:02",2,"Dynamic tasks must allow cross-variant task addition ""When I kicked of [this patch|https://evergreen.mongodb.com/version/5b4f9902e3c3316b5de38ee8] via {{evergreen patch -p mms -v e2e_local -t Setup_E2E_Local -y -f}} It should have added a new task """"new_e2e_Local_ATM_Import_Automation"""" to a separate static variant {{e2e_local_win}} yet it did not.  I also tried including the {{e2e_local_win}} variant in the patch but to no avail.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3680","07/20/2018 14:42:17",1,"S3 integration tests should generate unique names ""The S3 integration test should generate a unique name each time it is run. As it is currently written, it's possible for a previous successful run of the test to cause a subsequent test to succeed, even though it should have failed: https://github.com/evergreen-ci/evergreen/blob/414a2b6371ac0712153316792c13115e433d1a54/thirdparty/s3_test.go#L14-L15.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3682","07/22/2018 07:25:54",2,"Evergreen is generating BFG tickets for fail->fail transitions when only pass->fail transitions configured ""I realized that consecutive commits had BFG tickets created for them while going through the BFG tickets linked to BF-9759. I wouldn't ordinarily expect stepback to lead to the generation of BFG tickets but maybe there's some weird interaction with EVG-3645 going on? * BFG-81063 ** https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1604_arm64_mobile_jstestfuzz_211b5c3006f89e8235dd6d795d0c64defc77030d_18_06_08_22_18_23 * BFG-81067 ** https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1604_arm64_mobile_jstestfuzz_8fae595c44b14aa61951ba413e293449c2b49866_18_06_08_21_11_33 * BFG-81072 ** https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1604_arm64_mobile_jstestfuzz_72784578190b44abe381e3a181adc309a1bd4cb1_18_06_08_20_52_08 * BFG-81074 ** https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1604_arm64_mobile_jstestfuzz_c68e6339eac6228e97f7eb3af7bcac506ce3d9e3_18_06_08_20_49_16 * BFG-81078 ** https://evergreen.mongodb.com/task/mongodb_mongo_master_ubuntu1604_arm64_mobile_jstestfuzz_e88605e272251362d16c416791434d56acfadfa9_18_06_08_20_45_51""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3686","07/23/2018 19:33:58",1,"Stranded tasks query doesn't work ""   duration_secs: 0.013528195    error: problem finding terminated hosts: unknown operator: $and    job: task-stranded-cleanup.2018-07-23.18-18-00    job_type: task-stranded-cleanup    metadata: { [[+]|https://mongodb.splunkcloud.com/en-US/app/search/search?earliest=-60m%40m&latest=now&q=search%20index%3Devergreen%20metadata.level%20%3E%3D%2070%20AND%20NOT%20job_type%3D%22agent-deploy%22&display.page.search.mode=fast&dispatch.sample_ratio=1&display.general.type=events&sid=1532370174.2062849]    }    queue_type: *queue.remoteUnordered""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3689","07/23/2018 20:51:02",1,"Clearly document how to use Lobster to serve local log files ""Improve the documentation in the Lobster README about how to serve local log files using the Lobster server.""","",0,0,0,1,0,0,0,0,0,0,0,0,0,1,0 +"EVG-3691","07/23/2018 21:03:31",1,"Tasks by project route doesn't pass task ID correctly ""tasksByProjectPaginator""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3693","07/23/2018 22:37:49",1,"Cannot delete subscriptions from UI ""I get a """"Subscription not found"""" error. This only applies to subs which have bson.ObjectIds as their type.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3697","07/24/2018 17:50:50",2,"Spawn host expiration message received too early ""I was sent the following: at 7/24/18 @ 08:12 eastern time, which is much earlier than expected."""," Your rhel70 host with id i-09891d4b3acce8ce2 will be terminated at 2018-07-25 00:10:25.969 +0000 UTC. Visit https://evergreen.mongodb.com/ui/spawn to extend its lifetime. ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3712","07/24/2018 22:00:50",1,"v2 tasks subresource of build has null artifacts ""Example: https://evergreen.mongodb.com/rest/v2/builds/mongodb_mongo_master_enterprise_rhel_70_64_bit_9d87df4b3ba2e611870893b8a83529a9311719d6_18_07_23_19_29_28/tasks Array index: 7""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3714","07/25/2018 14:00:30",1,"Panic if project has no functions but generator does ""Stack: """," gimlet/middleware_grip.go:184 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/hashmap.go:487 model/generate.go:230 model/generate.go:134 data/generate.go:28 route/generate_routes.go:73 route/handler.go:86 http/server.go:1942 mux/mux.go:114 negroni/negroni.go:46 negroni/negroni.go:29 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:34 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:34 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth.go:37 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth_user.go:142 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_grip.go:192 negroni/negroni.go:38 negroni/negroni.go:86 http/server.go:2568 http/server.go:1825 runtime/asm_amd64.s:2197 ",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3715","07/25/2018 14:20:05",1,"Exclude gosec ""This linter was renamed from gas to gosec, so we need to change the exclusion in the makefile.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3716","07/25/2018 16:29:45",1,"Log provisioning retries at info ""These currently are logged at error because we log them in the job. However, they are expected, so we should log them at a lower level.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8465","07/27/2018 19:43:25",2,"Amboy can't update stats/status document """"""problem saving stat: problem updating status document for event-send:5b5b64e9c9ec445913aa8eaa-regression-jira-issue-BFG-Build Failure: not found"""" not found problem updating status document for event-send:5b5b64e62fbabe103eb18f4b-regression-jira-issue-BFG-Build Failure github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*mongoDB).SaveStatus /data/mci/e0a0a6d6230b1a3fa7afe162eb264533/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/driver_mongodb.go:315 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*lockManager).Lock /data/mci/e0a0a6d6230b1a3fa7afe162eb264533/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/driver_locker.go:224 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*mongoDB).Lock :25 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*remoteUnordered).Next /data/mci/e0a0a6d6230b1a3fa7afe162eb264533/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/remote.go:84 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool.startWorkerServer.func1 /data/mci/e0a0a6d6230b1a3fa7afe162eb264533/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool/helpers.go:123 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 problem saving stat github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*lockManager).Lock /data/mci/e0a0a6d6230b1a3fa7afe162eb264533/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/driver_locker.go:225 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*mongoDB).Lock :25 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*remoteUnordered).Next /data/mci/e0a0a6d6230b1a3fa7afe162eb264533/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/remote.go:84 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool.startWorkerServer.func1 /data/mci/e0a0a6d6230b1a3fa7afe162eb264533/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool/helpers.go:123 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3732","07/27/2018 19:56:07",1,"JIRA Ticket description length limit exceeded ""Failed to send alert: error creating JIRA ticket: HTTP request returned unexpected status `400 `: {""""errorMessages"""":[],""""errors"""":{""""description"""":""""The entered text is too long. It exceeds the allowed limit of 32,767 characters.""""}} extended: HTTP request returned unexpected status `400 `: {""""errorMessages"""":[],""""errors"""":{""""description"""":""""The entered text is too long. It exceeds the allowed limit of 32,767 characters.""""}}""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8351","07/27/2018 20:04:35",2,"buffered session inserter fails to insert some documents ""We occasionally saw errors that notifications couldn't be found by ID. EVG-3614 stopped using the bulk inserter, and we no longer see these errors.""","",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3737","07/30/2018 14:45:47",1,"Implicit project ""Project id is implicit. Query should be adjusted. The column should be removed.""","",0,0,0,0,0,0,0,0,1,0,0,1,0,0,0 +"EVG-3738","07/30/2018 15:01:29",1,"logkeeper app should have reasonable socket timeout ""90s to match evergreen?""","",1,0,0,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-3747","07/30/2018 19:41:09",2,"console errors on task page for perfplugin ""this causes graphs to not render, we think. e.g. https://evergreen.mongodb.com/task/mongo_go_driver_perf_perf_0a84d587c4836909f1d89c43665e96ecb14fad46_18_07_27_18_33_15""","",1,0,0,0,0,0,0,0,0,0,0,1,0,0,0 +"EVG-8535","07/30/2018 21:06:15",1,"curator logging agent should be able to watch a file ""if the current modes are """"pipe"""" and """"exec"""" this should be """"tail""""""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3749","07/30/2018 22:09:12",2,"patch command line args not overriding default ""I'm runningbut regardless, all the other buildvariants (and their tasks) are scheduled. However, on the buildvariant I'm interested in - {{benchmark}} - only the task I want scheduld - {{benchmark-tpch-micro}} is scheduled. See version at https://evergreen.mongodb.com/version/5b5f7d9be3c331561bf724cf for the result of the invocation above. My {{~/.evergreen.yml}} file looks like:"""," evergreen patch -p sqlproxy -y -d """"1709"""" -v benchmark -t benchmark-tpch-micro api_server_host: http://evergreen-api.mongodb.com:8080/api ui_server_host: https://evergreen.mongodb.com api_key: XXX user: adinoyi.omuya projects: - name: sqlproxy default: true alias: mvp variants: - code-quality,config-tests__os_full_matrix~windows,full_matrix__os_full_matrix~osx_mongodb_version~latest_mongodb_topology~standalone,full_matrix__os_full_matrix~ubuntu1404-64_mongodb_version~latest_mongodb_topology~standalone,full_matrix__os_full_matrix~windows_mongodb_version~latest_mongodb_topology~standalone,race-detector,full_matrix__os_full_matrix~osx_mongodb_version~3.2_mongodb_topology~sharded-cluster,full_matrix__os_full_matrix~ubuntu1404-64_mongodb_version~3.4_mongodb_topology~replica-set tasks: - all - name: mongosql-auth-c default: true variants: - all tasks: - all - name: sqlproxy-2.4 default: true variants: - code-quality,config-tests__os_full_matrix~windows,full_matrix__os_full_matrix~osx_mongodb_version~latest_mongodb_topology~standalone,full_matrix__os_full_matrix~ubuntu1404-64_mongodb_version~latest_mongodb_topology~standalone,full_matrix__os_full_matrix~windows_mongodb_version~latest_mongodb_topology~standalone,race-detector,full_matrix__os_full_matrix~osx_mongodb_version~3.2_mongodb_topology~sharded-cluster,full_matrix__os_full_matrix~ubuntu1404-64_mongodb_version~3.4_mongodb_topology~replica-set tasks: - all - name: mongosql-auth-c default: true variants: - all tasks: - all",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3753","07/31/2018 21:13:10",2,"Schedule task dependencies for scheduled task, even if dependency doesn't satisfy batch time ""We have a high batch time on our project (24 hours). Fairly often recently, most of the tasks will get on one period, but the depended on task (compile) has run more recently than 24 hours, and doesn't get scheduled. This leads to none of the other tasks running. Instead, the compile task (dependency) should be scheduled whenever something that is dependent on it is scheduled, regardless of the compile tasks' own batch time. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8366","08/01/2018 14:27:59",2,"Amboy keeps retrying some errored jobs """"","   error: problem unlocking 'host-termination-job.sir-h2e84zkg.2018-07-31.20-48-00': problem updating status document for host-termination-job.sir-h2e84zkg.2018-07-31.20-48-00: not found    extended: not found problem updating status document for host-termination-job.sir-h2e84zkg.2018-07-31.20-48-00 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*mongoDB).SaveStatus /data/mci/b1fb0b12d0cfc1873c727e023990ee55/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/driver_mongodb.go:315 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*lockManager).Unlock /data/mci/b1fb0b12d0cfc1873c727e023990ee55/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/driver_locker.go:249 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*mongoDB).Unlock :26 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*remoteBase).Complete /data/mci/b1fb0b12d0cfc1873c727e023990ee55/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/remote_base.go:152 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool.executeJob /data/mci/b1fb0b12d0cfc1873c727e023990ee55/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool/helpers.go:45 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool.worker /data/mci/b1fb0b12d0cfc1873c727e023990ee55/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool/helpers.go:101 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 problem unlocking 'host-termination-job.sir-h2e84zkg.2018-07-31.20-48-00' github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*lockManager).Unlock /data/mci/b1fb0b12d0cfc1873c727e023990ee55/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/driver_locker.go:255 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*mongoDB).Unlock :26 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue.(*remoteBase).Complete /data/mci/b1fb0b12d0cfc1873c727e023990ee55/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/queue/remote_base.go:152 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool.executeJob /data/mci/b1fb0b12d0cfc1873c727e023990ee55/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool/helpers.go:45 github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool.worker /data/mci/b1fb0b12d0cfc1873c727e023990ee55/gopath/src/github.com/evergreen-ci/evergreen/vendor/github.com/mongodb/amboy/pool/helpers.go:101 runtime.goexit /opt/go1.8/go/src/runtime/asm_amd64.s:2197 mci:PRIMARY> db.evg.service.jobs.findOne({_id:""""host-termination-job.sir-h2e84zkg.2018-07-31.20-48-00""""}) { """"_id"""" : """"host-termination-job.sir-h2e84zkg.2018-07-31.20-48-00"""", """"type"""" : """"host-termination-job"""", """"version"""" : 0, """"priority"""" : 2, """"status"""" : { """"owner"""" : """"evg.service.evergreenapp-3.build.10gen.cc.04dc0574-21d8-4f3e-9bb2-d2fa572e4cff"""", """"completed"""" : false, """"in_prog"""" : true, """"mod_ts"""" : ISODate(""""2018-08-01T13:26:49.969Z""""), """"mod_count"""" : 577, """"err_count"""" : 0 }, """"time_info"""" : { """"created"""" : ISODate(""""2018-07-31T20:48:06.819Z""""), """"start"""" : ISODate(""""0001-01-01T00:00:00Z""""), """"end"""" : ISODate(""""0001-01-01T00:00:00Z""""), """"wait_until"""" : ISODate(""""0001-01-01T00:00:00Z""""), """"max_time"""" : NumberLong(0) }, """"job"""" : { """"host_id"""" : """"sir-h2e84zkg"""", """"metadata"""" : { """"name"""" : """"host-termination-job.sir-h2e84zkg.2018-07-31.20-48-00"""", """"job_type"""" : { """"name"""" : """"host-termination-job"""", """"version"""" : 0 } } }, """"dependency"""" : { """"type"""" : """"always"""", """"version"""" : 0, """"edges"""" : [ ], """"dependency"""" : { """"should_rebuild"""" : true, """"type"""" : { """"name"""" : """"always"""", """"version"""" : 0 }, """"jobedges"""" : { """"edges"""" : [ ] } } } }",0,0,1,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-3769","08/01/2018 21:53:25",2,"Setup Failure: xc-subprocess on RHEL 7.2 zLinux [Evergreen Self-Tests @ 4e4310d2] ""h2. [xc-subprocess failed on RHEL 7.2 zLinux|https://evergreen.mongodb.com/task/mci_rhel72_s390x_xc_subprocess_4e4310d23ea0d0d7da2606cfdc5c647b04974123_18_08_01_17_51_19/0] Host: [rhel72-z-10.maristisv.build.10gen.cc|https://evergreen.mongodb.com/host/rhel72-z-10.maristisv.build.10gen.cc] Project: [Evergreen Self-Tests|https://evergreen.mongodb.com/waterfall/mci] Commit: [diff|https://github.com/evergreen-ci/evergreen/commit/4e4310d23ea0d0d7da2606cfdc5c647b04974123]: EVG-3866: use correct selector for terminated hosts ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-3816","08/02/2018 17:24:07",1,"Generated tasks should inherit the priority from the task that generated them ""Unless overridden in the task definition JSON""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3817","08/02/2018 19:26:38",2,"Setup failures not colored properly in patch results sidebar ""These failures would show up in pale purple on the grid and on individual results pages, but would still be colored gray in the results section on the right-hand side of the patch page. Reference patch: https://evergreen.mongodb.com/version/5b631dffe3c3316f9aecd40d""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-3821","08/03/2018 15:13:28",1,"Panic: concurrent map iteration and map write ""Stack is attached.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-3822","08/03/2018 15:20:15",2,"Create new status after initializing and before starting ""The SpawnHost function call can take much longer to return for containers than for conventional hosts, since Docker may need to import and build new images before actually creating and running new containers. This currently means that containers can be stuck in initializing for a while, and end up getting reaped by the scheduler after 3 minutes. By adding the HostSpawning (""""spawning"""") status, we are able to distinguish between uninitialized hosts and ones that have already called SpawnHost. ""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5117","08/03/2018 18:31:51",1,"last_green endpoint does not exclude patch builds """""," $ curl -s https://evergreen.mongodb.com/rest/v1/projects/curator/last_green?rhel70 Couldn't find version with id `1494` after successful aggregation. ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5125","08/05/2018 05:06:12",0,"Cannot get links to artifacts for execution tasks from project and githash ""I spiraled a bit here trying to come up with different options. It's possible I've overlooked something. https://evergreen.mongodb.com/rest/v1/versions/mongodb_mongo_master_bc880e13829b89ee46c0715c5534c8ef1ac387f3/status lists the task ids for the """"unittests!"""" display task and not the """"unittests"""" execution task. https://evergreen.mongodb.com/rest/v1/tasks/mongodb_mongo_master_enterprise_rhel_62_64_bit_coverage_display_unittests!_bc880e13829b89ee46c0715c5534c8ef1ac387f3_18_08_02_18_14_03 reports {{""""files"""": null}} as EVG-3283 originally described. https://evergreen.mongodb.com/rest/v2/tasks/mongodb_mongo_master_enterprise_rhel_62_64_bit_coverage_display_unittests!_bc880e13829b89ee46c0715c5534c8ef1ac387f3_18_08_02_18_14_03 reports {{""""artifacts"""": null}} despite the changes from EVG-3283. It appears the artifacts are only listed in https://evergreen.mongodb.com/rest/v2/tasks/mongodb_mongo_master_enterprise_rhel_62_64_bit_coverage_unittests_bc880e13829b89ee46c0715c5534c8ef1ac387f3_18_08_02_18_14_03, which isn't listed by the {{/rest/v1/versions//status}} endpoint. I tried to use the {{/rest/v2/projects//revisions//tasks}} endpoint, but it didn't work for me. https://evergreen.mongodb.com/rest/v2/projects/mongodb-mongo-master/revisions/bc880e13829b89ee46c0715c5534c8ef1ac387f3/tasks returns as does https://evergreen.mongodb.com/rest/v2/projects/mongodb_mongo_master/revisions/bc880e13829b89ee46c0715c5534c8ef1ac387f3/tasks """," { """"status"""": 404, """"error"""": """"task from project 'mongodb-mongo-master' and commit 'bc880e13829b89ee46c0715c5534c8ef1ac387f3' not found"""" } { """"status"""": 404, """"error"""": """"task from project 'mongodb_mongo_master' and commit 'bc880e13829b89ee46c0715c5534c8ef1ac387f3' not found"""" } ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5126","08/05/2018 05:28:54",2,"Cannot restart setup-failed display tasks ""I tried to restart the {{replica_sets_auth}} task in [my patch build|https://evergreen.mongodb.com/task/mongodb_mongo_v4.0_enterprise_rhel_62_64_bit_display_replica_sets_auth_patch_ad5ca4f9f516d575dc247ba12b2c054ed8d2544f_5b6665c2e3c33156e42cbf57_18_08_05_02_50_19] and got the following error: """"Error restarting: Error restarting task mongodb_mongo_v4.0_enterprise_rhel_62_64_bit_display_replica_sets_auth_patch_ad5ca4f9f516d575dc247ba12b2c054ed8d2544f_5b6665c2e3c33156e42cbf57_18_08_05_02_50_19: Task 'mongodb_mongo_v4.0_enterprise_rhel_62_64_bit_display_replica_sets_auth_patch_ad5ca4f9f516d575dc247ba12b2c054ed8d2544f_5b6665c2e3c33156e42cbf57_18_08_05_02_50_19' is currently 'setup-failed' - cannot reset task in this status"""". It'd be great if fixing this also made it possible so selecting """"Setup Failures"""" from the """"Restart"""" on the version and build pages could restart display tasks as well.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5140","08/06/2018 15:17:58",1,"Panic in gimlet route ""panic: project context not attached to request gimlet/middleware_grip.go:184 runtime/asm_amd64.s:515 runtime/panic.go:489 route/prefetch.go:78 route/task_restart.go:37 gimlet/framework.go:42 http/server.go:1942 negroni/negroni.go:46 negroni/negroni.go:29 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth.go:192 negroni/negroni.go:38 negroni/negroni.go:86 mux/mux.go:114 negroni/negroni.go:46 negroni/negroni.go:29 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:34 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:34 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth.go:37 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth_user.go:142 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_grip.go:192 negroni/negroni.go:38 negroni/negroni.go:86 http/server.go:2568 http/server.go:1825 runtime/asm_amd64.s:2197""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8831","08/06/2018 17:27:45",1,"make curator sync files more reliably ""don't run threads inside of the job avoid skipping copying for dev builds. ""","",0,0,0,0,1,0,0,0,0,0,0,0,1,0,0 +"EVG-5143","08/06/2018 20:57:57",2,"Servers getting auto-quarantined without a notice ""I see a few servers that were put into quarantine by mci user without creating a jira ticket today: https://evergreen.mongodb.com/host/rhel67-z-5.maristisv.build.10gen.cc https://evergreen.mongodb.com/host/rhel67-z-12.maristisv.build.10gen.cc https://evergreen.mongodb.com/host/rhel67-z-13.maristisv.build.10gen.cc https://evergreen.mongodb.com/host/rhel72-z-4.maristisv.build.10gen.cc https://evergreen.mongodb.com/host/rhel72-z-5.maristisv.build.10gen.cc https://evergreen.mongodb.com/host/sles12-z-1.maristisv.build.10gen.cc https://evergreen.mongodb.com/host/ubuntu1604-arm64-2.packet.build.10gen.cc (3 days ago) https://evergreen.mongodb.com/host/macos-1012-112.macstadium.build.10gen.cc Last time we saw a jira ticket for this was on 8/02""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-5144","08/07/2018 07:22:40",2,"Setup Failure: e2e-chrome on Ubuntu 18.04 (e2e) [Lobster @ d04f7d15] "" h2. [e2e-chrome failed on Ubuntu 18.04 (e2e)|https://evergreen-staging.corp.mongodb.com//task/lobster_ubuntu1804_e2e_chrome_d04f7d15900d2de0f7f24b2030d67f8e6bde67f5_18_08_05_17_06_36/0] Host: [ec2-54-164-127-144.compute-1.amazonaws.com|https://evergreen-staging.corp.mongodb.com//host/sir-1ck85bmh] Project: [Lobster|https://evergreen-staging.corp.mongodb.com//waterfall/lobster] Commit: [diff|https://github.com/evergreen-ci/lobster/commit/d04f7d15900d2de0f7f24b2030d67f8e6bde67f5]: Update to React 16, Eslint 5 (#48) ""","",0,0,0,0,1,0,0,0,0,0,0,0,0,1,0 +"EVG-5146","08/07/2018 14:28:25",2,"Host expiration warnings aren't getting sent? ""   error: unknown trigger: 'expiration'    event_id: 5b6858f1b237365acdb40bea    event_type: HOST    job: event-metajob    message: errors processing triggers for event    metadata: { [[+]|https://mongodb.splunkcloud.com/en-US/app/search/search?earliest=-60m%40m&latest=now&q=search%20index%3Devergreen-staging%20metadata.level%20%3E%3D%2070&display.page.search.mode=fast&dispatch.sample_ratio=1&display.general.type=events&sid=1533648416.7279320]    }    source: events-processing""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5147","08/07/2018 15:29:54",2,"Create switch for processed/unprocessed CP modes ""Add a switch to the perf BB / signal processing page which allow to change mode: """"processed change points"""" and """"unprocessed change points""""""","",0,0,0,0,0,0,0,0,1,0,1,1,0,0,0 +"EVG-5149","08/07/2018 16:00:58",2,"Need to check if a host is up before adding a host provisioning job for it ""I think the correct course of action here is to edit {{DescribeSpotRequestsAndSave}} in {{cloud/ec2_client.go}} so that it updates host's status' to running if they are running, and then change the host provisioning query so that it *doesn't* check IsUp for ec2 instances but also doesn't try to start hosts that aren't yet up. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5154","08/08/2018 12:24:33",1,"Signal Processing: Revision column is empty ""As the revision column is empty, I can see a list of change points, but can't know where that change point is. !image-2018-08-08-14-21-23-517.png|width=600! (What I really want is a clickable link to the task page, to the specific revision. I assume there's already a separate ticket for that.)""","",0,0,1,0,0,0,0,0,0,0,1,1,0,0,0 +"EVG-5162","08/08/2018 22:44:00",1,"Build Baron Plugin: Include link to extracted features ""The Build Baron Tool now has an endpoint to display the extracted features from the BF Suggestion Server. The Plugin should include a link to this page. Link should appear on all the page regardless of whether the suggestion is coming from JIRA or the suggestion server. ""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5163","08/09/2018 03:19:20",1,"Allow time-based notifications to be configured based on pass/fail ""Correct me if I'm wrong, but based on discussion with brian right now the notifications seem to be implemented so that they only generate if the first commit is passing and the next is either passing or failing. That seems to mean that if something times out and thus takes a long time, it will still generate a notification. that seems less useful, since mostly what I care about is """"this task passed before, still passes, but now it takes 50% longer"""". I also wouldn't hold up the resolution of the event-driven notifications on this since I haven't seen evidence of it going haywire yet. this just seems like it would improve the signal:noise ratio on these. (also, while I'm at it, can someone tell me if I should be saying """"150%"""" or """"50%"""" to get notified of things taking 1.5x their usual time?)""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5164","08/09/2018 06:54:11",1,"Parsing time failure for REST V2 ""patches by user"" endpoint ""Recently I got below 400 errors while accessing patches by user REST V2 endpoint.  The body of the response indicates it's time parsing related:   """," $ evg_patch_build.py stats Traceback (most recent call last): File """"/Users/lchen/workplace/kernel-tools/vendoring/evg_patch_build.py"""", line 546, in evg_patch_build(action, project, desc, wt_branch, patch, restart_all=args['-a']) File """"/Users/lchen/workplace/kernel-tools/vendoring/evg_patch_build.py"""", line 509, in evg_patch_build patch_id = patch or get_latest_patch() File """"/Users/lchen/workplace/kernel-tools/vendoring/evg_patch_build.py"""", line 128, in get_latest_patch p_rsp = request_rest_endpoint_json(p_url) File """"/Users/lchen/workplace/kernel-tools/vendoring/evg_patch_build.py"""", line 86, in request_rest_endpoint_json rsp.raise_for_status() File """"/usr/local/lib/python3.6/site-packages/requests/models.py"""", line 939, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://evergreen.mongodb.com/rest/v2/users/luke.chen/patches >>> r = requests.get('https://evergreen.mongodb.com/rest/v2/users/luke.chen/patches', headers=headers) >>> r.json() {u'status': 400, u'error': u'problem parsing time from \'0001-01-01 00:00:00 +0000 UTC\' (parsing time """""""" as """"""""2006-01-02T15:04:05.000Z"""""""": cannot parse """""""" as """""""""""")'} ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5169","08/09/2018 23:20:50",1,"Double forward slash in link header causes a 301 ""This URL: https://evergreen.mongodb.com/api/rest/v2/projects If it has enough projects, returns a link header which contains a double forward slash: When I request this URL I get a 301 from evergreen redirecting to this url with one of the double slashes taken out. Evergreen should generate single slash URLs in the link header."""," Link: ; rel=""""next"""" ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5170","08/09/2018 23:58:41",1,"/projects/:project/patches endpoint broken ""Ex: https://evergreen.mongodb.com/api/rest/v2/projects/mongo-ruby-driver/patches Yields: https://github.com/evergreen-ci/evergreen/wiki/REST-V2-Usage#fetch-patches-by-project states that start_at defaults to now. Curiously, the following URL: https://evergreen.mongodb.com/api/rest/v2/projects/mongo-ruby-driver/patches?start_at=2006-01-02T15:04:05.000Z Yields: """," { """"status"""": 400, """"error"""": """"parsing time \""""\"""" as \""""\""""2006-01-02T15:04:05.000Z\""""\"""": cannot parse \""""\"""" as \""""\""""\"""""""" } { """"status"""": 400, """"error"""": """"parsing time \""""2006-01-02T15:04:05.000Z\"""" as \""""\""""2006-01-02T15:04:05.000Z\""""\"""": cannot parse \""""2006-01-02T15:04:05.000Z\"""" as \""""\""""\"""""""" } ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5171","08/10/2018 17:01:41",1,"Waterfall resets to first page on filtering ""Repro: * Go to [the second page of the 4.0 waterfall|https://evergreen.mongodb.com/waterfall/mongodb-mongo-v4.0?skip=5] for example * Type something in the """"Filter Variant"""" page * Watch the page go to the first waterfall page of that project Impact: this is super annoying when trying to track down past history. Interestingly enough this bug doesn't appear if I type in the """"Filter Task"""" box instead.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5172","08/10/2018 17:19:17",1,"start_at values are required to be quoted ""The source specifies this: As a result, the following request fails: And this succeeds: The quotes should probably not be required."""," rest/model/time.go: APITimeFormat = """"\""""2006-01-02T15:04:05.000Z\"""""""" https://evergreen.mongodb.com/api/rest/v2/projects/mongo-ruby-driver/patches?start_at=2020-01-02T15:04:05.000Z { """"status"""": 400, """"error"""": """"parsing time \""""2020-01-02T15:04:05.000Z\"""" as \""""\""""2006-01-02T15:04:05.000Z\""""\"""": cannot parse \""""2020-01-02T15:04:05.000Z\"""" as \""""\""""\"""""""" } https://evergreen.mongodb.com/api/rest/v2/projects/mongo-ruby-driver/patches?start_at=%222020-01-02T15:04:05.000Z%22 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5174","08/10/2018 20:30:58",1,"Lack of patches should return an empty array, not 400 ""For example, api v2 GET projects/mongo-tools-v4.0/patches?start_at=""""2020-01-01T00:00:00.000Z"""" produces: 400: no patches found If there are no patches the return should be an empty array with a success HTTP status code.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5177","08/13/2018 13:31:09",2,"Aggregation options for grouped items ""Add aggregation for folded rows. Max on value, and count. Maybe, we could make it configurable by the user.""","",0,0,0,0,0,0,0,0,1,0,1,1,0,0,0 +"EVG-5178","08/13/2018 13:32:48",2,"Date column ""Each CP has a timestamp. We should add this column to the grid, also add default filter to query CPs for the last two weeks only. User should be able to change it. (This requires to write change filtering query parser/compiler)""","",0,0,0,0,0,0,0,0,1,0,1,1,0,0,0 +"EVG-5179","08/13/2018 15:37:20",1,"Remove poolSize and always use maxContainers when scheduling archlinux-docker hosts ""poolSize is redundant because it's the same as maxContainers in the pool settings. ""","",0,0,0,1,0,0,0,0,0,0,1,0,0,0,0 +"EVG-9256","08/13/2018 16:12:42",1,"maintence pass at sink application ""- disable background jobs that aren't going to be useful, - cleanup and isolate cost reporting code. - update vendored libs - fix tests as needed. ""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-5181","08/13/2018 16:14:10",2,"Task in task_group on single host ran despite failure of previous task ""The following task group is defined as: It was [observed in a build|https://evergreen.mongodb.com/build/mongodb_mongo_master_amazon_ec6f2a54d8b901e95e556d53647944be8ce441d5_18_08_13_05_46_37] in that {{compile}} & {{compile_unittests}} ran successfully and then {{unittests}} failed on this [host|https://evergreen.mongodb.com/host/sir-pqei7j7j]. The tasks {{compile_dbtest}} and {{compile_all}} were marked as blocked (and unscheduled). However {{dbtest}} ran on a [different host|https://evergreen.mongodb.com/host/sir-pip84bbj] (and failed since the artifacts did not exist)."""," - &compile_task_group_template name: compile_task_group_template max_hosts: 1 tasks: [] ... - <<: *compile_task_group_template name: compile_all_run_unittests_TG tasks: - compile - compile_unittests - unittests - compile_dbtest - dbtest - compile_all ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5190","08/14/2018 19:04:33",2,"Allow users to alert on subsets of failure types ""Not sure how deeply-impacting this is in Evergreen, but we're seeing a lot of Setup Failures hitting the BFG project that don't need to. Would be great if there was some way to ignore them. And while I'm at it, it's unclear that System Failure BFGs are very useful either, so I assume any solution should include the option to disable those too.""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-5193","08/14/2018 20:51:27",1,"Log time taken by scheduler operations ""With many tasks in the queue the scheduler takes a long time to complete. We have seen ~5 minute durations. We should log how long various operations take, especially how long it takes to run the sorting setup, how long it takes to run the sort, and how long the host allocator takes. We can use this information to make a faster scheduler.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5195","08/14/2018 21:29:28",0,"Put task status into a custom field in JIRA notifications ""Right now it's in the summary of a BFG and that means we have to regex search on it, which is insanely slow. Using a custom field would be much faster.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5198","08/15/2018 03:07:19",2,"add flag to distro to exclude a distro from running tasks in projects ""(e.g. docker hosts, used for parents and should be spawnable, but not for task execution...) should also be in the validator to prevent versions that use these distros from running""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5206","08/15/2018 21:02:07",2,"Re-notify after 2 days for 'test fails in task' trigger ""John Liu [3:57 PM] eh the task regression notification will re-notify of a failing task every 2 days I believe this is to preserve the behavior of the previous BFGs Ian Whalen [3:57 PM] yup John Liu [3:57 PM] the task regression by test does not have this check but we could definitely add it""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5210","08/16/2018 18:22:09",2,"ActivateElapsedBuilds does not schedule cross-variant dependencies ""It appears that tasks activate their dependencies in certain special cases (patch builds, stepback, patch builds), but I don't see that this happens in commit builds. It should happen there too for consistency, and to ensure that all activated tasks' dependencies are scheduled. It appears that \{{ActivateElapsedBuilds}} activates all tasks in a given build, but it doesn't activate their dependencies, so if the dependencies are cross-variant, it will not activate them.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5215","08/17/2018 07:48:04",1,"Setup Failure: e2e-chrome on Ubuntu 18.04 (e2e) [Lobster @ 418607b0] "" h2. [e2e-chrome failed on Ubuntu 18.04 (e2e)|https://evergreen-staging.corp.mongodb.com//task/lobster_ubuntu1804_e2e_chrome_418607b0f5d77c08c60db6b29ac9f6810960d4a1_18_08_15_14_03_00/0] Host: [ec2-34-230-66-20.compute-1.amazonaws.com|https://evergreen-staging.corp.mongodb.com//host/sir-97ti57eh] Project: [Lobster|https://evergreen-staging.corp.mongodb.com//waterfall/lobster] Commit: [diff|https://github.com/evergreen-ci/lobster/commit/418607b0f5d77c08c60db6b29ac9f6810960d4a1]: Allow user to change log file via 'Show Details' menu's input box when server is set (#54) ""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-5216","08/17/2018 14:22:27",1,"Change agent heartbeat failure to N times in a row from N times during a task ""Currently, the agent will fail a task if more than 10 heartbeats fail during task execution. This ticket is to change this behavior to more than 10 times in a row.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5218","08/17/2018 15:25:21",2,"Agent deploys fail immediately after deploy ""Investigate why BUILD-5992 happened""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5222","08/17/2018 18:17:30",1,"Batch describe instances makes API call with empty list """""," error getting host statuses for providers: error describing instances: after 10 retries, operation failed: MissingParameter: The request must contain the parameter InstanceId ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5225","08/17/2018 23:32:09",2,"Evergreen isn't consistent about failing task when creating BFG tickets ""BFG tickets appear to sometimes be created with the failing task as the execution task and sometimes created with the failing task as the display task. For example, in BF-10282 the original title was """"Failures: sharding_6 on ! Linux DEBUG [MongoDB (master) @ 801fb6ac] (addshard2.js, find_and_modify_after_multi_write.js, authCommands.js, auto_rebalance_parallel_replica_sets.js, change_stream_update_lookup_read_concern.js +10 more)"""" and in BFG-87625 the original title was """"Failed: sharding on ! Linux DEBUG [MongoDB (master) @ 801fb6ac]"""". I think ideally the links within a BFG ticket would go directly to the execution which caused the display task to be marked as a failure. However, I would want the title and custom JIRA fields to still refer to the name of the display task though.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5226","08/17/2018 23:48:25",0,"Evergreen returns 404 for certain inactive display tasks ""I think something may be misconfigured with how the {{benchrun_embedded*}} tasks are set up. * https://evergreen.mongodb.com/task/mongodb_mongo_master_rhel_62_64_bit_mobile_display_benchrun_embedded_9fd731be471c3d0f40bf5208f2bdd3923c9ea3e8_18_08_17_17_26_44 is an inactive display task which returns a 404. * https://evergreen.mongodb.com/task/mongodb_mongo_master_rhel_62_64_bit_mobile_benchrun_embedded_aggregation_5e461534b339c957d2e6dcf16015949a496a1110_18_08_16_22_58_49 is an execution task which doesn't have a """"Parent display task"""" link. * https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_display_sharding_59d4d78a68ef6347120c6dfcd6da6ec3d325722f_18_08_17_20_06_11 is a different inactive display task for the sharding tests which works completely fine. References for the {{benchrun_embedded*}} tasks in the {{etc/evergreen.yml}} project configuration file. * https://github.com/mongodb/mongo/blob/d0b0d782a14e9c0ac5724e35fb0bc2e20abcca67/etc/evergreen.yml#L178-L188 * https://github.com/mongodb/mongo/blob/d0b0d782a14e9c0ac5724e35fb0bc2e20abcca67/etc/evergreen.yml#L12789-L12825""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5227","08/20/2018 15:22:15",2,"Container changed from running back to building ""https://evergreen-staging.corp.mongodb.com/host/container-6564627122112293016""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5229","08/20/2018 19:22:53",1,"Do not run teardown scripts on task-spawned hosts """""," error running teardown script on remote host: : error parsing ssh info : Invalid hostname format: ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5232","08/20/2018 19:38:24",1,"Spawn hosts for tasks fails to retrieve generated key """""," error spawning host evg-ubuntu1604-test-20180820183226-4764860880446243780: key name must not be empty ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5236","08/21/2018 00:42:57",2,"avoid cross compiling zap tests ""these are almost entirely test harness assumptions about testdata and config files. after some thought, we decided to ditch the cross compile method and just compile these tests directly on these platforms. ""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5237","08/21/2018 03:51:23",1,"avoid/log termination jobs for terminated hosts ""seems like there are a couple of cases in the host termination job where we don't handle hosts that are already terminated very well. This is a small ticket to return early when it's clear we should and log a bit more in other cases. derives from MAKE-437 work""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5241","08/21/2018 16:22:11",1,"Gimlet middleware: Runtime error: invalid memory address or nil pointer dereference """""," gimlet/middleware_grip.go:184 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 service/version.go:112 service/ui.go:257 http/server.go:1942 negroni/negroni.go:46 negroni/negroni.go:29 negroni/negroni.go:38 negroni/negroni.go:38 service/middleware.go:239 gimlet/middleware_wrapper.go:16 negroni/negroni.go:38 negroni/negroni.go:86 mux/mux.go:114 negroni/negroni.go:46 negroni/negroni.go:29 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:41 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:53 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth.go:37 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth_user.go:142 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_grip.go:192 negroni/negroni.go:38 negroni/negroni.go:86 http/server.go:2568 http/server.go:1825 runtime/asm_amd64.s:2197 ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-9299","08/22/2018 18:43:36",0,"Revendor latest version of github.com/bluele/slack ""github.com/bluele/slack has been updated to properly escape slack messages""","",0,0,0,1,0,0,0,0,0,0,0,0,1,0,0 +"EVG-5249","08/23/2018 00:47:43",1,"attach.xunit_results does not indicate failure ""I tried passing it different file paths to upload and it always says: [2018/08/22 19:31:55.274] Running command 'attach.xunit_results' in """"upload test results"""" (step 2 of 4) [2018/08/22 19:31:55.274] Attach test results succeeded However nothing appears in the test results in evergreen UI. The task should indicate failure if it fails e.g. due to being passed a nonexistent path to upload.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5254","08/23/2018 18:42:35",0,"Include task name and whether it was a task failure or test failure in email subject ""Not having this information makes it hard to skim your inbox for specific tasks and whether it's a task or system failure or if it's JUnit test failures only""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5256","08/24/2018 17:21:16",2,"Allow renotification interval to be configurable for task-regression{,-by-test} ""task-regression{,-by-test} renotify after 48 hours, but we should make these configurable using the extra data fields""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5258","08/24/2018 19:25:15",1,"Can't restart display task with blocked execution task ""https://evergreen.mongodb.com/task/mci_ubuntu1604_display_lint_patch_3f997083ebbeb03548604f1f299d075733cf2252_5b80304c2a60ed5f8609e3a6_18_08_24_16_20_29""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5259","08/24/2018 20:13:40",2,"Investigate how builds are marked failed with no failing tasks ""I put some logging inside of the task model to figure out when/where builds are getting marked failed. If you search splunk with """"source=http:evergreen evg-3455"""" you'll find that builds that ultimately succeed, and are marked as Status: evergreen.BuildSucceeded at some point prior have their status in the DB set to failed.""","",0,0,0,1,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5261","08/24/2018 21:55:02",2,"Created ticket not displayed in the Build Baron Plugin ""On [this task page|https://evergreen.mongodb.com/task/mongodb_mongo_v3.6_enterprise_rhel_72_s390x_jstestfuzz_concurrent_replication_WT_14681d89a9093802a8b29455c8a361ccd36b42c9_18_08_23_17_20_52/0], the Build Baron Plugin does not display the BFG ticket that was automatically created. The ticket information is retrieved through an API call ({{plugin/buildbaron/created_tickets/)}} that returns a 500 error with a """"HTTP request returned unexpected status `404 `"""" error message. The message appears to come from the  [{{GetJIRATicket()}}|https://github.com/evergreen-ci/evergreen/blob/0f46336c89adc07fd5e0ca28834c111fbc3cb88c/thirdparty/jira.go#L166] function. A 404 for the JIRA API call could happen if the ticket key is invalid. This key is retrieved from Evergreen events by the Build Baron Plugin [here|https://github.com/evergreen-ci/evergreen/blob/0f46336c89adc07fd5e0ca28834c111fbc3cb88c/service/ui_plugin_build_baron.go#L113-L126].""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5264","08/26/2018 18:28:25",2,"Editing text in Lobster search bar is sluggish for very large logs ""The current behavior of the Lobster search bar is such that whenever you edit the current search term (delete/insert/replace a character), the search terms highlighted in the log are automatically updated. There seems to be a negative consequence to this, which is that for very large logs, editing the current search term becomes quite laggy. That is, trying to quickly type a term or delete a few characters becomes much slower than you would expect from a responsive text input box. Here is one [example log|https://logkeeper.mongodb.org/lobster/build/834158c1a5f92af0f569f178be004413/test/5b809f89c2ab68145a00ea9d#bookmarks=0%2C183196] that exhibits this behavior. It is a bit over 180,000 lines. Depending on user's preferences, one fix would be to consider _not_ updating the highlighted search terms until a user presses """"Enter"""" again. Only then would the highlighted search terms update to reflect the current text value in the search bar. Personally, I prefer this behavior since it ensures that the current context is not changed while entering a new search term i.e. if I am focused on one particular log line while entering a new search term, I know that the logs won't be scrolled to a different position until I actually press """"Enter"""". ""","",0,1,0,0,0,0,0,0,0,0,0,0,0,1,0 +"EVG-5266","08/27/2018 15:29:28",1,"race-agent failure (TestAbort) ""https://evergreen.mongodb.com/task/mci_race_detector_race_agent_ae9b15165d12b22d7020fdb6f1d83e485f50cc09_18_08_24_21_13_32""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5267","08/27/2018 15:40:51",1,"Display task doesn't show system-failures correctly ""The task there shows as having no build host and no logs. It is unclear from the task page why this was a system failure.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5268","08/27/2018 18:36:42",1,"Container name not displayed on some container tasks ""https://evergreen.mongodb.com/task/mci_archlinux_docker_test_agent_917220c726028ea2ba8d4f618778812321e011e8_18_08_27_15_59_27""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5270","08/28/2018 01:25:16",1,"Build on MSFT with a compile-failure didn't list compiler output for failing code ""[https://evergreen.mongodb.com/task_log_raw/mongodb_mongo_master_windows_64_2k8_debug_compile_patch_078d6b49548d90880556af6f55e3baf8b4709917_5b845e6de3c3314a2daee887_18_08_27_20_26_22/0?type=T&text=true] [https://evergreen.mongodb.com/host/sir-xzzr53qh] It looks like something might have gone wrong with the agent installation.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5271","08/28/2018 12:28:14",2,"Inability to log in under FF ""Whenever an user clicks over password field it instantly loses the focus, so the user cannot type password and log in. The second problem is console warning (""""An empty string cannot be an argument of getElementById()""""), which logged to console whenever user clicks anywhere. Both of this are FF related and couldn't be reproduced on Chrome (due to different implementation of getElementById function and other differences)""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5272","08/28/2018 15:01:14",2,"For task failures, display failing command on task page ""We record the name of the command that failed in the task document, but don't expose that anywhere. We should expose this in the UI to help users debug""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5274","08/29/2018 21:15:14",2,"Agent deploy jobs should requeue themselves ""Currently agent deploy jobs are generated every 15 seconds. This means that, if an agent deploy job doesn't finish quickly, another agent job can run at the same time. We should: 1. Round the timestamp to the nearest 10-minute or similar in the generator. 2. Requeue agent deploy jobs in the job itself, in a defer, only if it fails, and increment the attempt there.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5275","08/29/2018 22:41:57",2,"Overridden task shows up as ""Blocked"" ""Happened after the task completed successfully (sign depends on compile), see: sign: [https://evergreen.mongodb.com/task/sqlproxy_single_variant__os_single_variant~rhel70_sign_patch_9ff2d3c3c76471e68cc50903aa63bdd80a41a421_5b8704aee3c331672b83600a_18_08_29_20_40_15] and compile: [https://evergreen.mongodb.com/task/sqlproxy_single_variant__os_single_variant~rhel70_compile_patch_9ff2d3c3c76471e68cc50903aa63bdd80a41a421_5b8704aee3c331672b83600a_18_08_29_20_40_15]""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5276","08/30/2018 15:52:22",1,"Show what containers a parent contains, what parent a container belongs to ""on the host page""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5277","08/30/2018 15:52:51",1,"Add TTL indexes for subscriptions with an ID selector ""For subscriptions which contain a selector whose key is ID, we should add a TTL index to prevent the event-metajob from being hit too hard in the future. Biggest one is pull requests which create (num builds + 1) subscriptions per commit we receive via the webhooks.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5278","08/30/2018 15:56:20",1,"Add TTL index to notifications collection ""We presently store notifications indefinitely, but we never reuse them after sending. It's probably a good call to TTL this collection.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5279","08/30/2018 16:03:51",2,"Make the selection of 'start at origin' on perf graphs sticky by account ""It would be great if I could select the wrench and 'origin' once and then have it stick until changed.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5285","08/31/2018 20:34:14",1,"Link for tasks in email return not found ""I believe this is EVG-5211 but with email instead of jira. We should also check slack.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5286","08/31/2018 21:02:22",2,"Restarting a task doesn't update the build cache ""This leads to rogue/incorrect notifications when restarting a task""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5287","08/31/2018 21:24:17",2,"Many version finished notifications received for same version ""mci:SECONDARY> db.event_log.find({r_id: """"mci_d7795888f24f737e355d037f989ea43203add13f"""", """"data.status"""": """"failed""""}).count() 60""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5289","09/03/2018 15:41:48",1,"Move perf tools to the app ""Currently, perf tools are living at /static/plugins/perf. Since it's not a plugin anymore, the code should be migrated to /app/perf/.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-8644","09/04/2018 23:07:33",2,"write more rigerous integration tests for jasper ""* larger numbers of processes. (like 50 or 100) * processes that have to be terminated. * processes that resemble mongodb. * use the send.InternalSender to verify that managers respect output options.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-8621","09/05/2018 22:13:44",2,"implement a better in-memory send.Sender ""for use in the jasper interface to tee logs to a buffer that we can return in a rest/etc interface.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-5303","09/05/2018 22:42:58",1,"Github webhook not working ""Initially, we had the repo at [https://github.com/mongodb/mongo-odbc-driver/] configured with the following webhooks: !image-2018-09-05-17-39-10-283.png! The evergreen logs indicated the following error: even after deleting  ""","“POST https://api.github.com/repositories/122675902/hooks: 422 Validation Failed [{Resource:Hook Field: Code:custom Message:Hook already exists on this repository}]”",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5305","09/07/2018 12:58:52",2,"simplify test compilation and execution. ""using the ftdc/jasper makefiles as models (already upgraded sink, which is substantially similar to the evergreen makefile). This gets much easier after EVG-5246.""","",1,0,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5307","09/10/2018 04:55:58",0,"patchable=false tasks cannot be used in a display task with patchable=true tasks ""Since I'm using the {{s3Copy.copy}} command in the {{upload_benchrun_embedded_files}} task, I wanted to make it not run as part of a patch build in order to avoid confusing [the {{model.FindPushLogAfter(copyToLocation, v.RevisionOrderNumber)}} check|https://github.com/evergreen-ci/evergreen/blob/c17b8ca247e17800de7304c778c5af350a6c63d5/service/api_plugin_s3copy.go#L59] when it'd run as part of a mainline commit. I tried to include the {{upload_benchrun_embedded_files}} task in the existing {{benchrun_embedded}} display task but am getting an error message when navigating to its task page after scheduling the patch build. EVG-5226 describes some other weirdness around the {{benchrun_embedded*}} tasks that I wasn't sure if it is related given that I've based my changes on top of [660fb03|https://github.com/mongodb/mongo/commit/660fb03fe223cacc1c35d3c0e7b266ab5679f31d] from SERVER-37060. * Task: https://evergreen.mongodb.com/task/mongodb_mongo_master_rhel_62_64_bit_mobile_display_benchrun_embedded_patch_660fb03fe223cacc1c35d3c0e7b266ab5679f31d_5b95e6522a60ed2c27bc10d7_18_09_10_03_35_01 * Patch build: https://evergreen.mongodb.com/version/5b95e6522a60ed2c27bc10d7"""," { """"status"""": 500, """"error"""": """"request aborted"""" } ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5308","09/10/2018 14:09:32",1,"Panic due to missing execution task """""," path /task/mongodb_mongo_master_rhel_62_64_bit_mobile_display_benchrun_embedded_patch_660fb03fe223cacc1c35d3c0e7b266ab5679f31d_5b95e6522a60ed2c27bc10d7_18_09_10_03_35_01 stack gimlet/middleware_grip.go:184 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 task/results.go:16 service/task.go:299 service/ui.go:232 http/server.go:1942 negroni/negroni.go:46 negroni/negroni.go:29 negroni/negroni.go:38 negroni/negroni.go:38 service/middleware.go:239 gimlet/middleware_wrapper.go:16 negroni/negroni.go:38 negroni/negroni.go:86 mux/mux.go:114 negroni/negroni.go:46 negroni/negroni.go:29 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:41 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:53 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth.go:37 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth_user.go:142 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_grip.go:192 negroni/negroni.go:38 negroni/negroni.go:86 http/server.go:2568 http/server.go:1825 runtime/asm_amd64.s:2197 ",0,0,0,0,0,0,1,0,0,0,1,0,0,0,0 +"EVG-5313","09/11/2018 16:43:12",2,"Restart all tasks in a single-host task group if one task is restarted ""There are a number of cases where a task in a single-host task group might be restarted. If this task depends on previous tasks in a task group having run, then this task will fail in a way that might be mysterious to the user. Furthermore, there is not an indication in the UI of which tasks belong to a particular task group. Even if there were, selectively restarting each task in the group would require some painstaking clicking. We should, in cases where Evergreen restarts a task (the system-unresponsive case, when for example AWS has reaped a host) and when a user restarts a task, if that task is part of a single-host task group, Evergreen should restart all tasks in the group. Unlike multi-host task groups, users assume that single-host task groups have dependencies between the tasks.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5314","09/11/2018 20:29:05",2,"Expose image ID in rest v2 host API endpoint ""We currently do this in the distros endpoint. We should do it in the hosts endpoint also so that people can reason about which image changes were present when their task ran.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5315","09/12/2018 13:49:38",1,"Attempting to schedule display task returns 500 HTTP error about not being able to find distro ""This might be the first time we've attempted to have execution tasks within a display task run on different distros. [The {{generate_benchrun_embedded_files}} task is meant to run on the {{rhel62\-small}} distro|https://github.com/mongodb/mongo/blob/4592bf741ed8a7492e31a1e0a8ad997fcd0a2704/etc/evergreen.yml#L12948], and [the {{benchrun_embedded*}} tasks are meant to run on the {{centos6\-perf}} distro|https://github.com/mongodb/mongo/blob/4592bf741ed8a7492e31a1e0a8ad997fcd0a2704/etc/evergreen.yml#L12921-L12944]. https://evergreen.mongodb.com/task/mongodb_mongo_master_rhel_62_64_bit_mobile_display_benchrun_embedded_4592bf741ed8a7492e31a1e0a8ad997fcd0a2704_18_09_12_02_05_52 {quote} Error activating task mongodb_mongo_master_rhel_62_64_bit_mobile_display_benchrun_embedded_4592bf741ed8a7492e31a1e0a8ad997fcd0a2704_18_09_12_02_05_52: problem finding distro for activating task 'mongodb_mongo_master_rhel_62_64_bit_mobile_display_benchrun_embedded_4592bf741ed8a7492e31a1e0a8ad997fcd0a2704_18_09_12_02_05_52': problem finding buildvarianttask for task 'mongodb_mongo_master_rhel_62_64_bit_mobile_display_benchrun_embedded_4592bf741ed8a7492e31a1e0a8ad997fcd0a2704_18_09_12_02_05_52': could not find task benchrun_embedded in build variant rhel-62-64-bit-mobile {quote}"""," Request URL: https://evergreen.mongodb.com/tasks/mongodb_mongo_master_rhel_62_64_bit_mobile_display_benchrun_embedded_4592bf741ed8a7492e31a1e0a8ad997fcd0a2704_18_09_12_02_05_52 Request Method: PUT Request Payload: {""""active"""":true,""""action"""":""""set_active""""} ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8715","09/12/2018 15:23:31",2,"unify ""hashing"" and document parsing codepaths ""in order to identify schema changes in documents, we hash the bson values (including traversal) for all inputs and then we read the documents again to store the values again. the code paths for traversal and hashing are separate, so this ticket is to unify these code paths. It would be nice if we could also avoid the double traversal, however, that's a lower priority.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-5320","09/12/2018 21:18:19",1,"Panic in external termination job ""pool/abortable.go:121 runtime/asm_amd64.s:523 runtime/panic.go:513 runtime/panic.go:82 runtime/signal_unix.go:390 cloud/cloud_host.go:37 units/host_monitoring_external_termination.go:94 pool/helpers.go:28 pool/helpers.go:37 pool/abortable.go:174 pool/abortable.go:148 runtime/asm_amd64.s:1333 The query that inserts the jobs should filter out host intents""","",0,0,0,0,1,0,0,0,0,1,0,0,0,0,0 +"EVG-5322","09/13/2018 12:56:27",1,"Decommissioned intent hosts should be terminated without calling into a cloud manager ""Currently, if intent hosts are decommissioned, we attempt to terminate them by calling the cloud manager. This fails in the ec2 case, since the documents don't have enough metadata to be processed by the cloud manager. (They are neither on-demand nor spot.) The job errors, and another job is generated, which tries to terminate it again. We should instead check to see if the document is an intent and set it to terminated immediately.""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5323","09/13/2018 15:01:09",2,"Stack returned to agent from 400 is a list of integers """""," [evergreen.agent] 2018/09/07 21:38:02 [p=emergency]: error in agent loop, exiting: error getting next task: failed to get task: server returned 400 ({ """"error"""": { """"error"""": {}, """"stack"""": [ 24821304, 24826414, 25432232, 7220916, ",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5325","09/13/2018 20:00:39",1,"Create a REST endpoint to allow sending custom notifications ""The Cloud team needs the ability to send custom notifications to evergreen users. We will be running a script periodically against the Evergreen Stats Summary endpoints. If it determines that a particular commit caused a flakiness regression, or a consistent failure, we want to be able to send email / slack notifications to that user. Ideally, we'd be able to send these to Slack rooms also. ""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5327","09/13/2018 22:26:36",1,"Next task endpoint panic for nonexistent task group ""gimlet/middleware_grip.go:184 runtime/asm_amd64.s:515 runtime/panic.go:489 runtime/panic.go:63 runtime/signal_unix.go:290 model/task_queue.go:173 service/api_task.go:266 service/api_task.go:519 service/api.go:573 http/server.go:1942 negroni/negroni.go:46 negroni/negroni.go:29 negroni/negroni.go:38 negroni/negroni.go:38 service/api.go:166 gimlet/middleware_wrapper.go:16 negroni/negroni.go:38 negroni/negroni.go:86 mux/mux.go:114 negroni/negroni.go:46 negroni/negroni.go:29 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:41 negroni/negroni.go:38 negroni/negroni.go:38 negroni/static.go:53 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth.go:37 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_auth_user.go:142 negroni/negroni.go:38 negroni/negroni.go:38 gimlet/middleware_grip.go:192 negroni/negroni.go:38 negroni/negroni.go:86 http/server.go:2568 http/server.go:1825 runtime/asm_amd64.s:2197""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5330","09/14/2018 18:35:41",1,"task-execution-timeout job should mark execution tasks as sys-timed-out ""Currently it asks the display task to restart when it finishes, but it probably will never finish if we're in this state""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5332","09/17/2018 12:42:32",1,"Current class is only applied to 'all' thread levels view in the trend graphs ""The 'current' css class is only applied t points on the 'All threads view'. See the following images for [mixed_workloads|https://evergreen.mongodb.com/task/sys_perf_linux_3_node_replSet_mixed_workloads_ec6f2a54d8b901e95e556d53647944be8ce441d5_18_08_13_05_46_37]: !max-only.png|width=50%! !all-thread-levels.png|width=50%! ""","",0,0,1,0,0,0,0,0,0,0,0,1,0,0,0 +"EVG-5334","09/17/2018 15:22:41",2,"Allow restarting setup-failed tasks from the build page ""EVG-3248 added the ability to restart setup failures from the version page. We should also add the same feature to the build page.""","",0,1,0,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5335","09/17/2018 15:33:52",2,"combining lobster filters doesn't work ""I feel like this used to work but I can't get it to work with the new interface: https://logkeeper.mongodb.org/lobster/build/ba88d756f0698281c9999f9a7e793432/test/5b9be0a8f84ae82e18086488#bookmarks=0%2C8241&f=11ELECTION&f=11REPL_HB&f=10d20271 I expect this filter to be able to exclude all lines with ELECTION or REPL_HB, and to also exclude all lines *without* """"d20271"""". The first two filters work correctly, but I can't figure out how to make the third filter work. When I click on """"inverse"""" it does behave properly, but when I click on """"match"""" it doesn't seem to do anything -- the display is the same as if I didn't have the third filter at all.""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5337","09/17/2018 19:10:14",0,"s3 put should log that it uploaded no files when optional is set ""It is unclear to the user when optional is set if the command uploaded a file or nooped.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5341","09/18/2018 13:57:19",1,"Project route with non-existent project causes panic ""E.g., /project/asdf""","",0,0,1,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5343","09/18/2018 14:21:51",1,"> 1000 ""error clearing running task"" error in 10-minute period ""I believe we have seen this a couple times now. It leads to CPU spikes on the app servers. We should find out why this is and prevent it from happening. https://github.com/evergreen-ci/evergreen/blob/5e893fd7aeb172a034dce2c851d415745552daad/service/api_task.go#L184""","",0,0,0,0,0,0,1,0,0,1,0,0,0,0,0 +"EVG-5344","09/18/2018 15:29:02",2,"Mechanism to send users to templated Spawn Hosts configs ""To replace the functionality of https://mci.mms-build.10gen.cc/spawn, without exposing undue implementation detail to Cloud engineers, I would like to be able to send them links to specific Spawn Host configs. On """"Cloud MCI"""", these appear as separate Distros (ie. one item specifies an AMI _and_ an Ops Manager config to run inside it) Some ideas for Evergreen Spawn Hosts: * Templates ability to save per-team 'templates' for 'run Userdata at start'. ** Distro=ubuntu18 UserDataTemplate=Ops Manager 4.1.0-LDAP ** Admins could create these / manage them in git, or evg's MDB. They should be update-able via automation, not requiring human intervention. ** Ideally, I could target these distro/template combinations by url - https://evergreen.mongodb.com/spawn?distro=foo&template=bar would pre-populate the Spawn Hosts UI * (alternative workaround, not ideal) ability to fill the 'Userdata' box from the URI. ** this would let us build a web service which could construct these URIs Something like the functionality described above is necessary for Cloud to move off our custom MCI instance. cc: [~brian.samek] may have other ideas""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5346","09/19/2018 12:25:05",2,"Perf. discovery - wrong ratio formula ""There is a mistake in ratio formula - it's calculated by using log2, which is good for charts, but doesn't make that much sense for numbers. Correct formula should be linear.""","",0,0,1,0,0,0,0,0,0,0,1,1,0,0,0 +"EVG-5347","09/19/2018 15:30:15",1,"Move lint task to go 1.11 ""There are small differences between go 1.11 and go 1.8 gofmt. Since we tend to develop locally with go 1.11, we cause lint errors when linting in Evergreen with go 1.8 gofmt. We should move the lint task to go 1.11, presumably on archlinux container.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-5348","09/19/2018 15:46:25",1,"Submitting a buildvariant filter auto-adds a skip ""*Steps to repro:* 1) Go to [https://evergreen.mongodb.com/waterfall/mongodb-mongo-master] 2) Put 'Enterprise Ubuntu 18.04' in the filter variant box. *Actual result:* Land on [https://evergreen.mongodb.com/waterfall/mongodb-mongo-master?bv_filter=Enterprise%20Ubuntu%2018.04&skip=5] *Expexted result:* Land on [https://evergreen.mongodb.com/waterfall/mongodb-mongo-master?bv_filter=Enterprise%20Ubuntu%2018.04]""","",0,0,1,0,0,0,0,0,0,0,1,0,0,0,0 +"EVG-5351","09/20/2018 10:52:09",2,"Leverage new props of change points collection ""Perf team added few new properties to change points collection (in Atlas). For instance, task_id, hazard values. This might simplify queries and improve performance and display more consistent hazard values.""","",0,1,0,0,0,0,0,0,0,0,1,1,0,0,0 +"EVG-5354","09/20/2018 21:52:28",0,"Remove unused routes ""The home (""""/"""") and """"/token"""" routes are unused. We should remove them.""","",0,1,0,0,0,0,0,0,0,1,0,0,0,0,0 +"EVG-8635","09/20/2018 22:50:04",2,"benchmark throughput (bytes per ms) of output in various configurations ""using the yes command and a number of different logging configurations, see what the maximum possible throughput is for a process running in jasper. it's also interesting to us to see what the latency (mostly in a, """"are there pauses in collection."""") but the test of that is not obvious how to do correctly. should be possible to implement this using go test, though we'll need to add an additional task to evergreen and some makefile glue to run benchmarks.""","",1,0,0,0,0,0,0,0,0,0,0,0,1,0,0 +"EVG-8528","09/20/2018 22:52:10",2,"implement sender bencharmking ""implement throughput (messages/