On Sat, Aug 23, 2008 at 11:44:59PM -0400, Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm not sure all browsing setups support tooltips nicely.
Any half way modern browser that is not text based should support tool tips.
Are we in the business of excluding
Are we in the business of excluding text-based browsers? Or obsolete
ones, for that matter?
I don't think we would want to be in the business of
dealing successfully with every quirk of every browser
ever released.
Another way to look at it is supporting standards:
If graphical browsers
Tom Lane wrote:
Joshua D. Drake [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm not sure all browsing setups support tooltips nicely.
Any half way modern browser that is not text based should support tool tips.
Are we in the business of excluding text-based browsers? Or obsolete
ones, for
Steven Lembark [EMAIL PROTECTED] writes:
Are we in the business of excluding text-based browsers? Or obsolete
ones, for that matter?
I don't think we would want to be in the business of
dealing successfully with every quirk of every browser
ever released.
That's nothing but a straw-man.
Alvaro Herrera wrote:
Stefan Kaltenbrunner wrote:
Tom Lane wrote:
Can you modify the buildfarm's description of that machine to mention
the special malloc debug flags? It'd probably stop me from asking
you this question again ;-)
hmm - would take somebody with SQL-level access to do this -
Stefan Kaltenbrunner wrote:
Tom Lane wrote:
Can you modify the buildfarm's description of that machine to mention
the special malloc debug flags? It'd probably stop me from asking
you this question again ;-)
hmm - would take somebody with SQL-level access to do this - the script
to
Alvaro Herrera wrote:
But maybe it would be nice to have some sort of notes about this
buildfarm member text field that contains this information (or other
stuff like this is a VM running on bar or this is really the same
hardware as animal bar just with configuration baz ?
Andrew Dunstan [EMAIL PROTECTED] writes:
Yes, I started on it. The problem is that we have very little real
estate available on the dashboard to display it. I tried making it
available as a tooltip but Tom didn't like that much (in private
correspondence), and I didn't get back to doing
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Yes, I started on it. The problem is that we have very little real
estate available on the dashboard to display it. I tried making it
available as a tooltip but Tom didn't like that much (in private
correspondence), and I didn't get
Joshua D. Drake [EMAIL PROTECTED] writes:
Tom Lane wrote:
I'm not sure all browsing setups support tooltips nicely.
Any half way modern browser that is not text based should support tool tips.
Are we in the business of excluding text-based browsers? Or obsolete
ones, for that matter?
On Sat, May 17, 2008 at 03:52:07PM -0400, Tom Lane wrote:
So I coded this up, and fortunately thought to try it with ecpg's tests
before committing:
...
test preproc/whenever ... FAILED: test process exited with exit code 1
...
Apparently the exit(1) is intentional in that test.
..
Buildfarm member spoonbill's last four HEAD builds have all failed in
the same utterly bizarre way. It looks like about half of the test
results files got truncated at random places --- no errors, no nothing,
the file just ends early. What's up with that?
regards, tom
Tom Lane wrote:
Buildfarm member spoonbill's last four HEAD builds have all failed in
the same utterly bizarre way. It looks like about half of the test
results files got truncated at random places --- no errors, no nothing,
the file just ends early. What's up with that?
psql is coredumping:
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
psql is coredumping:
Huh. I wonder why it's only happening on that one machine.
Is there anything particularly unusual about datatype sizes
or alignment rules on that platform?
regards, tom lane
--
Sent via pgsql-hackers
Tom Lane wrote:
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
psql is coredumping:
Huh. I wonder why it's only happening on that one machine.
Is there anything particularly unusual about datatype sizes
or alignment rules on that platform?
hmm well it is a 64bit Sparc box running OpenBSD
Tom Lane wrote:
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
psql is coredumping:
Huh. I wonder why it's only happening on that one machine.
Is there anything particularly unusual about datatype sizes
or alignment rules on that platform?
hmm actually - the windows buildfarm
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
Tom Lane wrote:
Huh. I wonder why it's only happening on that one machine.
But if i had to guess this more likely caused by the special malloc
flags used on spoonbill (FGJPZ) - per your recommendations in:
Hah, yeah, that's it. The code was
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
psql is coredumping:
BTW, this exposes a pretty nasty omission in pg_regress: it fails to
say anything about a nonzero exit code from a psql child process
that's running a test. Seems like wait_for_tests() ought to complain
about that. Any
Tom Lane wrote:
Stefan Kaltenbrunner [EMAIL PROTECTED] writes:
Tom Lane wrote:
Huh. I wonder why it's only happening on that one machine.
But if i had to guess this more likely caused by the special malloc
flags used on spoonbill (FGJPZ) - per your recommendations in:
Hah, yeah, that's
On Sat, 17 May 2008, Tom Lane wrote:
Does anyone know how to get the child
process exit status on Windows?
GetExitCodeProcess, if you've got the process handle handy (which I assume
you do, since you most likely were calling one of the WaitFor...Object
family of functions.
I wrote:
BTW, this exposes a pretty nasty omission in pg_regress: it fails to
say anything about a nonzero exit code from a psql child process
that's running a test. Seems like wait_for_tests() ought to complain
about that. Any objections?
So I coded this up, and fortunately thought to try
I wrote:
We could possibly extend the syntax of regression schedule files to have
a way to say what's the expected exit status, but that seems like more
work than it's worth. Would it be all right to just remove the test of
on error stop mode?
What I did for the moment is just make it
Tom Lane wrote:
We could possibly extend the syntax of regression schedule files to have
a way to say what's the expected exit status, but that seems like more
work than it's worth. Would it be all right to just remove the test of
on error stop mode?
Woulnd't it be enough to report the exist
Peter Eisentraut [EMAIL PROTECTED] writes:
Woulnd't it be enough to report the exist status if a test fails, instead of
requiring a certain exit status for success?
What I have it doing is reporting the exit status if not zero, but it's
only an annotation on the short-form output; it doesn't
Tom Lane [EMAIL PROTECTED] writes:
Peter Eisentraut [EMAIL PROTECTED] writes:
Woulnd't it be enough to report the exist status if a test fails, instead of
requiring a certain exit status for success?
What I have it doing is reporting the exit status if not zero, but it's
only an annotation
25 matches
Mail list logo