Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:that (Results 1801 - 1825 of 189771) sorted by null

<<71727374757677787980>>

/prebuilts/go/darwin-x86/test/fixedbugs/
bug257.go	5 // license that can be found in the LICENSE file.     [all...]
/prebuilts/go/linux-x86/test/fixedbugs/
bug257.go	5 // license that can be found in the LICENSE file.     [all...]
/toolchain/binutils/binutils-2.27/gold/testsuite/
weak_undef_test.cc	13 // This program is distributed in the hope that it will be useful, 23 // We test that we correctly deal with weak undefined symbols. 24 // We need to make sure that a weak undefined symbol in the main 25 // program is resolved to zero by the linker and that no dynamic 26 // relocation is generated. We also make sure that a weak undefined 30 // This file will be linked with a shared library that does not 31 // define the symbol, so that the symbol remains undefined. 33 // an alternate shared library that does define the symbol, 34 // so that we can detect whether the symbol was left for runtime 37 // Similarly, this file will be linked with a shared library that     [all...]
/external/autotest/server/cros/cfm/configurable_test/
README.md	4 that clearly describes the steps executed. A sample of a configurable CfM test 24 leaves the meeting. It then verifies that an ATRUS device is visible and that 27 A configurable test can be setup in a `control` file so that third parties 28 that have no easy way to modify other source code can create and modify 40 Besides Actions, a test can be configured with configuration params that affect 49 that we use to test the framework itself.
/external/autotest/server/site_tests/network_WiFi_ReconnectInDarkResume/
control.DisconnectAfterSuspendDiffAP	2 # Use of this source code is governed by a BSD-style license that can be 15 This test verifies that the DUT that suspends connected, then subsequently 17 that later appears while it is still suspended. In this test, the preferred 18 network that appears during suspend is different from the network that the DUT 30 8) Verify that the DUT is connected to AP 1 upon resuming from suspend
control.DisconnectAfterSuspendSameAP	2 # Use of this source code is governed by a BSD-style license that can be 15 This test verifies that the DUT that suspends connected, then subsequently 17 that later appears while it is still suspended. In this test, the preferred 18 network that appears during suspend is the same network that the DUT was last 30 8) Verify that the DUT is connected to AP 2 upon resuming from suspend
control.DisconnectBeforeSuspendDiffAP	2 # Use of this source code is governed by a BSD-style license that can be 13 This test verifies that the DUT that suspends disconnected successfully 14 reconnects to a preferred network that appears while it is suspended. In this 15 test, the preferred network that appears during suspend is different from the 16 one that the DUT was last connected to before suspend. 27 8) Verify that the DUT is connected to AP 1 upon resuming from suspend
control.DisconnectBeforeSuspendSameAP	2 # Use of this source code is governed by a BSD-style license that can be 13 This test verifies that the DUT that suspends disconnected successfully 14 reconnects to a preferred network that appears while it is suspended. In this 15 test, the preferred network that appears during suspend is the same network that 27 8) Verify that the DUT is connected to AP 2 upon resuming from suspend
/external/e2fsprogs/
SUBMITTING-PATCHES	6 patch, which certifies that you wrote it or otherwise have the right to 12 By making a contribution to this project, I certify that: 18 (b) The contribution is based upon previous work that, to the best 20 license and I have the right under that license to submit that 30 (d) I understand and agree that this project and the contribution 31 are public and that a record of the contribution (including all
/external/guava/guava-gwt/src/com/google/common/annotations/
Annotations.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/src/com/google/common/base/
Base.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/src/com/google/common/cache/
Cache.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/src/com/google/common/collect/
Collect.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/src/com/google/common/escape/
Escape.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/src/com/google/common/html/
Html.gwt.xml	9 We used to set this only for packages that had manual supersource. 10 That worked everywhere that I know of except for one place: 12 The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: 14 The summary is that it ignores one file in favor of the other. 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. 21 (I hope that this workaround does not cause its own problems in the future.)
/external/guava/guava-gwt/src/com/google/common/io/
Io.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/src/com/google/common/math/
Math.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/src/com/google/common/primitives/
Primitives.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/src/com/google/common/util/concurrent/
Concurrent.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/src/com/google/common/xml/
Xml.gwt.xml	9 We used to set this only for packages that had manual supersource. 10 That worked everywhere that I know of except for one place: 12 The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: 14 The summary is that it ignores one file in favor of the other. 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. 21 (I hope that this workaround does not cause its own problems in the future.)
/external/guava/guava-gwt/src/com/google/thirdparty/publicsuffix/
PublicSuffixPatterns.gwt.xml	9 We used to set this only for packages that had manual supersource. 10 That worked everywhere that I know of except for one place: 12 The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: 14 The summary is that it ignores one file in favor of the other. 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. 21 (I hope that this workaround does not cause its own problems in the future.)
PublicSuffixType.gwt.xml	9 We used to set this only for packages that had manual supersource. 10 That worked everywhere that I know of except for one place: 12 The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: 14 The summary is that it ignores one file in favor of the other. 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. 21 (I hope that this workaround does not cause its own problems in the future.)
/external/guava/guava-gwt/test/com/google/common/collect/testing/
Testing.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->
/external/guava/guava-gwt/test/com/google/common/escape/testing/
Testing.gwt.xml	9 We used to set this only for packages that had manual supersource. 10 That worked everywhere that I know of except for one place: 12 The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: 14 The summary is that it ignores one file in favor of the other. 19 Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. 21 (I hope that this workaround does not cause its own problems in the future.)
/external/guava/guava-gwt/test/com/google/common/testing/
Testing.gwt.xml	13 <!-- We used to set this only for packages that had manual supersource. That worked everywhere that I know of except for one place: when running the GWT util.concurrent tests under Guava. The problem is that GWT responds poorly to two .gwt.xml files in the same Java package: http://goo.gl/CO7dLB The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. util.concurrent, unlike our other packages, has, as of this writing, test supersource but no prod supersource. GWT happens to use the prod .gwt.xml, so it looks for no supersource for tests, either. This causes it to fail to find AtomicLongMapTest. Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) -->

Completed in 1185 milliseconds

<<71727374757677787980>>