On Sun, Mar 09, 2025 at 06:09:24PM +0100, Johannes Kastl wrote:
> I need to check the test output more thorougly, but what I noticed the
> most errors are like this:
> 
> > --- /tmp/got-test-commit_logmsg_ref-wRvjHlc3Cx/stdout.expected  2025-03-09 17:51:18.666666620 +0100
> > +++ /tmp/got-test-commit_logmsg_ref-wRvjHlc3Cx/stdout   2025-03-09 17:51:18.683333287 +0100
> > @@ -1,7 +1,7 @@
> >  -----------------------------------------------
> >  cherrypick e9fc3edb034bb18912e4c3372a7fef0d42f1e167 (newbranch)
> >  from: Flan Hacker <flan_hacker@openbsd.org>
> > -date: Sun Mar  9 17:51:18 2025 UTC
> > +date: Sun Mar  9 16:51:18 2025 UTC
> >   
> >   changes to cherrypick but omit from the commit
> >   
> > test failed; leaving test data in /tmp/got-test-commit_logmsg_ref-wRvjHlc3Cx
> 
> Any idea how to fix those? Is there documentation on the tests so I
> can RTFM myself?
 
The tests are shell scripts which are fairly self-documenting. They
shouldn't be too difficult to read and tweak.
It might need some getting used to initially but there is not a lot of
varation. Once you've read and understood a few basic test cases it
shouldn't be too hard to add your own debug prints / set -x tweaks to
see where things are going off the rails.

Regarding the failure, it looks like 'git commit' and 'git show' are in
disagreement with 'date -u' about the current hour of UTC on your machine.
How could that be?