/external/valgrind/memcheck/tests/ |
H A D | pointer-trace.stderr.exp | 1 1,000 bytes in 1 blocks are definitely lost in loss record ... of ...
|
H A D | static_malloc.stderr.exp | 1 10 bytes in 1 blocks are definitely lost in loss record ... of ...
|
H A D | trivialleak.stderr.exp | 1 1,000 bytes in 1,000 blocks are definitely lost in loss record ... of ...
|
H A D | leak-delta.stderr.exp | 2 10 bytes in 1 blocks are still reachable in loss record ... of ... 9 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ... 14 21 (+21) bytes in 1 (+1) blocks are still reachable in loss record ... of ... 20 65 (+65) bytes in 2 (+2) blocks are still reachable in loss record ... of ... 27 10 (+10) bytes in 1 (+1) blocks are still reachable in loss record ... of ... 33 0 (-10) bytes in 0 (-1) blocks are still reachable in loss record ... of ... 38 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ... 44 0 (-10) bytes in 0 (-1) blocks are definitely lost in loss record ... of ... 49 10 (+10) bytes in 1 (+1) blocks are still reachable in loss record ... of ... 55 32 (+32) bytes in 1 (+1) blocks are definitely lost in loss recor [all...] |
H A D | leak-cases-full.stderr.exp | 5 16 bytes in 1 blocks are possibly lost in loss record ... of ... 11 16 bytes in 1 blocks are possibly lost in loss record ... of ... 17 16 bytes in 1 blocks are possibly lost in loss record ... of ... 23 16 bytes in 1 blocks are possibly lost in loss record ... of ... 29 16 bytes in 1 blocks are possibly lost in loss record ... of ... 35 16 bytes in 1 blocks are possibly lost in loss record ... of ... 41 16 bytes in 1 blocks are definitely lost in loss record ... of ... 47 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ... 53 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
|
H A D | leak-cases-possible.stderr.exp | 5 16 bytes in 1 blocks are definitely lost in loss record ... of ... 11 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ... 17 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
|
H A D | leak-tree.stderr.exp | 5 16 bytes in 1 blocks are definitely lost in loss record ... of ... 11 48 (16 direct, 32 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
|
H A D | leak-cycle.stderr.exp | 5 48 (16 direct, 32 indirect) bytes in 1 blocks are definitely lost in loss record ... of ... 11 48 (16 direct, 32 indirect) bytes in 1 blocks are definitely lost in loss record ... of ... 17 96 (16 direct, 80 indirect) bytes in 1 blocks are definitely lost in loss record ... of ... 23 96 (16 direct, 80 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
|
H A D | lks.stderr.exp | 21 16 bytes in 1 blocks are indirectly lost in loss record ... of ... 27 16 bytes in 1 blocks are indirectly lost in loss record ... of ... 33 16 bytes in 1 blocks are definitely lost in loss record ... of ... 39 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ... 45 32 (16 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
|
H A D | mempool.stderr.exp | 35 10 bytes in 1 blocks are definitely lost in loss record ... of ... 40 10 bytes in 1 blocks are definitely lost in loss record ... of ... 45 20 bytes in 1 blocks are definitely lost in loss record ... of ... 50 48 (32 direct, 16 indirect) bytes in 1 blocks are definitely lost in loss record ... of ...
|
H A D | leak-segv-jmp.stderr.exp | 15 1,000 bytes in 1 blocks are definitely lost in loss record ... of ... 31 1,000 bytes in 1 blocks are definitely lost in loss record ... of ... 47 1,000 bytes in 1 blocks are definitely lost in loss record ... of ... 63 1,000 bytes in 1 blocks are definitely lost in loss record ... of ... 68 40,000 bytes in 1 blocks are possibly lost in loss record ... of ...
|
/external/valgrind/gdbserver_tests/ |
H A D | mcleak.stderrB.exp | 3 10 bytes in 1 blocks are still reachable in loss record ... of ... 7 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ... 11 21 (+21) bytes in 1 (+1) blocks are still reachable in loss record ... of ... 15 65 (+65) bytes in 2 (+2) blocks are still reachable in loss record ... of ... 19 10 (+10) bytes in 1 (+1) blocks are still reachable in loss record ... of ... 23 0 (-10) bytes in 0 (-1) blocks are still reachable in loss record ... of ... 27 10 (+10) bytes in 1 (+1) blocks are definitely lost in loss record ... of ... 31 0 (-10) bytes in 0 (-1) blocks are definitely lost in loss record ... of ... 35 10 (+10) bytes in 1 (+1) blocks are still reachable in loss record ... of ... 39 32 (+32) bytes in 1 (+1) blocks are definitely lost in loss recor [all...] |
H A D | mcleak.stderr.exp | 3 10 bytes in 1 blocks are still reachable in loss record ... of ... 20 10 bytes in 1 blocks are still reachable in loss record ... of ... 24 21 bytes in 1 blocks are still reachable in loss record ... of ... 28 32 bytes in 1 blocks are definitely lost in loss record ... of ... 32 33 bytes in 1 blocks are still reachable in loss record ... of ...
|
H A D | mcblocklistsearch.stderrB.exp | 15 16 bytes in 1 blocks are still reachable in loss record ... of ... 20 16 bytes in 1 blocks are still reachable in loss record ... of ... 25 16 bytes in 1 blocks are still reachable in loss record ... of ... 30 16 bytes in 1 blocks are indirectly lost in loss record ... of ... 35 16 bytes in 1 blocks are indirectly lost in loss record ... of ... 40 16 bytes in 1 blocks are definitely lost in loss record ... of ... 45 48 (16 direct, 32 indirect) bytes in 1 blocks are definitely lost in loss record ... of ... 51 16 bytes in 1 blocks are definitely lost in loss record ... of ... 58 48 (16 direct, 32 indirect) bytes in 1 blocks are definitely lost in loss record ... of ... 64 0x........[16] indirect loss recor [all...] |
/external/ceres-solver/examples/ |
H A D | circle_fit.cc | 68 DEFINE_double(robust_threshold, 0.0, "Robust loss parameter. Set to 0 for " 130 // Configure the loss function. 131 LossFunction* loss = NULL; local 133 loss = new CauchyLoss(FLAGS_robust_threshold); 143 problem.AddResidualBlock(cost, loss, &x, &y, &m);
|
/external/autotest/client/common_lib/cros/network/ |
H A D | ping_runner.py | 80 10 packets transmitted, 7 received, +3 errors, 30% packet loss, time 9007ms 92 5 packets transmitted, 5 received, 0% packet loss, time 4007ms 96 9 packets transmitted, 9 received, +1 duplicates, 0% packet loss, time 90 ms 122 loss = PingResult._regex_int_from_string('([0-9]+)% packet loss', 124 if None in (sent, received, loss): 130 return PingResult(sent, received, loss, 138 return PingResult(sent, received, loss) 141 def __init__(self, sent, received, loss, 148 @param loss [all...] |
/external/valgrind/memcheck/tests/solaris/ |
H A D | ldynsym.stderr.exp | 1 10 bytes in 1 blocks are definitely lost in loss record ... of ...
|
/external/autotest/server/cros/network/ |
H A D | arping_runner.py | 117 self.loss = 100.0 * float(num_sent - len(latencies)) / num_sent 133 @param max_loss float maximum loss expressed as a percentage. 145 if max_loss is not None and self.loss > max_loss: 152 return ('%s(loss=%r, average_latency=%r, latencies=%r, responders=%r)' % 153 (self.__class__.__name__, self.loss, self.average_latency,
|
/external/ceres-solver/internal/ceres/ |
H A D | loss_function_test.cc | 47 void AssertLossFunctionIsValid(const LossFunction& loss, double s) { argument 52 loss.Evaluate(s, rho); 61 loss.Evaluate(s + kH, fwd); 62 loss.Evaluate(s - kH, bwd); 78 // Note that for the Huber loss the test exercises both code paths 125 // Check that loss before and after the approximation threshold are good. 151 // Wrap a few loss functions, and a few scale factors. This can't combine
|
/external/webrtc/webrtc/modules/rtp_rtcp/test/testFec/ |
H A D | test_packet_masks_metrics.cc | 15 * The metrics measure the efficiency (recovery potential or residual loss) of 16 * the FEC code, under various statistical loss models for the packet/symbol 17 * loss events. Various constraints on the behavior of these metrics are 25 * In the case of XOR, the residual loss is determined via the set of packet 26 * masks (generator matrix). In the case of RS, the residual loss is determined 40 * The type of packet/symbol loss models considered in this test are: 41 * (1) Random loss: Bernoulli process, characterized by the average loss rate. 42 * (2) Bursty loss: Markov chain (Gilbert-Elliot model), characterized by two 43 * parameters: average loss rat [all...] |
/external/webrtc/webrtc/modules/bitrate_controller/ |
H A D | send_side_bandwidth_estimation.h | 30 void CurrentEstimate(int* bitrate, uint8_t* loss, int64_t* rtt) const;
|
/external/webrtc/webrtc/modules/audio_coding/codecs/opus/ |
H A D | audio_encoder_opus_unittest.cc | 116 // Sets the packet loss rate to each number in the vector in turn, and verifies 117 // that the loss rate as reported by the encoder is |expected_return| for all 122 for (double loss : losses) { 123 encoder->SetProjectedPacketLossRate(loss);
|
/external/autotest/server/site_tests/network_WiFi_Regulatory/ |
H A D | network_WiFi_Regulatory.py | 62 if result.loss > 60:
|
/external/autotest/server/cros/ap_configurators/ |
H A D | ap_configurator.py | 90 if ping_result.loss == 100:
|
/external/webrtc/webrtc/modules/remote_bitrate_estimator/ |
H A D | remote_bitrate_estimators_test.cc | 53 LossFilter loss(&uplink_, 0); 55 loss.SetLoss(20.0); 62 LossFilter loss(&uplink_, 0); 65 loss.SetLoss(i);
|