testing timeout for developers

[huss]

Sometimes a test times out on a developer machine because the DB is slow in resetting between tests. @huss put in a --timeout 15000 on the mocha test to mostly avoid. Need to decide if it should stay and if the healthcheck (if ever works) would be better. This was tried but did not yet work: volumes:

healthcheck:

This checks if postgres is ready for work.

test: ["CMD-SHELL", "pg_isready -U postgres"]

interval: 5s

timeout: 5s

retries: 5

We try to get around this during the install by looping to try the DB setup if postgres says it is not yet ready.

[huss]

The tests modified by PR #660 using this.timeout in src/server/test/db/newCompressedReadingsTests.js shows a way to change the timeout for a single test. This might be interesting to limit timeout for other tests but does not address the fundamental problem.