You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to install Log::Async in this docker image.
This image builds the latest rakudo from github.
However tests are failing.
This is the error I am getting:
===> Testing: Log::Async:ver('0.0.4')
t/01-basic.t ............... ok
t/02-levels.t .............. ok
t/03-log.t ................. ok
t/04-filter.t .............. ok
t/05-concurrent.t .......... ok
t/06-sleep.t ............... ok
t/07-done.t ................ ok
t/08-commandline.t ......... ok
t/08-use.t ................. ok
t/09-commandline-filter.t .. ok
t/10-formatter.t ...........
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/5 subtests
t/11-log-async-context.t ... ok
t/12-context.t ............. ok
t/13-remove-tap.t .......... ok
t/14-frame.t ............... ok
t/15-untapped.t ............ ok
t/99-meta.t ................ ok
Test Summary Report
-------------------
t/10-formatter.t (Wstat: 256 Tests: 5 Failed: 1)
Failed test: 4
Non-zero exit status: 1
Files=17, Tests=77, 25 wallclock secs ( 0.09 usr 0.02 sys + 14.83 cusr 1.69 csys = 16.63 CPU)
Result: FAIL
# Failed test 'custom format again'
# at t/10-formatter.t line 62
# expected: $["trace: tracing paper", "debug: this is not a bug", "warning: this is your final warning"]
# got: $["trace: tracing paper"]
# Looks like you failed 1 test of 5
===> Testing [FAIL]: Log::Async:ver('0.0.4')
What could be going wrong?
Till Sep 6 2017, the tests were passing. I think the problem could be in rakudo itself.
This is what experts from rakudo have to say:
Best,
Suman
The text was updated successfully, but these errors were encountered:
Hi there,
I am trying to install Log::Async in this docker image.
This image builds the latest rakudo from github.
However tests are failing.
This is the error I am getting:
What could be going wrong?
Till Sep 6 2017, the tests were passing. I think the problem could be in rakudo itself.
This is what experts from rakudo have to say:

Best,
Suman
The text was updated successfully, but these errors were encountered: