Roundtrip test failure

Open
#38 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
haskell
Domain
testing

Research direction

Start with test/Test/Codec/CBOR/Cuddle/CDDL/Parser.hs at the failing Roundtripping should be id/Trip GroupEntry test. Rerun it with --match "/cddlParser/Roundtripping should be id/Trip GroupEntry/" and seed 1014413989, then trace the parser and formatter involved in the differing spaces. Done means the roundtrip test passes with the generated CDDL strings equal.

Written by the indexing model from the issue text.

Description

Failures:

  test/Test/Codec/CBOR/Cuddle/CDDL/Parser.hs:37:3:
  1) cddlParser, Roundtripping should be id, Trip GroupEntry
       Falsified (after 80 tests and 23 shrinks):
         GEType Nothing Nothing (Type0 (Type1 (T2Unwrapped (Name "x") (Just (GenericArg (Type1 (T2Unwrapped (Name "Z") Nothing) (Just (RangeOp Closed,T2Tag Nothing (Type0 (Type1 (T2Enum (Group ([GEGroup Nothing (Group ([GERef Nothing (Name "I") Nothing] :| []))] :| []))) Nothing :| [])))) :| [])))) Nothing :| []))
         GEType Nothing Nothing (Type0 (Type1 (T2Unwrapped (Name "x") (Just (GenericArg (Type1 (T2Unwrapped (Name "Z") Nothing) (Just (RangeOp Closed,T2Tag Nothing (Type0 (Type1 (T2Enum (Group ([GEType Nothing Nothing (Type0 (Type1 (T2Group (Type0 (Type1 (T2Name (Name "I") Nothing) Nothing :| []))) Nothing :| []))] :| []))) Nothing :| [])))) :| [])))) Nothing :| []))
         "~ x<~ Z .. #6(& ((I)))>" /= "~ x<~ Z .. #6(& (( I)))>"

  To rerun use: --match "/cddlParser/Roundtripping should be id/Trip GroupEntry/" --seed 1014413989

Randomized with seed 1014413989
Dominant language
Haskell
Stars
8
Forks
5
Avg merge
3d 12h
Merged PRs (30d)
4

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/cuddle

All issues in IntersectMBO/cuddle

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.