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

Unified Diff: sky/HACKING.md

Issue 875513002: Docs: Update formatting of skydb help (Closed) Base URL: https://github.com/domokit/mojo.git@master
Patch Set: Created 5 years, 11 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 side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: sky/HACKING.md
diff --git a/sky/HACKING.md b/sky/HACKING.md
index a77644f49ed8d7bb680217064b0b9ff998c1f563..217ad6827a4ad405545e7514c91e4fc82ec5e8cf 100644
--- a/sky/HACKING.md
+++ b/sky/HACKING.md
@@ -14,13 +14,16 @@ Running applications
* ``./sky/tools/skydb start out/Debug [url]``
- `skydb` has numerous commands, visible via skydb help. Common ones include:
- * skybd start BUILD_DIR [url]
- * skydb load [url]
- * skydb stop
- * skydb print_crash # Symbolicate the most recent crash from android.
+ `skydb` has numerous commands, visible via `skydb help`. Common ones include:
+ * `skybd start` BUILD_DIR [url]
+ * `skydb load` [url]
+ * `skydb stop`
+ * `skydb print_crash` # Symbolicate the most recent crash from android.
-Once skydb start is issued, all subsequent commands will be sent to the running mojo_shell instance (even on an attached android device). skydb start reads gn args from the passed build directory to determine whether its using android, etc.
+Once `skydb start` is issued, all subsequent commands will be sent to
+the running mojo_shell instance (even on an attached android device).
+`skydb start` reads gn args from the passed build directory to
+determine whether its using android, etc.
* ``./sky/tools/test_sky --debug``
* This runs the tests against ``//out/Debug``. If you want to run against
@@ -62,13 +65,15 @@ uploaded file in the reference.
2. Create an dummy reference file (foo-expected.sky).
3. Run the test (it will fail).
4. Copy the -actual.png file to googlestorage (see below).
-5. Put an <img> pointing to your newly uploaded png in the reference file at
+5. Put an ``<img>`` pointing to your newly uploaded png in the reference file at
http://storage.googleapis.com/mojo/sky-pngs/SHA1_HASH_HERE
Copying the file to googlestorage:
+```bash
$ sha1sum ../out/Debug/layout-test-results/framework/flights-app-pixels-actual.png
db0508cdfe69e996a93464050dc383f6480f1283 ../out/Debug/layout-test-results/framework/flights-app-pixels-actual.png
$ gsutil.py cp ../out/Debug/layout-test-results/framework/flights-app-pixels-actual.png gs://mojo/sky-pngs/db0508cdfe69e996a93464050dc383f6480f1283
+```
Long-term, we should not have these tests at all and should just
dump paint commands. In the short-term, if we find we're doing this
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698