mirror of https://github.com/status-im/consul.git
c8dfe43d29
During development a HTTP request will pause for 1 minute ONLY when an ?index is set. This gives a realistic emulation of blocking queries. During testing we can change this latency when we are testing blocking queries, which we do in numerous places. A problem can arise during testing on a very slow machine. If you are not testing blocking queries and therefore not set a latency to test with, if the machine you are testing on is slow enough a normal page can assert during a test, yet not tear down before a further blocking query request is made. This blocking query then uses the default latency which cause the page to hang for 1 minute, which in turn causes the test to timeout. This only seems to happen on a very slow system, but it does potentially explain why we occasionally see the odd flakey test popping up. |
||
|---|---|---|
| .. | ||
| .gitkeep | ||
| api.js | ||
| destroy-app.js | ||
| flash-message.js | ||
| get-nspace-runner.js | ||
| measure.js | ||
| module-for-acceptance.js | ||
| normalizers.js | ||
| repo.js | ||
| set-cookies.js | ||
| stub-super.js | ||
| type-to-url.js | ||
| yadda-annotations.js | ||