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.

Sign up for GitHub

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

Test standalone/io/file_stream_test leaves large temp file on ARM #26109

Closed
whesse opened this issue Mar 29, 2016 · 2 comments
Closed

Test standalone/io/file_stream_test leaves large temp file on ARM #26109

whesse opened this issue Mar 29, 2016 · 2 comments
Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. library-io P3 A lower priority bug or feature request type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@whesse
Copy link
Contributor

whesse commented Mar 29, 2016

This test is leaving a 100 MB test file in the temp directory every time it runs on ARM hardware. Skipping the test on ARM, for now. It does not leave a file on intel linux.
@whesse whesse added P3 A lower priority bug or feature request library-io type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) labels Mar 29, 2016
whesse added a commit that referenced this issue Mar 29, 2016
@whesse
Skip file test on ARM that leaves large file in temp directory
3706777 
BUG=#26109
R=sgjesse@google.com

Review URL: https://codereview.chromium.org/1841583004 .
@sgjesse sgjesse added the area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. label Mar 29, 2016
@whesse
Copy link
Contributor Author

whesse commented May 9, 2016

file_typed_data_test also leaves a 500 MB file in the temp directory, now.
The temp directory on our arm hardware is a separate mount, with only 1 MB space, so this breaks everything.

whesse added a commit that referenced this issue May 9, 2016
@whesse
Update status for dart:io file test on ARM.
1d1409d 
BUG=#26109
R=sgjesse@google.com

Review URL: https://codereview.chromium.org/1963593002 .
@whesse
Copy link
Contributor Author

whesse commented May 16, 2016

file_input_stream_test has at least 5 subtests which call writeLongFileSync, which creates a file of about 500 kB. This exceeds the temp directory size, especially since they are not cleaned up until the end.
Suppressing this test in the status file.

whesse added a commit that referenced this issue May 18, 2016
@whesse
Suppress test on ARM that creates large files.
9d3d9ae 
BUG=#26109
R=sgjesse@google.com

Review URL: https://codereview.chromium.org/1979983002 .
copybara-service bot pushed a commit that referenced this issue Oct 9, 2023
@rmacnak-google
[test] Remove ARM64-specific status entries.
c816c1d 
In particular, this un-skips the service tests.

TEST=ci
Bug: b/302156166
Bug: #26109
Bug: #27806
Bug: #33057
Bug: #52589
Change-Id: Ieddf50ac6c27d23c5efa26a7e5bf7f9044350a5e
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/328381
Reviewed-by: Jonas Termansen <sortie@google.com>
Commit-Queue: Ryan Macnak <rmacnak@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. library-io P3 A lower priority bug or feature request type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sgjesse @whesse @rmacnak-google