Tests fail due to commitBuffer: invalid argument (invalid character)
Open
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 334
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 50
Description
While building this occurred. Distro is ArchLinux:
Test suite failure for package cannon-0.31.0
cannon-tests: exited with: ExitFailure 1
[.. full log ..]
benchmarking Cannon.Dict/slices 1
time 31.03 ms (20.21 ms .. 43.63 ms)
0.656 Rcannon-tests: <stdout>: commitBuffer: invalid argument (invalid character)
Test suite failure for package types-common-0.16.0
tests: exited with: ExitFailure 1
[.. full log ..]
Tests
Properties
Ascii
validate (toText x) == Right x: OK (0.02s)
+++ OK, passed 100 tests.
unsafeFromByteString (toByteString x) == x: OK (0.01s)
+++ OK, passed 100 tests.
validate (toText x <> "tests: <stdout>: commitBuffer: invalid argument (invalid character)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the cannon-tests and types-common test failures on Arch Linux, starting with the reported commitBuffer invalid-character output. Inspect the full test log and the relevant test entry points to determine whether the failure is in the tests or the environment; done means both package test suites pass without the commitBuffer error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100