jaredhirsch

win/chrome: 9/10 success
  1 mysterious health-check failure

  #4:
    health-check: mysterious failure similar to IE failures.
      https://saucelabs.com/tests/7738aee799934079ae4ee20202a5a383#
      -- I really think we need to get rid of that checking body for a class stuff.

win/ff: 8/10 success
  3 personatestuser outage (irrelevant to wait-related stability)

jaredhirsch

**QUESTION**: Are tests any faster if we use implicit waits (onboard the 
              remote browser) or explicit waits (polling remotely & setting
              browser waits to 0)?

**ANSWER**: There's no significant difference. The difference is less than
            10% on average. This isn't a significant factor in choosing the
            wait implementation to use in writing tests.

**DATA**:

jaredhirsch

**QUESTION**

Some folks assert that a broad class of bugs is solved by favoring
explicit over implicit waits. We had previously been using implicit
waits by default in our code.

**ANSWER**

No substantial stability differences were observed.
Failures across chrome, ff, ie9, ie8:

jaredhirsch

TL;DR skip to the summary for the bash one-liner if so inclined :-)

Why & wherefore

I have an old tumblr that I want to back up. I don't use it regularly, but I want to have a backup of the whole site, design as well as content, just in case; it's not just the pictures I love, but the whole thing. I'm not particularly worried about downloading the streaming audio--can't help you there, gentle reader.

jaredhirsch

diff --git a/automation-tests/config/tests-to-ignore.js b/automation-tests/config/tests-to-ignore.js
index e2e4acd..b2ae522 100644
--- a/automation-tests/config/tests-to-ignore.js
+++ b/automation-tests/config/tests-to-ignore.js
@@ -3,8 +3,19 @@
  * file, You can obtain one at http://mozilla.org/MPL/2.0/. */
 
 // These are tests to ignore
+// XXX extract duplication if this file gets significantly longer
 

jaredhirsch

ETags & If-None-Match headers: a dialogue

1st request.

browser: can haz foo?

GET /foo HTTP/1.1

1st response.

jaredhirsch

ETags: a pretty sweet feature of HTTP 1.1

HTTP caching review

HTTP provides two ways for servers to control client-side caching of page components:

• freshness may be based on a date or a token whose meaning is app-specific
• whether or not the client needs to confirm the cached version is up-to-date with the server

This breaks down as follows:

• Cache locally and don't check before using.

jaredhirsch

zen of running a company.

lead by not leading.

prioritize by imposing no priorities.

build culture by not building culture.

jaredhirsch

diff --cc bin/keysigner
index db7e49a,1f668ba..0000000
--- a/bin/keysigner
+++ b/bin/keysigner
@@@ -22,7 -23,7 +23,11 @@@ heartbeat = require('../lib/heartbeat')
  shutdown = require('../lib/shutdown'),
  computecluster = require('compute-cluster'),
  urlparse = require('urlparse'),
++<<<<<<< HEAD
 +toobusy = require('../lib/busy_middleware.js');

jaredhirsch

# On branch b2g-merge
# Changes to be committed:
#
#  modified:   .awsbox.json
#	new file:   config/b2g.json
#	modified:   config/local.json
#	modified:   example/rp/index.html
#	new file:   lib/boolean-query.js
#	modified:   lib/configuration.js
#	modified:   lib/db.js