-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Adding validation tests for LazyMapCollection #2330
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
Conversation
@swift-ci Please test |
@gribozavr Note that while everything compiled and ran, there are still test failures. Not sure if that's expected or not, just wanted you to be aware. Let me know if you want additional changes. |
@austinzheng I see. We can't merge if there are test failures -- we'd need to investigate. |
@gribozavr The tests that fail are:
and
I can start taking a look at some of these tomorrow if you want. |
It would be great if you could look into these failures! |
@gribozavr Excellent, I'll take a look. If I can get the Map tests working perhaps I can PR those first separately, since there are only a few failures there. I'm also going to push a small change to make some of the failures more descriptive. By the way, |
39ad6e8
to
755c1ab
Compare
Absolutely!
Try |
|
@gribozavr I realized earlier that the non-lazy counterparts to the failing tests are dummied out (e.g. in I'm going to dummy out the tests in the lazy map suite until I figure out exactly what's going on. Fixing the |
More specifically, the GYB template appears as such:
|
If you're talking about the "use LifetimeTracked" comment, that is just a suggestion to improve testing. It is not indicating a bug or anything. |
I'll see if I can replicate the issue I'm seeing with the existing MinimalCollection tests then. |
755c1ab
to
d5e5302
Compare
d5e5302
to
0e22ef6
Compare
@gribozavr I've updated the PR with the following changes:
This PR should pass CI successfully. Let me know what you think. |
@swift-ci Please test and merge |
For future reference: I filed https://bugs.swift.org/browse/SR-1357, which is a possible bug uncovered by these tests. |
What's in this pull request?
Redoing #2247. Tests have been rebased onto latest
master
, and Dmitri's patch has been applied to make them compile. @gribozavrAdding pseudorandom data for the filter tests will be a follow-up PR.
Before merging this pull request to apple/swift repository:
Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
Validation Testing
Note: Only members of the Apple organization can trigger swift-ci.