-
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tests: investigate testdriver race #1104
Comments
leitzler
added a commit
that referenced
this issue
Sep 12, 2021
With #1101 a data race was accidentally introduced where the global testsetup.VimCommand was overwritten. We now make a local copy that is modified instead. Fixing this revealed that #1101 wasn't enough. Testscript conditions that matches a vim version also used the testscript subcommand instead of real vim. It now uses the real vim. Closes #1104
leitzler
added a commit
that referenced
this issue
Sep 13, 2021
With #1101 a data race was accidentally introduced where the global testsetup.VimCommand was overwritten. We now make a local copy that is modified instead. Fixing this revealed that #1101 wasn't enough. Testscript conditions that matches a vim version also used the testscript subcommand instead of real vim. It now uses the real vim. Closes #1104
leitzler
added a commit
that referenced
this issue
Sep 14, 2021
With #1101 a data race was accidentally introduced where the global testsetup.VimCommand was overwritten. We now make a local copy that is modified instead. Fixing this revealed that #1101 wasn't enough. Testscript conditions that matches a vim version also used the testscript subcommand instead of real vim. It now uses the real vim. Closes #1104
leitzler
added a commit
that referenced
this issue
Sep 15, 2021
With #1101 a data race was accidentally introduced where the global testsetup.VimCommand was overwritten. We now make a local copy that is modified instead. Fixing this revealed that #1101 wasn't enough. Testscript conditions that matches a vim version also used the testscript subcommand instead of real vim. It now uses the real vim. Closes #1104
leitzler
added a commit
that referenced
this issue
Sep 19, 2021
With #1101 a data race was accidentally introduced where the global testsetup.VimCommand was overwritten. We now make a local copy that is modified instead. Fixing this revealed that #1101 wasn't enough. Testscript conditions that matches a vim version also used the testscript subcommand instead of real vim. It now uses the real vim. Closes #1104
leitzler
added a commit
that referenced
this issue
Sep 20, 2021
With #1101 a data race was accidentally introduced where the global testsetup.VimCommand was overwritten. We now make a local copy that is modified instead. Fixing this revealed that #1101 wasn't enough. Testscript conditions that matches a vim version also used the testscript subcommand instead of real vim. It now uses the real vim. Closes #1104
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Two recent failed test:
Example:
The text was updated successfully, but these errors were encountered: