12:52 a.m.
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.0.Final
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:58 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka updated AS7-2827:
------------------------------
Description:
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long.
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * TimeoutRatios.FSIO );
{code}
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.0.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long.
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * TimeoutRatios.FSIO );
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:06 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka updated AS7-2827:
------------------------------
Description:
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
was:
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long.
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * TimeoutRatios.FSIO );
{code}
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.0.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:13 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka updated AS7-2827:
------------------------------
Description:
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
was:
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.0.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:50 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka updated AS7-2827:
------------------------------
Description:
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
was:
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.0.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:01 p.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-2827:
-----------------------------------
For platforms (if necessary):
* Windows
* Windows
* Solaris
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.0.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-2827:
---------------------------------------
Please resolve against CR1 if the work in pull request 771 took care of this.
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.0.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:33 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-2827:
---------------------------------------
Please either resolve this or use the workflow pulldown and choose the rejected pull
request option. The linked PR is no longer valid.
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.0.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:34 p.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-2827:
----------------------------------
Fix Version/s: 7.1.1.Final
(was: 7.1.0.Final)
Git Pull Request: https://github.com/jbossas/jboss-as/pull/769 (was:
https://github.com/jbossas/jboss-as/pull/769)
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:54 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka resolved AS7-2827.
-------------------------------
Resolution: Rejected
Rejecting QA requirement for configurable timeouts.
No one wants to fix their tests to make this possoble.
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:38 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka reopened AS7-2827:
-------------------------------
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:38 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka commented on AS7-2827:
-----------------------------------
PR 1524 Adds a org.jboss.as.test.shared.TimeRatio class to the shared module.
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:38 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka edited comment on AS7-2827 at 2/15/12 10:38 AM:
-------------------------------------------------------------
PR 1524 Adds a org.jboss.as.test.shared.time.TimeRatio class to the shared module.
was (Author: ozizka):
PR 1524 Adds a org.jboss.as.test.shared.TimeRatio class to the shared module.
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:42 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka edited comment on AS7-2827 at 2/15/12 10:40 AM:
-------------------------------------------------------------
PR 1524 Adds a org.jboss.as.test.shared.time.TimeRatio class to the shared module.
See https://docs.jboss.org/author/display/AS71/AS+7+Testsuite+Test+Developer+... -
Time-related coefficients (ratios)
was (Author: ozizka):
PR 1524 Adds a org.jboss.as.test.shared.time.TimeRatio class to the shared module.
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:19 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Radoslav Husar commented on AS7-2827:
-------------------------------------
https://github.com/jbossas/jboss-as/pull/1754
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:28 a.m.
[
https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka closed AS7-2827.
-----------------------------
TS: Configurable timeouts
-------------------------
Key: AS7-2827
URL: https://issues.jboss.org/browse/AS7-2827
Project: Application Server 7
Issue Type: Sub-task
Components: Test Suite
Reporter: Ondrej Zizka
Assignee: Ondrej Zizka
Fix For: 7.1.1.Final
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.
We should also divide them into categories, depending on what is expected to take long
(consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
* Database operations
For each category, there would be a ratio, 1.0 by default, which would multiply the
timeout.
So the timeout would look like:
{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}
Other possibility is to use @Annotations to mark tests belonging to certain group, like
@LongRunning or such.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5163
days inactive
5264
days old
15 comments
7 participants
participants (7)
-
Brian Stansberry (Commented) (JIRA) -
Brian Stansberry (JIRA)
-
Ondrej Zizka (Commented) (JIRA)
-
Ondrej Zizka (Created) (JIRA)
-
Ondrej Zizka (JIRA)
-
Ondrej Zizka (Updated) (JIRA)
-
Radoslav Husar (JIRA)