Skip to content
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

Fix the renamer tests #9815

Merged
1 commit merged into from
Apr 14, 2021
Merged

Fix the renamer tests #9815

1 commit merged into from
Apr 14, 2021

Conversation

zadjii-msft
Copy link
Member

Summary of the Pull Request

Clearly, I didn't run these tests on my last commit where I made the toasts lazy-load.

References

PR Checklist

Detailed Description of the Pull Request / Additional comments

For whatever reason, these tests are unhappy running back to back, but are just fine running isolated.

@ghost ghost added Area-CodeHealth Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc. Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal. labels Apr 14, 2021
@DHowett
Copy link
Member

DHowett commented Apr 14, 2021

@msftbot merge this in 1 minute

@ghost ghost added the AutoMerge Marked for automatic merge by the bot when requirements are met label Apr 14, 2021
@ghost
Copy link

ghost commented Apr 14, 2021

Hello @DHowett!

Because you've given me some instructions on how to help merge this pull request, I'll be modifying my merge approach. Here's how I understand your requirements for merging this pull request:

  • I won't merge this pull request until after the UTC date Wed, 14 Apr 2021 17:10:54 GMT, which is in 1 minute

If this doesn't seem right to you, you can tell me to cancel these instructions and use the auto-merge policy that has been configured for this repository. Try telling me "forget everything I just told you".

@ghost ghost merged commit 4941084 into main Apr 14, 2021
@ghost ghost deleted the dev/migrie/b/9769-renamer-tests branch April 14, 2021 17:11
@zadjii-msft
Copy link
Member Author

@miniksa weren't we supposed to be getting emails when nightly helix builds failed? Wonder why we didn't get any for this particular set

mpela81 pushed a commit to mpela81/terminal that referenced this pull request Apr 17, 2021
## Summary of the Pull Request

Clearly, I didn't run these tests on my last commit where I made the toasts lazy-load.

## References
* broken in in microsoft#9662
* 
## PR Checklist
* [x] Closes microsoft#9769
* [x] I work here
* [x] Tests added/passed
* [n/a] Requires documentation to be updated

## Detailed Description of the Pull Request / Additional comments

For whatever reason, these tests are unhappy running back to back, but are just fine running isolated.
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-CodeHealth Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc. AutoMerge Marked for automatic merge by the bot when requirements are met Issue-Bug It either shouldn't be doing this or needs an investigation. Product-Terminal The new Windows Terminal.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TestWindowRename unit tests are failing
4 participants