Yu Watanabe
Yu Watanabe
> Another different failure on Debian in https://github.com/systemd/systemd/actions/runs/9011374536/job/24758890861: > > ``` > gh run download 9013386982 --name ci-mkosi-9013386982-1-centos-9-failed-test-journals -D ci/ci-mkosi-9013386982-1-centos-9-failed-test-journals && journalctl --file ci/ci-mkosi-9013386982-1-centos-9-failed-test-journals/test/journal/TEST-46-HOMED.journal --no-hostname -o short-monotonic -u testsuite-46.service -p...
Thank you for the report. Fix is waiting in #32741.
Still failed. https://github.com/systemd/systemd/actions/runs/9142982772/job/25139145741?pr=32911 ``` [ 12.880974] TEST-60-MOUNT-RATELIMIT.sh[501]: + timeout 2m bash -c 'until journalctl -u init.scope --since=23:16:32 | grep -q '\''(mount-monitor-dispatch) entered rate limit'\''; do journalctl --sync; sleep 1; done'...
Ugh, I cannot download the journal. Could you provide another one?
Ah, 1e869a5de9063dfe6afac52bffc7c9c2d206b096 makes reloading synchronous only for state transition 'configured' -> 'initialized' or so. And .network file and drop-in files may not be assigned to the interface yet. I will...
So, I may misunderstand how Redirect message should be handled. If running with accept_ra=2, how kernel handles Redirect messages? What kind of entry is added to handle the subsequent echo...
@YHNdnzj Thank you! All comments are addressed. PTAL.
This is mostly ready for review, except for missing test cases for the new feature.
> Hmm, is this still targeting v256? No, unless someone strongly wants to push this to v256.