vendor: bump mountinfo to v0.3.1#727
Conversation
|
The PR from |
Unfortunately it contains some breaking changes (in names), so fix the code accordingly. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
kolyshkin
force-pushed
the
mountinfo-0.3.1
branch
from
8dc88e2 to
d53aa83
Compare
|
CI failures seem unrelated |
|
@cevich PTAL seems to be something wrong with Ubuntu images in cirrus? |
|
looking...whoa...WTH...I've never seen this before. It's not the images, it's a package that changed and is failing to upgrade during setup for some reason. These kinds of unpredictable failures are exactly why I don't like doing packaging stuffs at testing-time 😢 I think we decided to do it here since it's a low-traffic repo...and so here we are. Sheesh, I'm going to need to dig my heals in and get dirty on this one...and let me guess...all other PRs are having the same problem 😓 I'll put this at the top of my list to poke at on Monday. |
|
Note: if it is a wide-spread packaging problem, waiting and retrying the tests later is also a valid strategy. It's possible that an upstream fix is needed, I dunno yet for sure. |
|
Let me try quick/easy fix of updating images. There are a bunch of shell functions that need to be migrated anyway, to use their new shared versions. Let's see if the errors reproduce in #732 |
|
@rhatdan rebasing this once #732 merges will fix the package update failures here. Though this class of automation-problems will persist so long as package update/install is done at testing time. Plopping in freshly built images is a useful workaround (since presumably the new VM images already have many/most recent package updates). Also, FWIW, this process is now much easier than it was before. |
|
/me watching |
3 participants
Unfortunately it contains some breaking changes (in names),
so fix the code accordingly.