I saw the same error when running tempest against diablo. I assumed it was a diablo bug that was fixed in essex. I changed the test to skip on diablo but perhaps it is a real essex nova bug that is triggered by the old diablo flavor list but not the new essex one.
I saw the same error when running tempest against diablo. I assumed it was a diablo bug that was fixed in essex. I changed the test to skip on diablo but perhaps it is a real essex nova bug that is triggered by the old diablo flavor list but not the new essex one.