Fix failing tests that compare source of baseline methods #522
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In squeak, we do not log to the changes, meaning our original version will be the decompile string. To still compare the two, we this replace the t1 in the decompile with the actual name and pretty-print both strings.
|
SmalltalkHub is down and that is causing the Pharo test failures ... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proposal for fixing the issue where comparing the source of baseline methods fails in Squeak-trunk, because Squeak-trunk no longer logs the source code to the changes file when asked to
#suspendSystemUpdateEventsDuring:.We take two steps:
t1from the decompile string withspec(cc'ing @j4yk since we had talked about it in the issue before)