[bengl]

Checklist

• tests and code linting passes
• a test and/or benchmark is included
• the commit message follows commit guidelines

Affected core subsystem(s)

test

Description of change

Allow running tests in subdirectories of test/parallel. Currently it only works on test/parallel, but it could be changed to work in other directories. (Done in test/testpy/__init__.py.)

Split up most tests in test/parallel into reasonable subdirectories. There are some stragglers that didn't seem to make sense in subdirs, but I'm happy to change that if desired.

Fixes: #6217 (If it's decided that this is worth doing.)

[thefourtheye]

Can you split the commit? Moving files to different directories as a commit and the Python changes necessary as another one

[jbergstroem]

@thefourtheye perhaps hold off spending extra time until there's a consensus this will should land?

[thefourtheye]

@jbergstroem Sure.

[bengl]

Yes, happy to split it up once it's decided that this should be done. (Also rebase, etc.)

[orangemocha]

Reminder to self :

• Check that the --run argument still works as intended
• Check that status files still work as intended. Might need to update instructions for marking tests as flaky.

[imyller]

Looks like a good idea, but PR and discussion has stalled.

Can we reach consensus?

/ping @bengl still interested in pushing this effort forward?

[Trott]

I don't have a strong opinion either way on this one, but I know that there are people who still feel like they deal with fallout from the move from test/simple to test/parallel and friends, so definitely try to loop them in if this does start moving again. I don't remember who it was, but it was likely a subset of indutny, bnoordhuis, and piscisaureus.

[bnoordhuis]

My beef was mostly with git log ending at commit 0e19476 all the time but that's a paper-cut issue compared to being able to run tests in parallel.

GitHub not displaying test/ correctly is a much less compelling reason to split up everything again, IMO. Report it to GH and have them fix it instead of trying to work around it.

[targos]

My beef was mostly with git log ending at commit 0e19476 all the time

Unless you are talking about the log of directories, you can do git log --follow path/to/file to get the full log of a file.

[bnoordhuis]

I know, I have log.follow set in my .gitconfig, but that only works for a single file.

[bengl]

Gonna close this since if we do it, it should probably just be redone.

[jasnell]

Fwiw, I'd still really like to see this happen