Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Messed up output in CI logs

See original GitHub issue

I have mutmut running inside the CI process:

But, the output is not fully shown:

2.24s$ poetry run mutmut run || true
- Mutation testing starting - 
These are the steps:
1. A full test suite run will be made to make sure we 
   can run the tests successfully and we know how long 
   it takes (to detect infinite loops for example)
2. Mutants will be generated and checked
Mutants are written to the cache in the .mutmut-cache 
directory. Print found mutants with `mutmut results`.
Legend for output:
🎉 Killed mutants. The goal is for everything to end up in this bucket. 
⏰ Timeout. Test suite took 10 times as long as the baseline so were killed.  
🤔 Suspicious. Tests took a long time, but not long enough to be fatal. 
🙁 Survived. This means your tests needs to be expanded. 
mutmut cache is out of date, clearing it...
1. Running tests without mutations
⠸ Running... Done
2. Checking mutants
The command "poetry run mutmut run || true" exited with 0.

I guess, that is caused by animation. My proposed solution is to include --no-interaction flag to run command. In this case it will just out everything on new lines which is quite useful for CIs.

Issue Analytics

  • State:open
  • Created 5 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

boxedcommented, Mar 5, 2019

How about instead adding a flag --ci that has a totally different output scheme? Something that is more like a log format:

Running tests without mutation
Tests without mutation done
Checking mutants
Testing mutant 1
Mutant 1 survived
Testing mutant 2
Mutant 2 was killed


izabelakowalcommented, Apr 24, 2021

@boxed I’ve been testing my code with mutmut on github actions and run into the same problem recently. I’d love to give it a try and see if I’ll manage to create the “ci output” functionality.

Read more comments on GitHub >

github_iconTop Results From Across the Web

CI: Ouput log has missing lines (#210319) · Issues - GitLab
The output log of a failing job is incomplete with missing lines. Because of that, we cannot see what happened.
Read more >
How to process terraform apply logs for catching errors in CI
I'm running terragrunt in CI to automatically apply changes once they're merged, ... the problem is that run-all apply output is a little...
Read more >
Logging Information — CodeIgniter 4.2.10 documentation
Log Levels . You can log information to the local log files by using the log_message() method. You must supply the “level”...
Read more >
How do I get parts of my GitLab CI Job Log to fold when ...
I would prefer to go with an answer of "it is not supported" then make a rob for my own back by doing...
Read more >
Terminal output in logs is odd - CircleCI Discuss
The log output in circleci looks like its having encoding or ... when I look at the logs from the CircleCI web UI...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found