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
@palladiahttps://github.com/palladia you have the same tests failinghttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fci.appveyor.com%2fproject%2fPowerShell%2fpowershell-linux%2fbuild%2f1.0.160%23L2521&data=01%7c01%7cv-geflem%40microsoft.com%7cf840eee37a2941ceb33108d32e835b6b%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=t2cvCQWWR9rF6wg60hLYLZ1bnoJh6kEtH%2fcyGRJ1V8o%3d.
Do you have zero failing locally?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/488#issuecomment-180618442.
@palladiahttps://github.com/palladia you have the same tests failinghttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fci.appveyor.com%2fproject%2fPowerShell%2fpowershell-linux%2fbuild%2f1.0.160%23L2521&data=01%7c01%7cv-geflem%40microsoft.com%7cf840eee37a2941ceb33108d32e835b6b%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=t2cvCQWWR9rF6wg60hLYLZ1bnoJh6kEtH%2fcyGRJ1V8o%3d.
Do you have zero failing locally?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/488#issuecomment-180618442.
You need to figure out how to view the AppVeyor results.
There are consistently just shy of 40 tests failing with the error "The handle is invalid" as documented in this issue, and I don't believe we can fix this without some serious work in the host, which should probably not happen because of this comment.
On my Windows CoreCLR build, I get no error if I run the powershell command from "cmd", but same 36 errors if I run from the git-bash shell.
So I been testing using the git-bash shell, and I see this interesting dump:
$ ./bin/powershell.exe --noprofile -c "gcm"
Unhandled Exception: System.Management.Automation.CmdletInvocationException: The handle is invalid ---> System.IO.IOException: The handle is invalid
at System.ConsolePal.GetBufferInfo(Boolean throwOnNoConsole, Boolean& succeeded)
at System.Console.get_BufferWidth()
at Microsoft.PowerShell.Linux.Host.MyRawUserInterface.get_BufferSize()
at System.Management.Automation.Internal.Host.InternalHostRawUserInterface.get_BufferSize()
at Microsoft.PowerShell.Commands.Internal.Format.ConsoleLineOutput.get_ColumnNumber()
at Microsoft.PowerShell.Commands.Internal.Format.ConsoleLineOutput.WriteLine(String s)
at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessFormatStart(OutputContext c)
at Microsoft.PowerShell.Commands.Internal.Format.FormatMessagesContextManager.Process(Object o)
at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessObject(PSObject so)
at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessRecord()
at Microsoft.PowerShell.Commands.Internal.Format.FrontEndCommandBase.ProcessRecord()
at System.Management.Automation.Cmdlet.DoProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
at System.Management.Automation.Runspaces.Pipeline.Invoke()
at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
at Microsoft.PowerShell.Linux.Host.Listener.ExecuteHelper(String cmd, Object input)
at Microsoft.PowerShell.Linux.Host.Listener..ctor(String initialScript, Boolean loadProfiles)
at Microsoft.PowerShell.Linux.Host.Program.Main(String[] args)
v-geflem@MININT-88MISUS MINGW64 ~/Desktop/test/PowerShell (master)
Activity
[-]FIx 38 failing Windows tests[/-][+]Fix 38 failing Windows tests[/+]andyleejordan commentedon Feb 5, 2016
36 of these don't fail locally. Only two fail with
.\bin\powershell.exe --noprofile -c "invoke-pester test/powershell".andyleejordan commentedon Feb 5, 2016
I think we still need to solve the interactivity problem, which we may want to put off until after #495.
palladia commentedon Feb 5, 2016
See my PR
andyleejordan commentedon Feb 5, 2016
George Fleming (@palladia) you have the same tests failing.
Do you have zero failing locally?
palladia commentedon Feb 5, 2016
I am getting no failure on both Windows and Linux.
From: Andy Schwartzmeyer [mailto:notifications@github.com]
Sent: Friday, February 5, 2016 3:23 PM
To: PowerShell/PowerShell PowerShell@noreply.github.com
Cc: George Fleming (Insight Global) v-geflem@microsoft.com
Subject: Re: [PowerShell] Fix 38 failing Windows tests (#488)
@palladiahttps://github.com/palladia you have the same tests failinghttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fci.appveyor.com%2fproject%2fPowerShell%2fpowershell-linux%2fbuild%2f1.0.160%23L2521&data=01%7c01%7cv-geflem%40microsoft.com%7cf840eee37a2941ceb33108d32e835b6b%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=t2cvCQWWR9rF6wg60hLYLZ1bnoJh6kEtH%2fcyGRJ1V8o%3d.
Do you have zero failing locally?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/488#issuecomment-180618442.
palladia commentedon Feb 5, 2016
Can’t see your failures, as I have no AppVeyor access.
From: Andy Schwartzmeyer [mailto:notifications@github.com]
Sent: Friday, February 5, 2016 3:23 PM
To: PowerShell/PowerShell PowerShell@noreply.github.com
Cc: George Fleming (Insight Global) v-geflem@microsoft.com
Subject: Re: [PowerShell] Fix 38 failing Windows tests (#488)
@palladiahttps://github.com/palladia you have the same tests failinghttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fci.appveyor.com%2fproject%2fPowerShell%2fpowershell-linux%2fbuild%2f1.0.160%23L2521&data=01%7c01%7cv-geflem%40microsoft.com%7cf840eee37a2941ceb33108d32e835b6b%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=t2cvCQWWR9rF6wg60hLYLZ1bnoJh6kEtH%2fcyGRJ1V8o%3d.
Do you have zero failing locally?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/488#issuecomment-180618442.
andyleejordan commentedon Feb 5, 2016
Yes you do. You need to login to AppVeyor with your GitHub account and choose the PowerShell organization.
palladia commentedon Feb 5, 2016
Logged in, but haven’t figured out how to add PowerShell org. Which tests were failing?
From: Andy Schwartzmeyer [mailto:notifications@github.com]
Sent: Friday, February 5, 2016 3:36 PM
To: PowerShell/PowerShell PowerShell@noreply.github.com
Cc: George Fleming (Insight Global) v-geflem@microsoft.com
Subject: Re: [PowerShell] Fix 38 failing Windows tests (#488)
Yes you do. You need to login to AppVeyor with your GitHub account and choose the PowerShell organization.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/488#issuecomment-180622737.
andyleejordan commentedon Feb 5, 2016
You need to figure out how to view the AppVeyor results.
There are consistently just shy of 40 tests failing with the error "The handle is invalid" as documented in this issue, and I don't believe we can fix this without some serious work in the host, which should probably not happen because of this comment.
[-]Fix 38 failing Windows tests[/-][+]Fix 38 failing AppVeyor tests[/+]palladia commentedon Feb 11, 2016
On my Windows CoreCLR build, I get no error if I run the powershell command from "cmd", but same 36 errors if I run from the git-bash shell.
So I been testing using the git-bash shell, and I see this interesting dump:
andyleejordan commentedon Feb 11, 2016
This sample is where our entire host implemenation came from.
andyleejordan commentedon Feb 11, 2016
George Fleming (@palladia) I edited your comment so that GitHub recognizes the issue reference.