adjust nfs backup unit test memory usage
Bug #1432687 reported by
Tom Barron
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Tom Barron |
Bug Description
https:/
Swift backup service. Likely because the NFS backup service uses a different "chunk" size by default, the NFS backup unit
tests consume an inappropriate amount of memory and cause test failures due to "memory error" when tox is run in a 1GB
VM.
The tests should be modified to consume less memory and run successfully in a 1GB VM.
Changed in cinder: | |
assignee: | nobody → Tom Barron (tpb) |
tags: | added: tests |
description: | updated |
Changed in cinder: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Thank you!
On 3/16/15 12:43 PM, Andrew Kerr wrote: /review. openstack. netapp. com/#/c/ 203/, which added NFS backup support, ported a number of unit tests from the /review. openstack. org/#/c/ 149726/, which added NFS backup support, ported a number of unit tests from the
> ** Description changed:
>
> - https:/
> + https:/
> Swift backup service. Likely because the NFS backup service uses a different "chunk" size by default, the NFS backup unit
> tests consume an inappropriate amount of memory and cause test failures due to "memory error" when tox is run in a 1GB
> VM.
>
> The tests should be modified to consume less memory and run successfully
> in a 1GB VM.
>