| commit | 5803d1c121b113aa53f17daadc5f529368799a39 | [log] [tgz] |
|---|---|---|
| author | Manali Bhutiyani <manalib@google.com> | Tue Jul 07 22:31:37 2020 +0000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jul 07 22:31:37 2020 +0000 |
| tree | 9c457f52b3b59a5db4666f5a21331e3fe44a571c | |
| parent | f81f346c8cba2272d5881c03e28c45289fb1e836 [diff] |
[blobfs] test flake: Mitigate by removing check for the time being since the corruption api call is fire and forget, on slower devices, there might be a race between sending a notification and immediately checking if the other thread received it The short term solution is to remove the check. The long term solution is the following: Either change the api to wait on a reply (and spawn a different thread in blobfs) This has the weirdness, that if the blob is deleted before the notification is received by the main thread of pkg-cache, it might be an issue second option is to change the test on some kind of wait i.e conditionally wait for the check to be true Change-Id: Ibb9c6ff873b0a52acc1239abebd875d99d28e5f5 Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/404807 Commit-Queue: Manali Bhutiyani <manalib@google.com> Reviewed-by: Marie Janssen 💖 <jamuraa@google.com> Reviewed-by: James Sullivan <jfsulliv@google.com> Testability-Review: Marie Janssen 💖 <jamuraa@google.com>
Pink + Purple == Fuchsia (a new operating system)
Fuchsia is a modular, capability-based operating system. Fuchsia runs on modern 64-bit Intel and ARM processors.
Fuchsia is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.
See Getting Started.
See fuchsia.dev.