Redmine

FWIW: I just created a history of this issue. See the following table:

Given the recurrency of the issue I think this needs a good look for the root cause(s) of it and needs a proper, enduring solution for the observed behaviors (within the moving boundaries of the Rails framework over time).

Thanks Mischa, very useful!

I've already found the root cause, but I need to add and make more tests just to be sure that we have covered the known cases.

I'm not sure why I was not able to reproduce the issue using a functional test, so I covered this using a system test. The reported problem should be fixed now un trunk, please let me know if you find any issue.

Marius BALTEANU wrote in #note-10:

I'm not sure why I was not able to reproduce the issue using a functional test [...]

I'm not sure if it's related nor which functional test you mean, but I'm not sure at all whether any subversion repository fixture data from source:/trunk/test/fixtures/repositories/subversion_repository.dump.gz is actually used at all on Redmine CI runs given that the log entries of green builds are outputting:

svn: E155036: Please see the 'svn upgrade' command
svn: E155036: The working copy at '/var/lib/jenkins/workspace/trunk/DATABASE_ADAPTER/mysql/RUBY_VER/ruby-3.2' is too old (format 8) to work with client version '1.9.3 (r1718519)' (expects format 31). You need to upgrade the working copy first.