Hi Mikhail,
The first idea was to provide information similar to the assertions.
Each extension could use the macros wrapping the existing text and
adding the file name and line number. Since usually the text is based on
the constant string literal, the generation of the string would not
On 02/25/09 15:51, Mikhail Voytenko wrote:
This is of course nothing new, the discussions regarding better
error-handling design can be seen regularly. But in our case, even an
information, which exactly exception has caused the problem ( in our
scenario there is a high probability that an
Hi Andre,
Perhaps to use a build bots for CWS builds or for master builds here in
Hamburg could be a solution. But my intension is to search for all
requirements which are needed in build environment and want to find then
a solution. And I do not want to nail down now, that we have to use
build
Thorsten Ziehm wrote:
Hi Mathias,
I do not see the need to bring the build bots near to the build
environment here in Hamburg. The request for build bots was (as I know)
to have builds in different environments to find build issues in these
different environment. When these environment
Thorsten Ziehm wrote:
[...]
3. I want to have TestBots - or how ever you want to call it - with
defined environment to check each CWS automatically or by manual
trigger. On these BuildBots automated testing will run automatically
on each CWS.
and
6. It is needed to have builds
Hi,
Original-Nachricht
Von: Thorsten Ziehm thorsten.zi...@sun.com
Hi Andre,
Hmm? What request is not valid? That QA communitiy shoud be able to get
somehow reliable builds from buildbots to be able to do CWS tests?
I will explain it again. I try to explain my
Hi Frank,
On 02/26/09 09:20, Frank Schönheit wrote:
As much as I agree that error handling needs to be improved, I don't
like the idea to pollute exception messages with information about the
file where the exception happened. This information should be separated
from the mere message, since
Hi Stephan,
On 02/26/09 09:28, Stephan Bergmann wrote:
On 02/25/09 15:51, Mikhail Voytenko wrote:
This is of course nothing new, the discussions regarding better
error-handling design can be seen regularly. But in our case, even an
information, which exactly exception has caused the problem (
Hi Mikhail,
My intention was to allow user provide the developer with information
that identifies the source of the error.
That's understood.
It would be useful in case of
problems that appear once a year, and look to be mysterious from the
first view.
Ugly is a taste-related comment,
Frank Schönheit - Sun Microsystems Germany wrote:
(If I had a wish, I'd vote for changing UNO incompatibly, and adding a
Stack member to the css.uno.Exception class instead. Oh, well, just
dreaming :)
Hi Frank,
nah, please stick to that, there *must* be something out there that
*is*
On 02/26/09 14:01, Frank Schönheit - Sun Microsystems Germany wrote:
While it is helpful to you as a developer when somebody gives you a
screeshot reading Access denied. foobar.cxx, line 134, it is certainly
not at all helpful for the average end user who does not intend to send
you the screen
Hi,
Thorsten Ziehm schrieb:
*No* TestBots are *not* the solution for getting reliable builds.
TestBots are the solution for running automated tests on reliable
builds.
For 'testing' you can take every build you want. I haven't seen builds
of all build bots, but you can use that versions
Hi Stephan,
Even if there happen to be exception instances where the exception
message is designed to be meaningfully presented to an end user (do you
indeed use localized exception messages?)
(yes, indeed, we do)
this is not true for the
majority of exception instances (where the
Hello
André Schnabel schrieb:
Hi,
Thorsten Ziehm schrieb:
Ok - the discussion started, because Mechtilde told Stephan Bergman that
there are problems with builds from the buildbots, if we want to do CWS
testing on such builds.
The reason to bring this up was because community members
Hi,
Mechtilde schrieb:
And today evening I started the buildbot ubuntu-7.10 to create a build
OOO310_m3 to create a list of diferences between the HH-build and the
build from the build bot.
The first difference I found was that it was impossible to get a build.
Nice one :)
So I am a
15 matches
Mail list logo
