zfs send | zfs recv to fill the zvol on a pool that had lots of space, then set volsize, then patched it into the bhyve zone config with zonecfg, then booted

I'm building a fresh image, since there's some weirdness in the tests too, so I'll give both weirdnesses a try tomorrow.

ehh, pkg.oracle.com: Framework error: code: E_OPERATION_TIMEOUTED (28) reason: Operation too slow. Less than 1024 bytes/sec transferred the last 30 seconds

tsoome: indeed, Voyager is too far to upgrade it directly from oracle.com

I'm not on Voyager atm:D

jbk: it looks like cryptotest just failed on me because I already had dprov? that seems rude

(the second run worked, because cleanup removed the dprov I already had, which also seems rude)

sommerfeld: I saw your RFE for etags, you might also like gist.github.com/richlowe/c5ee6f81d72c9e65945a3a9151958175 (xref only supports real cscope not cscope-fast, but is easy enough to change the args around, the other tries to be smart)

richlowe: Thanks, I'll take a look.

One of the other things I'd like to share is a bringover_git for nightly.

i think that predates my work (not that i've done any crypto test work in several years)

i think i have some work to pull out the test data into separate files instead of a compiled .c file

that i'd need to finish up and throw up for review

but that's about it

oh, I thought you were mostly in there

i've done a fair amount of work in the past

to try to accompany the pkcs11 fixes i was doing

but i got essentially permanently blocked on fixing the outstanding issues there

so all that work has been stopped

jbk: the test data has already been pulled out of compiled C files

that was for the hash bits IIRC

i thought it was still there for the block ciphers

the format of the test vectors from NIST was slightly different I thought

(for block ciphers)

I guess those do remain

they were a rounding error compared to the hash tests

on an unrelated note.. is there anything that you can stick in a pipeline to throttle the output rate?

that works on illumos

mbuffer probably

yeah, mbuffer -r/-R

ahh ok

I do it sometimes to slow down my postgres backups, I'm pretty sure it works.

but I think it's fair to say nothing I've done/tried to do this week has _worked_, so maybe have bell book and candle ready

heh

i'll scrape up some chicken bones

tsoome: I'm getting tst.enum.d failures, I'm guessing that's something about your #15349?

types/tst.enum.d that is

dtrace: failed to compile script tst.enum.d: line 47: identifier redeclared: zero

looking at this more closely - how did this enum ever work?

(elements of my_enum2 all collide with my_enum)

hm

sigh.

obviously broken, but ...

oh well, obviously I have mixed it up...

fortunately, it is simple fix...

like this: code.illumos.org/c/illumos-gate/+/2654

→ CODE REVIEW 2654: 15349 dtrace should accept comma after last item in enum (fix tst.enum.d) (NEW) | illumos.org/issues/15349

Sorry I missed this in code review..