-
Notifications
You must be signed in to change notification settings - Fork 62
Disable ffprobe test internally #900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable ffprobe test internally #900
Conversation
@Dan-Flores has exported this pull request. If you are a Meta employee, you can view the originating diff in D82378431. |
Summary: Tests related to `custom_frame_mappings` that utilize ffprobe should be skipped internally as ffprobe is not available. In addition to adding the `pytest.skip` decorator to these tests, I removed `custom_frame_mapping` generation from `pytest.mark.parametrize` in `test_custom_frame_mappings_init_fails` to allow tests to run. Reviewed By: scotts Differential Revision: D82378431
44d40a1
to
0dcd99e
Compare
@Dan-Flores has exported this pull request. If you are a Meta employee, you can view the originating diff in D82378431. |
Summary: Tests related to `custom_frame_mappings` that utilize ffprobe should be skipped internally as ffprobe is not available. In addition to adding the `pytest.skip` decorator to these tests, I removed `custom_frame_mapping` generation from `pytest.mark.parametrize` in `test_custom_frame_mappings_init_fails` to allow tests to run. Reviewed By: scotts Differential Revision: D82378431
0dcd99e
to
5cb9e7d
Compare
@Dan-Flores has exported this pull request. If you are a Meta employee, you can view the originating diff in D82378431. |
Summary: Tests related to `custom_frame_mappings` that utilize ffprobe should be skipped internally as ffprobe is not available. In addition to adding the `pytest.skip` decorator to these tests, I removed `custom_frame_mapping` generation from `pytest.mark.parametrize` in `test_custom_frame_mappings_init_fails` to allow tests to run. Reviewed By: scotts Differential Revision: D82378431
5cb9e7d
to
fd8f09a
Compare
@Dan-Flores has exported this pull request. If you are a Meta employee, you can view the originating diff in D82378431. |
Summary: Tests related to `custom_frame_mappings` that utilize ffprobe should be skipped internally as ffprobe is not available. In addition to adding the `pytest.skip` decorator to these tests, I removed `custom_frame_mapping` generation from `pytest.mark.parametrize` in `test_custom_frame_mappings_init_fails` to allow tests to run. Reviewed By: scotts Differential Revision: D82378431
fd8f09a
to
f1f27d5
Compare
@Dan-Flores has exported this pull request. If you are a Meta employee, you can view the originating diff in D82378431. |
Summary: Tests related to `custom_frame_mappings` that utilize ffprobe should be skipped internally as ffprobe is not available. In addition to adding the `pytest.skip` decorator to these tests, I removed `custom_frame_mapping` generation from `pytest.mark.parametrize` in `test_custom_frame_mappings_init_fails` to allow tests to run. Reviewed By: scotts Differential Revision: D82378431
f1f27d5
to
458877f
Compare
@Dan-Flores has exported this pull request. If you are a Meta employee, you can view the originating diff in D82378431. |
Summary:
Tests related to
custom_frame_mappings
that utilize ffprobe should be skipped internally as ffprobe is not available.In addition to adding the
pytest.skip
decorator to these tests, I removedcustom_frame_mapping
generation frompytest.mark.parametrize
intest_custom_frame_mappings_init_fails
to allow tests to run.Reviewed By: scotts
Differential Revision: D82378431