Bump mocha timeout to 10000 to mitigate potential jenkins issues

[benbp]

Proposing a potential way to address what could be jenkins timeout issues when loading modules in mocha "before" blocks.

@RackHD/corecommitters @tldavies @davidzuhn

[tldavies]

👎 This should try to be fixed via jenkins with lowering the node count for the build slave first.

[davidzuhn]

What do you mean by "lowering the node count for the build slave"?

[tldavies]

So the old build slave for 1.1 release only have 2 nodes. While the new build slave has 4. I would lower that count to 2 again. As that worked in the passed when we had timeouts in jenkins.

Pretty much we dont have this problem when we build on the build machine that 1.1 was. Whats the difference between it and the build machine that 1.2 builds on.

This is also not a problem on the RackHD jenkins. Which makes it look like it is the problem is the difference in the build node.

[davidzuhn]

Do you mean cpus?

[tldavies]

The above photo shows 4 idle reduces it to 2.

[davidzuhn]

Most of the build failures have occurred when that build job was the only one running on the given node.