test(load-database): fix EPERM error in windows

[curbengh]

What does it do?

Continuation of #3975

Add workarounds for more reliable unit testing on Windows in CI env.

How to test

git clone -b BRANCH https://github.com/USER/hexo.git
cd hexo
npm install
npm test

Screenshots

Pull request tasks

• Add test cases for the changes.
• Passed the CI test.

[coveralls]

Coverage remained the same at 97.706% when pulling 1cd60a1 on curbengh:db-load-windows-2 into 5c098cc on hexojs:master.

[SukkaW]

Strangely.

Travis build is fine in my newest PR #4070. It looks like the E*** issue only occurs occasionally.

[curbengh]

It looks like the E*** issue only occurs occasionally.

the behavior is erratic. Console - generate - watch - delete is also inconsistent.

[curbengh]

Still have soft error in Node 8 Windows:

Unhandled rejection Error: ENOENT: no such file or directory, stat 'C:\Users\travis\build\hexojs\hexo\test\scripts\processors\source\foo.jpg'

#4037 may help (or not, see hexojs/hexo-fs#49 hexojs/hexo-fs#50).

[SukkaW]

@curbengh What about patch watch() - rename folder as well? My local machine (WSL 1) always failed on this item.

[curbengh]

Have you tried reverting #3965?

Check the folder box_tmp/test/a and b.txt's ownership and permission after this line,

hexo/test/scripts/box/box.js

Line 525 in 5c098cc

writeFile(src, 'a'),

[SukkaW]

@curbengh That error is not related with #3965. I believe WSL and its file watch strategy should be blamed.

[curbengh]

Another workaround I can think of is adding a delay (as used in this PR), await Promise.delay(300), perhaps before or after or both,

hexo/test/scripts/box/box.js

Line 528 in 5c098cc

await box.watch();

---

Node's FS api can be tricky in Windows microsoft/azure-pipelines-tasks#5472

[curbengh]

@SukkaW

If the workaround doesn't work, then this PR is ready (I can't think of any other workaround).

[SukkaW]

LGTM!