| Key: |
QA-35
|
| Type: |
Sub-task
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Pavel Cisar
|
| Reporter: |
Pavel Cisar
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
Not Specified
|
|
|
Remaining Estimate:
|
0 minutes
|
|
|
Time Spent:
|
30 minutes
|
|
|
|
|
Issue Links:
|
Depend
|
|
This issue depends on:
|
|
QA-21
Test db fixture initialization from backup uses absolute path to backup file
|
|
|
|
|
|
Relate
|
|
This issue relate to:
|
|
|
CORE-1063
Server hangs eating CPU and performs huge I/O copying different codepage fields
|
|
|
|
|
|
|
|
| The cvs commits can not be displayed for repository QMTest at the moment since the log has not yet been parsed. The log will be parsed the next time the VcsService runs. If you have administrators privileges you can hasten the next time the service will run in the service section of the Administration pages.
|
| The cvs commits can not be displayed for repository TCS at the moment since the log has not yet been parsed. The log will be parsed the next time the VcsService runs. If you have administrators privileges you can hasten the next time the service will run in the service section of the Administration pages.
|
| The cvs commits can not be displayed for repository Benchmarks at the moment since the log has not yet been parsed. The log will be parsed the next time the VcsService runs. If you have administrators privileges you can hasten the next time the service will run in the service section of the Administration pages.
|
| The cvs commits can not be displayed for repository VulcanJ at the moment since the log has not yet been parsed. The log will be parsed the next time the VcsService runs. If you have administrators privileges you can hasten the next time the service will run in the service section of the Administration pages.
|
| The cvs commits can not be displayed for repository FBTCS at the moment since the log has not yet been parsed. The log will be parsed the next time the VcsService runs. If you have administrators privileges you can hasten the next time the service will run in the service section of the Administration pages.
|
|
