don't wait for analyzer propagation in 3.6, as it will likely time out

[jsteemann]

Don't call /_api/analyzer/${name} in 3.6, because analyzers are propagated in the cluster with an up-to 60 second delay in that version. Waiting for the analyzers to propagate to all coordinators will very likely make the tests time out. In 3.7, the analyzer propagation is almost instantenously, so we can rely on the mechanism of calling /_api/analyzer/${name} on all coordinators.

Note: this requires that the backend version number is set correctly when running the tests. In src/tests/_config.ts, there is:

const ARANGO_VERSION = Number(
  process.env.ARANGO_VERSION || process.env.ARANGOJS_DEVEL_VERSION || 39999
);

So ARANGO_VERSION should be set to 30600 or 30700 or whatever is accurate when running the tests. Otherwise version 3.99.99 will be assumed!

[KVS85]

• 3.7: http://jenkins.arangodb.biz:8080/job/arangodb-ANY-arangojs-driver-matrix/1204/
• 3.6: http://jenkins.arangodb.biz:8080/job/arangodb-ANY-arangojs-driver-matrix/1205/

[KVS85]

http://jenkins.arangodb.biz:8080/job/arangodb-ANY-arangojs-driver-matrix/1207/