1. 10 Jul, 2023 1 commit
  2. 24 May, 2023 1 commit
    • moto's avatar
      Update smoke test (#3346) · 71b2634b
      moto authored
      Summary:
      * Delay the import of torchaudio until the CLI options are parsed.
      * Add option to set log level to DEBUG so that it's easy to see the issue with external libraries.
      
      Pull Request resolved: https://github.com/pytorch/audio/pull/3346
      
      Reviewed By: nateanl
      
      Differential Revision: D46022546
      
      Pulled By: mthrok
      
      fbshipit-source-id: 9f988bbd770c2fd2bb260c3cfe02b238a9da2808
      71b2634b
  3. 09 Dec, 2022 1 commit
    • atalman's avatar
      Toggle on/off ffmpeg test if needed (#2901) · ccda545c
      atalman authored
      Summary:
      Toggle on/off ffmpeg test if needed
      By default it ON, hence should not affect any current tests.
      To toggle ON no change required.
      To toggle OFF use:
      ```
      smoke_test.py --no-ffmpeg
      ```
      
      To be used when calling from builder currently. Since we do not install ffmpeg currently.
      
      Pull Request resolved: https://github.com/pytorch/audio/pull/2901
      
      Reviewed By: carolineechen, mthrok
      
      Differential Revision: D41874976
      
      Pulled By: atalman
      
      fbshipit-source-id: c57b19f37c63a1f476f93a5211550e980e67d9c7
      ccda545c
  4. 07 Jun, 2022 1 commit
  5. 11 May, 2022 1 commit
    • moto's avatar
      Move FFmpeg integrity test from conda smoke test to custom smoke test (#2381) · 9877f544
      moto authored
      Summary:
      Conda package build performs simple smoke test, which is different
      from smoke_test jobs we define on our CI jobs.
      
      Currently Conda packaging smoke test verifies the imporatability of
      `torchaudio.prototype.io`, which requires FFmpeg 4.
      
      1. We list FFmpeg 4 as runtime requirements, but this means that
      conda's dependency resolver takes FFmpeg 4 into consideration.
      FFmpeg 5 was release this year, and we can expect that user base
      will move to FFmpeg gradually. If user environment has some constraint
      on FFmpeg, torchaudio will have conflict and it will prevent users
      from install torchaudio.
      
      2. In #2377 the way optional dependency is checked/initialized is changed,
      so this Conda smoke test will no longer check the integrity with FFmpeg libraries.
      
      To solve the issues above, this commit moves the part that tests integrity with
      FFmpeg libraries to the smoke test we define on CircleCI.
      
      Pull Request resolved: https://github.com/pytorch/audio/pull/2381
      
      Reviewed By: carolineechen
      
      Differential Revision: D36323706
      
      Pulled By: mthrok
      
      fbshipit-source-id: 57ca816e0f3ad8e16d21e56062f6ed8a09ab93a3
      9877f544
  6. 06 May, 2022 1 commit
    • moto's avatar
      Refactor smoke test executions (#2365) · 6a8a28bb
      moto authored
      Summary:
      The smoke test jobs simply perform `import torchaudio` to check
      if the package artifacts are sane.
      
      Originally, the CI was executing it in the root directory.
      This was fine unless the source code is checked out.
      When source code is checked out, performing `import torchaudio` in
      root directory would import source torchaudio directory, instead of the
      installed package.
      
      This error is difficult to notice, so this commit introduces common script to
      perform the smoke test, while moving out of root directory.
      
      Pull Request resolved: https://github.com/pytorch/audio/pull/2365
      
      Reviewed By: carolineechen
      
      Differential Revision: D36202069
      
      Pulled By: mthrok
      
      fbshipit-source-id: 4396f85fec5c54869ada4c08f51304539f1b05cf
      6a8a28bb