Various specs fail on Windows for all Ruby versions
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 22/100
Rechercherichtung
The failing specs are listed by file and line, across spec/integration (committing_spec.rb, resolving_cherry_pick_conflict_spec.rb), spec/overcommit/git_repo_spec.rb, several spec/overcommit/hook/pre_commit specs, and replace_branch_spec.rb. Start by running one listed spec on Windows to see the actual error, since the issue gives no cause. Done when the listed specs pass on Windows and the path-handling and git-invocation differences are understood.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
At the moment of writing this Issue, these are the specs that are failing:
rspec ./spec/integration/committing_spec.rb:85 # commiting to an empty repo when a hook fails exits with a non-zero status
rspec ./spec/integration/resolving_cherry_pick_conflict_spec.rb:41 # resolving cherry-pick conflicts exits with a non-zero status
rspec ./spec/integration/resolving_cherry_pick_conflict_spec.rb:46 # resolving cherry-pick conflicts does not remove the CHERRY_PICK_HEAD file
rspec ./spec/integration/resolving_cherry_pick_conflict_spec.rb:52 # resolving cherry-pick conflicts keeps the commit message from the cherry-picked commit
rspec ./spec/overcommit/git_repo_spec.rb:218 # Overcommit::GitRepo.list_files when listing contents of a directory when directory contains a file when path contains spaces is expected to include "D:/a/_temp/d20240224-2700-ihp1yw/some-repo/some dir/file"
rspec ./spec/overcommit/hook/pre_commit/hard_tabs_spec.rb:26 # Overcommit::Hook::PreCommit::HardTabs when file contains hard tabs is expected to fail
rspec ./spec/overcommit/hook/pre_commit/local_paths_in_gemfile_spec.rb:27 # Overcommit::Hook::PreCommit::LocalPathsInGemfile when file contains a local path in Ruby 1.8 hash syntax format is expected to report a warning
rspec ./spec/overcommit/hook/pre_commit/local_paths_in_gemfile_spec.rb:33 # Overcommit::Hook::PreCommit::LocalPathsInGemfile when file contains a local path on its own line in Ruby 1.8 hash syntax format is expected to report a warning
rspec ./spec/overcommit/hook/pre_commit/local_paths_in_gemfile_spec.rb:39 # Overcommit::Hook::PreCommit::LocalPathsInGemfile when file contains a local path starting with leading spaces in Ruby 1.8 hash format is expected to report a warning
rspec ./spec/overcommit/hook/pre_commit/local_paths_in_gemfile_spec.rb:45 # Overcommit::Hook::PreCommit::LocalPathsInGemfile when file contains a local path in Ruby 1.9 hash syntax format is expected to report a warning
rspec ./spec/overcommit/hook/pre_commit/local_paths_in_gemfile_spec.rb:51 # Overcommit::Hook::PreCommit::LocalPathsInGemfile when file contains local path on its own line in Ruby 1.9 hash syntax format is expected to report a warning
rspec ./spec/overcommit/hook/pre_commit/local_paths_in_gemfile_spec.rb:57 # Overcommit::Hook::PreCommit::LocalPathsInGemfile when file contains local path starting with leading spaces in Ruby 1.9 hash format is expected to report a warning
rspec ./spec/overcommit/hook/pre_commit/merge_conflicts_spec.rb:27 # Overcommit::Hook::PreCommit::MergeConflicts when file contains a merge conflict marker is expected to fail
rspec ./spec/overcommit/hook/pre_commit/trailing_whitespace_spec.rb:26 # Overcommit::Hook::PreCommit::TrailingWhitespace when file contains trailing whitespace is expected to fail
rspec ./spec/overcommit/hook/pre_commit/trailing_whitespace_spec.rb:32 # Overcommit::Hook::PreCommit::TrailingWhitespace when file contains trailing tabs is expected to fail
rspec ./spec/overcommit/hook/prepare_commit_msg/replace_branch_spec.rb:79 # Overcommit::Hook::PrepareCommitMsg::ReplaceBranch#run when the checked out branch matches the pattern when skip_if exits with a zero status does not change the commit message
- Vorherrschende Sprache
- Ruby
- Sterne
- 4k
- Forks
- 288
- Ø Merge
- 2 T. 4 Std.
- Gemergte PRs (30 T.)
- 18
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus sds/overcommit
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
sds/overcommit#909 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 78/100
sds/overcommit#847 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 3/5 Ein halber Tag Anfängerfreundlichkeit 62/100
sds/overcommit#908 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 35/100
sds/overcommit#875 ·
Maintainer antworten meist innerhalb von 1 Tag
-
help wanted
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 18/100
sds/overcommit#869 ·
Maintainer antworten meist innerhalb von 1 Tag
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 62/100
seek4science/seek#2784 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 77/100
yosiat/panko_serializer#243 ·
-
enhancement priority: medium risk: low v1.9.0
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
davidteren/mutineer#379 ·
Maintainer antworten meist innerhalb von 2 Tagen
-
Translation tutorial: snippet crashes on chunks export and misses simple { t } entriesEvtl. vergeben @Mahdi-Hasan hat das heute übernommen. Offenresource-documentation
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
TarteelAI/quranic-universal-library#1020 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100