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

Jump to bottom

standalone/io/test_runner_test is flaky on sim arm and sim mips #12413

Closed
ricowind opened this issue Aug 13, 2013 · 2 comments
Closed

standalone/io/test_runner_test is flaky on sim arm and sim mips #12413

ricowind opened this issue Aug 13, 2013 · 2 comments
Assignees
@zanderso
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@ricowind
Copy link
Contributor

http://chromegw.corp.google.com/i/client.dart/builders/vm-mips-arm-sim-debug/builds/6879/steps/tests/logs/stdio

Marking as flaky in the status file
@ricowind
Copy link
Contributor Author

ricowind commented Sep 4, 2013

This is also flaking on the sim mips

Since we are now using the dart binary to drive the testing script on arm we should probably investigate this (this is a test of the ability to run the testing scripts).

cc @mkustermann.
Removed Priority-Unassigned label.
Added Priority-Medium label.
Changed the title to: "standalone/io/test_runner_test is flaky on sim arm and sim mips".

@iposva-google
Copy link
Contributor

Added Accepted label.

@ricowind ricowind added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Oct 2, 2013
@sgjesse sgjesse mentioned this issue Jun 3, 2015
Closed
@kevmoo kevmoo added P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed accepted labels Feb 29, 2016
@iposva-google iposva-google added the closed-obsolete Closed as the reported issue is no longer relevant label May 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zanderso zanderso

Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant P2 A bug or feature request we're likely to work on type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kevmoo @iposva-google @ricowind @zanderso