Skip to content

Failures on [vm/concurrency] Remove code duplication in isolate shutdown code #44141

@mkustermann

Description

@mkustermann

The cl/170984 I made is removing some code duplication. To keep validation of canonical constants (which we currently only do in helper isolate shutdown), I've moved the validation logic to a place where it's run for any isolate shutdown (even main isolate).

Doing so seems to reveal existing bugs that trigger during the canonicalization visitor checks:

The tests

language/closure/tearoff_bounds_instantiation_test Crash (expected Pass)
language/least_upper_bound/expansive_runtime_test Crash (expected Pass)
language/nnbd/normalization/generic_function_type_object_normalization_test Crash (expected Pass)
language_2/closure/tearoff_bounds_instantiation_test Crash (expected Pass)
language_2/least_upper_bound/expansive_runtime_test Crash (expected Pass)
vm/cc/CleanupBequestNeverReceived Crash (expected Pass)
vm/cc/CustomIsolates Crash (expected Pass)
vm/cc/ManySimpleTasksWithZones Crash (expected Pass)
vm/cc/ReceivesSendAndExitMessage Crash (expected Pass)

are failing on -n dartk-linux-debug-x64 and all other debug configurations.

Some are due to TypeParameter objects of signature functions (e.g. the language_2/closure/tearoff_bounds_instantiation_test).
Some are due to Type parameter objects (e.g. vm/cc/CleanupBequestNeverReceived)

@crelier Could you maybe take a look at those failures?

Metadata

Metadata

Assignees

Labels

area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions