int-basic-oracle - Build # 796 - Still Failing:
Check console output at https://ci.openbravo.com/job/int-basic-oracle/796/ to
view the results.
Committers since last success:
Changes for Build #795
Reinaldo Guerra <[email protected]> null
Fixed bug 27010: Invoice Dimensional Report should not consider voided
status.
A new primary filter, was added to the Sales Invoice Dimensional Report, to
allow exclude or not, documents voided in report's output.
This filter can be managed through a new preference that was created too, in
order to let user decide if filter will be shown. By default the filter will be
hidden and documents voided will be considered.
src-db/database/sourcedata/AD_REF_LIST.xml
src-db/database/sourcedata/AD_TEXTINTERFACES.xml
src/org/openbravo/erpCommon/ad_reports/ReportInvoiceCustomerDimensionalAnalysesJR.java
src/org/openbravo/erpCommon/ad_reports/ReportInvoiceCustomerDimensionalAnalysesJRFilter.html
src/org/openbravo/erpCommon/ad_reports/ReportInvoiceCustomerDimensionalAnalysesJRFilter.xml
src/org/openbravo/erpCommon/ad_reports/ReportInvoiceCustomerDimensionalAnalysesJR_data.xsql
Jorge Garcia <[email protected]> null
Fixed issue 28819: Include "Accounting" tab in Internal Consumption
It is necessary to include "Accounting" tab in Internal Consumption window.
The accounting tab has been added to the Internal Consumption window and
has been configurated properly.
Now, the Internal Consumption windows shows the Accounting tab.
src-db/database/sourcedata/AD_FIELD.xml
src-db/database/sourcedata/AD_TAB.xml
Jorge Garcia <[email protected]> null
Fixed issue 28917: There is no Processed field in transaction tab
In the Financial Account window, in the Transactions tab, there is no field
in order to know if a created transaction is processed or not.
The solution is to display the field Processed in the Windows, Tabs and Fields.
Now, the Processed Field is shown in the Transaction tab.
src-db/database/sourcedata/AD_FIELD.xml
Changes for Build #796
Augusto Mauch <[email protected]> null
Fixes bug 28870: Callouts are run when moving from grid to form with a
shortcut
When a dynamic column is modified, a call is done to the FIC to run the
callouts. The list of dynamic columns is stored in the form (in the view form
and also in the grid edit form), and is loaded from the
FIC response. For instance, when a record is created (either or grid or form
view), a call is done to the FIC in NEW mode, and the dynamicCols list is
initialized.
The cause of this issue is that it was possible to open a record in form view
in an inconsistent state, having the form's dynamicCols list not set. In this
state the callouts are not run. To get to this in
consistent state, the following steps should take place:
- The user creates a record in the grid (a call to the FIC in NEW mode is done,
and the dynamicCols list of the grid edit form is initialized)
- Without saving, the user presses Ctrl+F2 to edit the record in form view. No
FIC call is done (there is no need for it), so even though the record is shown
in the form view, its dynamicCols list is not s
et. The callouts will not run until a call to the FIC is done (for instance by
refreshing the record).
To fix this, the list of dynamicCols of the grid edit form is copied to the
form view. This is done in the ksAction_EditInForm function, which is the
function executed when the user presses Ctrl+F2 to move
from the grid view to the form view.
The list of dynamic columns returned from the FIC to the grid view is the same
as the one returned from the FIC to the form view, so it is not a problem is a
dynamic columns is shown in the form view but n
ot in the grid view.
modules/org.openbravo.client.application/web/org.openbravo.client.application/js/grid/ob-view-grid.js
Last 20 lines of the console output:
[...truncated 17130 lines...]
[junit]
[junit] Error:
[junit] Feb 27, 2015 9:19:58 PM org.openqa.selenium.remote.Augmenter
extractRemoteWebDriver
[junit] WARNING: Augmenter should be applied to the instances of
@Augmentable clases or previously augmented instances only
[junit]
BUILD FAILED
/srv/ci/workspace/int-basic-oracle/SANDBOX/automation/pi/src-test/com/openbravo/test/integration/erp/testsuites/smoke/build.xml:41:
The following error occurred while executing this line:
/srv/ci/workspace/int-basic-oracle/SANDBOX/automation/pi/src-test/com/openbravo/test/integration/erp/testsuites/smoke/financial/build.xml:30:
The following error occurred while executing this line:
/srv/ci/workspace/int-basic-oracle/SANDBOX/automation/pi/src-test/com/openbravo/test/integration/erp/testsuites/smoke/financial/build.xml:51:
The following error occurred while executing this line:
/srv/ci/workspace/int-basic-oracle/SANDBOX/automation/pi/build.xml:71: Test
com.openbravo.test.integration.erp.testsuites.smoke.financial.FINc_InvoiceToPayment
failed
Total time: 67 minutes 13 seconds
Build step 'Execute managed script' marked build as failure
Recording test results
Archiving artifacts
Checking \] ERROR|\] WARN
Email was triggered for: Failure
Sending email for trigger: Failure
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Openbravo-builds mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-builds
