Skip to content

collect timing information #2

Description

@fabiangreffrath

It will probably be interesting to call the source port in a time command in the ./testrunner script to get an impression on the run-time impact of certain features. However, I am not sure how homogenous the performance of the Travis server is and if the x gametics in y realtics information printed at the end of each run doesn't even already provide more reliable information.

What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions