Skip to content

Add new error code tests #35274

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

Merged
merged 1 commit into from
Aug 5, 2016
Merged

Add new error code tests #35274

merged 1 commit into from
Aug 5, 2016

Conversation

GuillaumeGomez
Copy link
Member

@sophiajt
Copy link
Contributor

sophiajt commented Aug 3, 2016

In case anyone is wondering - I'm using these to make sure we have coverage as we convert the new error codes. After we're done, it probably makes sense for these to live in their own directory in compile-fail

@sophiajt
Copy link
Contributor

sophiajt commented Aug 3, 2016

@bors r+

@bors
Copy link
Collaborator

bors commented Aug 3, 2016

📌 Commit fb2d940 has been approved by jonathandturner

@nagisa
Copy link
Member

nagisa commented Aug 4, 2016

Won’t these essentially duplicate existing tests?

@GuillaumeGomez
Copy link
Member Author

@bors: r-

@GuillaumeGomez
Copy link
Member Author

@nagisa: It's for #35233.

@GuillaumeGomez
Copy link
Member Author

Updated (some errors have disappear or be replaced).

@nagisa
Copy link
Member

nagisa commented Aug 4, 2016

I know what it is for. I'm wondering if there aren't already a test that
could be recycled for this. I'm pretty sure we already have a bunch o tests
for various error codes and messages.

On Aug 4, 2016 2:37 PM, "Guillaume Gomez" [email protected] wrote:

@nagisa https://github.com/nagisa: It's for #35233
#35233.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#35274 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AApc0hmV9klS_uT9AbBMinzAEkzMFScGks5qcc7kgaJpZM4JcNdQ
.

@GuillaumeGomez
Copy link
Member Author

@nagisa: They are, but they rarely target a specific error code.

@sophiajt
Copy link
Contributor

sophiajt commented Aug 4, 2016

@nagisa - there may already be a tested, but it's difficult to see what our coverage is without literally searching for each error code.

One possibly future fix would be to include the error code in the unit test filename, so that we can see error codes that aren't being checked. I noticed quite a few don't have tests that only got them because of @GuillaumeGomez's work.

We can also put them in a separate directory under compile-fail just like the borrowck errors, so they're not in the way, but I want to wait to do that until after people have updated them.

@sophiajt
Copy link
Contributor

sophiajt commented Aug 4, 2016

I'm seeing a lot of error codes without any tests. You'd think this would be duplicating work, and it probably will in some cases, but I think coverage is more important.

@bors r+

@bors
Copy link
Collaborator

bors commented Aug 4, 2016

📌 Commit 8502c6c has been approved by jonathandturner

@bors
Copy link
Collaborator

bors commented Aug 4, 2016

💡 This pull request was already approved, no need to approve it again.

@bors
Copy link
Collaborator

bors commented Aug 4, 2016

📌 Commit 8502c6c has been approved by jonathandturner

@bors
Copy link
Collaborator

bors commented Aug 5, 2016

⌛ Testing commit 8502c6c with merge 802d081...

bors added a commit that referenced this pull request Aug 5, 2016
@bors bors merged commit 8502c6c into rust-lang:master Aug 5, 2016
@GuillaumeGomez GuillaumeGomez deleted the err_codes branch August 5, 2016 08:48
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.

4 participants