diff options
author | Alexander Batischev <eual.jp@gmail.com> | 2021-06-13 01:45:02 +0300 |
---|---|---|
committer | Alexander Batischev <eual.jp@gmail.com> | 2021-06-13 01:45:02 +0300 |
commit | 8641c594b0d065f5000efd84d30333c2762ef74c (patch) | |
tree | ef554b000ef98a5556d31cc4276763cee10a0a2d /.gitlab-ci.yml | |
parent | 481c5d8df21c72db3a3d76e851d25426f3e40647 (diff) | |
download | obnam2-8641c594b0d065f5000efd84d30333c2762ef74c.tar.gz |
feat: restore symlink metadata
The weird thing about this commit is that all the tests for it already
exist: the subplot compares manifests of "live" and restored data, and
that includes the mtime. The subplot passes on CI, and it passed for me
too — until today.
Today, if I run `./check` on the main branch (which is currently at
481c5d8df21c72db3a3d76e851d25426f3e40647), subplot fails because the
symlinks' mtime is wrong. Most often it's just the nsec part that's
wrong: tests run fast enough that they finish within a second, and they
rarely happen at the edge of the second.
I don't understand why this didn't happen to me before, and why it
doesn't happen to CI — and to Lars, for that matter. git-bisect points
at 755c18a11f87040245964cf411ea8f518b61e0f5, which is a couple months
old, so we should've spotted the breakage by now.
Needless to say, I didn't do any major overhauls of my system lately,
just your usual `apt upgrade` (Debian bullseye/testing amd64). Did some
change in Subplot or Summain obfuscate this? It bothers me that I don't
understand how we could miss this for so long.
Diffstat (limited to '.gitlab-ci.yml')
0 files changed, 0 insertions, 0 deletions