-
Notifications
You must be signed in to change notification settings - Fork 225
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
SqlServerDsc: Attempt to mitigate issue #1260 #1268
Conversation
- Reverting the change that was made as part of the issue dsccommunity#1260 in the previous release, as it only mitigated the issue, it did not solve the issue.
- Updated the integration test to stop the named instance while installing the other instances to mitigate issue dsccommunity#1260.
Codecov Report
@@ Coverage Diff @@
## dev #1268 +/- ##
====================================
- Coverage 98% 97% -1%
====================================
Files 34 34
Lines 4197 4197
====================================
- Hits 4137 4106 -31
- Misses 60 91 +31 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 3 of 4 files at r1.
Reviewable status: 3 of 4 files reviewed, 2 unresolved discussions
Tests/Integration/MSFT_SqlSetup.config.ps1, line 415 at r1 (raw file):
'StopSqlServer
Should be 'Star...' here
Tests/Integration/MSFT_SqlSetup.Integration.Tests.ps1, line 651 at r1 (raw file):
catch { Write-Verbose -Message ('{0} {1}' -f $integrationErrorMessagePrefix, $_) -Verbose
We should not need this anymore, since laster Pester release. Throughout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 2 of 4 files reviewed, all discussions resolved (waiting on @johlju)
Tests/Integration/MSFT_SqlSetup.config.ps1, line 415 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
'StopSqlServer
Should be 'Star...' here
Done
Tests/Integration/MSFT_SqlSetup.Integration.Tests.ps1, line 651 at r1 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
We should not need this anymore, since laster Pester release. Throughout.
Done
6919390
to
ff21cbc
Compare
b4f37e7
to
6375da4
Compare
Closing this PR as this does not solve the problem. Will try to use parallel testing to solve this issue instead. |
- Clean up error handling in some of the integration tests that was part of a workaround for a bug in Pester. The bug is resolved, and the error handling is not again built into Pester.
Reopening and have switch testing to parallel testing (or sequentially on free AppVeyor accounts). |
Really strange that the code coverage in the build is missing rows, but it doesn't when running code coverage locally. 🤔 I will ignore it for now, it's a problem for another day (another PR). 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 47 of 48 files at r3, 2 of 2 files at r4.
Reviewable status: all files reviewed, 2 unresolved discussions
Tests/Integration/MSFT_SqlSetup.config.ps1, line 46 at r4 (raw file):
# Properties for mounting media ImagePath = "$env:TEMP\SQL2016.iso" #ImagePathServicePack = "$env:TEMP\SqlUpdates\SQLServer2016SP2-KB4052908-x64-ENU.exe"
We should remove this commented code
Tests/Integration/MSFT_SqlSetup.Integration.Tests.ps1, line 125 at r4 (raw file):
has hash
maybe switch to SHA1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 47 of 49 files reviewed, all discussions resolved (waiting on @johlju)
Tests/Integration/MSFT_SqlSetup.config.ps1, line 46 at r4 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
We should remove this commented code
Done
Tests/Integration/MSFT_SqlSetup.Integration.Tests.ps1, line 125 at r4 (raw file):
Previously, johlju (Johan Ljunggren) wrote…
has hash
maybe switch to SHA1
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 2 files at r5.
Reviewable status: complete! all files reviewed, all discussions resolved
Pull Request (PR) description
in the previous release, as it only mitigated the issue, it did not
solve the issue.
possible due to using excessive amount of memory on the AppVeyor build
worker. This will make the unit tests to take a bit longer to run.
(issue #1260).
build workers in AppVeyor. One build worker runs the integration tests,
while a second build worker runs the unit tests. The build workers runs
in parallel on paid accounts, but sequentially on free accounts.
(issue #1260).
part of a workaround for a bug in Pester. The bug is resolved, and
the error handling is not again built into Pester.
the other instances to mitigate issue SqlServerDsc: Integration tests fail to install instance #1260.
This Pull Request (PR) fixes the following issues
Attempt to mitigate issue #1260
Task list
Entry should say what was changed, and how that affects users (if applicable).
and comment-based help.
This change is