@StevenCostiou

Hi @adri09070
This test is failing

StDebuggerActionModelTest
 ✗ #testRecompileMethodToInBlockContextWithDeadHomeTwice (7ms)
TestFailure: Got 'methodWithDeadBlockContext

	^ [ (1 + 1) printString ] yourself' instead of 'methodWithDeadBlockContext

	^ [ (1 + 1) printString ] yourself yourself'.
StDebuggerActionModelTest(TestAsserter)>>assert:description:resumable:
StDebuggerActionModelTest(TestAsserter)>>assert:description:
StDebuggerActionModelTest(TestAsserter)>>assert:equals:
StDebuggerActionModelTest>>testRecompileMethodToInBlockContextWithDeadHomeTwice ...assert: (self class >> #methodWithDeadBlockContext) ast sourceCode
		equals: methodWithBlockContextOriginalSource , ' yourself yourself'
StDebuggerActionModelTest(TestCase)>>performT

Hi @Ducasse

Yes, this is because pharo-project/pharo#16319 should be merged first. That's why I put it to draft

Kicking the build again

This is strange since I integrated pharo-project/pharo#16319

May be pharo-project/pharo#16319 is not available yet?

Yes, I don't think pharo-project/pharo#16319 is available yet.
Moreover, the other PR has been merged into Pharo13 and this PR targets Pharo12.
Both PRs should be merged into Pharo13 and Pharo12.

You can change the target branch of this PR to Pharo13 (I have the rights to do it, but I don't find the button to do it on Github) and if the test passes, you could later merge both PRs into Pharo12

Ah, I found the button

But we still need pharo-project/pharo#16319 to be available. I don't know when new Pharo builds are built

Let us wait a bit and see.

I do not understand because the test is failing

StDebuggerActionModelTest
 ✗ #testRecompileMethodToInBlockContextWithDeadHomeTwice (5ms)

We just had to wait for the next Pharo build. The NewTools CI does not create a full image with the bootstrap.

Failing test is unrelated