Skip to content

Buggy solutions terminating with runtime errors create useless spam in sinol-make run #278

@meithecatte

Description

@meithecatte

I would like to include solutions with bugs that cause runtime errors, and make sure that my tests catch these bugs. However, this results in a wall of warnings along the lines of:

Solution nawb1.cpp had an error on test in/naw1g.in: process exited due to signal 6 Stderr:
[]
Solution nawb1.cpp had an error on test in/naw1h.in: process exited due to signal 11 Stderr:
[]
Solution nawb1.cpp had an error on test in/naw1i.in: process exited due to signal 11 Stderr:
[]
Solution nawb1.cpp had an error on test in/naw1j.in: process exited due to signal 11 Stderr:
[]

This is suboptimal. Perhaps it would be better to display only one line per buggy solution, and have the user refer to the table for details?

Alternatively, maybe this should be declared as part of sinol_expected_scores?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions