RE: Status updates
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
Re: Status updates
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
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
- 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
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
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
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)
- 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)
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
Re: Status updates
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
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
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
Re: Status updates
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
Re: Status updates
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
Re: Status updates
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
RE: Status updates
| - 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
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
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
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
Re: Status updates
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
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
| 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
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
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
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
