-
Notifications
You must be signed in to change notification settings - Fork 188
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
Fixing the CI build #183
Fixing the CI build #183
Conversation
Pester was failing to save its output because the output directory didn't exist. Without that, it couldn't actually publish the results.
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
Since the UT's are all modifying the shared state of the same test GitHub account, they end up stomping over each other and causing erroneous failures. These jobs therefore need to unfortunately run in series instead of parallel.
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @HowardWolosky, in |
Looking back at Run #20200527.1, the Running this test locally, it also fails for me. Looking at the html output, GitHub have changed the html, including the icon drawn by the htmlOutput hardcoded in GitHubContents.tests.ps1:
htmlOutput from GitHub today:
|
Thanks @X-Guardian. Hey @Shazwazza -- it looks like the brittleness of these tests is showing its head again. Are you still planning on working on the API to set Contents? |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
… a number of test failures
A typo in the pipeline passing of the organizationName resulted in the tests not getting a value for the organization name. I think this next run is going to be successful. |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run PowerShellForGitHub-CI |
Azure Pipelines successfully started running 1 pipeline(s). |
There were a number of issues going on:
v4.10.1
for the install because5.0
was just released andhas some breaking changes to investigate.
didn't exist. Without that, it couldn't actually publish the results.
ciOrganizationName
pipeline variable had a typo in it, which meantthat we were passing an empty string as the
OrganizationName
to teststhat needed it
Tests/Config/Settings.ps1
so that the hash generated on all platforms (Windows/mac/Linux) would be
the same.
two RepositoryContents tests to fail.
unit tests serially instead of in parallel, because they each modify the shared
state of the same account, and when running at the same time they were
stomping over each other and causing erroneous failures.
Resolves #182