Closed Xliff closed 1 year ago
Hello,
Can you copy/paste the Pakku command you ran and/or the actuall error you seeing when run it so I can investigate the error?
Thanks
# You planned 59 tests, but ran 65
may be this is the issue?
The test output showing planned 65, If you have plan 59
in the test file can you change it to plan 65
and see if the test succeeds?
Changing the number of tests to match fixed the issue. Seeing that this is a self authored issue, I must accept the mea culpa on this one. However it does pose the question: do you think this situation is an actual failure and worth the extra code to check?
Also, I am running a terminal where the bar graph implementation is not working. Should I file a separate issue and what particular information will you need?
Changing the number of tests to match fixed the issue. Seeing that this is a self authored issue, I must accept the mea culpa on this one. However it does pose the question: do you think this situation is an actual failure and worth the extra code to check?
This behavior actually comes from Raku's Test
module, it returns error exit code if the number of tests ran mismatch the planned tests.
if you run the test file using Raku eg. raku -I. t/01-basic.rakutest
and check the exit code right after with echo $?
you should get 0
when tests matches plan, and error code when tests don't match plan. so when Pakku checks the exit code and fnd it non zero it issues a test failure.
I do think this behavior is correct, If I don't know how many tests I need I just comment out the plan #
.
Also, I am running a terminal where the bar graph implementation is not working. Should I file a separate issue and what particular information will you need?
Could you create a separate issue for this? may be add the terminal type and if there is a screenshot of the issue would be helpfull as well.
Also there is a warning message in the README at the end of this section regarding terminals that don't support ASCII escape codes, may be it will be helpfull.
Also, I am running a terminal where the bar graph implementation is not working. Should I file a separate issue and what particular information will you need?
Just pushed a release with a fix for bar graph implementation on xterm
terminal, Let me know if that fixes the issue you saw in your terminal. Thanks.
Yep! Looks great! Can confirm it works on xterm in the following:
Distributor ID: Ubuntu
Description: Ubuntu Mantic Minotaur (development branch)
Release: 23.10
Codename: mantic
Thanks for confirming!
Hello,
I just started trying
Pakku
and I love it. I think it will finally allow me to start releasing this back log of code I have.Unfortunately, it's issuing a failure during the TST phase that I can't find during the real execution.
Here is the output from the test:
As you can see there are no actual failures, but Pakku might be interpreting the run of the test as a failure due to non-critical errors.
If you can fix this soon, I'd appreciate it. However, I might take a stab at it in breaks from $dayJob. Just thought I't pass the possibility along.