CI Issues

[kayoub5]

@chmorgan could you look into those?

• Travis jobs no longer running
• Azure jobs always failing with No hosted parallelism has been purchased or granted. To request a free parallelism grant, please fill out the following form https://aka.ms/azpipelines-parallelism-request
• Some CI jobs fail to find coverage files, the failure is always silent and not visible in GitHub status, possibly a missing token configuration.
  Possibly caused by https://docs.codecov.com/docs/about-the-codecov-bash-uploader

[chmorgan]

@kayoub5 travis is saying I've exceeded my monthly unique users. But it also says I have an unlimited unique users plan for free.

I'd be ok if we dropped travis. Their credits are very limited and the builds are relatively slow.

Thoughts?

[kayoub5]

@chmorgan their plus side is ARM support, we just need one CI job for ARM from Travis, that way we keep the quote to a minimum.

[chmorgan]

@kayoub5 I can't figure out how to restore the travis-ci build. It looks like all of their plans are paid now.

[chmorgan]

let me open an issue with them, their service frankly has had a number of glitches and issues, maybe they can fix it.

[chmorgan]

@kayoub5 travis is looking for a credit card to sign up for their free plan. I told them we'd likely pass since we have other CI providers and I'm not particularly interested in providing a credit card for what they say is a free plan. We'll see if their support person will respond.

[kayoub5]

Travis would be interesting for testing that library works on arm architecture, otherwise existing ci providers cover what we need.

[chmorgan]

@kayoub5 oh right, it was that travis needed a credit card for the OSS plan

[chmorgan]

@kayoub5 I confirmed the credentials are working for npcap. Not sure what could have broken... still looking

[chmorgan]

@kayoub5 maybe its the tls switchover that broke it?

https://devblogs.microsoft.com/devops/deprecating-weak-cryptographic-standards-tls-1-0-and-1-1-in-azure-devops-services/

[kayoub5]

@kayoub5 maybe its the tls switchover that broke it?

https://devblogs.microsoft.com/devops/deprecating-weak-cryptographic-standards-tls-1-0-and-1-1-in-azure-devops-services/

CI logs does not say anything HTTPS or cryptographic related, it's simply failing to provide npcap server with correct credentials during download step.