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
Mussel acceptance tests continue to execute, even after fatal error
has already occurred. This can be seen in the following test, which
continues to execute even when $DCMGR_HOST is not set correctly. The
test should stop after the first call to curl can not reach dcmgr.
Other tests probably have this same problem.
Not sure. Need to look at the current exception framework and see if
it is being used, and perhaps just use it more effectively. Or maybe
some new exception strategy or framework would be worth implementing.
For one test, this may not be worth fixing. On the other
hand, a clean solution could have other side benefits: (faster mussel
client, better error messages, cleaner logs, better Jenkins slave
utilization)
The text was updated successfully, but these errors were encountered:
Problem:
Mussel acceptance tests continue to execute, even after fatal error
has already occurred. This can be seen in the following test, which
continues to execute even when $DCMGR_HOST is not set correctly. The
test should stop after the first call to curl can not reach dcmgr.
Other tests probably have this same problem.
Solution:
Not sure. Need to look at the current exception framework and see if
it is being used, and perhaps just use it more effectively. Or maybe
some new exception strategy or framework would be worth implementing.
For one test, this may not be worth fixing. On the other
hand, a clean solution could have other side benefits: (faster mussel
client, better error messages, cleaner logs, better Jenkins slave
utilization)
The text was updated successfully, but these errors were encountered: