Guest log scenario test can take excessively long

Bug #1559214 reported by Peter Stachowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Low
Peter Stachowski

Bug Description

For some datastores (for example postgreSQL), the guest-log scenario test run_test_log_generator_user_by_row can take an inordinate amount of time, since a lot of data is written into the user log once it is enabled. This test should be capped so that an extremely large log file won't cause the tests to time out.

Changed in trove:
importance: Undecided → Low
assignee: nobody → Peter Stachowski (peterstac)
milestone: none → next
milestone: next → newton-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

Fix proposed to branch: master
Review: https://review.openstack.org/294707

Changed in trove:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/294707
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=c72b2463a443d305cee9d4e5c0506ef9e450844d
Submitter: Jenkins
Branch: master

commit c72b2463a443d305cee9d4e5c0506ef9e450844d
Author: Peter Stachowski <email address hidden>
Date: Fri Mar 18 16:32:36 2016 +0000

    Cap test_log_generator_user_by_row to 100

    For some datastores (for example postgreSQL), the guest-log scenario
    test test_log_generator_user_by_row can take an inordinate amount of
    time, since a lot of data is written into the user log once it is
    enabled. This test should be capped so that an extremely large log file
    won't cause the tests to time out.

    Change-Id: Ie10c5cc4d5390013d111aef27991a747ac2ff795
    Closes-Bug: #1559214

Changed in trove:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/trove 6.0.0.0b2

This issue was fixed in the openstack/trove 6.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.