#codecov — Public Fediverse posts

Ah, the eternal battle against #Skynet continues! 🤖 In a world where developers beg #codecov to save them from the #AI #apocalypse, one wonders if these heroes still haven’t found the off switch on their #Roombas. 🧹 Cower in fear as GitHub's "Copilot" becomes the overlord of your keyboard! ⌨️
https://github.com/codecov/feedback/issues/740 #GitHub #Copilot #HackerNews #ngated

Please add an option to block or disable "AI" · Issue #740 · codecov/feedback

https://github.com/codecov/feedback/issues/740

#HackerNews #AI #Block #Option #Codecov #Feedback #GitHub #Issue #Discussion

Ich habe die letzten Tage versucht zu #Codeberg umzuziehen. Grundsätzlich kein Problem, außer man möchte so lieb gewonnen Funktionen wie die Anbindung an #Codecov nutzen.
Der Umzug zu Codeberg wird hier in letzter Zeit immer wieder unter dem #unplugtrump Tag propagiert, aber so ganz passt das für mich nicht.
Ich nutze #Github kostenlos.
Das Repo ist öffentlich.
Ich nutze Ressourcen, die Github anbietet und "schädige" damit letztlich #Microsoft.
Warum sollte ich woanders hin umziehen?

We're slowly increasing the test coverage of the #fwupd project. This is really hard, as we're dealing with hardware and probably 25% of the code is for error handling -- some of which might be impossible to hit in reality.

That said, there's a huge amount of code we can test, and we've proactively found real bugs and a lots of niggles. #codecov is useful to work out what to focus on next: https://app.codecov.io/gh/fwupd/fwupd

My 2025 aim is 60% coverage, but it could be a long time to get there. :)

#rstats #testthat #codecov
Edit: uploading results from the different runners worked! I was just impatient.

Question

I have a function that has different behavior on Windows and (MacOS/Linux). I have tests that correctly check all of this (using testthat::skip_on_os() ). Everything is working as intended.

But when I run my CI checks, codecov marks the “windows” lines as untested. My naive solution of running the codecov action on a windows runner is also not solving it.

Any suggestions?

Just integrated my #CommonLisp project (euler-cl) with #Codecov ! Now I can see test coverage trends and enjoy a sweet badge 🙌

My setup will hopefully help others integrate Codecov (and maybe more!) into their CL projects. To get started take a look at this commit in particular: https://github.com/bahmanm/euler-cl/commit/855b014

I'd be happy to help you get your project integrated 🙋‍♂️

#Programming #DevOps #CICD #Testing #Lisp #Perl #Makefile

Oh, I'm this 🤏 close to finishing up my work to convert #SBCL test coverage reports (`sb-cover:report`) to a format understandable by #Codecov 🕺

That would mean, to say the least, I can have test coverage report badges for my #CommonLisp projects on Github 🤤

Stay tuned 📻

Does someone know a #jekyll plugin to render #codecov compatible #json ?

:boost_ok:

So satisfying to finally reach 100% code coverage for testing!

Hoping to publish paper on Comodo by the end of the year. If you are into #ComputationalMechanics #Biomechanics #GeometryProcessing #FiniteElementAnalysis help to contribute to Comodo.jl and FEBio.jl and you'll be one of the authors!

https://github.com/COMODO-research/Comodo.jl

#julialang #opensource #ContinuousIntegration #CodeCov

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

Here we go. S1E1!

Chad Whitacre is head of open source at Sentry, an application and performance monitoring software maker that moved to a business source license for its products in 2019, and then to a functional source license in November 2023. In this episode, he discusses the #tragedyofthecommons vs #enclosure, open source vs open products, #BSL vs #FSL and the story of "The #Codecov kerfuffle." #OSS #softwarecommons #opensource #opensourcesustainability #podcast

https://itopsquery.podbean.com/e/chad-whitacre-sentry/

Victory!

I got #Codecov working with a #Prolog project. Now I get code coverage reports as part of the pipeline.

Next is documenting the process for interested folks...

#CICD #DevOps #CircleCI

I'll be tackling a little #Prolog puzzle today - building a #Perl module to make SWI-Prolog's coverage reports play nice with #Codecov.

Improving my #CICD and #DevOps game!

https://github.com/bahmanm/prolog-etudes/pull/7/files

I do not understand this patch coverage report from #Codecov for a pull request for #PHPUnit.

It says at the top that code coverage decreases by 0.06% overall, but the code coverage of the individual files increases.

What am I missing?

Anyone experiencing issue with #codecov ?
Their #dotnet #tool only supports #netcore 2.1, 3.1 and #dotnet5 (all currently out of support) and since linux #github agent only has #dotnet6 and #dotnet7 sdks.
Anyone out there with a better option than installing a deprecated sdk ?
I'm using #nuke and would very much like not to have to customize the generated YAML file.

The project : github.com/candoumbe/candoumbe.types

#opensource

#Sentry mnie bardzo denerwuje.

Dawno temu używałem #CodeCov w swoich projektach. Nie było zbyt dobre, więc usunąłem konto.

Mimo to wciąż dostawałem maile o aktualizacji regulaminu. No więc w końcu wysłałem do nich żądanie #RODO, żeby usunęli moje dane osobowe. Szybko odpowiedzieli i orzekli, że dane zostały usunięte.

Dlaczego więc *znowu* dostaję maila o aktualizacji regulaminu, który nie powinien w ogóle mnie dotyczyć, na adres e-mail, który rzekomo usunięto?!

I'm really getting annoyed by #Sentry.

Long time ago, I've used #CodeCov for my projects. But it wasn't very good, so I've removed my account.

Nevertheless, I kept getting e-mails about ToS updates. So I've finally send a nice #GDPR request to have my data removed. They promptly replied and claimed to have had it all purged.

So why am I *still* receiving e-mails on updates to ToS that shouldn't apply to me, to an e-mail address that they have supposedly purged?!

An additional article was also helpful in setting up #coverage without #CodeCov on #GitHub. This outlined some useful details in the recent changes GitHub made in some of the versioning in their actions. Very well written.

https://hynek.me/articles/ditch-codecov-python/

#python

Helpful article in setting up a #GitHub #coverage badge without using 3rd-party #CodeCov. I was able to adapt the instructions using #nox instead of tox as outlined in the link. Good stuff, Maynard.

https://nedbatchelder.com/blog/202209/making_a_coverage_badge.html
#python

Anyone knows how to have two different #codecov reports for the same GitHub repo?

I'd like to generate code coverage reports for both the #Python and the #RStats implementation in https://github.com/HenrikBengtsson/port4me and have the listed at https://app.codecov.io/gh/HenrikBengtsson/port4me.

Does CodeCov.io support subfolders, merging codecov estimates, or something?

It is rather ironic when your code coverage for testing complains about not reaching the part of your algorithm that you marked in rust as `unreachable!()`.

#codecov #rust

Thank you #codecov for sponsoring me on GitHub Sponsors: https://github.com/sponsors/WyriHaximus

Automatic code coverage analysis has proven valuable when integrated with the CI pipeline. It can notify you automatically if your changes are about to drop the coverage.

Monitoring total coverage is the most helpful; patch coverage tends to report too many false positives.

#codecov #githubactions

Fighting #Codecov in a PR that shouldn't have any coverage impact. Even tried cheating by adding a new test (which increases coverage locally) but it didn't work.

https://github.com/tonybaloney/wily/pull/211

#codecov has withdrew its position on #opensource matter. They have admitted their mistake and also made amends by retracting all false advertising. The case is closed.

#Codecov admits their mistake in their recent #OpenSource announcement.

https://blog.sentry.io/lets-talk-about-open-source/

Code Coverage Tool 'Codecov' Goes Open Source

#codecov #foss

https://news.itsfoss.com/codecov-open-source/?utm_medium=erik.in&utm_source=mastodon

How the hell #lobsters has fraudulent article on the first page? Yeah I'm talking about #codecov and their lies about being open-source.

I receive e-mail, '#Codecov is now #OpenSource':

🙂

I read linked article:

🙁

Seriously?

#openwashing

Did someone say open-washing?

"Codecov is now open source"

https://about.codecov.io/blog/codecov-is-now-open-source/

'The Business Source License (this document, or the "License") is not an Open Source license. However, the Licensed Work will eventually be made available under an Open Source License, as stated in this License.'

https://github.com/codecov/codecov-api/blob/main/LICENSE

🤔
https://github.com/codecov/feedback/issues/48 #codecov #OpenWashing #OpenSource

@linux_mclinuxface @megmac They (@getsentry) are free to set a shorter time span though, 4 years is the max that BSL allows

In this specific scenario #Codecov has set it to 3 years, as 2026-06-31 is set as the change date: https://github.com/codecov/self-hosted/commit/7f644d0f6ad537ee4bc6b1b8a3b8a16efc343015 (corrected an hour ago by head of open source at Sentry)

Also:

> usage is limited to non-production use, or production use within the limits of the “Additional Use Grant”

With it in this case being: Don’t use this work to launch a competing SaaS

”available under the same BSL license as Sentry’s core repos” https://about.codecov.io/blog/codecov-is-now-open-source/

Been lovely to see #Codecov evolve ever since they joined @getsentry and nice to see them using the same #BSLLicense when they decided to now release their product as kind of #OpenSource 👏