crostini: Adding extra logging and promise resolution to flaky test
It appears that the test is failing in between tests, which implies that there may be errors in the setup/teardown. Adding extra logging to see if the teardown completes successfully and also adding some extra functionality to reject any unresolved promises at the end of each test, as the unresolved tests may be causing mocha to hang. Also added some extra logging to the js code itself, to help identify which promises are being unresolved. Bug: 1082027 Change-Id: I4eaefe54aaffd8a513bd158f713e4d1fa963f4af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2245574 Commit-Queue: Daniel Ng <danielng@google.com> Reviewed-by:Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#778622}
Showing
Please register or sign in to comment