Search
11:38:29
stassats
amelas: hi, do you have any questions?
11:46:51
amelas
I was looking at the tests after building, and I was wondering if there was any documentation for the with-test macro
11:55:09
amelas
I see a lot of tests that are :broken-on :win32
11:55:30
amelas
is there a distinction between :skipped-on and :broken-on?
12:12:20
stassats
amelas: broken-on is reported differently
12:12:38
stassats
skipped-on means it's not applicable
12:13:04
stassats
fails-on means that it can run without hosing the whole thing but doesn't work correctly
12:14:19
amelas
and is there a higher-level meaning? Should tests that are broken-on in theory be fixed?
14:58:41
flip214
I've got a docstring fix at https://github.com/phmarek/sbcl/commit/9ffa314ce37d88e9458d19ec4bd2a5f22b1711ad
15:02:25
stassats
format it and paste/mail it?
15:04:41
flip214
If you want... I thought that (once) registering that remote and then just "git remote update" and "git merge" would be easier
15:06:59
flip214
with appropriate aliases it might be ;)
17:43:03
flip214
I found some more typos... mail on the way.
17:45:46
flip214
stassats: are you planning to attend sbcl20 as well?
18:30:57
pfdietz
I had briefly considered going, but expense and time constraints prevented me.
18:33:59
flip214
pfdietz: ask Krystof about travel assistance
18:39:26
stassats
better to spend the time working on sbcl
18:40:13
stassats
BACKTRACE INTERRUPTED-CONDITION-WAIT keep intermittently failing on sb-safepoint
19:18:07
stassats
of course can't reproduce locally