There are 3 new failures found in the openjfx-compiler unit test suite. This cause is traced to the switch from scenario to runtime. Here is the results of running the 3 tests (in attachment) before and after switching to runtime:
Using Scenario
------------------------
~/JIRAXXX$ javafx deferAction
deferAction Script
Starting Script
java.lang.NullPointerException: Action function can not be null
Running Deferred Action
Running Deferred Action2
Running Deferred Action with Nesting
Running Nested Deferred Action
~/JIRAXXX$ javafx jfxc1043
timeline finished - 2.0
~/JIRAXXX$ javafx jfxc2544
0
1
2
3
4
5
Using runtime
-----------------------
~/JIRAXXX$ javafx deferAction
deferAction Script
Starting Script
java.lang.NullPointerException: Action function can not be null
~/JIRAXXX$ javafx jfxc1043
~/JIRAXXX$ javafx jfxc2544
0
Using Scenario
------------------------
~/JIRAXXX$ javafx deferAction
deferAction Script
Starting Script
java.lang.NullPointerException: Action function can not be null
Running Deferred Action
Running Deferred Action2
Running Deferred Action with Nesting
Running Nested Deferred Action
~/JIRAXXX$ javafx jfxc1043
timeline finished - 2.0
~/JIRAXXX$ javafx jfxc2544
0
1
2
3
4
5
Using runtime
-----------------------
~/JIRAXXX$ javafx deferAction
deferAction Script
Starting Script
java.lang.NullPointerException: Action function can not be null
~/JIRAXXX$ javafx jfxc1043
~/JIRAXXX$ javafx jfxc2544
0
- relates to
-
JDK-8103983 JFXC-1071 (Sever dependency of javafx.animation on Scenario)
-
- Resolved
-