Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(66)

Side by Side Diff: docs/using_a_linux_chroot.md

Issue 2695963002: Update web-platform-tests docs (Closed)
Patch Set: Created 3 years, 10 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « docs/testing/writing_layout_tests.md ('k') | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Using a chroot 1 # Using a chroot
2 2
3 If you want to run layout tests and you're not running Lucid, you'll get errors 3 If you want to run layout tests and you're not running Lucid, you'll get errors
4 due to version differences in libfreetype. To work around this, you can use a 4 due to version differences in libfreetype. To work around this, you can use a
5 chroot. 5 chroot.
6 6
7 ## Basic Instructions 7 ## Basic Instructions
8 8
9 * Run `build/install-chroot.sh`. On the prompts, choose to install a 64-bit 9 * Run `build/install-chroot.sh`. On the prompts, choose to install a 64-bit
10 Lucid chroot and activate all your secondary mount points. 10 Lucid chroot and activate all your secondary mount points.
(...skipping 62 matching lines...) Expand 10 before | Expand all | Expand 10 after
73 [run tests headless](layout_tests_linux.md#Using-an-embedded-X-server). 73 [run tests headless](layout_tests_linux.md#Using-an-embedded-X-server).
74 74
75 ### Having layout test results open in a browser 75 ### Having layout test results open in a browser
76 76
77 After running layout tests, you should get a new browser tab or window that 77 After running layout tests, you should get a new browser tab or window that
78 opens results.html. If you get an error "Failed to open 78 opens results.html. If you get an error "Failed to open
79 file:///path/to/results.html, check the 79 file:///path/to/results.html, check the
80 following conditions. 80 following conditions.
81 81
82 1. Make sure `DISPLAY` is set. See the 82 1. Make sure `DISPLAY` is set. See the
83 [Running X apps](#Running_X_apps) section above. 83 [Running X apps](#Running-X-apps) section above.
84 1. Install `xdg-utils`, which includes `xdg-open`, a utility for finding the 84 1. Install `xdg-utils`, which includes `xdg-open`, a utility for finding the
85 right application to open a file or URL with. 85 right application to open a file or URL with.
86 1. Install [Chrome](https://www.google.com/intl/en/chrome/browser/). 86 1. Install [Chrome](https://www.google.com/intl/en/chrome/browser/).
OLDNEW
« no previous file with comments | « docs/testing/writing_layout_tests.md ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698