Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove Base and Core from ambiguities test #309

Merged
merged 3 commits into from
Oct 15, 2024

Conversation

vtjnash
Copy link
Contributor

@vtjnash vtjnash commented Oct 15, 2024

Reporting ambiguities that cannot be fixed by the user since they are not part of the testtarget can be harmful to the user experience since they will never be useful, since at least JuliaLang/julia#36962.

Fixes #77

Reporting ambiguities that cannot be fixed by the user since they are
not part of the testtarget can be harmful to the user experience since
they will never be useful, since at least JuliaLang/julia#36962.

Fixes JuliaTesting#77
Copy link

codecov bot commented Oct 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.90%. Comparing base (065f7d7) to head (52ceaa4).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #309   +/-   ##
=======================================
  Coverage   74.90%   74.90%           
=======================================
  Files          11       11           
  Lines         761      761           
=======================================
  Hits          570      570           
  Misses        191      191           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@lgoettgens
Copy link
Collaborator

Thanks @vtjnash! If this approach comes from you, I suppose there is nothing else we can do here.

Would you consider this change a Bugfix (i.e. To be released in a patch release) or a larger change (I.e. to be released in a minor/breaking release)? I am thinking about this as many projects may expect these ambiguities and some @test_broken could fail now.

@vtjnash
Copy link
Contributor Author

vtjnash commented Oct 15, 2024

It is a bugfix. I don't know why any project would want to fail on ambiguities that have nothing to do with their package

@lgoettgens lgoettgens merged commit 1fca5d9 into JuliaTesting:master Oct 15, 2024
24 of 25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ambiguities in included modules
2 participants