Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-103879

Print resmoke fixture status as JSON with --logFormat=json parameter

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • DevProd Infrastructure
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Out tests running with a Resmoke fixture print the following table when the log format is plain.

      [js_test:index_diag] Fixture status:
      +--------------------------------------------+----------+-----+----+
      |full_name                                   |name      |port |pid |
      +--------------------------------------------+----------+-----+----+
      |ShardedClusterFixture:job0:shard0:primary   |j0:s0:prim|20001|1550|
      |ShardedClusterFixture:job0:shard1:primary   |j0:s1:prim|20002|1556|
      |ShardedClusterFixture:job0:mongos           |j0:s      |20003|3284|
      |ShardedClusterFixture:job0:configsvr:primary|j0:c:prim |20000|1553|
      +--------------------------------------------+----------+-----+----+
      

      When the log format is set to JSON (added in SPM-3895), this table is wrapped into JSON as text. A better / more useful way would be to print it as structured array of objects:

      [{
        "fullName": "ShardedClusterFixture:job0:shard0:primary",
        "name": "j0:s0:prim",
        "port": 20001,
        "pid": 1550
      },
      ...]
      

            Assignee:
            Unassigned Unassigned
            Reporter:
            romans.kasperovics@mongodb.com Romans Kasperovics
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: