You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently added PowerShell Core CI on Windows and Ubuntu and the number of tests that I had to fix for that were surprisingly small.
Locally, I always have 9 failures for PowerShell Core (both OS) but not in AppVeyor and when running the tests in the hosted Linux agent of VSTS confirm that it is probably AppVeyor that is hiding something.
We should find out about this BEFORE we fix the tests. The tests seem to have always failed for PowerShell Core by rerunning them on an old commit from January this year, therefore this is just technical debt due to the non-existence of PowerShell Core CI before.
The tests in question are listed in #944:
P.S. Below is a snippet to run the tests in the PowerShell v2 task in VSTS:
@kalgiz If you are interested, this would be a good and important issue to look into. It would be good to find out why the tests pass in AppVeyor or find a way of making them fail. Only after we have clarity about what happens in AppVeyor, the tests should be fixed.
Uh oh!
There was an error while loading. Please reload this page.
We recently added PowerShell Core CI on Windows and Ubuntu and the number of tests that I had to fix for that were surprisingly small.


Locally, I always have 9 failures for PowerShell Core (both OS) but not in AppVeyor and when running the tests in the hosted Linux agent of VSTS confirm that it is probably AppVeyor that is hiding something.
We should find out about this BEFORE we fix the tests. The tests seem to have always failed for PowerShell Core by rerunning them on an old commit from January this year, therefore this is just technical debt due to the non-existence of PowerShell Core CI before.
The tests in question are listed in #944:
P.S. Below is a snippet to run the tests in the PowerShell v2 task in VSTS:
The text was updated successfully, but these errors were encountered: