Skip to content

Conversation

@Catfish-Man
Copy link
Contributor

Finishing up @milseman's #710

@Catfish-Man Catfish-Man self-assigned this Feb 3, 2024
@Catfish-Man
Copy link
Contributor Author

@swift-ci please test

@Catfish-Man
Copy link
Contributor Author

New assertion already paying off

Test Case 'AlgorithmTests.testMatchesCollection' started at 2024-02-03 00:43:54.316
_StringProcessing/MEQuantify.swift:133: Assertion failed

@Catfish-Man
Copy link
Contributor Author

@swift-ci please test

@Catfish-Man
Copy link
Contributor Author

Nate thinks the remaining test failure is due to CI trying to run the tests concurrently

@Catfish-Man
Copy link
Contributor Author

Failure appears to be pre-existing, going ahead and merging

@Catfish-Man Catfish-Man merged commit a71041f into swiftlang:main Feb 7, 2024
@milseman
Copy link
Member

milseman commented Feb 7, 2024

@Catfish-Man Err, this is hitting an assert introduced by this PR. Should we revert and fix?

edit: I see, that was pre-fix. Let's in general try to get a clean CI before merging though, unless there's an emergency rush.

@milseman
Copy link
Member

milseman commented Feb 7, 2024

Is it a problem for tests to run concurrently? Why?

@Catfish-Man
Copy link
Contributor Author

Ok. I discussed with Nate first and made sure it passed locally

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.

2 participants