Packages are imported one by one in alphabetical order during runtime.

The test doesn't identify package's order-dependent issues; for instance,
importing "tf.foo" followed by "tf.bar" won't reveal that "tf.bar" depends on
"tf.foo" being imported first.

The `_api/v2/api_packages.txt` file is generated during the TensorFlow API v2
init files creation process and is subsequently stored in the wheel file after

may exist in your changes.

#### Running unit tests

There are two ways to run TensorFlow unit tests.

1.  Using tools and libraries installed directly on your system.

    Refer to the
    [CPU-only developer Dockerfile](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/dockerfiles/dockerfiles/devel-cpu.Dockerfile)
    and

        (neural) layers.
    *   Add `tf.contrib.bayesflow.halton_sequence`.
    *   Add `tf.contrib.data.make_saveable_from_iterator.`
    *   Add `tf.contrib.data.shuffle_and_repeat`.
    *   Add new custom transformation: `tf.contrib.data.scan()`.
    *   `tf.contrib.distributions.bijectors`:
    *   Add `tf.contrib.distributions.bijectors.MaskedAutoregressiveFlow`.