Yes, this workaround works for me, thanks!
commented on
merge request !224
"hack compat with python >= 3.11 + libfaketime"
at
Knot projects / deckard
CI here looks OK to me. Also on knot-resolver, though python >= 3.11 usage won't be common there yet, I think: https://gitlab.nic.cz/knot/knot-res...
Perhaps you could keep testing with this workaround? !224
opened
merge request
!224
"hack compat with python >= 3.11 + libfaketime"
at
Knot projects / deckard
We also see that, and I believe it's https://github.com/wolfcw/libfaketime/issues/430
commented on
merge request !223
"Detect jemalloc and do not proceed if used"
at
Knot projects / deckard
CI good now. Just the known val_nsec3_cnametocnamewctoposw.rpl
-
ee8e39ae · conftest: detect libjemalloc: test all binaries for libjemalloc, re...
- ... and 3 more commits. Compare 85e48517...ee8e39ae
commented on
merge request !223
"Detect jemalloc and do not proceed if used"
at
Knot projects / deckard
Uh, a mistake, I need to redo it 
commented on
merge request !223
"Detect jemalloc and do not proceed if used"
at
Knot projects / deckard
Done now. Ref: knot-resolver-ci!4 (merged)
-
85e48517 · conftest: detect libjemalloc: test all binaries for libjemalloc, re...
- ... and 3 more commits. Compare 807580ad...85e48517
commented on
merge request !223
"Detect jemalloc and do not proceed if used"
at
Knot projects / deckard
Ah yes, that works too.
commented on
merge request !223
"Detect jemalloc and do not proceed if used"
at
Knot projects / deckard
A directory? I thought we'd use this one and put a copy of requirements in there: https://gitlab.nic.cz/knot/knot-resolver-ci/-/tree/main/images/d...