[SERVER-18718] Move unit tests into a separate task Created: 16/Sep/13  Updated: 28/Sep/15  Resolved: 28/Sep/15

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-20315 Separate compile and unit test execut... Closed
Participants:

 Description   

Right now compile + unit tests are lumped into a single test result - this causes occasional confusion since a compile failure is different from a unit test failure. Even if they're run in series on the same machine, we should still have 'unit tests' appear as a separate task in the MCI front end and business logic.



 Comments   
Comment by Max Hirschhorn [ 28/Sep/15 ]

Closing as a duplicate of SERVER-20315. We should not compile the C++ unit tests during the compile task, and instead compile (and run) them as part of a new unittests task. Per discussion on both tickets, we shouldn't have any tasks depend on the success of the unittests task.

https://jira.mongodb.org/browse/SERVER-20315?focusedCommentId=1044038&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1044038

Comment by Andrew Morrow (Inactive) [ 15/Oct/14 ]

It also means that a single memory leak or memory error in the ASAN build means that no other tests will be run.

Generated at Thu Feb 08 03:48:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.