[SERVER-6807] fix 'dbtest' binary output formatting Created: 20/Aug/12  Updated: 06/Dec/22  Resolved: 11/May/20

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

Type: Bug Priority: Minor - P4
Reporter: Aaron Staple Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: neweng, stm, tig-unittests
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Tooling & Methods
Operating System: ALL
Participants:

 Description   

The output seems to be messed up by long test names

queryoptimizercursor | tests:  160 | fails:    0 | assert calls:  20506
queryutil            | tests:  206 | fails:    0 | assert calls:    921
remove               | tests:    2 | fails:    0 | assert calls:     12
repl                 | tests:   51 | fails:    0 | assert calls:    490
replicaSetMonitor_node | tests:   23 | fails:    0 | assert calls:     55
replicaSetMonitor_select_node | tests:   60 | fails:    0 | assert calls:     94
replset              | tests:    6 | fails:    0 | assert calls:      7
shard_chunk_manager  | tests:   13 | fails:    0 | assert calls:     60
sharding             | tests:    7 | fails:    0 | assert calls: 5694546
sock                 | tests:    1 | fails:    0 | assert calls:      3
spinlock             | tests:    1 | fails:    0 | assert calls:     65
 



 Comments   
Comment by Ryan Timmons [ 11/May/20 ]

Closing as wont-fix to indicate that there is currently no intention of doing this. Please re-open if there is priority for this. Perhaps this change could self-service by an appropriate server team if this is necessary rather than having to go thru the STM prioritization queue.

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