Open avishnyakov opened 4 years ago
Thanks @avishnyakov this has been on our backlog as our focus has been on PowerShellGet 3.0, but we are working to resolve this error.
Right, noted. Was not this scrum/agile thing all about drop everything and fix the broken build? 😕
@avishnyakov the build itself is not broken, they're flakey pester tests that need to be updated. But you're right, this should be addressed and we'll get to this in the immediate future. Unfortunately the CI testing for PowerShellGet needs a bit of work, but we'll need to make some changes, particulary on AppVeryor, soon so we'll certainly address this issue then.
All good. Thank you for sharing this, @alerickson.
@alerickson , could you please also comment on https://github.com/PowerShell/PowerShellGet/issues/584 "Yep, saw this" would be more than enough so we can propagate "Microsoft saw this" back to the team?
Builds been failing for 13 days and 2 months for master/development branch.
Examples: