yesodweb / yesodweb/persistent
persistent: Test failure on 32-bit arches with GHC 9.0.2
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 486
- Forks
- 306
- PR merge metrics
- No merged PRs in 30d
Description
Over in Debian unstable, we're seeing a test failure on all 32-bit architectures (armel, armhf, i386, mipsel) when building persistent 2.13.3.5:
Failures:
test/Database/Persist/THSpec.hs:240:26:
1) Database.Persist.THSpec.HasIdDef should have correct underlying sql type
expected: SqlInt64
but got: SqlInt32
To rerun use: --match "/Database/Persist/THSpec/HasIdDef/should have correct underlying sql type/"
Randomized with seed 10835329
Finished in 0.2322 seconds
231 examples, 1 failure, 3 pending
Test suite test: FAIL
Test suite logged to: dist-ghc/test/persistent-2.13.3.5-test.log
The tests are passing on 64-bit architectures (amd64, arm64, mips64el, ppc64el, s390x).
Full build logs for armel are available here: https://buildd.debian.org/status/fetch.php?pkg=haskell-persistent&arch=armel&ver=2.13.3.5-1&stamp=1659384152&raw=0
Contributor guide
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
Start with test/Database/Persist/THSpec.hs:240 and rerun the named HasIdDef example using the provided --match selector. Compare the failing 32-bit result, SqlInt32, with the expected SqlInt64 and the passing 64-bit behavior. Done means the test suite passes on the affected 32-bit architectures without regressing the 64-bit cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100