Test store paths, with property tests, fix bug#7639
Conversation
652f0b4 to
cd65f66
Compare
fbf181d to
13c355f
Compare
be2c9e5 to
61312a5
Compare
2f18473 to
ad3cdf3
Compare
Property tests are great! Co-authored-by: Cole Helbling <[email protected]>
The property test in fact found a bug: we were excluding numbers!
bdd13d8 to
018e257
Compare
|
Successfully created backport PR #7664 for |
|
This PR breaks buliding in
Which interprets everything as CXXFLAGS. The configure script then errors out about boost, but looking in config.status has a whole bunch of Reordering to put the new CXXFLAGS last makes it work. This is the documented behavior for ./configure |
|
@yorickvP I am seeing in a local |
|
@Ericson2314 you're right. |
|
@yorickvP Ah yes. I use fish too but not in my Nix development shell so I never noticed that. Glad it's working for you now! |
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
Motivation
We want mores tests in general. We also have separate code parsing store paths names (when parsing
StorePathand when parsingOutputsSpec) that want to keep in sync.The property test in fact found a bug: we were excluding numbers!
The commits are broken up so that reviewing commit by commit should make for easy reading.
Context
#7633 is an issue to start making property tests for Nix (a la QuickCheck). This kicks off that process, adding
rapidcheckas a dependency, and using it for these new tests.Checklist for maintainers
Maintainers: tick if completed or explain if not relevant
tests/**.shsrc/*/tests