RE: Status updates

[Simon Peyton Jones]

Sergei

Thank you for all these.  I believe I have (finally) nailed them all!

Simon

|  -Original Message-
|  From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of
|  Sergei Trofimovich
|  Sent: 09 September 2014 18:32
|  To: ghc-devs@haskell.org
|  Subject: Re: Status updates
|  
|  On Tue, 9 Sep 2014 08:34:03 -0500
|  Austin Seipp aus...@well-typed.com wrote:
|  
|- Sergei spent some time filing bugs that we should fix in the
|   testsuite, because they fail --slow validate. I believe these are
|  two
|   of them:
|  
| - https://ghc.haskell.org/trac/ghc/ticket/9567
| - https://ghc.haskell.org/trac/ghc/ticket/9566
|  
|  Yeah, I believe the complete list for --slow is only 5 failures:
|  
|  https://ghc.haskell.org/trac/ghc/ticket/9565 - dead loop in simplifier
|  https://ghc.haskell.org/trac/ghc/ticket/9424 - debugged ghc does not
|  unload Show instances after data redefinition (or not :])
|  https://ghc.haskell.org/trac/ghc/ticket/9426 - something similar with
|  redefinition in ghci
|  https://ghc.haskell.org/trac/ghc/ticket/9566 - corelint error in
|  simplifier
|  https://ghc.haskell.org/trac/ghc/ticket/9567 - another corelint error
|  in simplifier
|  
|  --
|  
|Sergei
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

GHC Weekly News (was: Status updates)

[Austin Seipp]

Hi *,

Note the title change. After some discussion with Simon last week, we
decided to change up the name a bit, since we want the discussion on

 - As Gabor mentioned on the list earlier, I accidentally broke the
Windows build. I'm sorry. :( We really need to get Phab building
Windows too ASAP... I'm working on a fix this morning. (There are
still a lot of upstream changes waiting to go into the Phabricator
code base.)

 - I sent out the HCAR draft this morning. Please edit it! I think we
have a few weeks of lead time however, so we're not in a rush like
last time. But I will remind you. :)

 - The server migration for ghc.haskell.org seems to have gone pretty
smoothly in the past week. It's had plenty of traffic so far. The full
migration is still ongoing and I want to complete it this week.

 - I've finished reorganizing some of the Git and Repository pages
after some discussion. We now have the Repositories[1] page, linked to
on the left side, which details some notes on the repositories we use,
and links to other various pages. I'm thinking of replacing this
side-bar root with a link to the main Git[2] page, perhaps.

 - Miscellaneous: ghc.haskell.org and phabricator.haskell.org now sets
the Strict-Transport-Security header. This just means you always use
SSL now when you visit those pages (so you can't be
connection-hijacked via a 503 redirect).

 - I'm merging some patches at the moment, although the windows fix is
currently what I'll push first: D205, D204, D203, D199, D194, D179,
D174. Do let me know if there's anything you want me to look at.

 - GHC works on Wine apparently for all you Linux users - thanks Mikolaj![3]

 - Jan had some questions about infrastructure which I just followed
up on this morning. In particular: does anyone feel strongly about his
first question?[4]

 - Herbert committed the first part of the Traversable/Foldable
changes, by moving the typeclasses to Prelude. This is part of an
ongoing series of patches. Things like adding Bifunctor will finally
come after this.[5]

Also, added bonus: we'll start including some of the tickets we closed
this week.

Closed tickets for the past week include: #9585, #9545, #9581, #6086,
#9558, and #3658.

Please let me know if you have any questions.

[1] https://ghc.haskell.org/trac/ghc/wiki/Repositories
[2] https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Git
[3] https://www.haskell.org/pipermail/ghc-devs/2014-September/006283.html
[4] https://www.haskell.org/pipermail/ghc-devs/2014-September/006275.html
[5] https://phabricator.haskell.org/D209

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Austin Seipp]

Hi *,

Here are some status updates:

 - I've merged the Applicative Monad patchset! Yay! Many thanks to
Nathan Howell for helping me out in the end there. Please let me know
if anything explodes horribly (I hope not).

 - Gabor has set up some build documentation for us based on HEAD,
hooray! See here - http://haskell.inf.elte.hu/ - I still need to fix
haskell.org/ghc to link to this properly (there may be other dead
links, please let me know).

 - As I'm sure most of you were aware, it was a slow week due to ICFP
 related events being most of last week.

 - As I'm also sure you were aware, Haskell.org suffered a lot of
instability this past week. I've been focusing most of my efforts
since about Thursday on this, since it's come and gone a lot and has
needed some consistent monitoring. Unfortunately, it is not done yet,
and there is still more work to be done. :(

 - ghc.haskell.org was migrated to a new server in the US as a part of
this effort this weekend (send a thanks to Herbert). In general, you
should notice nothing really new, but latency for UK citizens may be a
bit higher than it was before now.

 - Now that Applicative/Monad is done, there are some more changes to
'base' that will happen (Bifunctors, Foldable/Traversable) that will
need to happen. So I'm sure this discussion will start soon.

 - I still can't set up the Windows bot yet, sorry! Phabricator work
is still not yet available upstream. Hopefully soon.

 - Sergei spent some time filing bugs that we should fix in the
testsuite, because they fail --slow validate. I believe these are two
of them:

  - https://ghc.haskell.org/trac/ghc/ticket/9567
  - https://ghc.haskell.org/trac/ghc/ticket/9566

 We'll probably need to fix these before we turn it on. Simon, these
look like something up your alley...

 - For those who missed ICFP, Simon gave a nice status update for GHC,
which is on YouTube:
https://www.youtube.com/watch?v=Ex79K4lvJnolist=PL4UWOFngo5DW6nKDjK0UB5Oy9zmdWdo7Kindex=5

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Joachim Breitner]

Hi,


Am Dienstag, den 09.09.2014, 08:34 -0500 schrieb Austin Seipp:
  - I've merged the Applicative Monad patchset! Yay! Many thanks to
 Nathan Howell for helping me out in the end there. Please let me know
 if anything explodes horribly (I hope not).

Not horrible, but still, it breaks:

inplace/bin/ghc-cabal check libraries/filepath
inplace/bin/ghc-cabal configure libraries/filepath dist-install  
--with-ghc=/home/travis/build/ghc/ghc/inplace/bin/ghc-stage1 
--with-ghc-pkg=/home/travis/build/ghc/ghc/inplace/bin/ghc-pkg  
--disable-library-for-ghci --enable-library-vanilla --enable-library-for-ghci 
--disable-library-profiling --disable-shared --configure-option=CFLAGS=-Wall 
-fno-stack-protector-Werror=unused-but-set-variable -Wno-error=inline 
--configure-option=LDFLAGS=--configure-option=CPPFLAGS=
--gcc-options=-Wall -fno-stack-protector-Werror=unused-but-set-variable 
-Wno-error=inline --with-gcc=/usr/bin/gcc --with-ld=/usr/bin/ld 
--configure-option=--with-cc=/usr/bin/gcc --with-ar=/usr/bin/ar 
--with-alex=/opt/alex/3.1.3/bin/alex 
--with-happy=/opt/happy/1.19.4/bin/happy
Configuring filepath-1.3.0.2...
ghc-cabal: At least the following dependencies are missing:
base =4  4.8

https://s3.amazonaws.com/archive.travis-ci.org/jobs/34812365/log.txt

  - Gabor has set up some build documentation for us based on HEAD,
 hooray! See here - http://haskell.inf.elte.hu/ - I still need to fix
 haskell.org/ghc to link to this properly (there may be other dead
 links, please let me know).

It’s a blank page for me.


Thanks for the update and your work!
Joachim

-- 
Joachim “nomeata” Breitner
  m...@joachim-breitner.de • http://www.joachim-breitner.de/
  Jabber: nome...@joachim-breitner.de  • GPG-Key: 0xF0FBF51F
  Debian Developer: nome...@debian.org



signature.asc
Description: This is a digitally signed message part
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Austin Seipp]

Yes, brainfart - sorry!

Herbert kept telling me to bump base's version number after that
change - so I did. But I accidentally broke part of the bootstrap
process in my haste.

Not AMP related, at least. :) A fix is incoming shortly.

On Tue, Sep 9, 2014 at 8:43 AM, Joachim Breitner
m...@joachim-breitner.de wrote:
 Hi,


 Am Dienstag, den 09.09.2014, 08:34 -0500 schrieb Austin Seipp:
  - I've merged the Applicative Monad patchset! Yay! Many thanks to
 Nathan Howell for helping me out in the end there. Please let me know
 if anything explodes horribly (I hope not).

 Not horrible, but still, it breaks:

 inplace/bin/ghc-cabal check libraries/filepath
 inplace/bin/ghc-cabal configure libraries/filepath dist-install  
 --with-ghc=/home/travis/build/ghc/ghc/inplace/bin/ghc-stage1 
 --with-ghc-pkg=/home/travis/build/ghc/ghc/inplace/bin/ghc-pkg  
 --disable-library-for-ghci --enable-library-vanilla --enable-library-for-ghci 
 --disable-library-profiling --disable-shared --configure-option=CFLAGS=-Wall 
 -fno-stack-protector-Werror=unused-but-set-variable -Wno-error=inline 
 --configure-option=LDFLAGS=--configure-option=CPPFLAGS=
 --gcc-options=-Wall -fno-stack-protector-Werror=unused-but-set-variable 
 -Wno-error=inline --with-gcc=/usr/bin/gcc --with-ld=/usr/bin/ld 
 --configure-option=--with-cc=/usr/bin/gcc --with-ar=/usr/bin/ar 
 --with-alex=/opt/alex/3.1.3/bin/alex 
 --with-happy=/opt/happy/1.19.4/bin/happy
 Configuring filepath-1.3.0.2...
 ghc-cabal: At least the following dependencies are missing:
 base =4  4.8

 https://s3.amazonaws.com/archive.travis-ci.org/jobs/34812365/log.txt

  - Gabor has set up some build documentation for us based on HEAD,
 hooray! See here - http://haskell.inf.elte.hu/ - I still need to fix
 haskell.org/ghc to link to this properly (there may be other dead
 links, please let me know).

 It’s a blank page for me.


 Thanks for the update and your work!
 Joachim

 --
 Joachim “nomeata” Breitner
   m...@joachim-breitner.de • http://www.joachim-breitner.de/
   Jabber: nome...@joachim-breitner.de  • GPG-Key: 0xF0FBF51F
   Debian Developer: nome...@debian.org


 ___
 ghc-devs mailing list
 ghc-devs@haskell.org
 http://www.haskell.org/mailman/listinfo/ghc-devs




-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Karel Gardas]

  - Gabor has set up some build documentation for us based on HEAD,
hooray! See here - http://haskell.inf.elte.hu/ - I still need to fix
haskell.org/ghc to link to this properly (there may be other dead
links, please let me know).


It’s a blank page for me.


Should probably be http://haskell.inf.elte.hu/builders/

Karel
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Austin Seipp]

Nope, my bad again. The actual link is:

  http://haskell.inf.elte.hu/docs/

On Tue, Sep 9, 2014 at 8:49 AM, Karel Gardas karel.gar...@centrum.cz wrote:

   - Gabor has set up some build documentation for us based on HEAD,
 hooray! See here - http://haskell.inf.elte.hu/ - I still need to fix
 haskell.org/ghc to link to this properly (there may be other dead
 links, please let me know).


 It’s a blank page for me.


 Should probably be http://haskell.inf.elte.hu/builders/

 Karel

 ___
 ghc-devs mailing list
 ghc-devs@haskell.org
 http://www.haskell.org/mailman/listinfo/ghc-devs




-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Carter Schonwald]

not sure why, but in the build docs, the version numbers on the module
packages look... bonkers
http://haskell.inf.elte.hu/docs/7.9.20140908/html/libraries/index.html

eg
GHC.PackageDb
http://haskell.inf.elte.hu/docs/7.9.20140908/html/libraries/bin-package-db-0.0.0.0/GHC-PackageDb.html
binpa_JutoagPF9VL3G583BCA0

On Tue, Sep 9, 2014 at 9:50 AM, Austin Seipp aus...@well-typed.com wrote:

 Nope, my bad again. The actual link is:

   http://haskell.inf.elte.hu/docs/

 On Tue, Sep 9, 2014 at 8:49 AM, Karel Gardas karel.gar...@centrum.cz
 wrote:
 
- Gabor has set up some build documentation for us based on HEAD,
  hooray! See here - http://haskell.inf.elte.hu/ - I still need to fix
  haskell.org/ghc to link to this properly (there may be other dead
  links, please let me know).
 
 
  It’s a blank page for me.
 
 
  Should probably be http://haskell.inf.elte.hu/builders/
 
  Karel
 
  ___
  ghc-devs mailing list
  ghc-devs@haskell.org
  http://www.haskell.org/mailman/listinfo/ghc-devs
 



 --
 Regards,

 Austin Seipp, Haskell Consultant
 Well-Typed LLP, http://www.well-typed.com/
 ___
 ghc-devs mailing list
 ghc-devs@haskell.org
 http://www.haskell.org/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Sergei Trofimovich]

On Tue, 9 Sep 2014 08:34:03 -0500
Austin Seipp aus...@well-typed.com wrote:

  - Sergei spent some time filing bugs that we should fix in the
 testsuite, because they fail --slow validate. I believe these are two
 of them:
 
   - https://ghc.haskell.org/trac/ghc/ticket/9567
   - https://ghc.haskell.org/trac/ghc/ticket/9566

Yeah, I believe the complete list for --slow is only 5 failures:

https://ghc.haskell.org/trac/ghc/ticket/9565 - dead loop in simplifier
https://ghc.haskell.org/trac/ghc/ticket/9424 - debugged ghc does not
unload Show instances after data redefinition (or not :])
https://ghc.haskell.org/trac/ghc/ticket/9426 - something similar with 
redefinition in ghci
https://ghc.haskell.org/trac/ghc/ticket/9566 - corelint error in simplifier
https://ghc.haskell.org/trac/ghc/ticket/9567 - another corelint error in 
simplifier

-- 

  Sergei


signature.asc
Description: PGP signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: validate --slow bugs (was Re: Status updates)

[Thomas Miedema]

   - I still think we should turn on --slow mode for our buildbots soon,
  but this will cause noise. I'd really like some inputs on this - maybe
  someone would like to help clean up the 'slow' vaildate failures?
  Bonus points for this, since you don't even have to

 That's a great goal, but --slow enables compiler debug assertions,
 which seem to trigger real errors (full log of failures attached).


Also note that when debugging is on, tests that call
`compiler_stats_num_field` are currently skipped
https://github.com/ghc/ghc/blob/master/testsuite/driver/testlib.py#L305:L308.
This applies to almost all tests in `tests/perf/compiler`.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

validate --slow bugs (was Re: Status updates)

[Sergei Trofimovich]

On Wed, 3 Sep 2014 15:31:03 -0500
Austin Seipp aus...@well-typed.com wrote:

 Hi *,
 
 Here are some status updates for the past week, which have been a bit light.

Woot! Great list!

  - I still think we should turn on --slow mode for our buildbots soon,
 but this will cause noise. I'd really like some inputs on this - maybe
 someone would like to help clean up the 'slow' vaildate failures?
 Bonus points for this, since you don't even have to

That's a great goal, but --slow enables compiler debug assertions,
which seem to trigger real errors (full log of failures attached).

I've filled tickets for some of those assertion failures.
If someone more experienced in the area could guide us
hints on how to fix them (CCed Simon PJ).

If they all are non-issues please tell and I'll drop them.

If they are real bugs I can try to debug them a bit
and gather more info (maybe something specific is of interest?).

Highlights:

*** unexpected failure for T3500b(threaded2)
= T3500b(dyn) 3766 of 4100 [0, 12, 0] 
cd ./typecheck/should_run  
'/home/slyfox/dev/git/ghc-validate/bindisttest/install   dir/bin/ghc' 
-fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db 
-rtsopts -fno-ghci-history -o T3500b T3500b.hs -O -dynamic   
T3500b.comp.stderr 21
Compile failed (status 256) errors were:
[1 of 1] Compiling Main ( T3500b.hs, T3500b.o )
ghc: panic! (the 'impossible' happened)
  (GHC version 7.9.20140905 for x86_64-unknown-linux):
Simplifier ticks exhausted
When trying RuleFired foldr/augment
To increase the limit, use -fsimpl-tick-factor=N (default 100)
If you need to do this, let GHC HQ know, and what factor you needed
To see detailed counts use -ddump-simpl-stats
Total ticks: 12441

  Is it bad?

cd ./ghc-api  $MAKE -s --no-print-directory T8628/dev/null 
T8628.run.stdout 2T8628.run.stderr
Actual stderr output differs from expected:
--- /dev/null   2014-08-25 09:46:54.593424088 +0300
+++ ./ghc-api/T8628.run.stderr  2014-09-05 22:49:20.705589132 +0300
@@ -0,0 +1,4 @@
+WARNING: file compiler/simplCore/SimplEnv.lhs, line 539
+Ghci3.$fShowX
+WARNING: file compiler/simplCore/SimplEnv.lhs, line 539
+Ghci3.$fShowX
*** unexpected failure for T8628(normal)

  This looks nasty.

= tc124(hpc) 3135 of 4100 [0, 3, 0] 
cd ./typecheck/should_compile  
'/home/slyfox/dev/git/ghc-validate/bindisttest/install   dir/bin/ghc' 
-fforce-recomp -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db 
-rtsopts -fno-ghci-history -c tc124.hs -O -fhpc -hpcdir .hpc.tc124  
-fno-warn-incomplete-patterns tc124.comp.stderr 21
Compile failed (status 256) errors were:
*** Core Lint errors : in result of Simplifier ***
no location info: Warning:
In the type ‘a_12 - a_aia - a_aia’
@ a_12 is out of scope
*** Offending Program ***
Foo.f :: Foo.T - (GHC.Types.Int, GHC.Types.Char)
[LclIdX,
 Arity=1,
 Str=DmdType,
 Unf=Unf{Src=vanilla, TopLvl=True, Value=True, ConLike=True,
 WorkFree=True, Expandable=True, Guidance=IF_ARGS [20] 90 30}]
 

  This also looks scary.

Thanks!

-- 

  Sergei
make -C testsuite/tests CLEANUP=1 OUTPUT_SUMMARY=../../testsuite_summary.txt
make[1]: Вход в каталог 
`/home/slyfox/dev/git/ghc-validate/testsuite/tests'
python2 ../driver/runtests.py  -e ghc_compiler_always_flags='-fforce-recomp 
-dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db -rtsopts ' -e 
ghc_debugged=True -e ghc_with_native_codegen=1 -e ghc_with_vanilla=1 -e 
ghc_with_dynamic=1 -e ghc_with_profiling=0 -e ghc_with_threaded_rts=1 -e 
ghc_with_dynamic_rts=1 -e ghc_with_interpreter=1 -e ghc_unregisterised=0 -e 
ghc_dynamic_by_default=False -e ghc_dynamic=True -e ghc_with_smp=1 -e 
ghc_with_llvm=1 -e windows=False -e darwin=False -e in_tree_compiler=True -e 
clean_only=False --rootdir=. --config=../config/ghc -e 
'config.confdir=../config' -e 
'config.compiler=/home/slyfox/dev/git/ghc-validate/bindisttest/install   
dir/bin/ghc' -e 
'config.ghc_pkg=/home/slyfox/dev/git/ghc-validate/bindisttest/install   
dir/bin/ghc-pkg' -e 
'config.hp2ps=/home/slyfox/dev/git/ghc-validate/bindisttest/install   
dir/bin/hp2ps' -e 
'config.hpc=/home/slyfox/dev/git/ghc-validate/bindisttest/install   
dir/bin/hpc' -e 'config.gs=gs' -e 'config.platform=x86_64-unknown-linux' 
-e 'config.os=linux' -e 'config.arch=x86_64' -e 'config.wordsize=64' -e 
'default_testopts.cleanup=1' -e 'config.timeout=int() or config.timeout' -e 
'config.timeout_prog=../timeout/install-inplace/bin/timeout' -e 
'config.exeext=' -e 
'config.top=/home/slyfox/dev/git/ghc-validate/testsuite' --output-summary 
../../testsuite_summary.txt   --rootdir=../../libraries/array/tests  
--rootdir=../../libraries/base/tests  --rootdir=../../libraries/binary/tests  
--rootdir=../../libraries/bytestring/tests  
--rootdir=../../libraries/containers/tests

Status updates

[Austin Seipp]

Hi *,

Here are some status updates for the past week, which have been a bit light.

 - I spent a bunch of time code reviewing things and merging patches
this week. There are still things in Phabricator that need some
review, so please review them if you get a chance! You will probably
learn things and learning things is good. [1]

 - I spent more time getting a Windows builder working, and talking
with upstream about it. I believe it should Basically Work, but
unfortunately the changes for this have not gone upstream yet, so it
will probably be a week or two before I can officially do that

 - I have spent some time fixing some bugs, and I'm posting a review
for some shortly, notably 7602!

Unrelated to what I in particular am doing Right Now:

 - I would still _really_ like help with the Applicative Monad patch;
I haven't touched it much. Please pester me if you have some cycles to
spare. Or just helping me brainstorm would be really really useful![2]

 - After some minor instability in the tree earlier this week (test
failures), everything is back to normal (Thanks to Edward  Simon).
Please ping here if you're still having trouble on your machine.

 - I still think we should turn on --slow mode for our buildbots soon,
but this will cause noise. I'd really like some inputs on this - maybe
someone would like to help clean up the 'slow' vaildate failures?
Bonus points for this, since you don't even have to

 - Gabor Pali  I had a minor discussion this last week about fixing
nightly documentation snapshots. We've had complaints about this in
the past and the prior system totally disappeared, so it will be
really nice to fix this! Binary snapshots should be possible too, but
documentation is perhaps the more key thing.

 A little work is necessary for this though, and my time is limited as
always. Please let me know if you'd like to help with this, and I'll
pull you into the loop with Gabor so can tackle this.



I've probably forgotten some things other people have done the past
week, including myself. If you have any questions, suggestions, or
want to pop in on this email and say something, you should. :)

[1] https://phabricator.haskell.org/differential/
[2] https://phabricator.haskell.org/D13

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Austin Seipp]

On Wed, Sep 3, 2014 at 3:31 PM, Austin Seipp aus...@well-typed.com wrote:
  - I still think we should turn on --slow mode for our buildbots soon,
 but this will cause noise. I'd really like some inputs on this - maybe
 someone would like to help clean up the 'slow' vaildate failures?
 Bonus points for this, since you don't even have to

Hmmm, I accidentally the rest of this paragraph. To finish:

Bonus points here, since you can leave most of the 'heavy lifting' to
phabricator. I can just turn on --slow mode, you submit a patch, and
Phabricator tells you if it works. :)

And if you'd like to fix some problems but are shy, this might be a
good place to start! (Tests are small, self contained, and should be
easy to follow via the bug tracker - there shouldn't be *too* much to
wade through to get started.)

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Páli Gábor János]

2014-09-03 22:31 GMT+02:00 Austin Seipp aus...@well-typed.com:
  - Gabor Pali  I had a minor discussion this last week about fixing
 nightly documentation snapshots. We've had complaints about this in
 the past and the prior system totally disappeared, so it will be
 really nice to fix this! Binary snapshots should be possible too, but
 documentation is perhaps the more key thing.

I have not followed up on it, but for your information, I have started
building and publishing snapshots for the GHC documentation here:

  http://haskell.inf.elte.hu/docs/

It is based on the snapshots provided by the builders I have and it
uses a script that is derived from the mkDocs utility in the source
tree (under distrib).  As a consequence, the method is a bit
fragile, as it needs at least a Windows and non-Windows build to be
built in order to extract and combine the files from them.
Unfortunately, my Windows builders are not fully stable yet, although
they deemed to be usable enough mostly.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

RE: Status updates

[Simon Peyton Jones]

That's great!  Austin, can you fix the links on 
http://www.haskell.org/haskellwiki/GHC
so that the current HEAD snapshot link (currently dead) points to the right 
place?

thanks

Simon

| -Original Message-
| From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of Páli
| Gábor János
| Sent: 03 September 2014 21:48
| To: Austin Seipp
| Cc: ghc-devs@haskell.org
| Subject: Re: Status updates
| 
| 2014-09-03 22:31 GMT+02:00 Austin Seipp aus...@well-typed.com:
|   - Gabor Pali  I had a minor discussion this last week about fixing
|  nightly documentation snapshots. We've had complaints about this in
|  the past and the prior system totally disappeared, so it will be
|  really nice to fix this! Binary snapshots should be possible too, but
|  documentation is perhaps the more key thing.
| 
| I have not followed up on it, but for your information, I have started
| building and publishing snapshots for the GHC documentation here:
| 
|   http://haskell.inf.elte.hu/docs/
| 
| It is based on the snapshots provided by the builders I have and it
| uses a script that is derived from the mkDocs utility in the source
| tree (under distrib).  As a consequence, the method is a bit
| fragile, as it needs at least a Windows and non-Windows build to be
| built in order to extract and combine the files from them.
| Unfortunately, my Windows builders are not fully stable yet, although
| they deemed to be usable enough mostly.
| ___
| ghc-devs mailing list
| ghc-devs@haskell.org
| http://www.haskell.org/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Austin Seipp]

Hello *,

Here are some notes from what's happened this week:

 - I've rejiggered some of the wiki pages a bit more, including
updating the BugTracker page[1], Phabricator/Harbormaster docs[2],
   -- The bugtracker page mostly saw some minor updates in relation to
the updates from *last* week; notably the new 'upstream' status.
   -- I split the Phabricator page up a bit to be easier to read, so
Harbormaster is its own page now (but see more below).

 - I spent a day or two working on a Windows buildbot for Phabricator.
Good news: I think I have a reliable set of steps to get a windows SSH
instance running. However, I have not yet gotten it to build GHC
through msys2, so it's not working yet.

 - I spent time on Friday getting a fix for #7602 ready for real this
time. I'll put a review on Phabricator soon (my other machine doesn't
have `arc` credentials.) Hopefully OS X users can soon rejoice with a
solid performance boost.

 - I fiddled with Applicative-Monad a tiny bit, but haven't made much
progress still. Like last time, it would be really amazing if anyone
would like to help me out and try the patch yourself (feel free to
email/IRC, or see last weeks' email for more).

Other things:

 - Thomas Miedema helped out Herbert by writing a Trac anti-spam
plugin for us - Thank you so much Thomas!! Hopefully the spam will go
away soon.

 I am not yet sure if Thomas's new plugin is installed yet - Herbert?

Upcoming:

 - #7602 will go up for review.

 - I will land D165 today probably since it's ready and other
refactorings can come later. D166 (faster copies) is not yet ready.

 - I haven't done this yet, but I'm going to try to turn on `--slow`
./validate mode in the next day or two for Phabricator. At first, I'm
only going to configure this for *commits* first, and perhaps patches
will follow once we have more build machines.

 That means Phabricator is going to start annoying you with consistent
failures (I think `--slow` has a few right now), but putting on
pressure is the best way to fix it, I think. I'll send another email
about this shortly.

 - I will probably rejigger the Phabricator page again to be smaller.
I've had some complaints it's getting a bit large (due to the images,
mostly), so I'll probably move the hierarchy around a bit.

 - Sit down and do some thorough code review. We have about 3 major
features sitting on Phabricator at the moment which are going to need
extensive review before landing. I expect this will take a while. See:
  -- D169, source code notes: https://phabricator.haskell.org/D169
  -- D168: Partial type sigs: https://phabricator.haskell.org/D168
  -- D119: StaticValues extension: https://phabricator.haskell.org/D119

Please please please - feel free to review these patches! Even if they
are not your area of expertise, doing so will A) help you learn more
hopefully! and B) you can surely help still (pointing out typos,
needed docs, lint violations, suggestions) etc. That would be really
useful to help increase the 'shared ownership' we all have, I think.

[1] https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/BugTracker
[2] https://ghc.haskell.org/trac/ghc/wiki/Phabricator/Harbormaster

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Joachim Breitner]

Hi,


Am Dienstag, den 19.08.2014, 08:39 -0500 schrieb Austin Seipp:
  - Phabricator now has significantly better build integration, as I'm
 sure many of you have seen. It is less noisy (and doesn't email you as
 much), has better logging support (that actually works), and it now
 builds commits AND patches! It's been in-production since last week
 and a lot more reliable than the crap I wrote before.

can this fully replace Travis (which would be nice, given the problems
caused by Travis’s resource constraints)?

Greetings,
Joachim

-- 
Joachim “nomeata” Breitner
  m...@joachim-breitner.de • http://www.joachim-breitner.de/
  Jabber: nome...@joachim-breitner.de  • GPG-Key: 0xF0FBF51F
  Debian Developer: nome...@debian.org



signature.asc
Description: This is a digitally signed message part
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Austin Seipp]

Hello *,

Sorry for the scatter-brained-ness of my update. But without further
ado, here are some things that have been going on:

 - I was going to land AMP, but I've gotten stuck again! It seems that
now, Haddock infinite loops, but this one I really can't figure out.
See my comment on the ticket[1] if you're adventurous - a small patch
to Haddock and you should be able to build things, but it'll fail
while Haddocking `ghc-prim`. Any help here would be much appreciated!

 - Phabricator now has significantly better build integration, as I'm
sure many of you have seen. It is less noisy (and doesn't email you as
much), has better logging support (that actually works), and it now
builds commits AND patches! It's been in-production since last week
and a lot more reliable than the crap I wrote before.

  I am thinking of changing the Phabricator GHC commit builder to
validate all commits in `--slow` mode, which we can't do on Travis,
and will catch more failures. I assume most people would approve of
this. :)

 - The wiki has been updated in several spots:
- The Phabricator page is now more detailed about Audits and more
up to date about builds.[2] Yes, I know it looks long, but it's really
just due to a lot of pictures. It's actually quite short still.
- The Git workflow pages (starting from WorkingConventions/Git)
have seen some minor updates[3], but nothing substantial. Some old
pages still need to be deleted possibly, and some things (e.g. GitHub)
might need further tweaks.
- Yes, we're still seeing spam, but unfortunately nobody has had
time to fix the CAPTCHAs yet. If you can write some python and want
to, I'm sure Herbert would like to know. :)

 - There is a new status in Trac, primarily useful for patches, called
'upstream', which is very similar to 'patch', but says that the change
goes to an upstream library that GHC must synchronize with. This
difference is now much more important since many of our packages are
tracked through submodules. See the working conventions page for some
details and a pretty graph[4].

- I've gone ahead and split my old optimized-memcpy patch into two
patches - D165 and D166 on Phabricator. Hopefully these will go in
soon after some discussion with Johan about how we want to handle the
flags is talked out.

 - All of the Phabricator patches from outstanding contributors have
been merged, I think. There are some outstanding reviews still going
on, and some accepted commits still waiting for other reviewers I
believe.

 - Almost all of the current outstanding patches have been either
merged, taken out of patch state (in case they were in limbo), or
moved to 'upstream' status. Take a look at this wiki page:

https://ghc.haskell.org/trac/ghc/query?status=patchdifferential=orstatus=upstreamgroup=statuscol=idcol=summarycol=ownercol=typecol=prioritycol=milestonecol=componentorder=priority

These are all the patches and upstream tickets, specifically those
which do NOT have ongoing Phabricator code reviews for them. I chose
this so we don't see tickets that may already be going under review
elsewhere. Notably I'm testing the fusion tickets before merging them.

OK, I think that's it. Do let me know if you have any questions (or
would like to help with D13 :)

[1] https://phabricator.haskell.org/D13#26
[2] https://ghc.haskell.org/trac/ghc/wiki/Phabricator
[3] https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Git
[4] https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/BugTracker

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Austin Seipp]

Hi *,

Here's some weekly status updates!

 - I'm merging Applicative-Monad today after a few more minor fixes.
OMG YES. This only occurred after fighting off some nasty bugs that
took quite a while to track down. Unfortunately this ate up most of my
time this week.

 - I redid the Phabricator page quite a bit on the wiki, as I sent in
my earlier email. Do read over it and let me know what you think, I'll
be updating it more soon:
https://ghc.haskell.org/trac/ghc/wiki/Phabricator

 - I'm going to be redoing the Git wiki pages a bit today to
streamline them, which hopefully will only take a few hours.

 - I'm draining the patch queue still, both from Phabricator and Trac,
although I need to re-triage a few of the Trac tickets in particular
which are in 'patch' status.

 - We have a new committer afoot, Karel Gardas! Yay! He's been working
on Solaris support, so having direct access to commit will surely help
speed things up here.

 - DPH will soon be disabled by default in ./validate, although Geoff
has stepped up to help alleviate some of the pain (see prior emails
from me.)

After all that:

 - I'm going to fix bugs! Yes, I'll actually have time to do that.

 - Sometime this week I'll also hopefully finish off my Phabricator
integrations: better build bot, with accurate logs, and posting to
Trac from Phabricator. This is *almost* done, but still needs to be
tested/deployed a bit.

 - I may get around to finally pushing my patches for faster inline
copies this week (and -march support) if I still have time.

Do let me know if anything is on your mind, or if any of you have questions.

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Austin Seipp]

Thanks, Bryan!

On a related note, and to drum up some excitement - we have another
new committer (two in one day): Sergei Trofimovich :]

On Mon, Aug 4, 2014 at 12:58 PM, Bryan O'Sullivan b...@serpentine.com wrote:
 Hey Austin –

 It's very helpful and informative to know what you're up to. Thanks for
 taking the time to write these updates; I assure you they're appreciated.


 On Mon, Aug 4, 2014 at 9:51 AM, Austin Seipp aus...@well-typed.com wrote:

 Hi *,

 Here's some weekly status updates!

  - I'm merging Applicative-Monad today after a few more minor fixes.
 OMG YES. This only occurred after fighting off some nasty bugs that
 took quite a while to track down. Unfortunately this ate up most of my
 time this week.

  - I redid the Phabricator page quite a bit on the wiki, as I sent in
 my earlier email. Do read over it and let me know what you think, I'll
 be updating it more soon:
 https://ghc.haskell.org/trac/ghc/wiki/Phabricator

  - I'm going to be redoing the Git wiki pages a bit today to
 streamline them, which hopefully will only take a few hours.

  - I'm draining the patch queue still, both from Phabricator and Trac,
 although I need to re-triage a few of the Trac tickets in particular
 which are in 'patch' status.

  - We have a new committer afoot, Karel Gardas! Yay! He's been working
 on Solaris support, so having direct access to commit will surely help
 speed things up here.

  - DPH will soon be disabled by default in ./validate, although Geoff
 has stepped up to help alleviate some of the pain (see prior emails
 from me.)

 After all that:

  - I'm going to fix bugs! Yes, I'll actually have time to do that.

  - Sometime this week I'll also hopefully finish off my Phabricator
 integrations: better build bot, with accurate logs, and posting to
 Trac from Phabricator. This is *almost* done, but still needs to be
 tested/deployed a bit.

  - I may get around to finally pushing my patches for faster inline
 copies this week (and -march support) if I still have time.

 Do let me know if anything is on your mind, or if any of you have
 questions.

 --
 Regards,

 Austin Seipp, Haskell Consultant
 Well-Typed LLP, http://www.well-typed.com/
 ___
 ghc-devs mailing list
 ghc-devs@haskell.org
 http://www.haskell.org/mailman/listinfo/ghc-devs





-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Austin Seipp]

Hello *,

Here are some notes on what I've done in the past week, and what I
plan on doing going forward:

 - First and foremost, I made a bunch of improvements to
Phabricator/Trac. Now, most noticeably:

  1) Phabricator has a field for GHC trac tickets. You can specify
this when you run 'arc diff', and it will appear on the Differential
Revision. By default if you run 'arc diff', this field appears at the
bottom, below 'Subscribers:'.

  2) Phabricator now supports Trac markup syntax - if you say '#7602'
in a trac ticket, this turns into a hyperlink with the text Trac
#7602 and links to the ticket.

  3) The IRC bot on #ghc can now look up Trac tickets for you (this is
mostly only relevant to those of us there)

 - The final piece of this whole story is actually getting Phabricator
to *comment* on Trac. This is almost done, but due to the fact I'm
writing PHP (and thus have absolutely no idea what I'm doing) the code
still seems slightly broken somewhere since it's one of the larger
parts of the Phabricator integration. Hopefully I can finish this
soon.

  I will say though - thank you Herbert for helping me figure out the
Trac XML/RPC plugin, and getting it working for me!

 - Another Phabricator related thing: I've begun working on a better
Harbormaster build backend - it will actually report failures, support
concurrent builds, and give you stderr in log results! Yay!

 - I took some time to further clean up the Git wiki page following
last week, but only made minor progress here.

 - The patch queue is, in fact, being drained as we speak! I have a
whole bunch of incoming patches from contributors running under
./validate as I write this, including some cleanup commits too (to
detab/whitespace things). Not all of them, but a good chunk I could
fit in that were low-impact and correct.

 - I have not finished AMP. :( This is quickly going to be my #1
priority before fixing any bugs because at this point, it's holding up
other `base` improvements (Edward K, I'm sure, is getting a bit fiddly
about this getting done :)

This week:

 - Before fixing *any* new bugs myself, I'm going to finish AMP,
because it's a blocker for others including Edward, Simon, and future
base improvements. I'm thinking I may just do this before any more
Phabricator improvements.

 - I will hopefully finish the Trac and Phabricator setup soon. at the
very least I want to get the comment updates working. I'll probably
continue with the build system shenannigans sometime after.

 - The wiki pages and Git stuff still need more cleanup to streamline
them. This will be happening when I get a chance (Herbert already
improved some things I touched last week - Thanks!)

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Austin Seipp]

Hello *,

Here are some updates from this past week.

 - I sent an email earlier about 7.10.1 tickets - please vote on them!

 - Related to that - as I said last week, I finished remilestoning a
lot of tickets, but more remain. Please excuse any mail spam, but do
pay attention to your bugs if they change!

 - I cleaned up some tabs and whitespace in the compiler in
low-activity areas. You may have seen the commits go by, but otherwise
it shouldn't be a problem. I'll probably keep eliminating errors in
low-contention areas of the codebase as I can. Ditto with 'arc lint'.

 - I've cleaned up a bunch of wiki pages relating to the git
repositories, and submodule management, but more stuff remains. See
below for my reply to Simon.

 - I've been lazy about the Applicative-Monad work, since some of it
fell out of date. But now other work is pending on it, so it's time to
finish it Real Soon Now.

 - I'm working out some of the kinks in the Phabricator automation for
builds etc, but it's not quite done yet - sorry!

Here are some things I plan to do this week, roughly in order of priority:

 - I'm going to keep cleaning up these Git pages to make them more
sensible, since some of the information is still wrong. Please see the
comments below this and let me know what's wrong!

 - I will finalize these Phabricator things, which I should be able to
get done with soon. This is all mostly annoying HTTP endpoint and
PHP/Python stuff and is a bit of a chore to test/setup completely.

 - I am going to spend time next on landing AMP and get it back into
shape.  Yes, really landing it; I need to send something upstream to
Cabal still.

 - The patch queue on Trac needs to be drained and slipped my mind.

 - Given all that I'll also probably end up continuing to fix lint
errors, and hopefully fix bugs based on what people want in 7.10. :)

Below is a quick recap of what me and Simon discussed last week,
mostly stuff from the above:

 · Complete re-milestoning. Then email ghc-devs and ghc-users [send a 
 draft to Simon  Simon first]

o   Giving links to suitable query(s)

o   Saying that any ticket that isn’t

a)  milestoned 7.8.4 or 7.10.1, and

b)  high or highest priority,

isn’t going to get attended to by us.

o   Inviting them to bid (on the ticket) for high/highest 7.10.1 status, 
explaining why it is important to them.   And  that it’s more likely to be 
done if they help.

I sent this mail earlier - please bid on 7.10.1 tickets!

  · Trac/Phab integration

Doing this in a complete manner is turning out to be a bit of work and
I haven't gotten done yet with having comments appear on tickets just
yet. My goal is to have it so that when you say 'arc diff', you can
put the words:

Trac: #9832, #9123

into the review, and it will auto appear on Phabricator as a custom
field, hyperlink it, and then a comment will appear on Trac. I have to
write some PHP and Python on both ends to get this all working,
though.

Also the builder script is currently really crappy, so I'm fixing that
a bit, so it will correctly deal with concurrent builds and multiple
builders.

 · Document how to update a submodule; e.g. haddock

 o   We worked through an example

 o   We need a canonical place on the wiki to say which branch GHC should be 
 tracking on the submodule; and how to check that it is

 o   Need to talk to haddock and cabal folk about whether GHC should track 
 master or a branch in their repo. They may want a more stable branch to work 
 on.


 · Wiki pages

 o   Be sure to update 
 https://ghc.haskell.org/trac/ghc/wiki/Building/GettingTheSources, to include 
 simple cloning story

 o   Consolidate “how to use Git” information into WorkingConventions/Git, 
 perhaps headed “Git workflows”.  Merging WorkingConventions/Git with the 
 Git/Submodules page will make it intimidatingly long.

 §  Think about how to split it up.

 §  Tricks should be on a separate page.

 §  Focus on tasks, not technology

 o   wiki:Repositories page says where everything lives, but not how to use 
 them.

 §  Needs updating to have the correct data.

 §  Also integrate https://ghc.haskell.org/trac/ghc/wiki/Repositories/Upstream

This is now done with a first draft. I think I simplified the pages a
lot. See here:

https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Git

and:

https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/Git/Submodules

I plan on obsoleting the old Repositories pages since they're mostly
redundant and out of date now. There may be more info stuffed into
other places, but I imagine it will stay under this hierarchy.

There are still some links and prose that need to be rewritten that I
obviously missed however.

 · Merge AMP stuff.  Should be done now.  (Without join in Monad for 
 now, #9123.)  https://phabricator.haskell.org/D13

Unfortunately this is still pending a few things, so I haven't gotten
it done yet. :(

 o   Maybe make the bug tracker page easier to find.

 §  

Status updates

[Austin Seipp]

Hello all,

I've been lax on the status updates, but better late than never. :)
Here are some things that I've been up to.

 - 7.8.3 is released! Hooray!

 - Phabricator can now build code reviews if you submit them. I sent
an email about this earlier in the week[1] in case you missed it.
Unfortunately it has a rather stupid bug that it doesn't catch stderr
properly, but I'll fix that soon. :)

 - I also spent some time on trying to get Phabricator to post to Trac
(when a code review for a ticket is posted), but to no avail yet.
Hopefully I'll have this done in the next few days.

 - I spent a few hours yesterday and on Saturday on the AMP work
still, because I missed a few things actually (broken deriving
mechanism due to forgetting some changes). I also need to send one
more patch to Cabal upstream I believe, but otherwise things look OK.
I'll post a new code review today when I've finished.

 - This morning I've combed some tickets and remilestoning stuff,
since there was a *lot* left around for 7.6.2 still! This should all
be fixed. I'll keep doing this today and this morning probably.

 - I want to reorganize the wiki pages around the Git repository, and
I have been meaning to do this, but not gotten around to it yet. :(

Some other things on my mind:

 - When I released 7.8.3, I noticed we have a whole bunch of new
upstream distribution packages now, but the download page for those is
pretty out of date I think.[2] That should probably be updated.

 - There are patches in the Trac queue I need to get done with. If
I've ignored your patch I'm sorry! I'll try to get this done quickly.

 - Johan reminded me about D4 this morning[3] which I still need to
merge upstream after addressing the details in the review.

[1]: https://www.haskell.org/pipermail/ghc-devs/2014-July/005509.html

[2]: https://www.haskell.org/ghc/download_ghc_7_8_3#distros

[3]: https://phabricator.haskell.org/D4

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Simon Peyton Jones]

Cherished GHC devs,

GHC has long since exceeded the modest capacities of GHC HQ, even before Simon 
M's move to Facebook.  But in fact Simon's move simply made clearer something 
that was already true, namely that GHC is *mainly* reliant on the committed 
support of its developer community (i.e. you).  I am hugely grateful for all 
that you do, as are all Haskell users -- thank you.

I'm happy to say that Microsoft Research is continuing to fund Well Typed to 
offer front-line support for GHC, which currently takes the visible and 
energetic form of Austin.  He and Simon and I have a weekly Skype call to 
coordinate what we are going to do.

However, I feel that we have been less good at communicating with all of you, 
about what Austin is currently doing, and what we plan to do, when.  This has 
been particular visible recently, when the 7.8 releases have been repeatedly 
delayed, often with good reason, but we haven't been very good about keeping 
you in the loop.

So henceforth Austin is going to send you a weekly roundup, on Mondays, saying
- what he has been up to
- what he plans to do this week
- what he'd like help with
I'm hoping that this will help to keep you all better informed.  Perhaps you 
can do the same when you are actively working on things.

Keeping accurate, timely, and friendly communication going among GHC developers 
is very important.  Please yell if it's going wrong, and suggest ways to make 
it better.

Thanks again

Simon



| -Original Message-
| From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of
| Austin Seipp
| Sent: 14 July 2014 14:27
| To: ghc-devs@haskell.org
| Subject: Status updates
| 
| Hello all,
| 
| I've been lax on the status updates, but better late than never. :)
| Here are some things that I've been up to.
| 
|  - 7.8.3 is released! Hooray!
| 
|  - Phabricator can now build code reviews if you submit them. I sent an
| email about this earlier in the week[1] in case you missed it.
| Unfortunately it has a rather stupid bug that it doesn't catch stderr
| properly, but I'll fix that soon. :)
| 
|  - I also spent some time on trying to get Phabricator to post to Trac
| (when a code review for a ticket is posted), but to no avail yet.
| Hopefully I'll have this done in the next few days.
| 
|  - I spent a few hours yesterday and on Saturday on the AMP work still,
| because I missed a few things actually (broken deriving mechanism due
| to forgetting some changes). I also need to send one more patch to
| Cabal upstream I believe, but otherwise things look OK.
| I'll post a new code review today when I've finished.
| 
|  - This morning I've combed some tickets and remilestoning stuff, since
| there was a *lot* left around for 7.6.2 still! This should all be
| fixed. I'll keep doing this today and this morning probably.
| 
|  - I want to reorganize the wiki pages around the Git repository, and I
| have been meaning to do this, but not gotten around to it yet. :(
| 
| Some other things on my mind:
| 
|  - When I released 7.8.3, I noticed we have a whole bunch of new
| upstream distribution packages now, but the download page for those is
| pretty out of date I think.[2] That should probably be updated.
| 
|  - There are patches in the Trac queue I need to get done with. If I've
| ignored your patch I'm sorry! I'll try to get this done quickly.
| 
|  - Johan reminded me about D4 this morning[3] which I still need to
| merge upstream after addressing the details in the review.
| 
| [1]: https://www.haskell.org/pipermail/ghc-devs/2014-July/005509.html
| 
| [2]: https://www.haskell.org/ghc/download_ghc_7_8_3#distros
| 
| [3]: https://phabricator.haskell.org/D4
| 
| --
| Regards,
| 
| Austin Seipp, Haskell Consultant
| Well-Typed LLP, http://www.well-typed.com/
| ___
| ghc-devs mailing list
| ghc-devs@haskell.org
| http://www.haskell.org/mailman/listinfo/ghc-devs
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Páli Gábor János]

2014-06-06 3:26 GMT+02:00 Kazu Yamamoto k...@iij.ad.jp:
 I have one Mac Pro to build GHC. But it is behind a firewall.
 Is this useful for this purpose?

If it can reach the server (haskell.inf.elte.hu) on port 4938 then you
are probably good to go.  The other requirement would be to able to
run 24/7 so the clients could do their work seamlessly.
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Austin Seipp]

Hello all,

A cumulative status update will now appear, to summarize a few things
that have happened in the past little while since I've been somewhat
absent and short on time.

 - 7.8.3 is looming, because we have a lot of bugfixes as I said last
week: https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8.3

 That's nearly 30 tickets axed in the past few weeks since 7.8.2, so
not bad! As I said before, I'm eager to release sooner rather than
later as my time is short. Do keep weighing in if you have anything to
say or want something fixed. Now is really the time!

 - AMP/ORF - these are still on branches, but me and Simon have gotten
hung up on a few things delaying it. They'll go in soon, promise! (For
certain definitions of 'soon', cooperating with time schedules). AMP
in particular can probably land very, very soon.

  Otherwise we're past a lot of other churn, like removing external
core and whatnot.

 - I merged a bunch of patches this morning to the 7.8 branch,
bringing it close to what I expect we will ship 7.8.3 with. Again,
pester me soon if you want something!

 - There's now a proper CI link for GHC on Trac so people don't lose
it. The new builders are checking in regularly, so please watch out
for them - and subscribe to ghc-bui...@haskell.org if you haven't
already.

 - Some other churn in the tree has not yet passed; I still need to
improve and land my performance patches for copies, for example.

 - XCode 5.1 has introduced some other breaking changes I'll need to
fix (things *work*, but the testsuite is useless due to the warning
spewage), along with merging the remaining patches.

 - Also, if you have spare hardware, please email Gabor Pali (or just
email the list itself, or reply to this thread) if you're willing to
donate, that would be awesome. Another Mac OS X target would be
especially welcome, I think (my development machine is on loan right
now), and I will have better dedicated Windows targets soon.

I'll send another email about 7.8.3 shortly.

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

RE: Status updates

[Simon Peyton Jones]

|  - 7.8.3 is looming, because we have a lot of bugfixes as I said last
| week: https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8.3

Just to be clear, on that page:
  closed = done in 7.8.3 branch
  patch  = will go in 7.8.3 branch
  new/infoneeded = will NOT go in 7.8.3 unless you yell loudly and soon
   and argue for delay to get it in

|  - There's now a proper CI link for GHC on Trac so people don't lose it.
| The new builders are checking in regularly, so please watch out for them
| - and subscribe to ghc-bui...@haskell.org if you haven't already.

Where exactly is the link?  (Ie not what is the link but where on Trac is it 
posted?)

Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Austin Seipp]

Drats, I forgot that. Here's where it is:

Go to the GHC Trac hompeage: https://ghc.haskell.org/trac/ghc/ and
scroll down just a tiny bit. There's a section called 'Nightly builds'
with the updated link to the new UI, located on Gabor's server:
http://haskell.inf.elte.hu/builders/

Simon, did we talk about adding this to the sidebar? Or maybe we
should just highlight it on the front page a little more, and then
link to it from somewhere else on the sidebar (like Building Guide
links to the builder page).

On Thu, Jun 5, 2014 at 8:35 AM, Simon Peyton Jones
simo...@microsoft.com wrote:
 |  - 7.8.3 is looming, because we have a lot of bugfixes as I said last
 | week: https://ghc.haskell.org/trac/ghc/wiki/Status/GHC-7.8.3

 Just to be clear, on that page:
   closed = done in 7.8.3 branch
   patch  = will go in 7.8.3 branch
   new/infoneeded = will NOT go in 7.8.3 unless you yell loudly and soon
and argue for delay to get it in

 |  - There's now a proper CI link for GHC on Trac so people don't lose it.
 | The new builders are checking in regularly, so please watch out for them
 | - and subscribe to ghc-bui...@haskell.org if you haven't already.

 Where exactly is the link?  (Ie not what is the link but where on Trac is 
 it posted?)

 Simon




-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[山本和彦]

Hi,

  - Also, if you have spare hardware, please email Gabor Pali (or just
 email the list itself, or reply to this thread) if you're willing to
 donate, that would be awesome. Another Mac OS X target would be
 especially welcome, I think (my development machine is on loan right
 now), and I will have better dedicated Windows targets soon.

I have one Mac Pro to build GHC. But it is behind a firewall.
Is this useful for this purpose?

--Kazu
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Carter Schonwald]

I can build on my Mac.  Happy to do so since I'll be doing anyways :-)

On Thursday, June 5, 2014, Kazu Yamamoto k...@iij.ad.jp wrote:

 Hi,

   - Also, if you have spare hardware, please email Gabor Pali (or just
  email the list itself, or reply to this thread) if you're willing to
  donate, that would be awesome. Another Mac OS X target would be
  especially welcome, I think (my development machine is on loan right
  now), and I will have better dedicated Windows targets soon.

 I have one Mac Pro to build GHC. But it is behind a firewall.
 Is this useful for this purpose?

 --Kazu
 ___
 ghc-devs mailing list
 ghc-devs@haskell.org javascript:;
 http://www.haskell.org/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Manuel M T Chakravarty]

Austin,

Could we please make sure to include this bug for 7.8.3?

  https://ghc.haskell.org/trac/ghc/ticket/9078

The ticket already includes a patch that solves the problem for us.

As remarked by Levent, this bug will probably affect all EDSL that use Andy’s 
StableName-based observable sharing trick.

Cheers,
Manuel

Austin Seipp aus...@well-typed.com:
 Hello all,
 
 It has been another slow week here, and there wasn't a lot I touched
 in the tree this week. The primary highlights:
 
 * The AMP battle rages on! It turns out the addition of `join` to
 `Monad` has had some subtle implications for GND/Roles. See here for
 more: https://www.haskell.org/pipermail/ghc-devs/2014-May/004964.html
 
 * Simon is still reviewing the ORF work, as far as I know. Hopefully
 it will Land Real Soon Now.
 
 * Patches! Lots of them! I'm reviewing and merging several of them
 right now. In particular, all the ones slated for 7.8.3 are up for
 grabs[1] by me right now, but I do need to double-check some of them
 e.g. on Windows, to make sure nothing breaks.
 
 * Many branches have been deleted. Something like 20-30 of them, I
 think. Yay! Sorry for the spam to the commits list too, but it was a
 necessary evil.
 
 * I'm working away at some of the bugs. #7602 is building right now,
 with some nice improvements. That will go into the 7.8.3 branch, so OS
 X users will get a big performance gain, yay!
 
 * Another bug: #8736. I had a patch for this, but this one is tricky
 to fix because when we load object files, we don't actually know if
 they're static or dynamic. This is encoded in the interface file, but
 there are some tricky semantics about what to do in some cases of
 (legitimately) needing to re-read interface files that are a bit
 subtle. I'll be trying to revive my patch for this today.
 
 Other than that, there really hasn't been a lot to mention. Please, do
 get down on reviewing some bugs and helping fix them![1] I'm more than
 willing to help in any way I can.
 
 I'd also like some feedback: what do people think about the current
 list? Are there any of you readers who see one *you* think is truly
 critical? Maybe we can get some input to help narrow the scope if
 needed.
 
 Thanks!
 
 [1] 
 https://ghc.haskell.org/trac/ghc/query?status=infoneededstatus=mergestatus=newstatus=patchgroup=statusmilestone=7.8.3
 
 -- 
 Regards,
 
 Austin Seipp, Haskell Consultant
 Well-Typed LLP, http://www.well-typed.com/
 ___
 ghc-devs mailing list
 ghc-devs@haskell.org
 http://www.haskell.org/mailman/listinfo/ghc-devs

___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Austin Seipp]

Hello all,

It has been another slow week here, and there wasn't a lot I touched
in the tree this week. The primary highlights:

 * The AMP battle rages on! It turns out the addition of `join` to
`Monad` has had some subtle implications for GND/Roles. See here for
more: https://www.haskell.org/pipermail/ghc-devs/2014-May/004964.html

 * Simon is still reviewing the ORF work, as far as I know. Hopefully
it will Land Real Soon Now.

 * Patches! Lots of them! I'm reviewing and merging several of them
right now. In particular, all the ones slated for 7.8.3 are up for
grabs[1] by me right now, but I do need to double-check some of them
e.g. on Windows, to make sure nothing breaks.

 * Many branches have been deleted. Something like 20-30 of them, I
think. Yay! Sorry for the spam to the commits list too, but it was a
necessary evil.

 * I'm working away at some of the bugs. #7602 is building right now,
with some nice improvements. That will go into the 7.8.3 branch, so OS
X users will get a big performance gain, yay!

 * Another bug: #8736. I had a patch for this, but this one is tricky
to fix because when we load object files, we don't actually know if
they're static or dynamic. This is encoded in the interface file, but
there are some tricky semantics about what to do in some cases of
(legitimately) needing to re-read interface files that are a bit
subtle. I'll be trying to revive my patch for this today.

Other than that, there really hasn't been a lot to mention. Please, do
get down on reviewing some bugs and helping fix them![1] I'm more than
willing to help in any way I can.

I'd also like some feedback: what do people think about the current
list? Are there any of you readers who see one *you* think is truly
critical? Maybe we can get some input to help narrow the scope if
needed.

Thanks!

[1] 
https://ghc.haskell.org/trac/ghc/query?status=infoneededstatus=mergestatus=newstatus=patchgroup=statusmilestone=7.8.3

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Status updates

[Austin Seipp]

Hi all,

 - The HCAR entry was quickly completed last week thanks to everyone,
much appreciated for the quick response! And it made me aware of some
other new things in the pipeline, too. :)

 - Simon is in-progress reviewing the ORF work still. But it's
happening, so be patient of course (it's a large patch after all).

 - After a short discussion last week and a small grace period I
killed external core, and removed all traces of it from the GHC tree.
We constantly add things to GHC as Richard noted, so removing
something was nice, even if a little sad. The result was about 3,000
fewer lines in the source tree.

 - I need to send a patch upstream to Ross for the AMP changes, but I
slacked off a bit since the release of the new transformers got pushed
back, pending some discussions on librar...@haskell.org - I'll be
sending the results to Ross later today.

 - I spent some time working on removing the need for a build from
creation of the source distribution like I mentioned last week - so
'make sdist' almost works out of the box. I believe it works fine, but
it needs some more testing, and I feel like I should float the patch
by for review on the list first, Simon in particular might have
something to say. Do watch this space.

 - I'm going to continue working on trying HEAD with Stackage and
putting the results somewhere, I just sort of left this as is right
now.

Also, remember from last week, the 7.8.3 milestone has been shaped up
to be what we will look at - please do look over the tickets here when
you get a chance! I'll be likely seeing if any new tickets will go
here today:

https://ghc.haskell.org/trac/ghc/milestone/7.8.3

https://ghc.haskell.org/trac/ghc/query?status=infoneededstatus=mergestatus=newstatus=patchgroup=statusmilestone=7.8.3

Some other things worth noting:

 - It's time to merge up a lot of the patch queue. I'll be doing that
soon - if you floated a patch by and want to discuss it or you want to
make me aware of a patch you have, please let me know. At worst you
will just inform me of something I already knew.

 - Side note, since a few people might be keen to know - Herbert took
the time this week to move darcs.haskell.org onto a new server,
effectively putting it in legacy mode. The switch has not yet
happened, because we need to do a DNS switch.

That's all, it was pretty light this week for me actually! We didn't
actually have a call today yet actually, but we will have one next
week and have more to say for sure.

Do let me know if you have questions.

-- 
Regards,

Austin Seipp, Haskell Consultant
Well-Typed LLP, http://www.well-typed.com/
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Roman Cheplyaka]

Hi Austin,

Could you consider #9012 for 7.8.3?

* Austin Seipp aus...@well-typed.com [2014-05-05 11:54:20-0500]
 Hi all,
 
  - The HCAR entry was quickly completed last week thanks to everyone,
 much appreciated for the quick response! And it made me aware of some
 other new things in the pipeline, too. :)
 
  - Simon is in-progress reviewing the ORF work still. But it's
 happening, so be patient of course (it's a large patch after all).
 
  - After a short discussion last week and a small grace period I
 killed external core, and removed all traces of it from the GHC tree.
 We constantly add things to GHC as Richard noted, so removing
 something was nice, even if a little sad. The result was about 3,000
 fewer lines in the source tree.
 
  - I need to send a patch upstream to Ross for the AMP changes, but I
 slacked off a bit since the release of the new transformers got pushed
 back, pending some discussions on librar...@haskell.org - I'll be
 sending the results to Ross later today.
 
  - I spent some time working on removing the need for a build from
 creation of the source distribution like I mentioned last week - so
 'make sdist' almost works out of the box. I believe it works fine, but
 it needs some more testing, and I feel like I should float the patch
 by for review on the list first, Simon in particular might have
 something to say. Do watch this space.
 
  - I'm going to continue working on trying HEAD with Stackage and
 putting the results somewhere, I just sort of left this as is right
 now.
 
 Also, remember from last week, the 7.8.3 milestone has been shaped up
 to be what we will look at - please do look over the tickets here when
 you get a chance! I'll be likely seeing if any new tickets will go
 here today:
 
 https://ghc.haskell.org/trac/ghc/milestone/7.8.3
 
 https://ghc.haskell.org/trac/ghc/query?status=infoneededstatus=mergestatus=newstatus=patchgroup=statusmilestone=7.8.3
 
 Some other things worth noting:
 
  - It's time to merge up a lot of the patch queue. I'll be doing that
 soon - if you floated a patch by and want to discuss it or you want to
 make me aware of a patch you have, please let me know. At worst you
 will just inform me of something I already knew.
 
  - Side note, since a few people might be keen to know - Herbert took
 the time this week to move darcs.haskell.org onto a new server,
 effectively putting it in legacy mode. The switch has not yet
 happened, because we need to do a DNS switch.
 
 That's all, it was pretty light this week for me actually! We didn't
 actually have a call today yet actually, but we will have one next
 week and have more to say for sure.
 
 Do let me know if you have questions.
 
 -- 
 Regards,
 
 Austin Seipp, Haskell Consultant
 Well-Typed LLP, http://www.well-typed.com/
 ___
 ghc-devs mailing list
 ghc-devs@haskell.org
 http://www.haskell.org/mailman/listinfo/ghc-devs


signature.asc
Description: Digital signature
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Herbert Valerio Riedel]

On 2014-04-22 at 14:42:46 +0200, Austin Seipp wrote:

[...]

  - I've been looking into our CI setup for GHC, and evaluating things.
 Right now though, I am directly working on getting Windows build bots
 set up on Gabor's infrastructure. He gave me the credentials, and
 hopefully this should not take long, it just slipped my mind.

  But mostly I've been looking at CI systems for Hackage, so that we
 can try to continuously integrate a subset of important packages
 against GHC over time. Right now, we have Travis-CI thanks to Herbert,
 but not quite everyone uses this (or doesn't properly configure it to
 e.g. test HEAD).

 This would really help find things in the future, I think, especially
 closer to release. It would also really help find nasty bugs in the
 RCs, like the dreaded #8978

  Right now, after some thought, I'm looking into Michael's Stackage as
 a starting point for this, as he's done some awesome work. But I
 haven't yet done so in anger, and there are some other things I want
 to try too.

I want to add that a GitHub-integrated CI like Travis-CI and a
Hackage-CI are two different CI-systems that complement each other, in
case there may be the impression that one renders the other one
redundant.

Something like Travis-CI helps a package maintainer keep the HEAD branch
from breaking early during development even before the package is
actually uploaded to Hackage (furthermore, it helps pre-validating
patches in pull-requests so might save the package maintainer time with
patches that don't pass the test-suite). 

Whereas a build-the-world Hackage-CI would (the way I understand it)
help detecting that the Hackage *released* package-set is in a working
state for a given compiler configuration (including GHC HEAD[1]), w/o
any active cooperation from the package maintainer. And more
importantly, it may trigger rebuilds of depending packages, when new
packages is added to the Hackage index to help detect problems due to
inter-package interactions.


 [1]: However, I wonder how to keep Hackage buildable with GHC HEAD w/o
  having to patch up every package that will likely break sooner or
  later due to API (e.g. the AMP-refactoring will likely break
  stuff) and compiler changes[2], as I don't think cabal-install's
  --allow-newer will help in all cases.

 [2]: This already happened due to #8883 with the HTTP package, 
  see also haskell/HTTP#58


Cheers,
  hvr
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

RE: Status updates

[Simon Peyton Jones]

| having GHC HQ monitor breakage in (a subset) of hackage for HEAD would
| be great! I can imagine a daily (or weekly, depending on resources)
| build of all of hackage or stackage using HEAD, and when there is a
| breakage, then git bisect on our soon bisectable repo and a tool that
| would allow the common git hacker to easily built and test the one
| breaking package will let us know about problems quickly and with
| little friction.
| 
| (The sole purpose of this message is to convey motivation :-))

Please remember that ghc hq = Austin and me. And I have another job.  Relying 
on GHC for anything means that you may wait a long time.

So we increasingly rely on the army of GHC volunteers to do the heavy lifting.  
I'm increasingly encouraging Austin to see his role as 
   supporting, 
   encouraging,
   helping, 
   coordinating, 
   removing road-blocks from, 
   keeping well-informed,
   and thanking 
volunteers, rather than doing the work himself.

So Yay for motivation, but it's the ghc-devs community that you are addressing, 
not ghc hq.

And THANK YOU ghc-devs.  We love you.

Simon
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Joachim Breitner]

Hi,

Am Donnerstag, den 24.04.2014, 08:29 + schrieb Simon Peyton Jones:
 Please remember that ghc hq = Austin and me.

sorry, I meant and should have said, more generally, GHC developers.

Greetings,
Joachim
-- 
Joachim “nomeata” Breitner
  m...@joachim-breitner.de • http://www.joachim-breitner.de/
  Jabber: nome...@joachim-breitner.de  • GPG-Key: 0xF0FBF51F
  Debian Developer: nome...@debian.org



signature.asc
Description: This is a digitally signed message part
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Kim-Ee Yeoh]

On Thu, Apr 24, 2014 at 3:29 PM, Simon Peyton Jones
simo...@microsoft.comwrote:

 So we increasingly rely on the army of GHC volunteers to do the heavy
 lifting.  I'm increasingly encouraging Austin to see his role as
supporting,
encouraging,
helping,
coordinating,
removing road-blocks from,
keeping well-informed,
and thanking
 volunteers, rather than doing the work himself.


To that end, I have one or two book recommendations for Austin if he would
like them (ping me off-list). Organizing volunteers isn't easy but
specialists have worked hard on this problem and shared their results.

-- Kim-Ee
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs

Re: Status updates

[Joachim Breitner]

Hi,

Am Dienstag, den 22.04.2014, 07:42 -0500 schrieb Austin Seipp:
  - I've been looking into our CI setup for GHC, and evaluating things.
 Right now though, I am directly working on getting Windows build bots
 set up on Gabor's infrastructure. He gave me the credentials, and
 hopefully this should not take long, it just slipped my mind.
 
  But mostly I've been looking at CI systems for Hackage, so that we
 can try to continuously integrate a subset of important packages
 against GHC over time. Right now, we have Travis-CI thanks to Herbert,
 but not quite everyone uses this (or doesn't properly configure it to
 e.g. test HEAD).
 
 This would really help find things in the future, I think, especially
 closer to release. It would also really help find nasty bugs in the
 RCs, like the dreaded #8978
 
  Right now, after some thought, I'm looking into Michael's Stackage as
 a starting point for this, as he's done some awesome work. But I
 haven't yet done so in anger, and there are some other things I want
 to try too.

having GHC HQ monitor breakage in (a subset) of hackage for HEAD would
be great! I can imagine a daily (or weekly, depending on resources)
build of all of hackage or stackage using HEAD, and when there is a
breakage, then git bisect on our soon bisectable repo and a tool that
would allow the common git hacker to easily built and test the one
breaking package will let us know about problems quickly and with little
friction.

(The sole purpose of this message is to convey motivation :-))

Greetings,
Joachim


-- 
Joachim “nomeata” Breitner
  m...@joachim-breitner.de • http://www.joachim-breitner.de/
  Jabber: nome...@joachim-breitner.de  • GPG-Key: 0xF0FBF51F
  Debian Developer: nome...@debian.org



signature.asc
Description: This is a digitally signed message part
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs