Searched refs:happened (Results 1 – 25 of 316) sorted by relevance
12345678910>>...13
| /third_party/pulseaudio/src/pulsecore/ |
| D | poll-win32.c | 158 int i, ret, happened; in windows_compute_revents() local
178 happened = 0; in windows_compute_revents()
182 happened |= *p_sought & (POLLIN | POLLRDNORM); in windows_compute_revents()
185 happened |= POLLHUP; in windows_compute_revents()
206 happened |= *p_sought & (POLLOUT | POLLWRNORM | POLLWRBAND); in windows_compute_revents()
208 return happened; in windows_compute_revents()
257 int happened = 0; in windows_compute_revents_socket() local
260 happened |= (POLLIN | POLLRDNORM) & sought; in windows_compute_revents_socket()
273 happened |= (POLLIN | POLLRDNORM) & sought; in windows_compute_revents_socket()
278 happened |= POLLHUP; in windows_compute_revents_socket()
[all …]
|
| /third_party/openh264/autotest/unitTest/ |
| D | run_unitTest.sh | 43 echo There is something wrong happened when runing unittest on android devices,please to check
61 echo There is something wrong happened when runing unittest on ios devices,please to check
|
| /third_party/flutter/flutter/packages/flutter/test/widgets/ |
| D | custom_multi_child_layout_test.dart | 99 // Layout happened because the delegate was set.
100 expect(delegate.performLayoutSize, isNotNull); // i.e. layout happened
110 // Layout happened because shouldRelayout() returned true.
|
| D | custom_single_child_layout_test.dart | 123 // Layout happened because the delegate was set.
125 isNotNull); // i.e. layout happened
135 // Layout happened because shouldRelayout() returned true.
|
| /third_party/node/deps/npm/node_modules/verror/ |
| D | README.md | 99 of what it was doing. The end result is a message that explains what happened
125 code to provide a more complete description of what happened. Instead of saying
377 var err1 = new VError('something bad happened');
397 failed to connect to "127.0.0.1:215": something bad happened
400 ConnectionError: failed to connect to "127.0.0.1:215": something bad happened
431 request failed: failed to connect to "127.0.0.1:215": something bad happened
434 RequestError: request failed: failed to connect to "127.0.0.1:215": something bad happened
448 var err1 = new VError('something bad happened');
450 var err2 = new VError(err1, 'something really bad happened here');
457 VError: something really bad happened here: something bad happened
[all …]
|
| /third_party/e2fsprogs/scrub/ |
| D | e2scrub_fail.in | 36 A log of what happened follows:
|
| /third_party/flutter/skia/third_party/externals/harfbuzz/ |
| D | RELEASING.md | 33 That's what happened to 2.0.0 going out with 1.8.0 hb-version.h... So, that's
64 files against their previous releases to make sure nothing bad happened.
|
| /third_party/boost/libs/python/doc/reference/ |
| D | module.qbk | 30 throw "something bad happened"
|
| /third_party/openh264/autotest/unitTest/android/ |
| D | run_AutoTest_android.sh | 104 echo There is something wrong happened when run ${apk_name}
|
| /third_party/typescript_eslint/.github/ISSUE_TEMPLATE/ |
| D | typescript-eslint-utils.md | 52 What actually happened?
|
| D | typescript-estree.md | 55 What actually happened?
|
| D | typescript-eslint-parser.md | 67 What actually happened?
|
| D | eslint-plugin-tslint.md | 70 What actually happened?
|
| D | eslint-plugin-typescript.md | 68 What actually happened?
|
| /third_party/typescript_eslint/.github/ |
| D | ISSUE_TEMPLATE.md | 55 What actually happened?
|
| /third_party/node/deps/npm/node_modules/lockfile/ |
| D | README.md | 20 // er means that an error happened, and is probably bad.
|
| /third_party/flutter/flutter/.github/ISSUE_TEMPLATE/ |
| D | performance.md | 42 can have an intuitive understanding of what happened. Don’t use
|
| /third_party/node/doc/api/ |
| D | console.md | 32 console.error(new Error('Whoops, something bad happened'));
34 // Error: Whoops, something bad happened
59 myConsole.error(new Error('Whoops, something bad happened'));
60 // Prints: [Error: Whoops, something bad happened], to err
|
| /third_party/openh264/autotest/performanceTest/android/ |
| D | run_AutoTest_android.sh | 172 echo There is something wrong happened when run ${apk_name}
|
| /third_party/libwebsockets/READMEs/ |
| D | README.cmake.md | 37 CMake keeps a log of what happened with the failed test programs in
|
| /third_party/curl/docs/libcurl/ |
| D | ABI.md | 52 compatibility) happened the following times:
|
| /third_party/flutter/flutter/packages/flutter/test/services/ |
| D | platform_channel_test.dart | 125 'Something happened',
135 expect(e.message, equals('Something happened'));
|
| /third_party/flutter/skia/third_party/externals/sdl/premake/ |
| D | README-linux.txt | 5 progress made on this support happened toward the end of the meta-build system
|
| /third_party/typescript/.github/ISSUE_TEMPLATE/ |
| D | Bug_report.md | 69 <!-- What happened, and why it was wrong -->
|
| /third_party/grpc/doc/ |
| D | connectivity-semantics-and-api.md | 54 a shutdown or if a non-recoverable error has happened during attempts to connect
131 should just inform the user that some state change has happened, leaving it to
|
12345678910>>...13