-
Notifications
You must be signed in to change notification settings - Fork 6.8k
chore(e2e): fix consistent timeouts #6574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
99a9177
to
f1e780a
Compare
Ready for review. Being perfectly honest, I'm not 100% sure why this fixes the issue. My theory is that adding the extra |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does make sense why this stopped the timeouts, it still doesn't explain why the Gulp task wasn't completing on its own (which usually logs "Completed {{taskName}}" and exits the process). The task should complete if the promise resolves or rejects.
return downloadGoldScreenshotFiles(database); | ||
}) | ||
.then(() => { | ||
console.log(` Downloading golds done (took ${Date.now() - lastActionTime}ms)`); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want these to be formatted better, you can import {log} from 'gulp-util'
.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
No description provided.