Skip to content
CI

Rename app field #3063

Sign in to view logs

Rename app field

Rename app field #3063

Triggered via pull request July 10, 2024 08:42
@disrupteddisrupted
ready_for_review #506
refactor/app
Status Failure
Total duration 2m 14s
Artifacts –

ci.yaml

on: pull_request
Matrix: Test
publish-docs-from-main
0s
publish-docs-from-main
publish-dev-docs-from-pr
0s
publish-dev-docs-from-pr
Publish snapshot to TestPyPI  /  Publish snapshot
Publish snapshot to TestPyPI / Publish snapshot
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 6 warnings
Test (ubuntu-22.04, 3.12)
Process completed with exit code 1.
Test (ubuntu-22.04, 3.10): tests/cli/test_schema_generation.py#L106
Type of "type" is unknown (reportUnknownMemberType)
Test (ubuntu-22.04, 3.10): kpops/components/base_components/helm_app.py#L191
Type of "model_dump" is partially unknown
Test (ubuntu-22.04, 3.10): kpops/components/base_components/helm_app.py#L211
Type of parameter "handler" is unknown (reportUnknownParameterType)
Test (ubuntu-22.04, 3.10): kpops/components/base_components/helm_app.py#L212
Argument type is unknown
Test (ubuntu-22.04, 3.10): tests/pipeline/test_components/components.py#L14
Import "kpops.components.common.topic" could not be resolved (reportMissingImports)
Test (ubuntu-22.04, 3.10): tests/pipeline/test_components/components.py#L14
Type of "OutputTopicTypes" is unknown (reportUnknownVariableType)
Test (ubuntu-22.04, 3.10): tests/pipeline/test_components/components.py#L14
Type of "TopicConfig" is unknown (reportUnknownVariableType)
Test (ubuntu-22.04, 3.10): tests/pipeline/test_components/components.py#L38
Type of "topic_config" is unknown (reportUnknownVariableType)
Test (ubuntu-22.04, 3.10): tests/pipeline/test_components/components.py#L38
Type of "topics" is partially unknown
Test (ubuntu-22.04, 3.10): tests/pipeline/test_components/components.py#L39
Type of "type" is unknown (reportUnknownMemberType)
Test (ubuntu-22.04, 3.11)
Process completed with exit code 1.
Test (windows-2022, 3.12)
Process completed with exit code 1.
Test (windows-2022, 3.11)
Process completed with exit code 1.
Test (windows-2022, 3.10)
Process completed with exit code 1.
Test (ubuntu-22.04, 3.12)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test (ubuntu-22.04, 3.10)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test (ubuntu-22.04, 3.11)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test (windows-2022, 3.12)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test (windows-2022, 3.11)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Test (windows-2022, 3.10)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/