It should be fixed by this commit: https://code.openbravo.com/erp/devel/pi/rev/dcbd22cb0169
Sorry for the inconveniences, Álvaro On Fri, Aug 14, 2015 at 9:46 AM, Álvaro Ferraz <[email protected]> wrote: > Hi, > > I am checking it. > > Regards, > Álvaro > > On Fri, Aug 14, 2015 at 9:42 AM, Stefan Huehner < > [email protected]> wrote: > >> Hi guys, >> can you please check your commits as starting that build 2 costing >> tests always fail. >> >> + also check why you did push this in first place to pi and why that >> error was not found by using try. >> >> + also please remember to never commit and then go away and leave the >> build failing all night. >> >> Thanks, >> Stefan >> >> >> On Thu, Aug 13, 2015 at 2:08 PM, <[email protected]> wrote: >> > int-checks-pgsql - Build # 1711 - Unstable: >> > >> > Check console output at >> https://ci.openbravo.com/job/int-checks-pgsql/1711/ to view the results. >> > >> > >> > Committers since last success: >> > >> > Changes for Build #1711 >> > >> > Víctor Martínez Romanos <[email protected]> null >> > Related to issue 30463: code review improvements >> > Usage of constant for the Goods Movement window id >> > Utility.getContext(this, vars, M_Warehouse_ID, windowId) called one time >> > Avoid possible NPE when windowId is null >> > src/org/openbravo/erpCommon/info/Locator.java >> > >> > Atul Gaware <[email protected]> null >> > Fixes Issue 30463: Move a Storage Bin process of Goods Movement >> window allows >> > to choose any locator without taking into account the organization >> > >> > In case of Good Movements window with id 170, org id set in transaction >> is >> > sent as a filter for locator selector. >> > >> > While applying default filters to Locator selector in Alias and >> Warehouse a >> > check is provided to check whether login profile warehouse's >> organization is >> > included under the organization selected in the transaction. >> > src/org/openbravo/erpCommon/info/Locator.java >> > src/org/openbravo/erpCommon/info/Locator_data.xsql >> > >> > David Miguelez <[email protected]> null >> > Related to Issue 29723. Code Review changes. >> > Modifies Query to improve performance. >> > src-db/database/sourcedata/OBUISEL_SELECTOR.xml >> > >> > Alvaro Ferraz <[email protected]> null >> > Related to issue 29723: Modify an assert in TestCosting >> > src-test/src/org/openbravo/test/costing/TestCosting.java >> > >> > Alvaro Ferraz <[email protected]> null >> > Fixes issue 29723: Avoid cost adjustmens in Landed Cost + Standard >> Algorithm >> > >> > Cost Adjustments will not be created in landed cost created with >> Standard Algorithm. >> > Goods Receipt selector in Landed Cost window - Receipt tab, will only >> show receipts processed with current costing rule. >> > Landed Cost and Landed Cost Cost documents will create cost adjustment >> only if active costing rule does not use Standard Algorithm. >> > Landed Cost and Landed Cost Cost differences will be posted to a IPV >> account (instead of an Asset account) if used costing rule does not use >> Standard Algorithm. >> > src-db/database/sourcedata/AD_AUXILIARINPUT.xml >> > src-db/database/sourcedata/AD_FIELD.xml >> > src-db/database/sourcedata/OBUISEL_SELECTOR.xml >> > src/org/openbravo/costing/LCMatchingCancelHandler.java >> > src/org/openbravo/costing/LCMatchingProcess.java >> > src/org/openbravo/costing/LandedCostProcess.java >> > src/org/openbravo/costing/ReactivateLandedCost.java >> > src/org/openbravo/erpCommon/ad_forms/DocLCCost.java >> > src/org/openbravo/erpCommon/ad_forms/DocLandedCost.java >> > >> > >> > >> > >> > Last 20 lines of the console output: >> > >> > [...truncated 14434 lines...] >> > [ "$(jps | grep Bootstrap || true)" != "" ] && echo "Tomcat has fail to >> stop" && exit 1 || true >> > [ "$i" != "0" ] && secs=$(echo "$i * 5" | bc) && echo "Waiting for >> $secs secs for tomcat to stop" >> > >> > echo >> > fi >> > >> > [int-checks-pgsql] $ /bin/bash -xe /tmp/hudson7029842112102945938.sh >> > ++ grep Bootstrap >> > ++ jps >> > ++ true >> > + '[' '' '!=' '' ']' >> > POST BUILD TASK : SUCCESS >> > END OF POST BUILD TASK : 1 >> > Archiving artifacts >> > Checking ERROR|syntax error at or near|SQL error in query >> > Recording test results >> > Build step 'Publish JUnit test result report' changed build result to >> UNSTABLE >> > Email was triggered for: Unstable (Test Failures) >> > Sending email for trigger: Unstable (Test Failures) >> > >> > >> ------------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > Openbravo-builds mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/openbravo-builds >> > >> > >
------------------------------------------------------------------------------
_______________________________________________ Openbravo-builds mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-builds
