| /external/mobile-data-download/javatests/com/google/android/libraries/mobiledatadownload/file/behaviors/ |
| D | SyncingBehaviorAndroidTest.java | 58 SyncingBehavior syncing = new SyncingBehavior(); in syncing_sync() local
59 try (OutputStream out = storage.open(uri1, WriteStreamOpener.create().withBehaviors(syncing))) { in syncing_sync() argument
64 syncing.sync(); in syncing_sync()
|
| D | BUILD | 52 "//java/com/google/android/libraries/mobiledatadownload/file/behaviors:syncing",
|
| /external/mobile-data-download/javatests/com/google/android/libraries/mobiledatadownload/file/openers/ |
| D | StringOpenerTest.java | 71 SyncingBehavior syncing = Mockito.spy(new SyncingBehavior()); in invokes_autoSync() local
72 storage.open(uri1, WriteStringOpener.create("some string").withBehaviors(syncing)); in invokes_autoSync()
73 Mockito.verify(syncing).sync(); in invokes_autoSync()
|
| D | WriteProtoOpenerTest.java | 111 SyncingBehavior syncing = Mockito.spy(new SyncingBehavior()); in invokes_autoSync() local
112 storage.open(uri1, WriteProtoOpener.create(TEST_PROTO).withBehaviors(syncing)); in invokes_autoSync()
113 Mockito.verify(syncing).sync(); in invokes_autoSync()
|
| D | WriteByteArrayOpenerTest.java | 129 SyncingBehavior syncing = Mockito.spy(new SyncingBehavior()); in invokes_autoSync() local
131 uri1, WriteByteArrayOpener.create(makeArrayOfBytesContent()).withBehaviors(syncing)); in invokes_autoSync()
132 Mockito.verify(syncing).sync(); in invokes_autoSync()
|
| D | StreamMutationOpenerTest.java | 182 SyncingBehavior syncing = Mockito.spy(new SyncingBehavior()); in canMutate_withSync() local
184 storage.open(uri, StreamMutationOpener.create().withBehaviors(syncing))) { in canMutate_withSync() argument
192 Mockito.verify(syncing).sync(); in canMutate_withSync()
|
| D | BUILD | 185 "//java/com/google/android/libraries/mobiledatadownload/file/behaviors:syncing",
207 "//java/com/google/android/libraries/mobiledatadownload/file/behaviors:syncing",
401 "//java/com/google/android/libraries/mobiledatadownload/file/behaviors:syncing",
488 "//java/com/google/android/libraries/mobiledatadownload/file/behaviors:syncing",
|
| /external/tremolo/ |
| D | README | 7 When syncing with svn, please ensure that these defects are not
|
| /external/mobile-data-download/java/com/google/android/libraries/mobiledatadownload/file/behaviors/ |
| D | BUILD | 38 name = "syncing",
|
| /external/seccomp-tests/ |
| D | Android.bp | 71 // TODO(rsesek): Remove after syncing in upstream.
|
| D | README.md | 21 1. Configure a remote to use as the source repository (limited to only syncing the master branch):
|
| /external/ipsec-tools/ |
| D | Android.bp | 116 …// Turn off unused XXX warnings. Should be removed/fixed when syncing with upstream. b/18523687, b…
|
| /external/cronet/third_party/metrics_proto/ukm/ |
| D | report.proto | 58 // pref, so is only available if the user is signed-in and syncing.
|
| /external/bpftool/ |
| D | README.md | 9 All the gory details of syncing can be found in `scripts/sync-kernel.sh`
|
| /external/oboe/apps/fxlab/docs/ |
| D | Dev-Guide.md | 22 The `DuplexEngine` is responsible for managing and syncing the input and output Oboe streams for re…
|
| /external/perfetto/protos/perfetto/trace/ftrace/ |
| D | ftrace_event_bundle.proto | 71 // proper clock syncing at parsing time in TraceProcessor. We cannot use the
|
| /external/mesa3d/docs/relnotes/ |
| D | 18.2.1.rst | 192 - Revert "radeonsi: avoid syncing the driver thread in si_fence_finish"
|
| /external/libxaac/ |
| D | README.md | 67 …HAACPLUS_DEC_CONFIG_PARAM_DISABLE_SYNC | Sets the flag of ADTS syncing or not ADTS syncing as 0 or…
|
| /external/cronet/third_party/metrics_proto/ |
| D | chrome_user_metrics_extension.proto | 150 // and syncing.
|
| D | omnibox_event.proto | 393 // profile on this device, and all other devices syncing with this
399 // device. Note that this will soon be across syncing devices with the
|
| /external/libbpf/ |
| D | README.md | 5 All the gory details of syncing can be found in `scripts/sync-kernel.sh`
|
| /external/e2fsprogs/doc/RelNotes/ |
| D | v1.19.txt | 19 working well since ext3 is much less aggressive about syncing blocks to
|
| /external/ltp/android/ |
| D | README.md | 85 Sometimes you need to perform this step after syncing:
|
| /external/AFLplusplus/docs/ |
| D | fuzzing_in_depth.md | 201 (address sanitizer) anyway after syncing test cases from other fuzzing
668 The syncing process itself is very simple. As the `-M main-$HOSTNAME` instance
|
| /external/markdown/docs/ |
| D | contributing.md | 501 [sync changes]: https://help.github.com/articles/syncing-a-fork
|