You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by "samuela (via GitHub)" <gi...@apache.org> on 2023/02/08 21:54:16 UTC

[GitHub] [beam] samuela opened a new issue, #25390: [Failing Test]: Many failing tests in Python v2.44.0 SDK

samuela opened a new issue, #25390:
URL: https://github.com/apache/beam/issues/25390

   ### What happened?
   
   I'm seeing the following test suite results when running the v2.44.0 Python tests:
   ```
   =========================== short test summary info ============================
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_pickle_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_proto_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_sharded_key_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_singleton_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_state_backed_iterable_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_timer_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_timestamp_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_timestamp_prefixing_window_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_tuple_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_tuple_sequence_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_utf8_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_varint_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_windowed_value_coder - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/coders/slow_coders_test.py::CodersTest::test_windowedvalue_coder_paneinfo - AttributeError: type object 'CodersTest' has no attribute 'seen'
   FAILED apache_beam/dataframe/pandas_doctests_test.py::DoctestTest::test_top_level - AssertionError: 4 != 0
   FAILED apache_beam/dataframe/pandas_doctests_test.py::DoctestTest::test_dataframe_tests - AssertionError: 2 != 0
   FAILED apache_beam/dataframe/pandas_doctests_test.py::DoctestTest::test_groupby_tests - AssertionError: 9 != 0
   FAILED apache_beam/dataframe/pandas_doctests_test.py::DoctestTest::test_ndframe_tests - AssertionError: 1 != 0
   FAILED apache_beam/typehints/typed_pipeline_test.py::MainInputTest::test_typed_ptransform_fn_post_hints - AssertionError: TypeCheckError not raised
   FAILED apache_beam/typehints/typed_pipeline_test.py::MainInputTest::test_typed_ptransform_fn_conflicting_hints - AssertionError: "MyMap.*expected.*int.*got.*str" does not match "Type hint ...
   FAILED apache_beam/typehints/typed_pipeline_test.py::MainInputTest::test_typed_ptransform_fn_multi_input_types_kw - AssertionError: TypeCheckError not raised
   FAILED apache_beam/typehints/typed_pipeline_test.py::MainInputTest::test_typed_ptransform_fn_pre_hints - AssertionError: TypeCheckError not raised
   FAILED apache_beam/typehints/typed_pipeline_test.py::MainInputTest::test_typed_ptransform_fn_multi_input_types_pos - AssertionError: TypeCheckError not raised
   ERROR apache_beam/coders/fast_coders_test.py::CodersTest::test_windowedvalue_coder_paneinfo - AssertionError: {<class 'apache_beam.coders.coders.NullableCoder'>, <class ...
   ERROR apache_beam/coders/fast_coders_test.py::CodersTest::test_state_backed_iterable_coder - AssertionError: {<class 'apache_beam.coders.coders.TimestampPrefixingWindow...
   ERROR apache_beam/dataframe/schemas_test.py::test_name_func
   = 23 failed, 5283 passed, 977 skipped, 14805 warnings, 3 errors in 154.27s (0:02:34) =
   ```
   
   To reproduce 
   1. Checkout https://github.com/NixOS/nixpkgs/pull/215385/commits/f9b7e743fe715262064ac9e838891d6ee9ef32c2.
   2. Run `nix-build -A python3Packages.apache-beam`
   3. Observe test failures.
   
   ### Issue Failure
   
   Failure: Test is continually failing
   
   ### Issue Priority
   
   Priority: 2 (backlog / disabled test but we think the product is healthy)
   
   ### Issue Components
   
   - [X] Component: Python SDK
   - [ ] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [ ] Component: IO connector
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [beam] tvalentyn closed issue #25390: [Failing Test]: Many failing tests in Python v2.44.0 SDK

Posted by "tvalentyn (via GitHub)" <gi...@apache.org>.
tvalentyn closed issue #25390: [Failing Test]: Many failing tests in Python v2.44.0 SDK
URL: https://github.com/apache/beam/issues/25390


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [beam] tvalentyn commented on issue #25390: [Failing Test]: Many failing tests in Python v2.44.0 SDK

Posted by "tvalentyn (via GitHub)" <gi...@apache.org>.
tvalentyn commented on issue #25390:
URL: https://github.com/apache/beam/issues/25390#issuecomment-1435453258

   I assume this is not happening when tests are not running in parallel. to verify you can also open a PR against 2.44.0 release branch and that will run the unit tests.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [beam] samuela commented on issue #25390: [Failing Test]: Many failing tests in Python v2.44.0 SDK

Posted by "samuela (via GitHub)" <gi...@apache.org>.
samuela commented on issue #25390:
URL: https://github.com/apache/beam/issues/25390#issuecomment-1423359916

   `@pytest.mark.no_xdist` should cause them to be skipped, no? FWIW I tried running without xdist and saw similar test failures in `apache_beam/coders/coders_test_common.py`, so I'm not so sure that it's an xdist-related failure


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [beam] Abacn commented on issue #25390: [Failing Test]: Many failing tests in Python v2.44.0 SDK

Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #25390:
URL: https://github.com/apache/beam/issues/25390#issuecomment-1423344439

   Running these tests in parallel will cause this error. Reason: https://github.com/apache/beam/blob/9fcb3a5b48a6db0dcf57f454d1d1eca10cf1c41b/sdks/python/apache_beam/coders/coders_test_common.py#L109-L112
   
   to run unit tests manually, invoke the following command at `sdks/python` directory
   ```
   bash scripts/run_pytest.sh py310
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [beam] samuela commented on issue #25390: [Failing Test]: Many failing tests in Python v2.44.0 SDK

Posted by "samuela (via GitHub)" <gi...@apache.org>.
samuela commented on issue #25390:
URL: https://github.com/apache/beam/issues/25390#issuecomment-1423290139

   See https://gist.github.com/samuela/87b4c7fdcabcc3992f7f7ac2fc21b9ba for a complete log of all the failures in their full pytest verbosity.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


[GitHub] [beam] Abacn commented on issue #25390: [Failing Test]: Many failing tests in Python v2.44.0 SDK

Posted by "Abacn (via GitHub)" <gi...@apache.org>.
Abacn commented on issue #25390:
URL: https://github.com/apache/beam/issues/25390#issuecomment-1423372802

   `@pytest.mark.no_xdist` is just a marker. If invoke pytest command directly it does not take effect. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org