On Tue, Jun 5, 2012 at 5:14 PM, wrote:
> int-full-pgsql - Build # 3619 - Unstable:
>
> Check console output at http://builds.openbravo.com/job/int-full-pgsql/3619/
> to view the results.
New immediate issue created.
https://issues.openbravo.com/view.php?id=20688
Stefan
--
On Wed, Jun 6, 2012 at 3:17 PM, wrote:
> int-dbcons-pgsql - Build # 3150 - Failure:
>
> Check console output at
> http://builds.openbravo.com/job/int-dbcons-pgsql/3150/ to view the results.
New immediate issue created to track this:
https://issues.openbravo.com/view.php?id=20690
Thanks,
Stefan
On Thu, Jun 7, 2012 at 7:41 PM, wrote:
> int-api - Build # 3088 - Failure:
>
> Check console output at http://builds.openbravo.com/job/int-api/3088/ to view
> the results.
New immediate issue created:
https://issues.openbravo.com/view.php?id=20707
Mikel looks like related to your recent 20703
On Fri, Jun 8, 2012 at 9:08 PM, Pablo Luján wrote:
> Issue raised as an immediate regression:
> https://issues.openbravo.com/view.php?id=20715
Already fixed and working again.
Looks like this is a duplicate of the reported & fixed 20709 issue.
Stefan
On Mon, Jun 25, 2012 at 9:45 PM, wrote:
> int-modules-pgsql - Build # 1752 - Still Failing:
>
> Check console output at
> http://builds.openbravo.com/job/int-modules-pgsql/1752/ to view the results.
New immediate issue is created to track this problem:
https://issues.openbravo.com/view.php?id=2
On Wed, Dec 19, 2012 at 11:21 AM, wrote:
> int-dbcons-pgsql - Build # 3587 - Failure:
>
> Check console output at
> http://builds.openbravo.com/job/int-dbcons-pgsql/3587/ to view the
> results.
>
Hi Gorka,
that issue looks like related with your recent reservations merge.
Can you please take a
On Tue, Mar 19, 2013 at 12:43 PM, Pablo Luján wrote:
> I've reported it as a regression:
> https://issues.openbravo.com/view.php?id=23341
>
Hi,
this was caused by an error in the test/job configuration and has been
fixed there.
Stefan
-
On Wed, Apr 24, 2013 at 8:49 AM, Pablo Luján wrote:
> Javi,
>
> Your commit [1] has caused this API fail. Could you take a look?
> [1] https://code.openbravo.com/erp/devel/pi/rev/0136b85e15e3
He is not working today, i asked support team to take a look at this.
for me looks like real api change
On Wed, Apr 24, 2013 at 10:34 AM, Javier Echarri
wrote:
>
> I have just done the backout.
> We will speak tomorrow about that.
Ok, thanks.
Stefan
--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the onl
On Fri, May 31, 2013 at 4:34 PM, wrote:
> int-smoke-pgsql-test - Build # 980 - Failure:
>
> Check console output at
> http://builds.openbravo.com/job/int-smoke-pgsql-test/980/ to view the results.
> Javier Etxarri
> Fixes issue 23385: Organization is generated even
> if the Initial Org
On Tue, Apr 8, 2014 at 6:37 PM, wrote:
> int-checks-pgsql - Build # 392 - Failure:
>
> Check console output at https://ci.openbravo.com/job/int-checks-pgsql/392/ to
> view the results.
>
Hi Guillermo,
can you please take a look at your last commit.
It seems to have made the int-checks-* builds
On Fri, May 9, 2014 at 11:20 AM, wrote:
> int-checks-pgsql - Build # 485 - Unstable:
>
> Check console output at https://ci.openbravo.com/job/int-checks-pgsql/485/ to
> view the results.
that is a false positive. Some bug on our side in rm.
Nothing wrong with Atul's commit.
Stefan
--
On Mon, Jun 2, 2014 at 1:30 PM, wrote:
> int-inc-oracle - Build # 659 - Failure:
>
> Check console output at https://ci.openbravo.com/job/int-inc-oracle/659/ to
> view the results.
Hi Eduardo,
i reported the following regression for this.
Looks like your Open Balances commit introduces this pr
On Mon, Jun 23, 2014 at 8:27 PM, wrote:
> int-basic-pgsql - Build # 330 - Failure:
>
> Check console output at https://ci.openbravo.com/job/int-basic-pgsql/330/ to
> view the results.
>
False positive, please ignore (+ora build also).
Just me doing some maintenance.
Stefan
--
On Mon, Jun 23, 2014 at 8:40 PM, Stefan Huehner
wrote:
> On Mon, Jun 23, 2014 at 8:27 PM, wrote:
>> int-basic-pgsql - Build # 330 - Failure:
>>
>> Check console output at https://ci.openbravo.com/job/int-basic-pgsql/330/ to
>> view the results.
>>
>
> Fa
FYI: hardware failure of one ci server (ci6).
Plan is to get fixed or worked around until tomorrow.
On Thu, Sep 25, 2014 at 2:58 PM, wrote:
> int-gui-oracle - Build # 555 - Failure:
>
> Check console output at https://ci.openbravo.com/job/int-gui-oracle/555/ to
> view the results.
>
>
> Commit
First failure was temporary.
Job failed continuously after that because of bug in erp build-system.
Which is now logged as:
https://issues.openbravo.com/view.php?id=27700
Worked around manually in that job (deleting build.apply once manually).
Stefan
On Sat, Sep 27, 2014 at 3:44 AM, wrote:
>
Hi,
that is the usual expected 1 time failure after publishing a release
(and we just are publishing q4).
The developers needing to take action are already notified automatically.
an i have also asked them to work on that today.
Stefan
On Tue, Dec 30, 2014 at 11:47 AM, wrote:
> int-api - Bui
On 06/08/2010 02:45 PM, hud...@builds.openbravo.com wrote:
> int-api - Build # 61 - Still Failing:
>
> Check console output at http://builds.openbravo.com/job/int-api/61/ to view
> the results.
Tracked via:
https://issues.openbravo.com/view.php?id=13581
> David Alsasua
> Fixes issue 13
On 06/30/2010 06:47 PM, Juan Pablo Aroztegi wrote:
> I don't understand this failure, this is the error message, in the JS
> part:
>
> /srv/hudson/workspace/int-full-oracle/build.xml:519: The following error
> occurred while executing this line:
> /srv/hudson/workspace/int-full-oracle/src/build.xml
On 07/09/2010 04:57 PM, Juan Pablo Aroztegi wrote:
> Hi Sivaraman,
>
> It seems that your commit has broken the API. Could you please handle
> this? If it wasn't intentional, the commit should be fixed. And if is
> intended, then the usual API acceptance procedure should be launched.
You where to
On 07/13/2010 12:42 PM, Juan Pablo Aroztegi wrote:
> Thanks Dmitry, Siva.
>
> I think that we have to speed up this process so that it never takes
> more than 24h since the build fails.
Problem here is that the api-discussion (PJU,DME,developer) changed into
a discussion if the change itself is c
On 08/17/2010 04:12 PM, hud...@builds.openbravo.com wrote:
> int-api - Build # 322 - Failure:
>
> Check console output at http://builds.openbravo.com/job/int-api/322/ to view
> the results.
Acked as false positive, as the now deleted file was never shipped in
any mp.
Regards,
Stefan
-
On 09/13/2010 05:34 PM, hud...@builds.openbravo.com wrote:
> int-api - Build # 411 - Failure:
>
> Check console output at http://builds.openbravo.com/job/int-api/411/ to view
> the results.
Logged as issue:
https://issues.openbravo.com/view.php?id=14542
Stefan
--
On 09/14/2010 03:26 PM, hud...@builds.openbravo.com wrote:
> int-api - Build # 413 - Still Failing:
>
> Check console output at http://builds.openbravo.com/job/int-api/413/ to view
> the results.
Old issue fixed in this build: 14542
New issue tracked as:
https://issues.openbravo.com/view.php?id=
On 01/05/2011 04:42 PM, hud...@builds.openbravo.com wrote:
> int-full-pgsql - Build # 914 - Failure:
>
> Stefan Hühner
> Update sampledata, to remove unplanned c_region entries with
> ad_client_id='0'
> As those are shipped in Masterdata.xml and should be included in the
> sampledata
>
On 01/08/2011 03:45 AM, hud...@builds.openbravo.com wrote:
> int-api - Build # 772 - Still Failing:
>
> Check console output at http://builds.openbravo.com/job/int-api/772/ to view
> the results.
>
Tracked via this issue now:
https://issues.openbravo.com/view.php?id=15586
Stefan
-
On 01/15/2011 11:57 AM, hud...@builds.openbravo.com wrote:
> int-api - Build # 854 - Still Failing:
>
> Check console output at http://builds.openbravo.com/job/int-api/854/ to view
> the results.
The following issue track this problem:
https://issues.openbravo.com/view.php?id=15663
Regards,
St
On 01/25/2011 01:28 AM, hud...@builds.openbravo.com wrote:
> int-api - Build # 937 - Still Failing:
>
> Check console output at http://builds.openbravo.com/job/int-api/937/ to view
> the results.
>
Two issues are created to track those problems:
https://issues.openbravo.com/view.php?id=15763
htt
On 01/25/2011 01:25 AM, hud...@builds.openbravo.com wrote:
> int-dbcons-pgsql - Build # 1013 - Failure:
>
> Check console output at
> http://builds.openbravo.com/job/int-dbcons-pgsql/1013/ to view the results.
Tracked as this issue now:
https://issues.openbravo.com/view.php?id=15765
Regards,
Ste
On 01/31/2011 06:20 PM, hud...@builds.openbravo.com wrote:
> int-api - Build # 1004 - Failure:
>
> Check console output at http://builds.openbravo.com/job/int-api/1004/ to view
> the results.
int-api failing since yesterday evening:
Tracked via this issue now:
https://issues.openbravo.com/view.p
On 04/04/2011 12:28 PM, Pablo Sarobe wrote:
> Thanks Stefan!
>
> So you are telling me that whenever I change something in a html manual
> window (add a column or change the labels) I need to do a compile.complete?
That or do the equivalent steps manually and that's like this at least
for years..
On 04/02/2011 08:53 PM, Pablo Sarobe wrote:
> Fixed!
> Everything was fine except for the labels that I renamed because nothing
> changed in my ad_textinterfaces but in CI , as you can see, failed
> because "isused" field changed from isused='Y' to isused='N'
In the last step those would even hav
On 05/11/2011 07:05 PM, jenk...@builds.openbravo.com wrote:
> int-api - Build # 1711 - Failure:
>
> Check console output at http://builds.openbravo.com/job/int-api/1711/ to view
> the results.
Expected as outcome of latest reintegration of the cleanup work.
https://issues.openbravo.com/view.php?
On 05/26/2011 02:58 PM, jenk...@builds.openbravo.com wrote:
> int-api - Build # 1813 - Failure:
>
> Check console output at http://builds.openbravo.com/job/int-api/1813/ to view
> the results.
fixed, sorry next run should succeed again
hud...@builds.openbravo.com wrote:
> erp_devel_pi-module-integrity-test - Build # 365 - Failure:
>
> Check console output at
> http://builds.openbravo.com/job/erp_devel_pi-module-integrity-test/365/ to
> view the results.
An issue has been created to track this:
https://issues.openbravo.com/vi
Hello Reinaldo,
that special nightly job fails and looks like maybe related to your
Accounting tab changes.
Can you please look into that and fix it?
Note: special topic you may need some help from platform team.
On Sat, Feb 28, 2015 at 2:37 AM, wrote:
> int-full-pgsql-compile-all - Build # 44
Please ignore, internal testing job only.
On Tue, Apr 7, 2015 at 2:46 PM, wrote:
> test-container_14_basic_pgsql - Build # 2 - Failure:
>
> Check console output at
> https://ci.openbravo.com/job/test-container_14_basic_pgsql/2/ to view the
> results.
>
>
> Committers since last success:
>
>
Unexpected behavior change.
We need to run api-check fixed with version java6, until we raise min
version of java to java7.
We will change + fix that during today.
On Thu, May 7, 2015 at 9:59 AM, wrote:
> int-api - Build # 1379 - Still Failing:
>
> Check console output at https://ci.openbravo.
Follow up to close that topic.
Apparently caused by project pushed to pi too early (not going via
try) and having a bug.
Change have been reverted in pi for now (switched off) to avoid the bug.
Stefan
On Mon, May 11, 2015 at 9:44 AM, Priya Muthukumar
wrote:
> Hi,
>
> This failure is taken care
for info:
looks like known bug (corner case)
accounting server running just when tomcat is shutdown end of the test
-> makes currently running accounting serve fail.
Re-running job...
On Thu, May 21, 2015 at 6:11 PM, wrote:
> int-initial-pgsql - Build # 948 - Unstable:
>
> Check console output
Hi,
may i please remind people to try to avoid or reduce the time where
int is broken without any explanation.
In this case here hard to avoid but please send a info mail ideally
when you do the push to pi immediately (!) and not only 3 days later.
And in case of doubt: Weekend is no excuse. I g
Hi Eduardo,
that commits seems to break install.source
As you point to some ad_table_id which seems to not exist in pi.
Can you please check + fix that urgently.
As on top of pi it will also break all other unrelated try pushes until fixed.
Thanks,
Stefan
On Tue, Jun 2, 2015 at 7:31 PM, wrote
Hi,
Gorka can you please check this failure?
As looks at triggered by your Navigation Model merge. Old WAD code
apparently not happy with some of your AD definitions.
That is special nightly job compiling all AD window in 2.50 mode
You can do same locally adding
-Dwad.generateAllClassic250Windo
Hi Victor & Asier,
that is special job testing to compile all windows in 2.50 mode which
is (for now) still supported.
And now that old wad code does not like some detail of the AD definition
could you please look into that?
Thx,
Stefan
On Fri, Aug 14, 2015 at 4:14 AM, wrote:
> int-full-pgsq
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.
Tha
irm?
>
> https://issues.openbravo.com/view.php?id=30578
>
> On Fri, Aug 14, 2015 at 9:48 AM Asier Lostalé
> wrote:
>>
>> I'm going to take a look
>>
>> On Fri, Aug 14, 2015 at 9:47 AM Stefan Huehner
>> wrote:
>>>
>>> Hi Victor &
Please ignore.
Expected to fail until all developers re-apply their changes done
during freeze which did already happen.
So next build is expected to be good again already.
Stefan
On Tue, Aug 18, 2015 at 1:57 PM, wrote:
> int-api - Build # 1578 - Failure:
>
> Check console output at https://c
My mail 30min before yours already said fixed by the developers and to
be ignored.
That one time failure is normal and expected and happens every single
release until all developers manually after that failure reapply their
changes.
There is nothing to check or do normally by us all people requir
Confirmed fixed
int-api - Build # 1579 - Fixed:
On Tue, Aug 18, 2015 at 3:22 PM, Stefan Huehner
wrote:
> My mail 30min before yours already said fixed by the developers and to
> be ignored.
>
> That one time failure is normal and expected and happens every single
> release until
ignore failure.
Cancelled by me as only next run will have fix which should finally fix int-obx.
On Thu, Aug 20, 2015 at 1:47 PM, wrote:
> int-gui-oracle - Build # 1181 - Failure:
>
> Check console output at https://ci.openbravo.com/job/int-gui-oracle/1181/ to
> view the results.
>
>
> Commit
False positive.
When background accounting is just running when tomcat is being shut
down some errors are shown in logs triggering job to be marked as
unstable.
On Fri, Aug 21, 2015 at 3:02 PM, wrote:
> int-initial-pgsql - Build # 1088 - Unstable:
>
> Check console output at https://ci.openbrav
Please ignore all those failures.
Side-effect of a wrong change we did to a global script :(
Fixed now.
Stefan
On Mon, Aug 31, 2015 at 5:18 PM, wrote:
> int-upgrade-pgsql - Build # 1109 - Failure:
>
> Check console output at https://ci.openbravo.com/job/int-upgrade-pgsql/1109/
> to view the
Accidental api-change by them.
They'll fix that up soon.
On Tue, Nov 10, 2015 at 12:57 PM, wrote:
> int-api - Build # 1713 - Failure:
>
> Check console output at https://ci.openbravo.com/job/int-api/1713/ to view
> the results.
>
>
> Committers since last success:
>
> Changes for Build #1713
Expected after release.
The 2 developers who need to re-do something this time are already notified
automatically.
We'll probably add some notification here as well for next time.
Stefan
On Mon, Nov 23, 2015 at 7:41 AM, wrote:
> int-api - Build # 1762 - Failure:
>
> Check console output at ht
Please ignore, next build is already fine.
Cause: me checking on disabled part of the tests but need to fix up
existing issues in pi first.
On Thu, Dec 3, 2015 at 11:56 AM, wrote:
> int-inc-pgsql - Build # 2259 - Unstable:
>
> Check console output at https://ci.openbravo.com/job/int-inc-pgsql/2
Hi Asier,Carlos:
you could look into that error please?
I know that the 1398 build works but the changes from augusto do not sounds
like they should be able to trigger this.
See the error in tomcat openbravo.log of the 1399 job.
I checked postgres (9.1) log files and do not find anything inter
Hi Platform team,
can you please look into this?
As maybe related to your latest project.
Asier: i assume your current try to improve logging into for that error
message is probably already related to that
Stefan
On Wed, Apr 13, 2016 at 6:40 PM, wrote:
> int-gui-pgsql - Build # 1522 - Unstabl
Hi Naroa,
can you please check and fix?
Looks like in the api-checks commit you did is missing the 'hg remove' part
for the AD_SHORTNAME.xml file
Thanks,
Stefan
On Thu, May 19, 2016 at 12:10 PM, wrote:
> int-api - Build # 2076 - Still Failing:
>
> Check console output at https://ci.openbravo.c
FYI: Expected issue as part of post-release process.
As you know will happen
- After release
- if any api-change was accepted during the code-freeze for that release
- until all people you did api-changes during code-freeze re-apply those
'accept api-change commits' after release.
All but one hav
Hi Carlos,
as Asier is out can you please look into that.
As you know 3.0 windows having buttons still use some part of 2.50 code.
So we have this nightly job compiling 'all existing windows' in 2.50 mode
to ensure that keeps working.
And that job now failed. So probably some recent changes (eit
confirmed fixed.
Thx,
Stefan
On Wed, Jun 22, 2016 at 6:34 PM, Álvaro Ferraz
wrote:
> Hi,
>
> It should be fixed now:
> https://code.openbravo.com/erp/devel/pi/rev/4fcce5e429ce
>
> Regards,
> Álvaro
>
> On Wed, Jun 22, 2016 at 2:10 PM, Stefan Huehner <
> st
Known issue > background jobs (accounting) running tomcat shutdown.
Regards,
Stefan
On Sun, Aug 21, 2016 at 4:22 AM, wrote:
> int-initial-oracle - Build # 1590 - Unstable:
>
> Check console output at https://ci.openbravo.com/job/
> int-initial-oracle/1590/ to view the results.
>
>
> Committers
The old 'background processes' still running during tomcat shutdown known
issue. -> Ignore
On Wed, Aug 31, 2016 at 10:36 AM, wrote:
> int-upgrade-pgsql - Build # 1614 - Unstable:
>
> Check console output at https://ci.openbravo.com/job/
> int-upgrade-pgsql/1614/ to view the results.
>
>
> Comm
Fallout from default stack change.
Please ignore this failure.
Thx,
Stefan
On Sun, Oct 16, 2016 at 4:09 AM, wrote:
> int-basic-pgsql - Build # 1601 - Failure:
>
> Check console output at https://ci.openbravo.com/job/int-basic-pgsql/1601/
> to view the results.
>
>
> Committers since last succe
Hi Atul,
looks like your commit has a problem on oracle as the pl function you
modified does cause compile errors on oracle.
So see what the error is you can i.e. use 'compile' of the pl in
sql-developer as gui for developing on oracle or by testing manually on
oracle.
Stefan
On Mon, Oct 17, 20
Bug on our rm side, as effect of stack update.
Please ignore this failure. We'll fix on our side.
On Fri, Oct 21, 2016 at 3:40 PM, wrote:
> up-2.50topi-pgsql - Build # 156 - Failure:
>
> Check console output at https://ci.openbravo.com/job/
> up-2.50topi-pgsql/156/ to view the results.
>
>
> Co
Hello Asier & Naroa,
this error seems to come from your OBScheduler visibility changes. Now
already fixed (by your api-checks push) and re manually re-running the
failing jobs.
Please try to time your pushes to pi+api-checks a bit better to not break
int-api.
And if it happens please do reply-all
Hello Kepa,
looks like you did backout the failing change already. Thanks for that.
Some comments apart:
that looks like code pushed which never went through try and which was
never even compiled once locally.
Please always test should changes before pushing them.
If an problem should happen ->
69 matches
Mail list logo
