Skip to content

Tests: Have a way to "freeze" the code used when compiling the compiler #2303

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

Closed
smarter opened this issue Apr 25, 2017 · 5 comments · Fixed by #14255
Closed

Tests: Have a way to "freeze" the code used when compiling the compiler #2303

smarter opened this issue Apr 25, 2017 · 5 comments · Fixed by #14255

Comments

@smarter
Copy link
Member

smarter commented Apr 25, 2017

Some of the tests compile (part of) the compiler's code. When debugging an issue this can be problematic because debugging might involving changing the compiler code, and thus affective the issue we're trying to fix. It would be nice if we could temporarily freeze the code used in the tests to avoid this. One way to do that would be to make a fresh git clone of dotty somewhere else and run the tests with some option like --tests-src=../dotty-upstream.

@SethTisue
Copy link
Member

Some of the tests compile (part of) the compiler's code

They do? What's an example? Not sure what this means.

@smarter
Copy link
Member Author

smarter commented Jan 11, 2022

@dwijnand
Copy link
Member

Ah. That one looks more of a comprehensive integration test than asserting some specific behaviour. What do you think if we move that to a new file? Or maybe move it into FromTastyTests.

@smarter
Copy link
Member Author

smarter commented Jan 11, 2022

I'm happy if anyone looks into our test infrastructure at all no matter what they do 😄

@SethTisue
Copy link
Member

lolcry

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants