Core and Libcore Unit tests produce failures
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
Attempted:
./development/testrunner/runtest.py -b core | tee core-unittest.log
./development/testrunner/runtest.py -b libcore | tee libcore-unittest.log
Both generated failures as seen in attached.
```
Original issue reported on code.google.com by `kati...@gmail.com` on 16 Oct 2009 at 8:30
Attachments:
- [core-unittest.log](https://storage.googleapis.com/google-code-attachments/rowboat/issue-3/comment-0/core-unittest.log)
- [libcore-unittest.log](https://storage.googleapis.com/google-code-attachments/rowboat/issue-3/comment-0/libcore-unittest.log)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running development/testrunner/runtest.py with the core and libcore targets, capturing output as shown in the issue. Read core-unittest.log and libcore-unittest.log to identify the failing tests and their causes. Done means the reported unit-test failures are resolved and both targets complete successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100