summaryrefslogtreecommitdiff
path: root/qa/vagrant
diff options
context:
space:
mode:
authorNik Everett <nik9000@gmail.com>2016-11-02 11:29:15 -0400
committerNik Everett <nik9000@gmail.com>2016-11-02 12:38:51 -0400
commit24d5f31a545599cf6a46cec7d86668c531313e50 (patch)
tree0d882038cddfc77c86a757b5d4d9860fa5ef8e9b /qa/vagrant
parent799a12ad63b35faa539d50e7d8720c05036399fd (diff)
Make painless's assertion about out of bound less brittle
Instead of asserting that the message is shaped a certain way we cause the exception and catch it and assert that the messages are the same. This is the way to go because the exception message from the jvm is both local and jvm dependent. This is the CI failure that found this: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+5.x+java9-periodic/515/consoleFull
Diffstat (limited to 'qa/vagrant')
0 files changed, 0 insertions, 0 deletions