Re: Using same stdout/stderr files for multiple tests?

2019-01-22 Thread Ömer Sinan Ağacan
These days when I need something like this I just use a make rule, which is not great as you have to run multiple tests in one make rule and you can't run only one with the TESTS parameter or skip some of the tests. Another problem is I can't have multiple tests that use single source file, again

Re: Using same stdout/stderr files for multiple tests?

2019-01-22 Thread Ben Gamari
Ömer Sinan Ağacan writes: > I have a test that I want to run with different compile and runtime > parameters. > I managed to reuse the source file across different tests by adding a > extra_files(['source.hs']) to the tests, but I don't know how to do the same > for > stdout/stderr files. Any

[GitLab] Introducing Marge-bot

2019-01-22 Thread Ben Gamari
Hi everyone, As you might have noticed there is a new face on GitLab: Meet @marge-bot. Marge will be helping us with the pain of merging merge requests: Currently the typical workflow to merge an accepted MR involves the following: 1. Rebase the MR on top of the current `master` branch 2.

Re: Drop into a nix shell with ghcHEAD

2019-01-22 Thread Matthew Pickering
I have now added a small wrapper script which allows you to pull artefacts by MR number. https://github.com/mpickering/ghc-artefact-nix#ghc-head-from-script ``` # Fetches MR 180 ghc-head-from 180 ``` ``` #Fetches ghc/master ghc-head-from ``` The most convenient way to access the script is to

Re: Drop into a nix shell with ghcHEAD

2019-01-22 Thread Matthew Pickering
I just extended it slightly so you can grab artifacts from MRs as well. The interface is not perfect but should still be useful. https://github.com/mpickering/ghc-artefact-nix You can specify the two options `fork` and `branch` in order to download an artefact for a contributors branch in order