-
Notifications
You must be signed in to change notification settings - Fork 191
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
revise taskkill procedure on windows #267
Merged
Merged
Changes from all commits
Commits
Show all changes
37 commits
Select commit
Hold shift + click to select a range
8059485
add lh and smoke ci
paulirish 059ca08
ci on branches
paulirish ad6e637
tweaks
paulirish 9346117
extra logging
paulirish 16364c3
log stderrout
paulirish 262dd6a
link
paulirish 8a9c768
more logging
paulirish 4728b80
Revert "more logging"
paulirish 8898ba3
bring back reject
paulirish 59829a8
extra kill
paulirish 8b723c4
hmm
paulirish 35a8fe7
Revert "Revert "more logging""
paulirish 31c1a16
log it out
paulirish 6674664
k
paulirish 4a2679f
trace
paulirish b7b7b6c
kill catch
paulirish 210c7e0
encoding
paulirish 0bea7c7
drop cl changes
paulirish 08e8ef1
just pr
paulirish 2a4f4e7
spawn chrome non-detached on windows
paulirish 210f2bf
rename chrome => chromeProc
paulirish 9d5b507
adopt much of playwright's kill approach
paulirish 4771eaf
headless thing
paulirish bde6f3a
take lh github master out of lockfile
paulirish d84ba2b
install and add -D lh at same time
paulirish d395385
drop diff
paulirish 8353ed6
upload artifacts path
paulirish 537054f
Merge branch 'lighthouse-smoke' into adopt-pw-kill
paulirish 402f785
fixlogs
paulirish 85034bd
other windows smoketests beyond just lantern
paulirish 0f3786d
formatting
paulirish 8994710
Merge branch 'lighthouse-smoke' into adopt-pw-kill
paulirish 39b7d6f
no retries. hardmode
paulirish c32034d
utf8 encoding
paulirish c1a9b54
less
paulirish 05a9c54
Merge branch 'master' into adopt-pw-kill
paulirish 3f7b664
chromeProc -> chromeProcess
paulirish File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
The smoke tests still pass even with this rejection right?
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.
no they don't.
removing this rejection is deliberate actually. as mentioned in #266, pptr and pw deliberately do not reject in this case.
and i've been convinced that this is reasonable. there appears to be a race condition and taskkill is attempting to kill processes that are already gone. what's interesting is that when this happens. the processes that fail to be killed (cuz they're not found) are all child proc of the primary chrome proc. the chrome proc is always successfully killed.
take a peek at the SO item linked in microsoft/playwright#7500 .... PW used this
MEMUSAGE
hack for a while but then determined it wasnt needed. so i'm following their latest pattern.i think it's still important we have some visibility on when taskkill returns an error, but it's not a fatal situation.
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.
They removed it because
Which we also do not do so lgtm.