Skip to content
This repository was archived by the owner on Jul 16, 2020. It is now read-only.

test-cases: Fix two bugs #314

Merged
merged 2 commits into from
Jun 23, 2016
Merged

test-cases: Fix two bugs #314

merged 2 commits into from
Jun 23, 2016

Conversation

markdryan
Copy link
Contributor

  1. The first commit fixes Test-cases makes it hard to tell why a unit test fails #295. Test-cases now collects the logs of failing tests cases and outputs them to standard err when all tests have been run.
  2. The second fixes issue, test-cases can hang when packages are specified in a certain order #307, which is a hang that could occur if you specified the packages to test in a certain order.

Mark Ryan added 2 commits June 23, 2016 18:40
Test-cases now gathers up the logs of failed test cases and outputs them
after the report.  Logs are grouped by unit test so it should be easy
to locate the cause of the failure.  Also, we only output logs from failed
test-cases so these logs are not hidden amongst the logs of those that
succeed.  Failed logs are currently only output for textual reports.

Fixes ciao-project#295

Signed-off-by: Mark Ryan <[email protected]>
The code that computed the root package of all packages under test was
buggy.  Depending on the order of the packages supplied to test-cases,
it was possible to enter an endless loop.  This PR fixes the issue.

Fixes ciao-project#307

Signed-off-by: Mark Ryan <[email protected]>
@coveralls
Copy link

coveralls commented Jun 23, 2016

Coverage Status

Coverage remained the same at 62.799% when pulling 2ba00d6 on markdryan:master into f1a0995 on 01org:master.

@mcastelino mcastelino merged commit c3a8a64 into ciao-project:master Jun 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Test-cases makes it hard to tell why a unit test fails
4 participants