Bug 474499 - JavaFX Toolkit - Graphical Component - Action error during the single click - StepExecutionException: null
Summary: JavaFX Toolkit - Graphical Component - Action error during the single click -...
Status: CLOSED INVALID
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: RC (show other bugs)
Version: 3.0   Edit
Hardware: All Windows All
: P3 normal (vote)
Target Milestone: 4.0   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 421595
  Show dependency tree
 
Reported: 2015-08-07 08:50 EDT by Maissmaallsmyss Maulhs-Vvuillss CLA
Modified: 2016-05-19 03:39 EDT (History)
2 users (show)

See Also:


Attachments
TestResults&Logs (11.17 KB, application/x-zip)
2015-08-07 08:50 EDT, Maissmaallsmyss Maulhs-Vvuillss CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maissmaallsmyss Maulhs-Vvuillss CLA 2015-08-07 08:50:02 EDT
Created attachment 255699 [details]
TestResults&Logs

I am sporadically getting an Action Error (Timeout) on a try to close the dialog (click left single on the "ok" button). Or the click is quite often actually not executed (I have 5-6 or even more errors due to this during evening PRODUCTIVE execution) so the dialog remains opened and prevents further test execution.

Jubula 8.1.6

JavaFX Log
2015-08-07 14:36:08.620 [Connection.ReaderThread:Socket[addr=g8.dev.bredex.local/10.54.50.36,port=60078,localport=54598]] ERROR o.e.j.r.j.d.EventThreadQueuerJavaFXImpl - java.lang.InterruptedException
2015-08-07 14:36:08.621 [Connection.ReaderThread:Socket[addr=g8.dev.bredex.local/10.54.50.36,port=60078,localport=54598]] ERROR o.e.j.c.internal.Communicator - Exception while calling listener
org.eclipse.jubula.rc.common.exception.StepExecutionException: null
Comment 1 Maissmaallsmyss Maulhs-Vvuillss CLA 2015-08-07 08:52:08 EDT
I also get the StepExecutionException: null in the Bug 474497 - JavaFX Toolkit - ListView - sporadical wrong list entry selection
Comment 2 Marcel Hein CLA 2015-08-11 03:07:02 EDT
This might be caused by our Environment(G8) at Bredex. Could you check if this is still a Problem when you execute Tests on a VM or a your Laptop.
Comment 3 Maissmaallsmyss Maulhs-Vvuillss CLA 2015-08-13 05:16:35 EDT
I have not observed such errors during last two PRODUCTION Tests executions under the VM. So this works for me and probably can be closed.
Comment 4 Oliver Goetz CLA 2015-08-14 05:36:55 EDT
Closed due to comment 3