You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 30, 2020. It is now read-only.
I am using plugin version 3.3.1 and I observed that behavior of error message changed in a recent version. I have around 20 simulations as part of test suite and when there is a failure in one of them, the error message now reads "There're failed simulations: simulation1FQN, simulation2FQN, ..., simulation20FQN" when in fact only one simulation failed. This is tedious for us to check all the simulation reports to see which actually failed.
This used to work properly before where the error message was "Some simulations failed: failedSimulationFQN".
I've tracked down the problem to an enhancement commit 82ad702#diff-7bc60cc739fa8b7bb64a003d960de9ebR85-R86. If you now look at the marked lines, the message now logs all simulations instead of just failed simulations. I would like this behavior to be restored.
Thanks,
Anoop
The text was updated successfully, but these errors were encountered:
I am using plugin version
3.3.1
and I observed that behavior of error message changed in a recent version. I have around 20 simulations as part of test suite and when there is a failure in one of them, the error message now reads "There're failed simulations: simulation1FQN, simulation2FQN, ..., simulation20FQN" when in fact only one simulation failed. This is tedious for us to check all the simulation reports to see which actually failed.This used to work properly before where the error message was "Some simulations failed: failedSimulationFQN".
I've tracked down the problem to an enhancement commit 82ad702#diff-7bc60cc739fa8b7bb64a003d960de9ebR85-R86. If you now look at the marked lines, the message now logs all simulations instead of just failed simulations. I would like this behavior to be restored.
Thanks,
Anoop
The text was updated successfully, but these errors were encountered: