Bug 1213875

Summary:	(6.4.1) [SET] WFLY-3947 - Incorrect EJB Calendar Based Timeouts
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	baranowb <bbaranow>
Component:	Testsuite	Assignee:	baranowb <bbaranow>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Slavicek <pslavice>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	cdewolf, jawilson, jpallich, mkopecky, ozizka, pslavice
Target Milestone:	CR2
Target Release:	EAP 6.4.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 09:59:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	996500, 1207953

Description baranowb 2015-04-21 13:22:18 UTC

Seems like without it, whenever I try to do a test run on fresh branch I get: 

-------------------------------------------------------------------------------
 Test set: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase
-------------------------------------------------------------------------------
 Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.452 sec <<< FAILURE! - in org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase
testCalendarBasedTimeout(org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase)  Time elapsed: 3.451 sec  <<< FAILURE!
java.lang.AssertionError: Eastern European Time
 at org.junit.Assert.fail(Assert.java:88)
 at org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.testWithStartInThePast(CalendarBasedTimeoutTestCase.java:539)
 at org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.testCalendarBasedTimeout(CalendarBasedTimeoutTestCase.java:129


Wick cherry-picked commit from said JIRA I can run testsuite( ongoing ) - without it fails due to failure in 'ejb3' module.

Comment 4 Rostislav Svoboda 2015-04-23 11:55:19 UTC

Re-acking after "qa_ack flag reset for and jboss-eap-6.4.0 and jboss-eap-6.4.z items" cleanup.

Comment 5 Panagiotis Sotiropoulos 2015-04-27 08:47:39 UTC

*** Bug 1125944 has been marked as a duplicate of this bug. ***

Comment 8 Marek Kopecky 2015-05-18 07:18:41 UTC

Verified on EAP 6.4.1.CP.CR2

We don't see this error on EAP 6.4.1.CP.CR2

Comment 10 Petr Penicka 2017-01-17 09:59:07 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.

Comment 11 Petr Penicka 2017-01-17 10:00:13 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.