On Sun, 2015-02-22 at 16:39 -0800, Bill Deegan wrote:
> Russel,
>
> I have a 32 bit ubuntu VM I've been using to work on these tests.
> On my 32 bit VM dmd does have 64 bit support built in, so adding -m64
> doesn't fail and the test fails.
> I did have to add the following:
> environment = Enviro
On Sun, 2015-02-22 at 22:09 -0800, Bill Deegan wrote:
> Greetings,
>
> With help from Dirk and Russel we're green (no failures in runtest.py) on
> all buildbot slaves.
>
> I'd like to suggest that going forward any failures after a patch must be
> fixed before any other patch is applied.
>
> Any
Greetings,
With help from Dirk and Russel we're green (no failures in runtest.py) on
all buildbot slaves.
I'd like to suggest that going forward any failures after a patch must be
fixed before any other patch is applied.
Any objections?
-Bill
___
Scon
Russel,
I have a 32 bit ubuntu VM I've been using to work on these tests.
On my 32 bit VM dmd does have 64 bit support built in, so adding -m64
doesn't fail and the test fails.
I did have to add the following:
environment = Environment(
CFLAGS=['-m64'],
DLINKFLAGS=['-m64'],
DFLAGS=['-m
Or even better.. some javascript magic to translate to the users time
zone.. ;)
I'm prepping a new server, once it's ready I'll be upgrading to the latest
buildbot.
Once that's stable I'll take a look at this.
Might take a week or two to be ready to migrate.
On Sun, Feb 22, 2015 at 2:28 AM, Russ
Is there any chance we can replace the PST label with the offset from
UTC of the time given on the Buildbot Waterfall output? Or better still
report UTC?
--
Russel.
=
Dr Russel Winder t: +44 20 7585 2200 voip: sip
Hi,
Second person in a week moaning about there being no bug tracking on
BitBucket.
Assuming there is no appetite for moving from Tigris to BitBucket
issues, there needs to be notices in 96pt bold font telling people where
to go for bug reports. I can add something to the README if that helps.
-
Bill,
I think we both missed that the Debian 7 failing test is still failing
because the:
test.run()
is not returning as the return code is not 0. I assume this should be:
test.run(status=2)
I'll make this change and a pull request. If this is not the correct
solution to the on
