You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
List all conflicting filenames due to case-insensitivity issues #1401
Sometimes when I'm being "lazy", I work directly from github.com. And as it doesn't like all the files in the rules folder, you can't view them easily.
Merging #1159 broke the build, so I deleted said file when I noticed. However, it doesn't tell you what the names of the conflicting files actually are
Generating sqlite DB
src/chrome/content/rules/geocaching.com.xml failed case-insensitivity testing.
Rules exist with identical case-insensitive names, which breaks some filesystems.
Forcing the unit tests to be re-run, rather than displaying a potentially old/cached/out of date test run.
My working example is at Wikimedia for MediaWiki et al, generally we rebase (via one click in gerrit) before merging, which forces one set of test runs, but then on merging, they go through the CI workflow (again), to make sure the tests all pass before actually being merged into the branch. Or, just comment "recheck" has a similar result.
It's just more because you have to go out of your way to re-run the tests via github, or like I did with this case, notice the failure popping up elsewhere. Which I was then able to quickly resolve.
Nope, I'll try having a look around. I can't imagine this would be the first project on github that would want to force a test run before the merge actually being done, even more so with potentially "stale" pull requests
Activity
reedy commentedon Apr 10, 2015
(another reason having things rebased before merging would be nice)
jsha commentedon Apr 10, 2015
Yep, spitting out conflicts sounds like a great idea!
I'm not sure how rebasing would have helped, though?
reedy commentedon Apr 11, 2015
Forcing the unit tests to be re-run, rather than displaying a potentially old/cached/out of date test run.
My working example is at Wikimedia for MediaWiki et al, generally we rebase (via one click in gerrit) before merging, which forces one set of test runs, but then on merging, they go through the CI workflow (again), to make sure the tests all pass before actually being merged into the branch. Or, just comment "recheck" has a similar result.
It's just more because you have to go out of your way to re-run the tests via github, or like I did with this case, notice the failure popping up elsewhere. Which I was then able to quickly resolve.
No big deal though :)
jsha commentedon Apr 13, 2015
That sounds great, and easy with gerrit. Do you know of any way to make it that easy with github?
reedy commentedon Apr 13, 2015
Nope, I'll try having a look around. I can't imagine this would be the first project on github that would want to force a test run before the merge actually being done, even more so with potentially "stale" pull requests