Skip to content
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

Many dart:isolate tests are being skipped in dartium as spawnFunction is not allowed in the main DOM isolate #14626

Closed
a-siva opened this issue Oct 30, 2013 · 2 comments
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). closed-duplicate Closed in favor of an existing report

Comments

@a-siva
Copy link
Contributor

a-siva commented Oct 30, 2013

Many dart:isolate tests are being skipped or Fail in dartium as spawnFunction is not allowed in the main DOM isolate.

All these tests do not use any of the DOM functionality they just need a background isolate to run. These tests would work if they are re-written to first spawn a test isolate using spawnURI and then run the actual test code which does spawnFunction etc.

The following tests are marked failing on Dartium

Issue #13921: spawnFunction is not allowed on Dartium's DOM thread.

browser/compute_this_script_browser_test: Fail
browser/typed_data_message_test: Skip # 13961
count_test: Fail
cross_isolate_message_test: Fail
global_error_handler2_test: Fail
global_error_handler_test: Fail
illegal_msg_test: Fail
isolate_complex_messages_test: Fail
isolate_stress_test: Fail
mandel_isolate_test: Fail
message2_test: Fail
message_test: Fail
mint_maker_test: Fail
nested_spawn2_test: Fail
nested_spawn_test: Fail
request_reply_test: Fail
spawn_function_custom_class_test: Fail
spawn_function_test: Fail
stacktrace_message_test: Fail
unresolved_ports_test: Fail

LibTest/isolate/isolate_api/spawnFunction_A01_t01: Fail # Issue #13921
LibTest/isolate/isolate_api/spawnFunction_A01_t02: Fail # Issue #13921
LibTest/isolate/isolate_api/spawnFunction_A01_t03: Fail # Issue #13921
LibTest/isolate/isolate_api/spawnFunction_A01_t04: Fail # Issue #13921
LibTest/isolate/isolate_api/spawnFunction_A01_t05: Fail # Issue #13921
LibTest/isolate/isolate_api/spawnFunction_A02_t01: Fail # Issue #13921
LibTest/isolate/isolate_api/spawnFunction_A03_t01: Fail # Issue #13921
LibTest/isolate/isolate_api/spawnFunction_A04_t02: Fail # Issue #13921
LibTest/isolate/isolate_api/spawnFunction_A04_t02: Timeout # Issue #13719: Please triage this failure.
LibTest/isolate/isolate_api/spawnFunction_A04_t03: Fail # Issue #13921
LibTest/isolate/isolate_api/spawnFunction_A04_t03: Timeout # Issue #13719: Please triage this failure.
LibTest/isolate/isolate_api/streamSpawnFunction_A01_t01: Fail # Issue #13921
LibTest/isolate/IsolateSink/add_A01_t01: Fail # Issue #13921
LibTest/isolate/IsolateSink/add_A01_t02: Fail # Issue #13921
LibTest/isolate/IsolateSink/add_A02_t01: Fail # Issue #13921
LibTest/isolate/IsolateSink/close_A01_t03: Fail # Issue #13921
LibTest/isolate/IsolateSink/close_A01_t04: Fail # Issue #13921
LibTest/isolate/IsolateSink/operator_equality_A01_t01: Fail # Issue #13921
LibTest/isolate/ReceivePort/toSendPort_A01_t02: Pass, Fail # Issue #13719: Please triage this failure.
LibTest/isolate/SendPort/send_A02_t01: Fail # Issue #13921
LibTest/isolate/SendPort/send_A02_t04: Fail # Issue #13921
LibTest/isolate/SendPort/send_A02_t05: Fail # Issue #13921
LibTest/isolate/SendPort/send_A02_t06: Fail # Issue #13921

typed_array_test: Fail # Issue #13921
typed_array_int64_uint64_test: Fail # Issue #13921

Language/12_Expressions/12_Spawning_an_Isolate_A01_t01: Fail # Issue #13921

@whesse
Copy link
Contributor

whesse commented Mar 27, 2014

This is basically just an extension of issue #13921, isn't it, with discussion happening on both issues. Should it be marked as duplicate? There isn't really an Area-Test - nobody is responsible for that area.

@lrhn
Copy link
Member

lrhn commented Oct 29, 2014

Added Duplicate label.
Marked as being merged into #13921.

@a-siva a-siva added Type-Defect area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). closed-duplicate Closed in favor of an existing report labels Oct 29, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-test Cross-cutting test issues (use area- labels for specific failures; not used for package:test). closed-duplicate Closed in favor of an existing report
Projects
None yet
Development

No branches or pull requests

4 participants