Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Don't merge] CI sanity check -- please ignore #197

Closed
wants to merge 9 commits into from

Conversation

lorentey
Copy link
Member

This is double checking against a potential CI issue, where CI tests may be running on an outdated snapshot.

With #196, I'm seeing symptoms that appear as if CI tests are running on an older checkout, rather than the latest source tree.

Checklist

  • I've read the Contribution Guidelines
  • My contributions are licensed under the Swift license.
  • I've followed the coding style of the rest of the project.
  • I've added tests covering all new code paths my change adds to the project (if appropriate).
  • I've added benchmarks covering new functionality (if appropriate).
  • I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
  • I've updated the documentation if necessary.

It is not tenable to continue supporting ancient toolchains
indefinitely, as each supported toolchain version adds a nontrivial
amount of prerelease testing work. Additionally, working around
bugs in older toolchains that have been long since resolved is not a
productive use of anyone’s time.

Users who are stuck on older toolchains are of course welcome to
continue using the last package release that supports their
platform. (And they may continue to receive bug fix updates, as
we can always tag new bugfix releases on older minor release
branches.)
@lorentey
Copy link
Member Author

@swift-ci test

@lorentey
Copy link
Member Author

Huh, same unexpected output. 🤔

[560/567] Testing PersistentCollectionsTests.PersistentSetTests/test_symmetricDifference_exhaustive
error: Exited with signal code 4
[561/567] Testing PersistentCollectionsTests.PersistentSetTests/test_union_exhaustive
[562/567] Testing DequeTests.RangeReplaceableCollectionTests/test_customRemoveLast_many
[563/567] Testing DequeTests.RangeReplaceableCollectionTests/test_appendManyFromMinimalCollection
[564/567] Testing DequeTests.RangeReplaceableCollectionTests/test_appendOne
[565/567] Testing DequeTests.RangeReplaceableCollectionTests/test_appendManyFromMinimalSequence
[566/567] Testing DequeTests.RangeReplaceableCollectionTests/test_appendManyFromBridgedArray
[567/567] Testing DequeTests.RangeReplaceableCollectionTests/test_appendManyFromContiguousArray
Test Suite 'Selected tests' started at 2022-10-10 22:30:52.834Test Suite 'swift-collectionsPackageTests.xctest' started at 2022-10-10 22:30:52.834Test Suite 'DequeTests' started at 2022-10-10 22:30:52.834Test Case '-[DequeTests.DequeTests test_prependManyFromBridgedArray]' started.Swift/ArrayBuffer.swift:319: Fatal error: unsupported
Test Suite 'Selected tests' started at 2022-10-10 22:33:59.539Test Suite 'swift-collectionsPackageTests.xctest' started at 2022-10-10 22:33:59.540Test Suite 'RangeReplaceableCollectionTests' started at 2022-10-10 22:33:59.540Test Case '-[DequeTests.RangeReplaceableCollectionTests test_sequenceInitializer_bridgedArray]' started.Swift/ArrayBuffer.swift:319: Fatal error: unsupported
Test Suite 'Selected tests' started at 2022-10-10 22:33:16.241Test Suite 'swift-collectionsPackageTests.xctest' started at 2022-10-10 22:33:16.241Test Suite 'RangeReplaceableCollectionTests' started at 2022-10-10 22:33:16.241Test Case '-[DequeTests.RangeReplaceableCollectionTests test_appendManyFromBridgedArray]' started.Swift/ArrayBuffer.swift:319: Fatal error: unsupported

@lorentey
Copy link
Member Author

@swift-ci clean test macOS platform

@lorentey
Copy link
Member Author

@swift-ci test macOS platform

@lorentey
Copy link
Member Author

@swift-ci test

@lorentey lorentey closed this Oct 11, 2022
@lorentey lorentey deleted the test branch October 11, 2022 00:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant