| 2015-07-23 12:40:02 |
Valeriy Ponomaryov |
bug |
|
|
added bug |
| 2015-07-23 12:40:28 |
Valeriy Ponomaryov |
description |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job report different results on the same state if run it again and again.
Results for three runs:
RUN statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called. |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
RUN statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called. |
|
| 2015-07-23 12:42:50 |
Valeriy Ponomaryov |
description |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
RUN statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called. |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
RUN statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called.
Some debug discovered several problem places, that have different coverage:
manila/db/sqlalchemy/api
manila/service
manila/test
manila/tests/network/test_share_network_db
manila/tests/test_service
manila/openstack/common/scheduler/weights/__init__
manila/share/drivers/hds/sop |
|
| 2015-07-23 12:43:56 |
Valeriy Ponomaryov |
summary |
manila coverage job shows different results after reruns |
manila 'cover' tox job shows different results after reruns |
|
| 2015-07-23 12:52:06 |
Valeriy Ponomaryov |
description |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
RUN statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called.
Some debug discovered several problem places, that have different coverage:
manila/db/sqlalchemy/api
manila/service
manila/test
manila/tests/network/test_share_network_db
manila/tests/test_service
manila/openstack/common/scheduler/weights/__init__
manila/share/drivers/hds/sop |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
RUN statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
4 43573 4584 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called.
Some debug discovered several problem places, that have different coverage:
manila/db/sqlalchemy/api
manila/service
manila/test
manila/tests/network/test_share_network_db
manila/tests/test_service
manila/openstack/common/scheduler/weights/__init__
manila/share/drivers/hds/sop |
|
| 2015-07-23 12:52:22 |
Valeriy Ponomaryov |
description |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
RUN statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
4 43573 4584 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called.
Some debug discovered several problem places, that have different coverage:
manila/db/sqlalchemy/api
manila/service
manila/test
manila/tests/network/test_share_network_db
manila/tests/test_service
manila/openstack/common/scheduler/weights/__init__
manila/share/drivers/hds/sop |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
Runs statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
4 43573 4584 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called.
Some debug discovered several problem places, that have different coverage:
manila/db/sqlalchemy/api
manila/service
manila/test
manila/tests/network/test_share_network_db
manila/tests/test_service
manila/openstack/common/scheduler/weights/__init__
manila/share/drivers/hds/sop |
|
| 2015-07-23 12:52:34 |
Valeriy Ponomaryov |
description |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
Runs statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
4 43573 4584 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called.
Some debug discovered several problem places, that have different coverage:
manila/db/sqlalchemy/api
manila/service
manila/test
manila/tests/network/test_share_network_db
manila/tests/test_service
manila/openstack/common/scheduler/weights/__init__
manila/share/drivers/hds/sop |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
Run№ statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
4 43573 4584 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called.
Some debug discovered several problem places, that have different coverage:
manila/db/sqlalchemy/api
manila/service
manila/test
manila/tests/network/test_share_network_db
manila/tests/test_service
manila/openstack/common/scheduler/weights/__init__
manila/share/drivers/hds/sop |
|
| 2015-07-23 12:52:45 |
Valeriy Ponomaryov |
tags |
|
tests unit |
|
| 2015-07-23 13:24:55 |
Valeriy Ponomaryov |
description |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
Run№ statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
4 43573 4584 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called.
Some debug discovered several problem places, that have different coverage:
manila/db/sqlalchemy/api
manila/service
manila/test
manila/tests/network/test_share_network_db
manila/tests/test_service
manila/openstack/common/scheduler/weights/__init__
manila/share/drivers/hds/sop |
We have tox job "cover" that calculate total code coverage with unit tests.
And this job reports different results on the same state if run it again and again.
Results for three runs:
Run№ statements missing excluded coverage
1 43573 4568 0 90%
2 43573 4580 0 89%
3 43573 4577 0 89%
4 43573 4584 0 89%
Looks like we have some concurrency issues in unit tests that lead to really different code lines be called.
Some debug discovered several problem places, that have different coverage:
manila/db/sqlalchemy/api
manila/service
manila/share/drivers/generic
manila/test
manila/tests/network/test_share_network_db
manila/tests/share/drivers/test_generic
manila/tests/share/test_manager
manila/tests/test_service
manila/openstack/common/scheduler/weights/__init__
manila/share/drivers/hds/sop |
|
| 2015-07-24 11:34:15 |
Valeriy Ponomaryov |
manila: importance |
Undecided |
Medium |
|
| 2015-07-24 14:19:09 |
OpenStack Infra |
manila: status |
New |
In Progress |
|
| 2015-07-24 14:19:09 |
OpenStack Infra |
manila: assignee |
|
Valeriy Ponomaryov (vponomaryov) |
|
| 2015-07-24 14:19:19 |
Valeriy Ponomaryov |
manila: milestone |
|
liberty-2 |
|
| 2015-07-29 13:55:58 |
Ben Swartzlander |
manila: milestone |
liberty-2 |
liberty-3 |
|
| 2015-09-03 13:30:31 |
Thierry Carrez |
manila: milestone |
liberty-3 |
liberty-rc1 |
|
| 2015-09-04 16:10:12 |
Valeriy Ponomaryov |
manila: importance |
Medium |
Low |
|
| 2015-09-08 09:12:58 |
Valeriy Ponomaryov |
manila: milestone |
liberty-rc1 |
|
|
| 2015-09-08 09:13:01 |
Valeriy Ponomaryov |
manila: assignee |
Valeriy Ponomaryov (vponomaryov) |
|
|
| 2015-09-08 09:13:05 |
Valeriy Ponomaryov |
manila: status |
In Progress |
Confirmed |
|
| 2018-03-15 16:13:22 |
Tom Barron |
manila: status |
Confirmed |
Fix Released |
|
