Fix #2762 - eval after zip may cause interruption

[mpilquist]

In the fix for #2717, we discovered that sometimes after zipping, a closed scope is used for evaluation. We fixed #2717 by ensuring that manual interruption checks occur on the nearest open scope in the case the current scope has been closed already. We needed a similar check for effect evaluation, which checks interruption inside interruptibleEval.

[diesalbla]

@mpilquist So, I have noticed that this Pull Request has broken the memory leak tests. In particular, the test broadcastThrough identity and observe + zip seems to have broken after the change.

Edit those memory leak tests were being run with the Graal VM, OpenJDK Runtime Environment GraalVM CE 21.3.0 (build 17.0.1+12-jvmci-21.3-b05).

[mpilquist]

I see these failures on HEAD - 2173855:

==> X fs2.MemoryLeakSpec.parJoin
==> X fs2.MemoryLeakSpec.broadcastThrough identity

Moving back a few commits to 61b593c:

==> X fs2.MemoryLeakSpec.parJoin
==> X fs2.MemoryLeakSpec.hung merge
==> X fs2.MemoryLeakSpec.broadcastThrough identity

v3.2.0 is good

b811c67 is bad:

==> X fs2.MemoryLeakSpec.parJoin
==> X fs2.MemoryLeakSpec.broadcastThrough identity
==> X fs2.MemoryLeakSpec.observe + zip

0d3ef3b is good

2861a4e is bad:

==> X fs2.MemoryLeakSpec.drain onComplete
==> X fs2.MemoryLeakSpec.hung merge
==> X fs2.MemoryLeakSpec.attempts + pull

d508c4c is good

0d6f6cb is good

7268392 is bad:

==> X fs2.MemoryLeakSpec.hung merge
==> X fs2.MemoryLeakSpec.retry

df62117 is good

3b5edc5 is good

Offending commit:

72683927716d3eb666fd507dd4ff717c9f233349 is the first bad commit
commit 72683927716d3eb666fd507dd4ff717c9f233349
Author: danicheg <e.danicheg@yandex.ru>
Date:   Sun Nov 28 14:55:09 2021 +0300

    Bump CE version to 3.3.0

 build.sbt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

[armanbilge]

Hmm, seems plausible to me that these tests may need to be adjusted, due to the increased memory pressure caused by fiber dumps. Run with tracing disabled?

[mpilquist]

Yeah, I'm trying to disable tracing on the integration tests now