RefreshVersionsUpgradeMigrationTest fails on windows
See original GitHub issue- I have read the guidelines for submitting issues
🐛 Describe the bug
Emil Kantis has the RefreshVersionsUpgradeMigrationTest
tests failing on windows on the main branch.
It’s maybe a line-ending issue, windows vs Unix
📱 Tech info
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
jmfayard/refreshVersions: Life is too short to google ... - GitHub
refreshVersions helps Gradle users with the tedious manual work usually involved in adding and updating dependencies and their versions.
Read more >Change Log - gradle refreshVersions - GitHub Pages
The migration will be done automatically on upgrade of refreshVersions, without upgrading the versions of androidx.tests dependencies themselves.
Read more >Found conflicts between different versions of 'assembly' that ...
This error occurs during a build when more than one version of the same dependent assembly is referenced in a build of the...
Read more >Change log for 4.8.52
Kubernetes upgraded from 1.20.0-beta.2 to 1.21.11 ... Fix windows NodePublish failing because mount target doesn't exist #1081 ...
Read more >Gradle migration - Development - Image.sc Forum
For instance, the Maven-based build was configured to fail on javac warnings, and I missed this setting when migrating to Gradle.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Found the culprit, it was as you suggested, I added a proper
.gitattributes
file to ensure the line endings are kept inLF
except for the.bat
files (i.e. for the Windows Gradle wrapper).Thank you.
Found a workaround for the file path length issue, however, I am unable to see the exact failure reason through the logs or through the Gradle scan:
https://scans.gradle.com/s/sinfl72i4iliw/tests/:refreshVersions:test/de.fayard.refreshVersions.migration.upgrade.RefreshVersionsUpgradeMigrationTest/test removal of migration call for Gradle Groovy DSL()?top-execution=1
I copied the two but the diff window in my IDE tells me they are the same.
@Kantis Can you run the test locally on your Windows machine (with the latestmain
branch), then open the difference in a diff window (there should be a clickable “link” in the test failure logs for that), screenshot that and post it here so I can see what the mismatch is about? That’d be very helpful.