Merge "Remove resolv/AndroidTest.xml" am: 48af3735cd am: 86d9034f6f am: dfff854a39

<?xml version="1.0" encoding="utf-8"?>

<!-- Copyright (C) 2017 The Android Open Source Project

     Licensed under the Apache License, Version 2.0 (the "License");

     you may not use this file except in compliance with the License.

     You may obtain a copy of the License at

          http://www.apache.org/licenses/LICENSE-2.0

     Unless required by applicable law or agreed to in writing, software

     distributed under the License is distributed on an "AS IS" BASIS,

     WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

     See the License for the specific language governing permissions and

     limitations under the License.

-->

<!-- This test config file is auto-generated. -->

<configuration description="Config for resolv_integration_test.">

    <option name="test-suite-tag" value="apct" />

    <option name="test-suite-tag" value="apct-native" />

    <target_preparer class="com.android.tradefed.targetprep.PushFilePreparer">

        <option name="cleanup" value="true" />

        <option name="push" value="resolv_integration_test->/data/local/tmp/resolv_integration_test" />

    </target_preparer>

    <test class="com.android.tradefed.testtype.GTest" >

        <option name="native-test-device-path" value="/data/local/tmp" />

        <option name="module-name" value="resolv_integration_test" />

        <!--

            On 2018-12-12, GetAddrInfoStressTest_Binder_100 suddenly jumped

            from ~1xs to ~70s runtime in APCT continuous integration, causing

            resolv_integration_test to flake with the default 60s timeout.

            We're not sure what caused the regression, but it's not due to a change

            in the Android image and unlikely to affect users.

            Just bump the timeout to 120s for now.

        -->

        <option name="native-test-timeout" value="120000" />

    </test>

</configuration>