Skip to content

Fixed Conflict with Swifts Task by renaming Task to MTask #1103

Fixed Conflict with Swifts Task by renaming Task to MTask

Fixed Conflict with Swifts Task by renaming Task to MTask #1103

Re-run triggered December 10, 2024 12:38
Status Failure
Total duration 1m 10s
Artifacts

tests.yml

on: pull_request
linter-check
29s
linter-check
pod-spec-lint
58s
pod-spec-lint
Yaml linting check
3s
Yaml linting check
Matrix: integration_tests
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 12 warnings
integration-tests on macos-latest
Process completed with exit code 1.
integration-tests on ubuntu-20.04
The job was canceled because "macos-latest" failed.
integration-tests on ubuntu-20.04
The operation was canceled.
linter-check: Tests/MeiliSearchIntegrationTests/Utils.swift#L49
Attribute Name Spacing Violation: `@escaping` must have a trailing space before the associated type (attribute_name_spacing)
linter-check: Tests/MeiliSearchIntegrationTests/Utils.swift#L74
Attribute Name Spacing Violation: `@escaping` must have a trailing space before the associated type (attribute_name_spacing)
linter-check: Tests/MeiliSearchIntegrationTests/Utils.swift#L93
Attribute Name Spacing Violation: `@escaping` must have a trailing space before the associated type (attribute_name_spacing)
linter-check: Tests/MeiliSearchIntegrationTests/Utils.swift#L98
Attribute Name Spacing Violation: `@escaping` must have a trailing space before the associated type (attribute_name_spacing)
linter-check: Tests/MeiliSearchUnitTests/MockURLSession.swift#L66
Attribute Name Spacing Violation: There must not be any space between access control modifier and scope (attribute_name_spacing)
pod-spec-lint
Process completed with exit code 1.
Yaml linting check
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
linter-check
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
linter-check: Demos/PerfectDemo/Sources/PerfectTemplate/main.swift#L27
Blanket Disable Command Violation: The disabled 'force_try' rule was already disabled (blanket_disable_command)
linter-check: Demos/PerfectDemo/Sources/PerfectTemplate/main.swift#L27
Blanket Disable Command Violation: Use 'next', 'this' or 'previous' instead to disable the 'force_try' rule once, or re-enable it as soon as possible` (blanket_disable_command)
linter-check: Demos/PerfectDemo/Sources/PerfectTemplate/main.swift#L62
Optional Data -> String Conversion Violation: Prefer failable `String(bytes:encoding:)` initializer when converting `Data` to `String` (optional_data_string_conversion)
linter-check: Demos/PerfectDemo/Sources/PerfectTemplate/main.swift#L108
Optional Data -> String Conversion Violation: Prefer failable `String(bytes:encoding:)` initializer when converting `Data` to `String` (optional_data_string_conversion)
linter-check: Demos/VaporDemo/Sources/App/routes.swift#L41
Optional Data -> String Conversion Violation: Prefer failable `String(bytes:encoding:)` initializer when converting `Data` to `String` (optional_data_string_conversion)
linter-check: Demos/VaporDemo/Sources/App/routes.swift#L74
Optional Data -> String Conversion Violation: Prefer failable `String(bytes:encoding:)` initializer when converting `Data` to `String` (optional_data_string_conversion)
linter-check: Sources/MeiliSearch/Model/Task/TaskDetails.swift#L16
Cyclomatic Complexity Violation: Function should have complexity 10 or less; currently complexity is 13 (cyclomatic_complexity)
linter-check: Sources/MeiliSearch/Model/Task/TaskType.swift#L28
Cyclomatic Complexity Violation: Function should have complexity 10 or less; currently complexity is 12 (cyclomatic_complexity)
linter-check: Sources/MeiliSearch/Tasks.swift#L115
Vertical Parameter Alignment Violation: Function parameters should be aligned vertically if they're in multiple lines in a declaration (vertical_parameter_alignment)
linter-check: Sources/MeiliSearch/Tasks.swift#L116
Vertical Parameter Alignment Violation: Function parameters should be aligned vertically if they're in multiple lines in a declaration (vertical_parameter_alignment)