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

Tests Fail #4

Closed
zoffixznet opened this issue Dec 11, 2015 · 3 comments
Closed

Tests Fail #4

zoffixznet opened this issue Dec 11, 2015 · 3 comments

Comments

@zoffixznet
Copy link
Contributor

Built with rakudo brewed today:

==> Fetching DateTime::Math
Use of uninitialized value %ENV of type Any in string context
Any of .^name, .perl, .gist, or .say can stringify undefined things, if needed.  in sub git-fetch at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/A36DB4DD6E30E31F0409D703B4392DA5E8CE3A4E:46
==> Building DateTime::Math
==> Testing DateTime::Math
Use of uninitialized value %ENV of type Any in string context
Any of .^name, .perl, .gist, or .say can stringify undefined things, if needed.  in block  at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/site/sources/56A2FE43AE962A734AE0B520B19C164B5E28FEA3:84
Ambiguous call to 'infix:«>»'; these signatures all match:
:(DateTime:D \a, DateTime:D \b)
:(DateTime $a, DateTime $b)
  in block <unit> at t/math.t:27

# Looks like you planned 17 tests, but ran 8
t/math.t .. 
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 9/17 subtests 

Test Summary Report
-------------------
t/math.t (Wstat: 65280 Tests: 8 Failed: 0)
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 17 tests but ran 8.
Files=1, Tests=8,  4 wallclock secs ( 0.02 usr  0.01 sys +  2.85 cusr  0.35 csys =  3.23 CPU)
Result: FAIL
@timo
Copy link

timo commented Mar 30, 2016

The tests still fail. The reason is, that rakudo ships these infix operators in core now, but with a very slightly different signature. That's why it doesn't give a redeclaration error while compiling, but a "ambiguous call" while testing.

@supernovus
Copy link
Collaborator

The latest pull request I just merged should be the fix for this issue.

@JJ
Copy link
Contributor

JJ commented Jun 24, 2020

And this one has an outstanding issue. Let's check this out.

@JJ JJ closed this as completed in 5f92a90 Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants