Re: Action Required: Status of Harbormaster for Differentials
Joachim Breitner writes: > [ Unknown signature status ] > Hi, > > Am Freitag, den 26.08.2016, 09:38 -0400 schrieb Ben Gamari: >> The reason for this new requirement is that `arc diff` will soon push >> submitted diffs to a "staging area", a Git repository managed by >> Phabricator containing a branch for each submitted Differential. > > this is great, because it means that we can run performance builds via > perf.haskell.org on all DRs automatically! > > Will the staging repository be publicly available? > Indeed, it's available at [1]. There are no > And will it also contain the usual branches (master, ghc-8.0, wip/), so > that I can simply take that as the upstream repo for gipeda’s sake? > Not as things are currently configured and I'm not sure how easy it would be to reliably accomplish this. The only thing you'll find in that repository currently is tags (not branches as I stated earlier; sorry!) with names of the form phabricator/base/1234 and phabricator/diff/1234. These contain the base and head commits of revision 1234, respectively. Note that 1234 does not identify a differential; rather it is a revision of a differential (e.g. the number that you see in the "ID" column of the history table fn a differential in the web interface). Cheers, - Ben [1] https://phabricator.haskell.org/diffusion/GHCDIFF/ signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Action Required: Status of Harbormaster for Differentials
Hi, Am Freitag, den 26.08.2016, 09:38 -0400 schrieb Ben Gamari: > The reason for this new requirement is that `arc diff` will soon push > submitted diffs to a "staging area", a Git repository managed by > Phabricator containing a branch for each submitted Differential. this is great, because it means that we can run performance builds via perf.haskell.org on all DRs automatically! Will the staging repository be publicly available? And will it also contain the usual branches (master, ghc-8.0, wip/), so that I can simply take that as the upstream repo for gipeda’s sake? Greetings, Joachim -- Joachim “nomeata” Breitner m...@joachim-breitner.de • https://www.joachim-breitner.de/ XMPP: nome...@joachim-breitner.de • OpenPGP-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://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
RE: [Diffusion] [Build Failed] rGHCae66f356fb0d: Allow typed holes to be levity-polymorphic
Ben or others Something is wrong with the .stderr file for T12531 (typed holes), which I just fixed. Not easy for me to sort out at home..might someone look? Or mark it as expect fail and I'll deal with it on Monday Thanks Simon From: nore...@phabricator.haskell.org [mailto:nore...@phabricator.haskell.org] Sent: 26 August 2016 18:24 To: Simon Peyton Jones Subject: [Diffusion] [Build Failed] rGHCae66f356fb0d: Allow typed holes to be levity-polymorphic Harbormaster failed to build B10796: rGHCae66f356fb0d: Allow typed holes to be levity-polymorphic! BRANCHES master USERS simonpj (Author) O7 (Auditor) O11 (Auditor) COMMIT https://phabricator.haskell.org/rGHCae66f356fb0d EMAIL PREFERENCES https://phabricator.haskell.org/settings/panel/emailpreferences/ To: simonpj, Harbormaster ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Cross-compiling Template Haskell via -fexternal-interpreter and IPC
Alberto Valverde writes: > On Thu, Jul 7, 2016 at 9:30 AM, Simon Marlow wrote: > >> I agree, named pipes are probably a better plan, perhaps a better solution >> overall than the way we currently pass FD numbers on the command line. Do >> named pipes work work as expected through wine? We would have to be >> careful to clean them up again afterwards. >> > > I've implemented IPC with named pipes and it appeared to work through wine > but now I'm investigating an issue which causes GHC to "freeze" when > talking to the external interpreter when it is not running on a TTY (ie: in > a build process) Hi Alterto, What ever happened to this? Is there any way I can be of assistance? It would be great to get this merged. Cheers, - Ben signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Action Required: Status of Harbormaster for Differentials
tl;dr. I am working on restoring Harbormaster support for Differentials. Towards this end, GHC's Phabricator instance will soon require that you add an SSH public key to your account in order to upload patches with `arc diff`. Hello everyone, As you are no doubt aware Harbormaster has not been building Differentials for a very long time now. I am currently looking at options for restoring this service but it appears that doing so will require a bit of action on the part of our contributors. Specically, you will need to add an SSH key to Phabricator. You can do so by navigating to the Phabricator Settings [1] page, selecting the "Personal Account Settings" option, and selecting "SSH Public Keys" from the list on the left. There you can click on the "SSH Key Actions" menu on the top-right corner and click on the "Upload Public Key" item. Here you can specify a key name and paste the key contents (e.g. the contents of $HOME/.ssh/id_rsa.pub). The reason for this new requirement is that `arc diff` will soon push submitted diffs to a "staging area", a Git repository managed by Phabricator containing a branch for each submitted Differential. This will allow more reliable Harbormaster builds and merges as we will no longer need to rely on Phabricator correctly applying Differential patches (which has historically been problematic, especially for Differentials where the base commit is unavailable). If there are no objections, I would like to enable the staging area for the rGHC repository in three days, on Monday, 29 August 2016. After this date `arc diff` will try to push submitted differentials to the staging area, which will require a public key. Note, however, that pushing to the staging area can always be disabled with `arc diff`'s `--skip-staging` flag (although we won't be able to run CI builds on Differentials submitted in this way). To be clear: I would have liked to provide an option that did not require key-based authentication, but sadly neither Phabricator nor Gitolite provide any such option. I apologize for the added friction that this new requirement imposes. If enough people feel strongly that this is too onerous then I'm happy to entertain alternative solutions. Cheers, - Ben [1] https://phabricator.haskell.org/settings/ signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
Re: Trac commit notifications on stable branches
Ah right my bad. Seems like a good change to me then. Matt On Fri, Aug 26, 2016 at 12:06 AM, Ben Gamari wrote: > Matthew Pickering writes: > >> I did notice today that I received a lot of emails as you were merging >> patches to the stable branch. >> > Well, the email volume was no different from my usual merge practices > since I typically leave comments of the sort that the Trac hook produces > manually. The only difference is this time they were automatically > produced. Unfortunately, the Trac notification messages don't mention > which branch the commit is on unlike the messages I typically leave > manually. I'm evaluating options for fixing this. > > If it seemed like there was a lot of messages today that is merely > because I was doing a lot of cleanup on the ghc-8.0 branch today. > > Cheers, > > - Ben > ___ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
