Repository navigation
e2e: settings-UI specs fail in a full run under load #2207
Description
What happens
In a full native e2e run on a busy machine (load average 13 to 24), three settings-UI specs failed:
tests/e2e/empty-format-default.test.ts(3 tests)tests/e2e/external-settings-change.test.ts("merges a choice edited here and a different choice edited elsewhere in the same second")tests/e2e/global-var-autocomplete.test.ts(timed out after 10 s)
Rerun alone on a fresh instance, all 9 tests in those files passed, still at load 24. The same files passed in the full run on the previous commit. None of the code under test had changed.
Expected
These specs pass in a full run under load, or wait on the state they assert instead of on time. Found during the 2.32.0 release (#2199).
Activity
test(e2e): fail when a native spec writes Obsidian's vault config
test(e2e): set vault options in memory so a restore holds under load
test(e2e): set vault options in memory so a restore holds under load (c…