Giter Site home page Giter Site logo

colcon-output's Introduction

colcon-output

An extension for colcon-core to customize the output in various ways.

colcon-output's People

Contributors

cottsay avatar dirk-thomas avatar ipa-fez avatar jparisu avatar nuclearsandwich avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

colcon-output's Issues

Would like verbs to be able to override what the jobs are called in SummaryHandler

I have an experimental verb which operates at the repo- rather than package level. It's working great, but it's too bad that the summary at the end of a run still refers to n packages finished, in this code (and elsewhere):

count, plural_suffix, _ = _msg_arguments(
self._ended - self._interrupted - self._failed)
print('Summary: {count} package{plural_suffix} finished '
'[{duration_string}]'.format_map(locals()))

Not sure how much visibility this code and the running verb have into each other, but it would be nice if the SummaryHandler could somehow be passed a singular/plural tuple of what to refer to the jobs as.

Help: what does these failure messages mean?

Hello,
I pull the latest ros2 stack code and run colcon build/test, many these error messages show up when colcon test-result --verbose:

build/action_msgs/test_results/action_msgs/xmllint.xunit.xml: 1 test, 0 errors, 1 failure, 0 skipped

  • action_msgs.xmllint package.xml
    <<< failure message
    Diff with 329 lines

build/action_tutorials_cpp/test_results/action_tutorials_cpp/xmllint.xunit.xml: 1 test, 0 errors, 1 failure, 0 skipped

  • action_tutorials_cpp.xmllint package.xml
    <<< failure message
    Diff with 329 lines

build/action_tutorials_interfaces/test_results/action_tutorials_interfaces/xmllint.xunit.xml: 1 test, 0 errors, 1 failure, 0 skipped

  • action_tutorials_interfaces.xmllint package.xml
    <<< failure message
    Diff with 329 lines

Display ongoing count in status bar

currently the number of ongoing jobs is displayed only in the terminal title. It wouls be benefictial to have this as part of the status line. Maybe by default or maybe optionally.

I'm thinking of something like:
[time] [%d/%d complete] [%d ongoing] [JOB1_STATUS] ... [JOBN_STATUS]

colcon event handler which print stdout on error

Description

  • As a developer, it would be easier to find broken tests in terminal logs if there was an option to only dump stdout of tests that failed.

Current Behavior

  • Currently, I can either run my builds with colcon test --event-handlers console_cohesion+ and then scroll through the terminal to find the broken test OR I can run colcon test and then have to go to log/latest_test/my_pkg/stdout.log to find the broken test.

  • The first option is too noisy

  • The second option has the disadvantage that in (our) CI, these logs aren't easily accessible

    • As far as I can tell, there is no simple way to say,
    for each failing package:
        print file log/latest_test/<pkg>/stdout.log
    

Desired Behavior

  • An option like console test --event-handlers console_stdout_on_fail+ where:
    • If a package succeeds, the output looks like console test
    • If a package fails, the output looks like console test --event-handlers console_cohesion+

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.