feat(tidy3d-client): pole residue broadband injection (FXC-3352) (#3819) #9101
flex-copybara-sync[bot]tidy3d-python-client-tests.yml
on: push
determine-test-scope
4s
Matrix: extras-integration-tests / integration-tests-basic
Matrix: extras-integration-tests / integration-tests-full
Matrix: local-tests
Matrix: remote-tests
move-type-imports
0s
verify-linting
0s
static-type-checks (mypy)
0s
Run zizmor 🌈
0s
lint-branch-name
0s
enforce-changelog-policy
0s
lint-commit-messages
0s
verify-schema-change
0s
verify-version-consistency
0s
test-submodules
0s
develop-cli-tests
/
test-dev-commands
pr-requirements-pass
0s
Annotations
27 errors and 11 warnings
|
python-3.13-ubuntu-latest
Process completed with exit code 1.
|
|
python-3.13-macos-latest
Process completed with exit code 1.
|
|
python-3.10-ubuntu-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.10-ubuntu-latest
Process completed with exit code 1.
|
|
python-3.12-ubuntu-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.12-ubuntu-latest
Process completed with exit code 1.
|
|
python-3.11-ubuntu-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.11-ubuntu-latest
The operation was canceled.
|
|
python-3.11-macos-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.11-macos-latest
The operation was canceled.
|
|
python-3.12-macos-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.12-macos-latest
Process completed with exit code 1.
|
|
extras-integration-tests / python-3.10-linux-x86_64
Process completed with exit code 1.
|
|
python-3.10-macos-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.10-macos-latest
The operation was canceled.
|
|
python-3.10-windows-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.10-windows-latest
The operation was canceled.
|
|
python-3.11-windows-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.11-windows-latest
The operation was canceled.
|
|
extras-integration-tests / python-3.10-macos-arm64
Process completed with exit code 1.
|
|
python-3.13-windows-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.13-windows-latest
The operation was canceled.
|
|
extras-integration-tests / python-3.13-windows-x64-3.13
Process completed with exit code 1.
|
|
python-3.12-windows-latest
The strategy configuration was canceled because "remote-tests._3_13_macos-latest" failed
|
|
python-3.12-windows-latest
The operation was canceled.
|
|
extras-integration-tests / python-3.10-windows-x64-3.10
Process completed with exit code 1.
|
|
workflow-validation
Process completed with exit code 1.
|
|
python-3.13-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
python-3.13-macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
python-3.10-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
python-3.12-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
python-3.11-ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
python-3.11-macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
python-3.12-macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
extras-integration-tests / python-3.10-linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
extras-integration-tests / python-3.10-macos-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
extras-integration-tests / python-3.13-windows-x64-3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
extras-integration-tests / python-3.10-windows-x64-3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|