git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: Re: t7900 fails with recent debian systemd?
Date: Wed, 6 Dec 2023 17:36:12 -0500	[thread overview]
Message-ID: <20231206223612.GA650770@coredump.intra.peff.net> (raw)
In-Reply-To: <20231206223145.GA638844@coredump.intra.peff.net>

On Wed, Dec 06, 2023 at 05:31:45PM -0500, Jeff King wrote:

> I noticed t7900 failing today. The failure looks like this:
> 
>   $ ./t7900-maintenance.sh -v -i -x
>   [...]
>   + systemd-analyze verify systemd/user/git-maintenance@hourly.service
>   Unit git-maintenance@hourly.service not found.
>   error: last command exited with $?=1
>   not ok 36 - start and stop Linux/systemd maintenance
> 
> The problem started after upgrading my Debian unstable system to the
> systemd 255~rc4-2 deb. Downgrading back to 254.5-1 makes the test pass
> again.
> 
> I'm sure it's something silly with finding paths in XDG_CONFIG_HOME or
> something like that. I haven't dug further, but I thought I'd post this
> to save somebody else going through the same initial debugging. (And of
> course any wisdom or further debugging is greatly appreciated).

After stracing, it is indeed looking for:

  trash directory.t7900-maintenance/systemd/user/git-maintenance@hourly.service

but that file doesn't exist. We installed git-maintenance@hourly.timer,
and git-maintenance@.service. Is the latter supposed to be a wildcard of
some kind? Maybe the rules changed. I don't really know anything about
systemd.

-Peff

  reply	other threads:[~2023-12-06 22:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 22:31 t7900 fails with recent debian systemd? Jeff King
2023-12-06 22:36 ` Jeff King [this message]
2023-12-06 22:40   ` Eric Sunshine
2023-12-07  6:27     ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231206223612.GA650770@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).