Skip to content

json-stream-0.3.2.1 test suite failure #7

@peti

Description

@peti

Citing from http://hydra.cryp.to/build/1139825/log/raw:

Running 1 test suites...
Test suite spec: RUNNING...

Parser
  Basic parsing
    Parses null values
    Parses bool values
    Parses string values with special chracters
    Parses fractional values with exponent
    Parses objects 1
  Object accesors
    objectWithKey works
    yield test 1
    <*> test 1 reverse keys
    <|> test 1
    >^> returns first items even if second is in previous chunk
    >^> returns second item if first does not match
    arrayFound generates events
    objectFound generates events
  Edge cases
    Correct incremental parsing 1
    Correct incremental parsing 2
    Correct incremental parsing 3
    Correctly skips data
    Correctly returns unparsed data 1
    Correctly returns unparsed data 2
    Correctly returns unparsed data 3
    Correctly returns unparsed data 4
    Correctly returns unparsed data 4
    Correctly returns unparsed data 4
    Handles values in interleaving order
  Control parser
    takeI limits number of values
    ignores non-match for array
    ignores non-match for object
    ignores non-match for string
    ignores non-match for number
    ignores non-match for bool
    nullable sets values correctly
    matches null values
  Tests of previous errors
    arrayOf (pure True) should return only n*True, not (n+1)
    objectWithKey should return only first key with given name
    binds correctly convenience operators
    binds correctly convenience operators 2
    binds correctly .| at the last moment
    binds correct .| 2
    Parses correctly empty arrays:
    Parses correctly runs ignore parser on array:
    Parses correctly runs ignore parser on array:
    Parses correctly handles empty strings when sliced:
    Correctly parses safeString when sliced
  Compare parsing of strings aeason vs json-stream
    Parses "{}" the same as aeson
    Parses "{ \"v\":\"1\"} " the same as aeson
    Parses "{ \"v\":\"1\"\r\n} " the same as aeson
    Parses "{ \"v\":1}" the same as aeson
    Parses "{ \"v\":\"ab'c\"}" the same as aeson
    Parses "{ \"PI\":3.141E-10}" the same as aeson
    Parses "{ \"PI\":3.141e-10}" the same as aeson
    Parses "{ \"v\":12345123456789} " the same as aeson
    Parses "{ \"v\":123456789123456789123456789}" the same as aeson
    Parses "[ 1,2,3,4] " the same as aeson
    Parses "[ \"1\",\"2\",\"3\",\"4\"] " the same as aeson
    Parses "[ { }, { },[]] " the same as aeson
    Parses "{ \"v\":\"\\u2000\\u20ff\"} " the same as aeson
    Parses "{ \"v\":\"\\u2000\\u20FF\"} " the same as aeson
    Parses "{ \"a\":\"hp://foo\"} " the same as aeson
    Parses "{ \"a\":null} " the same as aeson
    Parses "{ \"a\":true} " the same as aeson
    Parses "  { \"a\" : true }   " the same as aeson
    Parses "{ \"v\":1.7976931348623157E308} " the same as aeson
  Compare benchmark jsons
    JSONs from benchamark directory are the same FAILED [1]

Failures:

  test/ParserSpec.hs:340:
  1) Parser, Compare benchmark jsons, JSONs from benchamark directory are the same
       uncaught exception: IOException of type NoSuchThing (benchmarks/json-data: getDirectoryContents: does not exist (No such file or directory))

Randomized with seed 208273968

Finished in 0.0026 seconds
63 examples, 1 failure

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions