-
Notifications
You must be signed in to change notification settings - Fork 14
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
Use Aqua and JET in tests #130
Conversation
043c905
to
ff15e3d
Compare
Codecov Report
@@ Coverage Diff @@
## main #130 +/- ##
==========================================
+ Coverage 86.21% 89.71% +3.50%
==========================================
Files 9 9
Lines 2350 2440 +90
==========================================
+ Hits 2026 2189 +163
+ Misses 324 251 -73
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
ff15e3d
to
199dba6
Compare
Hmm, can't reproduce the JET failures locally. Will try on a linux machine. UPDATE: No change :/ |
199dba6
to
aa6b0f9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome; thanks @Drvi!
The nightly JET failures are being tracked here |
This reverts commit 6297d57.
Using Aqua, this PR automates checking for method ambiguities, unbound type parameters, undefined exports, and compat bounds being set.
Using JET to make sure
xparse
doesn't have dynamic dispatch or boxed variables in closures. There seem to be code paths leading to dynamic dispatch when parsingDate
andTime
types.