Skip to content

Better error reporting for scisample #3

Description

@daub1

Summary
Make scisample error reporting more like study validation error reporting.
What is the current behavior?

2020-10-16 13:30:36 - ERROR - Sampler data is invalid
Traceback (most recent call last):
{ FIFTY-TWO lines of traceback }
codepy.scisample.utils.SamplingError: Sampler data is invalid

What is the desired behavior?

Reporting like that for study validation error reporting.

2020-10-16 13:30:53 - ERROR - Error in phase or flavor data for run-generate-baseline
2020-10-16 13:30:53 - ERROR - '01:00' does not match '^([0-9][0-9]-)?[0-9]{1,2}:[0-9][0-9]:[0-9][0-9]$'

Failed validating 'pattern' in schema['properties']['walltime']:
    {'pattern': '^([0-9][0-9]-)?[0-9]{1,2}:[0-9][0-9]:[0-9][0-9]$',
     'type': 'string'}

On instance['walltime']:
    '01:00'
2020-10-16 13:30:53 - ERROR - Study is missing data, cannot write a maestro specifiation

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions