Newest at the top
| 2024-04-29 23:14:03 +0200 | cashew | (~cashewsta@65.17.175.150) |
| 2024-04-29 23:12:45 +0200 | <tomsmeding> | does it spin infinitely on one case or does it progress super slowly |
| 2024-04-29 23:12:15 +0200 | <shapr> | heh, ok |
| 2024-04-29 23:12:12 +0200 | <tomsmeding> | at least then you know what you're getting :p |
| 2024-04-29 23:12:07 +0200 | <tomsmeding> | try `cabal run nofib-accelerate -f nofib --enable-coverage` |
| 2024-04-29 23:11:47 +0200 | <tomsmeding> | can `cabal test` die |
| 2024-04-29 23:11:45 +0200 | <tomsmeding> | it doesn't even write the file until it's done? |
| 2024-04-29 23:11:44 +0200 | <shapr> | I can re-run with --test-show-details=direct if you want |
| 2024-04-29 23:11:33 +0200 | <shapr> | so either it's not writing to the file, or it writes at the end |
| 2024-04-29 23:11:25 +0200 | <shapr> | doctest.log is the only file |
| 2024-04-29 23:10:58 +0200 | <tomsmeding> | find dist-newstyle/ -name '*-test.log' |
| 2024-04-29 23:10:45 +0200 | andrewboltachev | (~andrewbol@178.141.238.156) (Quit: Client closed) |
| 2024-04-29 23:10:43 +0200 | <tomsmeding> | dist-newstyle/build/.../test/*-test.log |
| 2024-04-29 23:10:34 +0200 | <shapr> | oh |
| 2024-04-29 23:10:27 +0200 | <tomsmeding> | at it prints the log location when it's done |
| 2024-04-29 23:10:24 +0200 | shapr | shrugs |
| 2024-04-29 23:10:19 +0200 | tomsmeding | hates cabal test even more |
| 2024-04-29 23:09:38 +0200 | <shapr> | and that one passed quickly |
| 2024-04-29 23:09:34 +0200 | <shapr> | I only see that for doctest |
| 2024-04-29 23:08:39 +0200 | <tomsmeding> | doesn't `cabal test` say something like "writing output to XXX.log"? |
| 2024-04-29 23:08:25 +0200 | <shapr> | where's the log file? |
| 2024-04-29 23:08:13 +0200 | <tomsmeding> | send me the log file if you will |
| 2024-04-29 23:08:01 +0200 | <shapr> | I might as well kill it, it won't help me get closer to my goal |
| 2024-04-29 23:07:54 +0200 | <tomsmeding> | I guess it might print to the log file |
| 2024-04-29 23:07:41 +0200 | <shapr> | I don't actually want to know what it's doing, I want the coverage info |
| 2024-04-29 23:07:38 +0200 | <tomsmeding> | for one reason -- this one |
| 2024-04-29 23:07:33 +0200 | <tomsmeding> | I despise `cabal test` |
| 2024-04-29 23:07:30 +0200 | <shapr> | I know about --test-show-details=direct but I was hoping it would just do the thing :-) |
| 2024-04-29 23:07:21 +0200 | <shapr> | haha |
| 2024-04-29 23:07:19 +0200 | <tomsmeding> | classic beginner mistake |
| 2024-04-29 23:07:18 +0200 | <shapr> | memory did increase from 30GB ram to 60GB ram in the past hour |
| 2024-04-29 23:07:16 +0200 | <tomsmeding> | are you running `cabal test` without `--test-show-details=direct` |
| 2024-04-29 23:07:01 +0200 | <shapr> | it's not printing anything to stdout, I don't know |
| 2024-04-29 23:07:01 +0200 | <tomsmeding> | did that change in the past hour |
| 2024-04-29 23:06:51 +0200 | <tomsmeding> | what's the case it's currently doing |
| 2024-04-29 23:06:50 +0200 | <shapr> | it hasn't increased memory usage |
| 2024-04-29 23:06:42 +0200 | <shapr> | I can't tell |
| 2024-04-29 23:06:22 +0200 | <tomsmeding> | is it progressing, or has it stalled somewhere? |
| 2024-04-29 23:06:05 +0200 | <shapr> | I dunno |
| 2024-04-29 23:06:02 +0200 | <shapr> | it's at three hours five minutes |
| 2024-04-29 23:06:00 +0200 | <tomsmeding> | this feels like a bug in coverage tracking |
| 2024-04-29 23:05:47 +0200 | <shapr> | I require coverage info for kudzu, that's what got me here |
| 2024-04-29 23:05:46 +0200 | <tomsmeding> | shapr: yes |
| 2024-04-29 23:05:41 +0200 | <tomsmeding> | it didn't even finish the third case in the time I previously did the whole suite |
| 2024-04-29 23:05:17 +0200 | <tomsmeding> | there's your problem for sure |
| 2024-04-29 23:05:07 +0200 | <tomsmeding> | bajeezus nofib-interpreter has just finished building and started executing with --enable-coverage and this is at least 1e4 times slower |
| 2024-04-29 23:04:49 +0200 | <shapr> | because it shows you how few paths are executed? |
| 2024-04-29 23:04:39 +0200 | <shapr> | how so? |
| 2024-04-29 23:04:33 +0200 | <tomsmeding> | but path-sensitive coverage tracking, while more accurate, is very depressing to test with |
| 2024-04-29 23:04:14 +0200 | <tomsmeding> | sure, path-insensitive coverage tracking is overly optimistic, that's known |