Re: Running Roboto Tests locally?
thanks for the link. Quick review ...
- the initial warnings are obviously from the container startup, not harmful
- InterruptedExceptions -- I think Michal Rehak was working around that (if I overheard and remembered the conversation correctly)
- the did not pass canCommit/commit failed messages come from asynchronous writes and strict datastore. they usually indicate the data being written has been modified while the write was being set up, hinting at unsychronized or racy access
- the session cookie exceptions seem to be normal if switches come and go -- maybe we could downgrade them
By the looks of it this should not be hard to get stabilized as a matter of two-three weeks -- unless they end up uncovering something very significantly wrong in app design.
On 05/07/2014 10:23 PM, Luis Gomez wrote: