Tests fail with git.commit.time error

[archived-2]

When running tests, it is common for several hundred of them to fail with the error:

java.time.format.DateTimeParseException: Text '${git.commit.time}' could not be parsed at index 0

at java.base/java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:2050)
	at java.base/java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1952)
	at java.base/java.time.LocalDateTime.parse(LocalDateTime.java:493)
	at org.qortal.controller.Controller.<init>(Controller.java:260)
	at org.qortal.controller.Controller.getInstance(Controller.java:280)
	at org.qortal.group.Group.addMember(Group.java:145)
	at org.qortal.group.Group.addMember(Group.java:149)
	at org.qortal.group.Group.create(Group.java:280)
	at org.qortal.transaction.CreateGroupTransaction.process(CreateGroupTransaction.java:99)
	at org.qortal.block.Block.processTransactions(Block.java:1403)
	at org.qortal.block.Block.process(Block.java:1303)
	at org.qortal.block.GenesisBlock.process(GenesisBlock.java:297)
	at org.qortal.block.BlockChain.rebuildBlockchain(BlockChain.java:553)
	at org.qortal.block.BlockChain.validate(BlockChain.java:501)
	at org.qortal.test.common.Common.resetBlockchain(Common.java:123)
	at org.qortal.test.common.Common.useSettings(Common.java:114)
	at org.qortal.test.common.Common.useDefaultSettings(Common.java:118)
	at org.qortal.test.AccountRefCacheTests.before(AccountRefCacheTests.java:30)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:564)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:157)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
	at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:33)
	at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:220)
	at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:53)

Last time I was able to solve this by pushing my remote branch to origin, but today I have seen the same problem on master.

I need to debug this further in order to understand what is happening.