Home liberachat/#haskell: Logs Calendar

Logs: liberachat/#haskell

←Prev  Next→ 1,802,280 events total
2025-11-25 18:16:49 Wygulmage joins (~Wygulmage@user/Wygulmage)
2025-11-25 18:17:48 Frostillicus joins (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-11-25 18:18:23 <Wygulmage> Is there a way to run multiple tests on the same input in QuickCheck? It's much simpler for me if things all fail in the same way when they have the same bug, and different ways if they have different bugs.
2025-11-25 18:24:31 × connrs quits (~connrs@user/connrs) (Ping timeout: 240 seconds)
2025-11-25 18:24:44 <hseg> tomsmeding: https://0x0.st/KW3r.txt is the log for cabal test --verbose (for shake on a custom xdg linux)
2025-11-25 18:25:05 <hseg> reminder: https://0x0.st/KWJE.txt is my cabal/config
2025-11-25 18:26:18 <tomsmeding> Wygulmage: what about (.&&.)?
2025-11-25 18:31:03 <tomsmeding> hseg: how does that setup.exe even end up there? How is it built, and why is it in an old-style dist folder?
2025-11-25 18:31:36 <hseg> not sure -- but src/Test/Docs.hs references it explicitly by name
2025-11-25 18:31:53 <tomsmeding> if you clean the build first and then rebuild, does it say anything about it?
2025-11-25 18:32:10 tomsmeding has been burned by doctests not working in the most spectacular of ways once, long ago, and has avoided touching them since
2025-11-25 18:32:33 <tomsmeding> also why is the thing called setup.exe -- this is not windows?
2025-11-25 18:32:44 <hseg> running git clean -dffx ; cabal build shake-test
2025-11-25 18:32:50 <hseg> tomsmeding: oh, that's hardcoded
2025-11-25 18:33:24 peterbecich joins (~Thunderbi@172.222.148.214)
2025-11-25 18:33:29 <hseg> https://github.com/ndmitchell/shake/blob/master/src/Test/Docs.hs#L17
2025-11-25 18:33:35 connrs joins (~connrs@user/connrs)
2025-11-25 18:34:24 × humasect quits (~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection)
2025-11-25 18:34:29 <tomsmeding> and this is the only occurrence of "setup.exe" in that repo
2025-11-25 18:34:38 <tomsmeding> this feels a little bit like a shake problem and not a haskell problem
2025-11-25 18:34:49 <hseg> fair
2025-11-25 18:34:58 <tomsmeding> have you managed to run this test suite outside of a special aur build?
2025-11-25 18:35:17 <tomsmeding> or is the directory name there just incidental and is this a manual build from the git repo
2025-11-25 18:35:25 <hseg> manual build from git repo
2025-11-25 18:35:29 <tomsmeding> I see
2025-11-25 18:35:42 <tomsmeding> open an issue, I guess :p
2025-11-25 18:35:43 <hseg> in service of eventually packaging a statically-built shake
2025-11-25 18:35:49 <hseg> fair 'nuff
2025-11-25 18:38:06 × mulk quits (~mulk@pd95144c3.dip0.t-ipconnect.de) (Ping timeout: 252 seconds)
2025-11-25 18:46:41 leah2 joins (~leah@vuxu.org)
2025-11-25 18:48:39 merijn joins (~merijn@host-vr.cgnat-g.v4.dfn.nl)
2025-11-25 18:49:14 <hseg> hrm. https://github.com/ndmitchell/shake/issues/267 and comments there suggest the test suite expects GHC_PACKAGE_PATH to be set properly in its environment
2025-11-25 18:49:22 <hseg> is there some way of getting cabal to do that?
2025-11-25 18:50:48 Googulator56 joins (~Googulato@2a01-036d-0106-4ad8-11e2-562e-881b-eb37.pool6.digikabel.hu)
2025-11-25 18:50:54 × Googulator quits (~Googulato@2a01-036d-0106-4ad8-11e2-562e-881b-eb37.pool6.digikabel.hu) (Quit: Client closed)
2025-11-25 18:53:10 <geekosaur> iirc cabal throws an error if you do that?
2025-11-25 18:53:17 <hseg> it does
2025-11-25 18:53:24 × Frostillicus quits (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer)
2025-11-25 18:53:48 <geekosaur> mm, actually that's if you set it outside cabal. I don't know if it's possible to have cabal set it for commands it runs
2025-11-25 18:54:00 Frostillicus joins (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-11-25 18:54:26 <geekosaur> but it would have potential issues since it would expose the store, which external commands could then modify without cabal knowing about it
2025-11-25 18:55:15 × merijn quits (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-11-25 18:55:25 <hseg> right... what's GHC_ENVIRONMENT that I see cabal exec setting?
2025-11-25 18:57:10 <geekosaur> it's an environment file
2025-11-25 18:57:39 <geekosaur> usually you want that disabled, which I think is what cabal is doing
2025-11-25 18:58:00 <geekosaur> (see `--package-env` in cabal)
2025-11-25 18:58:11 <hseg> nope, the opposite -- it seems to be how it's communicating the package db info to the program it runs
2025-11-25 18:58:42 <hseg> unfortunately, it seems that setup.exe doesn't know to pick up on that file?
2025-11-25 19:02:31 <hseg> hrm. any way of making Setup.hs read GHC_ENVIRONMENT? I'm only seeing support for --package-db
2025-11-25 19:02:54 × Everything quits (~Everythin@172-232-54-192.ip.linodeusercontent.com) (Quit: leaving)
2025-11-25 19:03:55 × Frostillicus quits (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 240 seconds)
2025-11-25 19:03:59 Everything joins (~Everythin@172-232-54-192.ip.linodeusercontent.com)
2025-11-25 19:04:01 <hseg> ... wait, shouldn't it Just Work?
2025-11-25 19:04:14 <hseg> after all, GHC reads it from its environment
2025-11-25 19:04:36 Frostillicus joins (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-11-25 19:06:13 kitadamian joins (~kitadamia@95.49.84.49.ipv4.supernova.orange.pl)
2025-11-25 19:06:41 merijn joins (~merijn@host-vr.cgnat-g.v4.dfn.nl)
2025-11-25 19:10:55 × merijn quits (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-11-25 19:11:31 jmcantrell joins (~weechat@user/jmcantrell)
2025-11-25 19:11:34 <hseg> .... OK, we're gradually closing in on a culprit -- it seems GHC_ENVIRONMENT is getting unset somewhere along the line
2025-11-25 19:13:02 tomsmeding wishing hseg luck from the sideline
2025-11-25 19:14:04 × peterbecich quits (~Thunderbi@172.222.148.214) (Ping timeout: 256 seconds)
2025-11-25 19:16:02 tromp joins (~textual@2001:1c00:3487:1b00:bd07:71f2:e20b:fdc)
2025-11-25 19:18:01 × jmcantrell quits (~weechat@user/jmcantrell) (Ping timeout: 264 seconds)
2025-11-25 19:18:46 <hseg> hrmph. it seems cabal _builds_ the test suite with GHC_ENVIRONMENT set, but doesn't _run_ it with it
2025-11-25 19:18:51 <hseg> urggh
2025-11-25 19:19:39 mulk joins (~mulk@pd9514972.dip0.t-ipconnect.de)
2025-11-25 19:19:44 merijn joins (~merijn@host-vr.cgnat-g.v4.dfn.nl)
2025-11-25 19:23:55 × merijn quits (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-11-25 19:24:08 <hseg> Giving up, I'll use something else then
2025-11-25 19:25:54 tomsmeding wonders how long ago it has been that this has worked properly in the first place
2025-11-25 19:28:10 × ttybitnik quits (~ttybitnik@user/wolper) (Quit: Fading out...)
2025-11-25 19:35:06 merijn joins (~merijn@host-vr.cgnat-g.v4.dfn.nl)
2025-11-25 19:37:12 <geekosaur> hack, see if it's there with `cabal run`? (there are enough differences between the two that using `cabal run` to run test suites is relatively common)
2025-11-25 19:39:19 × merijn quits (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2025-11-25 19:39:35 × Frostillicus quits (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer)
2025-11-25 19:40:06 Frostillicus joins (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-11-25 19:43:35 pavonia joins (~user@user/siracusa)
2025-11-25 19:44:02 <hseg> nope -- dumping environment under cabal run shows no GHC_* envvars
2025-11-25 19:44:16 <tomsmeding> and under `cabal exec`?
2025-11-25 19:44:33 <tomsmeding> (build it first with `cabal build`, then run with `cabal exec`)
2025-11-25 19:46:09 <geekosaur> I'd expect not; I was hoping that, since `cabal run` can build first, it'd just keep it exported
2025-11-25 19:46:35 <hseg> under cabal exec it does pick up GHC_ENVIRONMENT, but for some reason it isn't satisfied
2025-11-25 19:47:07 <hseg> wait!
2025-11-25 19:47:25 <hseg> cleaning the test environment, ghc clearly logs that it's loading the package environment
2025-11-25 19:48:04 <hseg> it's just that the compiled Setup.hs configure call doesn't make use of GHC_ENVIRONMENT
2025-11-25 19:50:31 merijn joins (~merijn@host-vr.cgnat-g.v4.dfn.nl)
2025-11-25 19:50:35 × sindu quits (~sindu@2.148.32.207.tmi.telenormobil.no) (Ping timeout: 240 seconds)
2025-11-25 19:50:50 Googulator33 joins (~Googulato@2a01-036d-0106-4ad8-11e2-562e-881b-eb37.pool6.digikabel.hu)
2025-11-25 19:50:54 × Googulator56 quits (~Googulato@2a01-036d-0106-4ad8-11e2-562e-881b-eb37.pool6.digikabel.hu) (Quit: Client closed)
2025-11-25 19:53:40 <hseg> ahhhh. the problem is that setup.hs does nothing with GHC_ENVIRONMENT
2025-11-25 19:54:30 <hseg> it wants to get its package dbs on the command line
2025-11-25 19:55:31 × merijn quits (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2025-11-25 19:56:22 × Frostillicus quits (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 244 seconds)
2025-11-25 19:57:36 Square2 joins (~Square4@user/square)
2025-11-25 19:57:52 Frostillicus joins (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-11-25 20:00:11 peterbecich joins (~Thunderbi@172.222.148.214)
2025-11-25 20:01:07 × Square3 quits (~Square@user/square) (Ping timeout: 250 seconds)
2025-11-25 20:04:04 ft joins (~ft@p508db844.dip0.t-ipconnect.de)
2025-11-25 20:05:55 merijn joins (~merijn@host-vr.cgnat-g.v4.dfn.nl)

All times are in UTC.