Skip to content

Inconsistent results in coverage test #249

@skliper

Description

@skliper

Checklist (Please check before submitting)

  • I reviewed the Contributing Guide.
  • I reviewed the CF README.md file to see if the feature is in the major future work.
  • I performed a cursory search to see if the feature request is relevant, not redundant, nor in conflict with other tickets.

Is your feature request related to a problem? Please describe.
Likely related to random number use in unit tests (#228

Failed coverage here: https://github.com/skliper/CF/runs/6581159060?check_suite_focus=true

Overall coverage rate:
  lines......: 99.9% (2678 of 2681 lines)
  functions..: 100.0% (258 of 258 functions)
  branches...: 99.2% (1056 of 1065 branches)
9 branches missed, 8 allowed
3 lines missed, 2 allowed

Note it passed in the very next run w/ no code changes (was just a requirements update)

Describe the solution you'd like
Remove whatever random test implementation is causing this (all others eventually to fix #86)

Describe alternatives you've considered
None

Additional context
#86

Requester Info
Jacob Hageman - NASA/GSFC

Metadata

Metadata

Assignees

No one assigned

    Labels

    draco-rc2unit-testRelated to coverage or functional tests

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions