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

tests(devtools): fix webserver #12236

Merged
merged 3 commits into from
Mar 12, 2021
Merged

tests(devtools): fix webserver #12236

merged 3 commits into from
Mar 12, 2021

Conversation

connorjclark
Copy link
Collaborator

Fixes #12209

@connorjclark connorjclark requested a review from a team as a code owner March 11, 2021 22:27
@connorjclark connorjclark requested review from adamraine and removed request for a team March 11, 2021 22:27
@google-cla google-cla bot added the cla: yes label Mar 11, 2021
@@ -17,7 +17,7 @@ export latest_content_shell="$LH_ROOT/.tmp/chromium-web-tests/content-shells/$la
# - /inspector-sources -> the inspector resources from the content shell
# - CORS (Access-Control-Allow-Origin header)

ln -s "$DEVTOOLS_PATH/out/Default/resources/inspector" "$DEVTOOLS_PATH/test/webtests/http/tests/inspector-sources"
ln -s "$latest_content_shell/out/Release/resources/inspector" "$DEVTOOLS_PATH/test/webtests/http/tests/inspector-sources"
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

How I debugged...

I removed the output redirection of the webserver to dev/null and noticed 404s. integration_runner.js was missing. I realized line wasn't doing what the comment suggested... the inspector-sources file is meant to come from content_shell, the reason is that the compiled devtools framework code should match the content shell binary.

I guess integration_runner.js was being generated by devtools before, but no longer is. the incorrect symbolic link was overlooked because of that.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Scratch that. DT team refactored the BUILD rules, and so we weren't building the right thing any more. And the output folder changed slightly.

@@ -2,11 +2,11 @@ Tests that exporting works.

++++++++ testExportHtml

# of .lh-audit divs (original): 137
# of .lh-audit divs (original): 136
Copy link
Member

Choose a reason for hiding this comment

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

What changed here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

file last changed with csp-xss https://github.com/GoogleChrome/lighthouse/commits/master/third-party/chromium-webtests/webtests/http/tests/devtools/lighthouse/lighthouse-export-run-expected.txt

I don't see why this would have changed, since the audit is in experimental, so doesn't show in DT.

@devtools-bot devtools-bot merged commit f620d12 into master Mar 12, 2021
@devtools-bot devtools-bot deleted the dt-test-fix branch March 12, 2021 16:09
paulirish pushed a commit that referenced this pull request Mar 23, 2021
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.

smoke-devtools running indefinitely
3 participants