GitLab

* Import torchaudio #1105 37692d8d

Summary: Import torchaudio up to #1105 37692d8d

Reviewed By: datumbox

Differential Revision: D25671497

fbshipit-source-id: 5af11c801321f2bb964245ac6ed74979310f4b5f

There's an issue with the CUDA 11.0 package for conda with
conda-package-handling that relates to https://github.com/conda/conda-package-handling/issues/71



This should fix issues with the conda smoke testing we encountered previously.
Signed-off-by: Eli Uriegas <eliuriegas@fb.com>

* Import torchaudio #1034 70f429a4

Summary: Import torchaudio #1027 0cf4b8a9

Reviewed By: vincentqb, cpuhrsch

Differential Revision: D24958707

fbshipit-source-id: d06dd6b59197cc2c16bec5a9012cbf33a172b6b3

* Import torchaudio #1066 4406a6bb

Summary: Import up to #1066

Reviewed By: cpuhrsch

Differential Revision: D25373068

fbshipit-source-id: 890d36a25259b93428b3037c3123ff5a2cacfa04

* Import torchaudio #996 758f6c2a

Reviewed By: cpuhrsch

Differential Revision: D24606263

fbshipit-source-id: 4301b1df84d20c671783ec34c52d5b257374abf1

* Import torchaudio #1004 5e54c770

Summary: Import torchaudio up to #1004 5e54c770

Reviewed By: vincentqb, cpuhrsch

Differential Revision: D24841498

fbshipit-source-id: 3829130636f36779d84f01ff0d0120b80b2396d7

This reverts commit 1ecbc249.

Reason: The macOS CI jobs are stuck with xdist recently.

Upstream is on 9.4.1 and we were experiencing issues when conda-build
was attempting to check for overlinking and failed out due to some files
not existing in xcode 9.0
Signed-off-by: Eli Uriegas <eliuriegas@fb.com>

When running smoke test, proper way to install conda package is to
install from workspace, instead of installing from archive.
Otherwise the dependencies are not properly installed

https://github.com/conda/conda/issues/1884

For this, we pass the whole `conda-bld` directory from
conda package build job to upload job then smoke test job.

`torchaudio` does not have a mandatory third-party python package dependency,
so this was not an issue.

See also https://github.com/pytorch/text/pull/803

librosa 0.8.0 has been released which include fix for
https://github.com/librosa/librosa/issues/1160 at
https://github.com/librosa/librosa/pull/1164

This CC adds CI test to check the backward compatibility of Torchscript functions/object dumps.

The job first dumps Torchscript objects into file from torchaudio 0.6.0 release environment (x Python 3.6, 3.7, 3,8), then load & run the function in master build (in Python 3.6, 3.7, 3.8).

If there is a BC-breaking change in master build, (registration schema change), then the test should fail.

At this moment, `info` function does not work due to suspected bug in torch side, so the test is disabled for `info` function. See https://github.com/pytorch/pytorch/issues/42258 for the detail. Once https://github.com/pytorch/pytorch/issues/42258 is resolved we can enable it.

We have been running unit test with editable installation. (i.e. `python setup.py develop`), with which we missed issues like #842. 

This CC makes installation in CI non-editable, and change test directory structure so that the source code will not shadow the installed version of `torchaudio`. With simple `pytest test`, `pytest` modifies `sys.path` and prepend checked out repository, which shadows the installed version.

To remedy this, the whole test suites has been moved from `./test` to `./test/torchaudio_unittest`. This adds nice module structure to our test code and we can do absolute import in each test module, which makes it possible again to run test with `python -m unittest torchaudio_unittest/XXX.py`

This change does not affect the regular development process (`python setup.py develop` && `pytest test`)

Currently our test suites automatically/silently skip tests on C++ extension
if it is not available. This is nice in local env, but in CI these tests should be
enforced and reported as failure if C++ extension is not available.

This PR adds switch for making tests fail if C++ extension is not available,
and make CI for *nix fail if that's the case.

Currently macOS CI job takes twice the time of linux unit tests.
This PR uses `pytest-xdist` to run unit tests in parallel on macOS CI job. 

Interestingly applying the same technique to linux unit tests make the test execution longer.
So the change is only applied to macOS.

macOS 27 mins -> 17 mins 😸
linux 14 mins -> 1 hours 😾

* Pin llvmlite

* Add comments

* Use cmake for third party

* Apply patch to libmad

* Update gitignore

* Update docker test image