12:04:13 what distrubted file system on illumos in general to use? (SmartOS or in VM) 15:45:39 [illumos-gate] 18172 ZFS tests spew false negatives after 17694 -- Gordon Ross 18:47:59 [illumos-gate] 18176 nvme sctostr test fails -- Robert Mustacchi 21:34:22 so my predraft IPD 63 has some formatting glitches around double-underscore when my doc is displayed on github. I don't see this in the html generated by the asciidoc CLI python script. anyone bump into this? 21:35:30 source has: Illumos defines `LC_GLOBAL_LOCALE` as `(__global_locale())` 21:36:00 and github treats the `__` as "go italic", while the CLI doesn't treat it as special. 22:00:07 when I was using asciidoc for arm64-gate documentation, I think someone suggested (maybe a random website? maybe someone here?) that I use asciidoc and asciidoctor 22:00:41 I can't imagine how parsing _ within ` as special isn't a bug in something though. 22:33:45 found another site on github where they used +++__enter__+++ 22:44:29 and that appears to have done the trick.. 22:48:08 I wish I understood why 22:56:43 gwr: one thing you could do with tests, though I don't endorse it, is this: 1) a rule `skip_pattern` that takes a list of regular expressions of ests that would be found but should not be run (see also, the ZFS noise, a useful tool for `autotest` too). 2) the general concept of arch-specific rules, I don't know how ConfigParser allows for it, but for eg you accept rules of the form `i86pc.tests =`, `i86pc.timeout = `, and crucially 22:56:44 `i86pc.skip_pattern`. You can then do `aarch64.skip_pattern = [r'\.32$']` for the 32-bit ignorance, and can also tune things like timeouts for platform variability. With extension (the 'arch' value alone is a bit shit), that would help oxide-y environments to othat are not i86pc but are intel. 22:57:46 I say "I don't endorse it" in the sense I came up with it in the bath after wherever people last chatted about tests, and have not thought about it further :) 22:57:52 it might be great, I'll accept praise :) 23:25:46 it would also let me skip known failures easily, where a test circumstantially needs a facility not yet on illumos/arm 23:26:04 like the sleep test using dtrace in its implementation 23:56:00 [illumos-gate] 18163 Fix low-hanging 17694-discovered test bugs -- Dan McDonald