See
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/594/display/redirect?page=changes>
Changes:
[noreply] Pin hugging face docs (#28106)
------------------------------------------
[...truncated 618.33 KB...]
cases users do not need to specify any custom values for any of these
parameters and may simply rely on default ones instead.
If you choose to specify custom parameters, please make sure you've
read the documentation below carefully.
First, please check :class:`google.api_core.retry.Retry`
class documentation for the proper definition of timeout and deadline
terms and for the definition the three different types of timeouts.
This class operates in terms of Retry Timeout and Polling Timeout. It
does not let customizing RPC timeout and the user is expected to rely on
default behavior for it.
The roles of each argument of this method are as follows:
``timeout`` (int): (Optional) The Polling Timeout as defined in
:class:`google.api_core.retry.Retry`. If the operation does not complete
within this timeout an exception will be thrown. This parameter affects
neither Retry Timeout nor RPC Timeout.
``retry`` (google.api_core.retry.Retry): (Optional) How to retry the
polling RPC. The ``retry.timeout`` property of this parameter is the
Retry Timeout as defined in :class:`google.api_core.retry.Retry`.
This parameter defines ONLY how the polling RPC call is retried
(i.e. what to do if the RPC we used for polling returned an error). It
does NOT define how the polling is done (i.e. how frequently and for
how long to call the polling RPC); use the ``polling`` parameter for
that.
If a polling RPC throws and error and retrying it fails, the whole
future fails with the corresponding exception. If you want to tune which
server response error codes are not fatal for operation polling, use
this
parameter to control that (``retry.predicate`` in particular).
``polling`` (google.api_core.retry.Retry): (Optional) How often and
for how long to call the polling RPC periodically (i.e. what to do if
a polling rpc returned successfully but its returned result indicates
that the long running operation is not completed yet, so we need to
check it again at some point in future). This parameter does NOT define
how to retry each individual polling RPC in case of an error; use the
``retry`` parameter for that. The ``polling.timeout`` of this parameter
is Polling Timeout as defined in as defined in
:class:`google.api_core.retry.Retry`.
For each of the arguments, there are also default values in place, which
will be used if a user does not specify their own. The default values
for the three parameters are not to be confused with the default values
for the corresponding arguments in this method (those serve as "not set"
markers for the resolution logic).
If ``timeout`` is provided (i.e.``timeout is not _DEFAULT VALUE``; note
the ``None`` value means "infinite timeout"), it will be used to control
the actual Polling Timeout. Otherwise, the ``polling.timeout`` value
will be used instead (see below for how the ``polling`` config itself
gets resolved). In other words, this parameter effectively overrides
the ``polling.timeout`` value if specified. This is so to preserve
backward compatibility.
If ``retry`` is provided (i.e. ``retry is not None``) it will be used to
control retry behavior for the polling RPC and the ``retry.timeout``
will determine the Retry Timeout. If not provided, the
polling RPC will be called with whichever default retry config was
specified for the polling RPC at the moment of the construction of the
polling RPC's client. For example, if the polling RPC is
``operations_client.get_operation()``, the ``retry`` parameter will be
controlling its retry behavior (not polling behavior) and, if not
specified, that specific method (``operations_client.get_operation()``)
will be retried according to the default retry config provided during
creation of ``operations_client`` client instead. This argument exists
mainly for backward compatibility; users are very unlikely to ever need
to set this parameter explicitly.
If ``polling`` is provided (i.e. ``polling is not None``), it will be
used
to control the overall polling behavior and ``polling.timeout`` will
control Polling Timeout unless it is overridden by ``timeout`` parameter
as described above. If not provided, the``polling`` parameter specified
during construction of this future (the ``polling`` argument in the
constructor) will be used instead. Note: since the ``timeout`` argument
may
override ``polling.timeout`` value, this parameter should be viewed as
coupled with the ``timeout`` parameter as described above.
Args:
timeout (int): (Optional) How long (in seconds) to wait for the
operation to complete. If None, wait indefinitely.
retry (google.api_core.retry.Retry): (Optional) How to retry the
polling RPC. This defines ONLY how the polling RPC call is
retried (i.e. what to do if the RPC we used for polling returned
an error). It does NOT define how the polling is done (i.e. how
frequently and for how long to call the polling RPC).
polling (google.api_core.retry.Retry): (Optional) How often and
for how long to call polling RPC periodically. This parameter
does NOT define how to retry each individual polling RPC call
(use the ``retry`` parameter for that).
Returns:
google.protobuf.Message: The Operation's result.
Raises:
google.api_core.GoogleAPICallError: If the operation errors or if
the timeout is reached before the operation completes.
"""
self._blocking_poll(timeout=timeout, retry=retry, polling=polling)
if self._exception is not None:
# pylint: disable=raising-bad-type
# Pylint doesn't recognize that this is valid in this case.
> raise self._exception
[1m[31mE google.api_core.exceptions.Cancelled: 499 Operation
successfully rolled back : Not enough servers to allocate the requested nodes.
We have temporarily sold out of Cloud Bigtable in this zone. Our support team
has been notified and will be bringing more resources on board. Please try a
different zone or try again later. 1: Operation successfully rolled back : Not
enough servers to allocate the requested nodes. We have temporarily sold out of
Cloud Bigtable in this zone. Our support team has been notified and will be
bringing more resources on board. Please try a different zone or try again
later.[0m
[1m[31m../../build/gradleenv/1398941892/lib/python3.8/site-packages/google/api_core/future/polling.py[0m:261:
Cancelled
[33m=============================== warnings summary
===============================[0m
../../build/gradleenv/1398941892/lib/python3.8/site-packages/hdfs/config.py:28
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/build/gradleenv/1398941892/lib/python3.8/site-packages/hdfs/config.py>:28:
DeprecationWarning: the imp module is deprecated in favour of importlib; see
the module's documentation for alternative uses
from imp import load_source
../../build/gradleenv/1398941892/lib/python3.8/site-packages/google/rpc/__init__.py:18
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/build/gradleenv/1398941892/lib/python3.8/site-packages/google/rpc/__init__.py>:18:
DeprecationWarning: pkg_resources is deprecated as an API. See
https://setuptools.pypa.io/en/latest/pkg_resources.html
import pkg_resources
../../build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py:2871:
20 warnings
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py>:2871:
DeprecationWarning: Deprecated call to
`pkg_resources.declare_namespace('google')`.
Implementing implicit namespace packages (as specified in PEP 420) is
preferred to `pkg_resources.declare_namespace`. See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
declare_namespace(pkg)
../../build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py:2871:
16 warnings
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py>:2871:
DeprecationWarning: Deprecated call to
`pkg_resources.declare_namespace('google.cloud')`.
Implementing implicit namespace packages (as specified in PEP 420) is
preferred to `pkg_resources.declare_namespace`. See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
declare_namespace(pkg)
../../build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py:2350
../../build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py:2350
../../build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py:2350
../../build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py:2350
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py>:2350:
DeprecationWarning: Deprecated call to
`pkg_resources.declare_namespace('google')`.
Implementing implicit namespace packages (as specified in PEP 420) is
preferred to `pkg_resources.declare_namespace`. See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
declare_namespace(parent)
../../build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py:2871
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py>:2871:
DeprecationWarning: Deprecated call to
`pkg_resources.declare_namespace('google.logging')`.
Implementing implicit namespace packages (as specified in PEP 420) is
preferred to `pkg_resources.declare_namespace`. See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
declare_namespace(pkg)
../../build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py:2871
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/build/gradleenv/1398941892/lib/python3.8/site-packages/pkg_resources/__init__.py>:2871:
DeprecationWarning: Deprecated call to
`pkg_resources.declare_namespace('google.iam')`.
Implementing implicit namespace packages (as specified in PEP 420) is
preferred to `pkg_resources.declare_namespace`. See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
declare_namespace(pkg)
../../build/gradleenv/1398941892/lib/python3.8/site-packages/google/rpc/__init__.py:20
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/build/gradleenv/1398941892/lib/python3.8/site-packages/google/rpc/__init__.py>:20:
DeprecationWarning: Deprecated call to
`pkg_resources.declare_namespace('google.rpc')`.
Implementing implicit namespace packages (as specified in PEP 420) is
preferred to `pkg_resources.declare_namespace`. See
https://setuptools.pypa.io/en/latest/references/keywords.html#keyword-namespace-packages
pkg_resources.declare_namespace(__name__)
apache_beam/examples/snippets/snippets_test.py::SnippetsTest::test_model_bigqueryio_xlang
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/sdks/python/apache_beam/examples/snippets/snippets_test.py>:767:
BeamDeprecationWarning: options is deprecated since First stable release.
References to <pipeline>.options will not be supported
p.options.view_as(GoogleCloudOptions).temp_location = 'gs://mylocation'
apache_beam/examples/snippets/snippets_test.py::SnippetsTest::test_model_bigqueryio_xlang
apache_beam/examples/snippets/snippets_test.py::SnippetsTest::test_model_bigqueryio_xlang
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_all_types
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_nested_records_and_lists
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_streaming
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_streaming_with_at_least_once
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_streaming_with_auto_sharding
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_with_at_least_once_semantics
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/sdks/python/apache_beam/io/gcp/bigquery.py>:2101:
BeamDeprecationWarning: options is deprecated since First stable release.
References to <pipeline>.options will not be supported
is_streaming_pipeline = p.options.view_as(StandardOptions).streaming
apache_beam/examples/snippets/snippets_test.py::SnippetsTest::test_model_bigqueryio_xlang
apache_beam/examples/snippets/snippets_test.py::SnippetsTest::test_model_bigqueryio_xlang
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_all_types
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_nested_records_and_lists
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_streaming
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_streaming_with_at_least_once
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_streaming_with_auto_sharding
apache_beam/io/external/xlang_bigqueryio_it_test.py::BigQueryXlangStorageWriteIT::test_with_at_least_once_semantics
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/sdks/python/apache_beam/io/gcp/bigquery.py>:2107:
BeamDeprecationWarning: options is deprecated since First stable release.
References to <pipeline>.options will not be supported
experiments = p.options.view_as(DebugOptions).experiments or []
apache_beam/examples/snippets/snippets_test.py: 2 warnings
apache_beam/io/external/xlang_bigqueryio_it_test.py: 10 warnings
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/sdks/python/apache_beam/transforms/external.py>:679:
BeamDeprecationWarning: options is deprecated since First stable release.
References to <pipeline>.options will not be supported
self._expansion_service, pipeline.options)
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
- generated xml file:
<https://ci-beam.apache.org/job/beam_PostCommit_Python_Xlang_Gcp_Direct/ws/src/sdks/python/pytest_gcpCrossLanguage.xml>
-
[36m[1m=========================== short test summary info
============================[0m
[31mFAILED[0m
apache_beam/io/gcp/bigtableio_it_test.py::[1mTestReadFromBigTableIT::test_read_xlang[0m
- google.api_core.exceptions.Cancelled: 499 Operation successfully rolled back
: Not enough servers to allocate the requested nodes. We have temporarily sold
out of Cloud Bigtable in this zone. Our support team has been notified and will
be bringing more resources on board. Please try a different zone or try again
later. 1: Operation successfully rolled back : Not enough servers to allocate
the requested nodes. We have temporarily sold out of Cloud Bigtable in this
zone. Our support team has been notified and will be bringing more resources on
board. Please try a different zone or try again later.
[31mERROR[0m
apache_beam/io/gcp/bigtableio_it_test.py::[1mTestWriteToBigtableXlangIT::test_delete_cells_mutation[0m
- google.api_core.exceptions.Cancelled: 499 Operation successfully rolled back
: Not enough servers to allocate the requested nodes. We have temporarily sold
out of Cloud Bigtable in this zone. Our support team has been notified and will
be bringing more resources on board. Please try a different zone or try again
later. 1: Operation successfully rolled back : Not enough servers to allocate
the requested nodes. We have temporarily sold out of Cloud Bigtable in this
zone. Our support team has been notified and will be bringing more resources on
board. Please try a different zone or try again later.
[31mERROR[0m
apache_beam/io/gcp/bigtableio_it_test.py::[1mTestWriteToBigtableXlangIT::test_delete_cells_with_timerange_mutation[0m
- google.api_core.exceptions.Cancelled: 499 Operation successfully rolled back
: Not enough servers to allocate the requested nodes. We have temporarily sold
out of Cloud Bigtable in this zone. Our support team has been notified and will
be bringing more resources on board. Please try a different zone or try again
later. 1: Operation successfully rolled back : Not enough servers to allocate
the requested nodes. We have temporarily sold out of Cloud Bigtable in this
zone. Our support team has been notified and will be bringing more resources on
board. Please try a different zone or try again later.
[31mERROR[0m
apache_beam/io/gcp/bigtableio_it_test.py::[1mTestWriteToBigtableXlangIT::test_delete_column_family_mutation[0m
- google.api_core.exceptions.Cancelled: 499 Operation successfully rolled back
: Not enough servers to allocate the requested nodes. We have temporarily sold
out of Cloud Bigtable in this zone. Our support team has been notified and will
be bringing more resources on board. Please try a different zone or try again
later. 1: Operation successfully rolled back : Not enough servers to allocate
the requested nodes. We have temporarily sold out of Cloud Bigtable in this
zone. Our support team has been notified and will be bringing more resources on
board. Please try a different zone or try again later.
[31mERROR[0m
apache_beam/io/gcp/bigtableio_it_test.py::[1mTestWriteToBigtableXlangIT::test_delete_row_mutation[0m
- google.api_core.exceptions.Cancelled: 499 Operation successfully rolled back
: Not enough servers to allocate the requested nodes. We have temporarily sold
out of Cloud Bigtable in this zone. Our support team has been notified and will
be bringing more resources on board. Please try a different zone or try again
later. 1: Operation successfully rolled back : Not enough servers to allocate
the requested nodes. We have temporarily sold out of Cloud Bigtable in this
zone. Our support team has been notified and will be bringing more resources on
board. Please try a different zone or try again later.
[31mERROR[0m
apache_beam/io/gcp/bigtableio_it_test.py::[1mTestWriteToBigtableXlangIT::test_set_mutation[0m
- google.api_core.exceptions.Cancelled: 499 Operation successfully rolled back
: Not enough servers to allocate the requested nodes. We have temporarily sold
out of Cloud Bigtable in this zone. Our support team has been notified and will
be bringing more resources on board. Please try a different zone or try again
later. 1: Operation successfully rolled back : Not enough servers to allocate
the requested nodes. We have temporarily sold out of Cloud Bigtable in this
zone. Our support team has been notified and will be bringing more resources on
board. Please try a different zone or try again later.
[31m= [31m[1m1 failed[0m, [32m8 passed[0m, [33m16 skipped[0m, [33m6954
deselected[0m, [33m74 warnings[0m, [31m[1m5 errors[0m[31m in 204.31s
(0:03:24)[0m[31m =[0m
> Task :sdks:python:test-suites:direct:py38:gcpCrossLanguageCleanup
Stopping expansion service pid: 3523573.
Skipping invalid pid: 3523574.
> Task :sdks:python:test-suites:direct:py311:gcpCrossLanguagePythonUsingJava
> FAILED
> Task :sdks:python:test-suites:direct:py311:gcpCrossLanguageCleanup
Stopping expansion service pid: 3523692.
Skipping invalid pid: 3523693.
> Task :sdks:python:test-suites:xlang:fnApiJobServerCleanup
Killing process at 3523628
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task
':sdks:python:test-suites:direct:py38:gcpCrossLanguagePythonUsingJava'.
> Process 'command 'sh'' finished with non-zero exit value 1
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
==============================================================================
2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task
':sdks:python:test-suites:direct:py311:gcpCrossLanguagePythonUsingJava'.
> Process 'command 'sh'' finished with non-zero exit value 1
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
==============================================================================
* Get more help at https://help.gradle.org
Deprecated Gradle features were used in this build, making it incompatible with
Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings
and determine if they come from your own scripts or plugins.
See
https://docs.gradle.org/7.6.2/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 1 invalid unit(s) of work during
this build to ensure correctness.
Please consult deprecation warnings for more details.
BUILD FAILED in 5m 11s
115 actionable tasks: 79 executed, 32 from cache, 4 up-to-date
Publishing build scan...
https://ge.apache.org/s/qpkk5wqi2wv7k
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
