Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365543 - TimerExecScheduler_Test#testSerializationIsThreadSafe failed from time to time
Summary: TimerExecScheduler_Test#testSerializationIsThreadSafe failed from time to time
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.5 M4   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-05 01:42 EST by Ivan Furnadjiev CLA
Modified: 2011-12-05 07:35 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Furnadjiev CLA 2011-12-05 01:42:03 EST 
This test failed for me couple of times in the last week. Now it failed on Hudson build too. Could be related to the changes for bug 364863?
Comment 1 Ralf Sternberg CLA 2011-12-05 05:15:39 EST 
This tests always fails for me when running the tycho build locally. I don't see it in the Junit tests started from the IDE.
Comment 2 Rüdiger Herrmann CLA 2011-12-05 07:35:58 EST 
The test setup was nonsense. It ran several threads in parallel that added tasks to and serialized one and the same scheduler in each thread. Serializing however, is not meant to be thread safe. What should be tested is: several threads add and remove tasks while *one* thread serializes the scheduler. Changed the test accordingly.

Please reopen if you see the test fail again.