Skip to content
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

fix(start): wait for emulated android to really be ready before signaling #161

Merged
merged 1 commit into from
Nov 28, 2016

Conversation

sjelin
Copy link
Contributor

@sjelin sjelin commented Nov 24, 2016

Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be
booted up and ready to instance chrome.

While I was doing that I moved some stuff into lib/utils.ts since I felt like too much of
lib/cmds/start.ts was being devoted to this one feature.

Additionally, --started-signifier wasn't sending anything to the console, so I fixed that too (see #166)

@sjelin sjelin force-pushed the started_api branch 8 times, most recently from 4590b30 to f3bda88 Compare November 24, 2016 09:28
@sjelin
Copy link
Contributor Author

sjelin commented Nov 24, 2016

Blocked on #163

@sjelin sjelin force-pushed the started_api branch 3 times, most recently from 9846f02 to 4bbae01 Compare November 28, 2016 22:01
@sjelin
Copy link
Contributor Author

sjelin commented Nov 28, 2016

Unblocked!

error.message + ')');
})
.then<string>(() => {
logger.info('Waiting on for ' + avdName + ' to be ready to launch chrome');
Copy link
Contributor

Choose a reason for hiding this comment

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

'Waiting for '

@@ -422,6 +438,7 @@ function sendStartedSignal(signal: string, viaIPC: boolean) {
logger.warn('No IPC channel, sending signal via stdout');
}
}
console.log(signal);
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this supposed to be here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes. The signal goes to stdout if it isn't send by and IPC channel. This functionality was accidentally removed in 1f9713a, and I fixed it while debugging this PR. I could make a issue to document the bug/fix if you'd like

Copy link
Contributor

Choose a reason for hiding this comment

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

Ah, I see. Yeah, it'd be nice to have a short comment explaining that.

@heathkit
Copy link
Contributor

lgtm, minor nits

…ling

Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be
booted up and ready to instance chrome.

While I was doing that I moved some stuff into `lib/utils.ts` since I felt like too much of
`lib/cmds/start.ts` was being devoted to this one feature.

Also closes angular#166
@sjelin sjelin merged commit 26586f1 into angular:master Nov 28, 2016
@sjelin sjelin deleted the started_api branch November 28, 2016 22:56
sjelin added a commit to sjelin/webdriver-manager that referenced this pull request Dec 16, 2016
…ling (angular#161)

Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be
booted up and ready to instance chrome.

While I was doing that I moved some stuff into `lib/utils.ts` since I felt like too much of
`lib/cmds/start.ts` was being devoted to this one feature.

Also closes angular#166
sjelin added a commit to sjelin/webdriver-manager that referenced this pull request Dec 20, 2016
…ling (angular#161)

Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be
booted up and ready to instance chrome.

While I was doing that I moved some stuff into `lib/utils.ts` since I felt like too much of
`lib/cmds/start.ts` was being devoted to this one feature.

Also closes angular#166
sjelin added a commit to sjelin/webdriver-manager that referenced this pull request Dec 20, 2016
…ling (angular#161)

Before, we were just waiting for the emulator to be running, rather than waiting for the OS to be
booted up and ready to instance chrome.

While I was doing that I moved some stuff into `lib/utils.ts` since I felt like too much of
`lib/cmds/start.ts` was being devoted to this one feature.

Also closes angular#166
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants