Friends
The nightly-build infrastructure for GHC is in disarray, and we could really do
with help. We really want
* Continuous integration so that new test failures show up fast
* Nightly builds on a variety of platforms, giving
snapshots that are easy to install
Originally we used
Hi Simon:
I'm happy to help with Buildbot, Travis CI, or whatever build system is
preferred.
I have administered and curated the continuous integration environment at
Verafin for several years. I have reasonable experience with a variety of
operating systems and test systems.
I can't
Hi,
Am Dienstag, den 01.04.2014, 10:25 + schrieb Simon Peyton Jones:
Joachim Breitner has set up Travis-CI. (I don't know exactly what
that is, but it sounds useful.)
Travis is a free cloud service that runs arbitrary tests (in our case, a
stripped version of validate) upon pushes to git
| I've been getting the impression that a lot of the stickier GHC bugs are
| Windows specific, while very few GHC hackers actually use Windows, other
| than to ensure that GHC works on it.
...
| Perhaps it should be demoted to second-tier GHC support as well, at
| least to the extent that Windows
Hi Joachim:
From what I understand Travis CI limits running time for each build. We may be
able to create binaries of stage1 and/or stage2 in one build and test them in
another. We could also fan out the test process using a Build Matrix to let
GHC's full suite fit into the time limit as
On 2014-04-01 at 12:46:05 +0200, Joachim Breitner wrote:
Hi,
Am Dienstag, den 01.04.2014, 10:25 + schrieb Simon Peyton Jones:
Joachim Breitner has set up Travis-CI. (I don't know exactly what
that is, but it sounds useful.)
Travis is a free cloud service that runs arbitrary tests (in
Hi,
Am Dienstag, den 01.04.2014, 11:08 + schrieb Alain O'Dea:
From what I understand Travis CI limits running time for each build.
We may be able to create binaries of stage1 and/or stage2 in one build
and test them in another. We could also fan out the test process
using a Build Matrix
Hi Tuncer,
Am Dienstag, den 01.04.2014, 13:41 +0200 schrieb Tuncer Ayaz:
Hence: Travis is _not_ going to be a solution for us; we will want our
own infrastructure.
I do agree, but if anybody wants to look more closely into using
Travis-CI, I suggest to also consider drone.io. It appears
Indeed, there is no reason not to use Ian et al's Builder stuff. It's one of
the options. But it depends on a critical evaluation of what the advantages
and disadvantages of different approaches are
Simon
| -Original Message-
| From: Glasgow-haskell-users
On Tue, Apr 1, 2014 at 1:48 PM, Joachim Breitner wrote:
Hi Tuncer,
Am Dienstag, den 01.04.2014, 13:41 +0200 schrieb Tuncer Ayaz:
Hence: Travis is _not_ going to be a solution for us; we will
want our own infrastructure.
I do agree, but if anybody wants to look more closely into using
I'm going to read up on Ian's Buildbot work and experiment with that in the
meantime. If other challenges come up I'm glad to dive in and help.
On Apr 1, 2014, at 12:03, Simon Peyton Jones simo...@microsoft.com wrote:
Indeed, there is no reason not to use Ian et al's Builder stuff. It's
A couple of poor assumptions are made here.
The first is that the userbase of GHC on Windows is poor. This is false. In
fact, the poor state of Windows is mentioned on #haskell more frequently as
of late. In the last week I've talked almost every day to (different)
people who have had Windows
A couple of poor assumptions are made here.
I'm not sure where here is. In my email I specifically said exactly what
you are saying (only I was not as eloquent as you).
What we need is some developers who are willing to give some love and support
to the Windows version of GHC. And they
Kyle, we need you to help us with windows support! :-)
On Tuesday, April 1, 2014, Simon Peyton Jones simo...@microsoft.com wrote:
A couple of poor assumptions are made here.
I’m not sure where “here” is. In my email I specifically said exactly
what you are saying (only I was not as
2014-04-01 14:03 GMT+02:00 Simon Peyton Jones simo...@microsoft.com:
Indeed, there is no reason not to use Ian et al's Builder stuff. It's one of
the
options. But it depends on a critical evaluation of what the advantages and
disadvantages of different approaches are
I found Ian's buildbot
hey all, I just exported the igloo builder code from darcs to git, and put
it here https://github.com/cartazio/ghc-builder
would this be something worth adding to github.com/haskell ? (i can easily
add it if other folks it should be surfaced more visibly)
On Tue, Apr 1, 2014 at 11:04 AM, Páli
Thank you Carter.
I think it's reasonable to incubate it on your Github profile for now until we
are certain it is fully working again. Either way works though :)
Best,
Alain
On Apr 1, 2014, at 17:45, Carter Schonwald carter.schonw...@gmail.com wrote:
hey all, I just exported the igloo
2014-04-01 20:15 GMT+02:00 Alain O'Dea alain.o...@gmail.com:
until we are certain it is fully working again.
In what sense? I have been using the latest checkout from the darcs
repository for both the server and the clients, I seldom experienced
any serious problems. Of course, there is place
good to know (i assumed it was in working order from your remarks)
I think making it more surfaced / discoverable might enable a lot more
volunteer build bots (which is an issue aside from maintaining it)
of course, officially moving it to github should be with ian's blessing,
its mostly his
2014-04-01 20:50 GMT+02:00 Carter Schonwald carter.schonw...@gmail.com:
I think making it more surfaced / discoverable might enable a lot more
volunteer build bots (which is an issue aside from maintaining it)
As Karel has indicated, I have been already running an instance of the
server and I
On Tue, Apr 01, 2014 at 12:46:05PM +0200, Joachim Breitner wrote:
happy with buildbot, it might not be the worst choice.
For reference, the reason we moved away from buildbot is that it needs
to maintain a TCP connection for the duration of the build. With some
builds taking many hours (either
Hi,
Am Dienstag, den 01.04.2014, 21:07 +0200 schrieb Johan Tibell:
If the false positive rate is low, feel free to automatically have the
emails sent to ghc-devs@. We want to know when we broke stuff ASAP.
unfortunately, it is not as low as it should be, partially because of
hitting the 50
2014-04-01 23:30 GMT+02:00 Joachim Breitner m...@joachim-breitner.de:
Or we could have a ghc-bots mailinglist where any kind of
machine-generated GHC-related mails can be sent to, then interested
parties can subscribe.
There is ghc-builds [1] for the daily snapshot builders, would not
that be
Hi,
Am Dienstag, den 01.04.2014, 23:38 +0200 schrieb Páli Gábor János:
2014-04-01 23:30 GMT+02:00 Joachim Breitner m...@joachim-breitner.de:
Or we could have a ghc-bots mailinglist where any kind of
machine-generated GHC-related mails can be sent to, then interested
parties can subscribe.
24 matches
Mail list logo
