| commit | d022034ea0563a2ee2a41e7b5475e135e3a6596d | [log] [tgz] |
|---|---|---|
| author | Steffen Meschkat <mesch@google.com> | Mon Dec 17 13:37:14 2018 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Dec 18 00:08:21 2018 +0000 |
| tree | 67ebc7389de6779ec23356fe5cd289d49ad19d95 | |
| parent | 9532c6af8d4aa389f16ef5afdc284dba13f71fc4 [diff] |
[modular tests] Increase robustness against timeout. The way we use timeouts is not robust, because on slow machines tests just take longer and might run into timeouts. Until we can control time better, a few mitigations: * For all integration tests, increase total integration test timeout used by default in dev_base_shell from 15s to 30s. * In the link_data test, stop a story before delete, so we are less likely to hit the total sessionmgr teardown timeout at the end of the test. * Also in the link_data test, Signal() to base shell that the test is at the end, rather than to Logout() outright. This doesn't affect timeouts, but is just more uniform. TESTED=/pkgfs/packages/modular_tests/0/test/run_modular_tests.sh on a chromebook. Change-Id: Icdba9d12544a42d8eb5b3cf3286e70d7927ad7db
Peridot is a framework for composed, intelligent and distributed user experiences.
Applications not explicitly designed to interoperate (and possibly implemented in different programming languages) are ephemerally downloaded and dynamically composed to run in a shared context. The framework manages application lifecycle, resources and view hierarchy; and well as context and suggestion infrastructure.
State of Peridot experiences is transparently synchronized across user devices using a distributed offline-first storage system.