Searched refs:as (Results 1 – 25 of 496) sorted by relevance
12345678910>>...20
106 ProcessMemory.AppSummary as = pm.getAppSummary(); in testProcessMemory() local107 assertTrue(0 <= as.getJavaHeapPssKb()); in testProcessMemory()108 assertTrue(0 <= as.getNativeHeapPssKb()); in testProcessMemory()109 assertTrue(0 <= as.getCodePssKb()); in testProcessMemory()110 assertTrue(0 <= as.getStackPssKb()); in testProcessMemory()111 assertTrue(0 <= as.getGraphicsPssKb()); in testProcessMemory()112 assertTrue(0 <= as.getPrivateOtherPssKb()); in testProcessMemory()113 assertTrue(0 <= as.getSystemPssKb()); in testProcessMemory()114 assertTrue(0 <= as.getTotalSwapPss()); in testProcessMemory()115 assertTrue(0 <= as.getTotalSwapKb()); in testProcessMemory()
41 // tag this module as a cts test artifact62 // tag this module as a cts test artifact83 // tag this module as a cts test artifact103 // tag this module as a cts test artifact123 // tag this module as a cts test artifact145 // tag this module as a cts test artifact167 // tag this module as a cts test artifact188 // tag this module as a cts test artifact207 // Tag this module as a cts test artifact
1 # DO NOT DELETE: OWNERS is intended to be empty as module owner and bug component are defined2 # in parent directory. This file is needed as a placeholder for verification purpose as we
26 // tag this module as a cts test artifact46 // tag this module as a cts test artifact66 // tag this module as a cts test artifact86 // tag this module as a cts test artifact106 // tag this module as a cts test artifact
35 // tag this module as a cts test artifact67 // tag this module as a cts test artifact98 // tag this module as a cts test artifact131 // tag this module as a cts test artifact157 // tag this module as a cts test artifact189 // tag this module as a cts test artifact
34 Dhrystone is used most. There should be, as far as possible, only41 been updated as well.43 o As far as it is possible without changes to the Dhrystone statistics,54 remain unchanged as much as possible. (Very few changes were59 benchmark into something different from what has become known as64 of representative programs that can be used as benchmarks; users should68 distributed as widely as possible. (Version 2.1 differs from version96 danger that the compiler considers them as "dead variables" and109 statements, operand types and locality) still hold as much as possible.111 version 2.1 should be the same as for previous versions.[all …]
25 // tag this module as a cts test artifact43 // tag this module as a cts test artifact61 // tag this module as a cts test artifact80 // tag this module as a cts test artifact
21 // tag this module as a cts test artifact35 // tag this module as a cts test artifact49 // tag this module as a cts test artifact
18 // Tag this module as a cts test artifact32 // Tag this module as a cts test artifact46 // Tag this module as a cts test artifact
21 // tag this module as a cts test artifact38 // tag this module as a cts test artifact54 // tag this module as a cts test artifact
36 // Tag this module as a cts test artifact66 // Tag this module as a cts test artifact99 // Tag this module as a cts test artifact132 // Tag this module as a cts test artifact
26 // tag this module as a cts test artifact45 // tag this module as a cts test artifact65 // tag this module as a cts test artifact
25 // tag this module as a cts test artifact43 // tag this module as a cts test artifact62 // tag this module as a cts test artifact
37 // Tag this module as a cts test artifact57 // Tag this module as a cts test artifact77 // Tag this module as a cts test artifact
18 // Tag this module as a cts test artifact39 // Tag this module as a cts test artifact60 // Tag this module as a cts test artifact
30 // tag this module as a cts test artifact55 // tag this module as a cts test artifact79 // tag this module as a cts test artifact
34 // tag this module as a cts test artifact62 // tag this module as a cts test artifact91 // tag this module as a cts test artifact
35 // Tag this module as a cts test artifact69 // Tag this module as a cts test artifact104 // Tag this module as a cts test artifact
21 // Use the same cert as the app that also defined the permission23 // tag this module as a cts test artifact
24 // Includes the jni code as a shared library32 // tag this module as a cts test artifact
20 // tag this module as a cts test artifact35 // tag this module as a cts test artifact
25 // tag this module as a cts test artifact43 // tag this module as a cts test artifact