Skip to content

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

Merged
merged 1 commit into from
Aug 22, 2017
Merged

chore(e2e): fix consistent timeouts #6574

merged 1 commit into from
Aug 22, 2017

Conversation

jelbourn
Copy link
Member

No description provided.

@jelbourn jelbourn added the in progress This issue is currently in progress label Aug 21, 2017
@jelbourn jelbourn requested a review from devversion as a code owner August 21, 2017 19:48
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 21, 2017
@jelbourn jelbourn force-pushed the e2e-hang branch 2 times, most recently from 99a9177 to f1e780a Compare August 21, 2017 21:35
@jelbourn jelbourn changed the title wip e2e hang chore(e2e): fix consistent timeouts Aug 21, 2017
@jelbourn jelbourn requested review from crisbeto and tinayuangao and removed request for devversion August 21, 2017 22:21
@jelbourn jelbourn added pr: needs review and removed in progress This issue is currently in progress labels Aug 21, 2017
@jelbourn
Copy link
Member Author

Ready for review.

Being perfectly honest, I'm not 100% sure why this fixes the issue. My theory is that adding the extra log statements just prevents Travis from thinking the task timed out.

Copy link
Contributor

@kara kara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kara kara added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels Aug 22, 2017
Copy link
Member

@crisbeto crisbeto left a 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)`);
Copy link
Member

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'.

@kara kara merged commit e0b1094 into angular:master Aug 22, 2017
@jelbourn jelbourn deleted the e2e-hang branch April 2, 2018 22:30
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants