Changes between Version 1 and Version 2 of Ticket #4626


Ignore:
Timestamp:
2017-11-13T11:16:11Z (7 years ago)
Author:
Per Östlund
Comment:

I had Martin disable the unit checking for the Hudson library testing job for the new frontend, but now that you mention it it makes more sense to just turn it off in the new frontend instead. I will do that, it's just a matter of flipping the debug flag to be false by default.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4626 – Description

    v1 v2  
    1 Even after the fixes of #4615, the unit-checking feature is the performance bottleneck of the new front-end, even for models that actually don't have unit information in their variables (see, e.g. the AdvectionReaction models of the ScalableTestSuite).
     1The unit-checking feature is the performance bottleneck of the new front-end, even for models that actually don't have unit information in their variables (see, e.g. the AdvectionReaction models of the ScalableTestSuite).
    22
    33This may not be a big problem, because unit testing usually makes sense when developing new models, and that is normally done using small scale test models, so making this module faster is really not a high priority.