[
https://issues.jboss.org/browse/JBIDE-8777?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-8777:
-----------------------------------
https://hudson.qa.jboss.com/hudson/job/xulrunner-1.9.2/ suggests a successful build of
XulRunner 1.9.2, which is posted here:
http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/
Then, in VPE:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
contains 1.9.2.16.
And in the JBT aggregate:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
contains 1.9.2.16.
So... all appears to be flowing correctly. If tests are failing, that's another issue.
Do VPE JUnits run locally?
Note too that VPE builds are running, but timing out after 4hrs. Perhaps something in the
UI test is blocking?
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--vp...
VPE JUnits do not run on Hudson with XULRunner 1.9.2.16
-------------------------------------------------------
Key: JBIDE-8777
URL:
https://issues.jboss.org/browse/JBIDE-8777
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Visual Page Editor core, XULRunner
Affects Versions: 3.3.0.M1
Reporter: Yahor Radtsevich
Assignee: Yahor Radtsevich
Priority: Critical
Fix For: 3.3.0.M2
Attachments: vpe.trunk.test.results.diff.txt
Last time when we tried to run VPE JUnits with XULRunner 1.9.2 on Hudson (almost a year
ago), they did not work. Now we need to check if this issue persists with new XULRunner
1.9.2.16 and Eclipse 3.7.
XULRunner 1.9.2.16 bundles are
[
here|https://svn.jboss.org/repos/jbosstools/branches/xulrunner-1.9.2.16/x...].
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira