| blob | a1f5eed3c6208c03df954198b51676d11ee1c598 |
1 {-# LANGUAGE OverloadedStrings #-}
3 -- | This is a set of unit tests for the dependency solver,
4 -- which uses the solver DSL ("UnitTests.Distribution.Solver.Modular.DSL")
5 -- to more conveniently create package databases to run the solver tests on.
7 where
9 -- base
14 -- test-framework
18 -- Cabal
23 )
25 -- cabal-install
34 tests =
35 [ testGroup
36 "Simple dependencies"
40 preferOldest $
45 , runTest $ indep $ mkTest db1 "indepTwoVersions" ["C", "D"] (solverSuccess [("B", 1), ("B", 2), ("C", 1), ("D", 1)])
46 , runTest $ indep $ mkTest db1 "aliasWhenPossible1" ["C", "E"] (solverSuccess [("B", 1), ("C", 1), ("E", 1)])
47 , runTest $ indep $ mkTest db1 "aliasWhenPossible2" ["D", "E"] (solverSuccess [("B", 2), ("D", 1), ("E", 1)])
48 , runTest $ indep $ mkTest db2 "aliasWhenPossible3" ["C", "D"] (solverSuccess [("A", 1), ("A", 2), ("B", 1), ("B", 2), ("C", 1), ("D", 1)])
56 ]
57 , testGroup
58 "Flagged dependencies"
63 , runTest $ indep $ mkTest db18 "linkFlags3" ["A", "B"] (solverSuccess [("A", 1), ("B", 1), ("C", 1), ("D", 1), ("D", 2), ("F", 1)])
64 ]
65 , testGroup
66 "Lifting dependencies out of conditionals"
68 , runTest $ twoLevelDeepCommonDependencyLogMessage "two level deep common dependency log message"
70 ]
71 , testGroup
72 "Manual flags"
79 setVerbose $
82 -- TODO: We should check the summarized log instead of the full log
83 -- for the manual flags error message, but it currently only
84 -- appears in the full log.
88 constraints cs $
91 ]
92 , testGroup
93 "Qualified manual flag constraints"
97 constraints cs $
99 solverSuccess
105 ]
107 cs =
110 ]
112 constraints cs $
114 solverSuccess
120 ]
122 cs =
125 ]
127 constraints cs $
129 solverSuccess
135 ]
140 constraints cs $
144 cs =
147 ]
149 checkFullLog lns =
150 all
154 ]
156 constraints cs $
157 setVerbose $
160 ]
161 , testGroup
162 "Stanzas"
163 [ runTest $ enableAllTests $ mkTest db5 "simpleTest1" ["C"] (solverSuccess [("A", 2), ("C", 1)])
165 , runTest $ enableAllTests $ mkTest db5 "simpleTest3" ["E"] (solverSuccess [("A", 1), ("E", 1)])
167 , runTest $ enableAllTests $ mkTest db5 "simpleTest5" ["G"] (solverSuccess [("A", 2), ("G", 1)])
169 , runTest $ indep $ enableAllTests $ mkTest db5 "simpleTest7" ["E", "G"] (solverSuccess [("A", 1), ("A", 2), ("E", 1), ("G", 1)])
170 , runTest $ enableAllTests $ mkTest db6 "depsWithTests1" ["C"] (solverSuccess [("A", 1), ("B", 1), ("C", 1)])
171 , runTest $ indep $ enableAllTests $ mkTest db6 "depsWithTests2" ["C", "D"] (solverSuccess [("A", 1), ("B", 1), ("C", 1), ("D", 1)])
173 ]
174 , testGroup
175 "Setup dependencies"
181 , runTest $ mkTest db8 "setupDeps6" ["C", "D"] (solverSuccess [("A", 1), ("B", 1), ("B", 2), ("C", 1), ("D", 1)])
182 , runTest $ mkTest db9 "setupDeps7" ["F", "G"] (solverSuccess [("A", 1), ("B", 1), ("B", 2), ("C", 1), ("D", 1), ("E", 1), ("E", 2), ("F", 1), ("G", 1)])
184 , runTest $ indep $ mkTest dbSetupDeps "setupDeps9" ["A", "B"] (solverSuccess [("A", 1), ("B", 1), ("C", 1), ("D", 1), ("D", 2)])
187 ]
188 , testGroup
189 "Base shim"
196 , expectFailBecause "#9467" $ runTest $ mkTest db12s "baseShim7" ["A"] (solverSuccess [("A", 1)])
197 , expectFailBecause "#9467" $ runTest $ mkTest db11s "baseShim7-simple" ["A"] (solverSuccess [("A", 1)])
199 ]
200 , testGroup
201 "Base and non-reinstallable"
204 solverFailure (isInfixOf "rejecting: base-1.0.0 (constraint from non-reinstallable package requires installed instance)")
206 allowBootLibInstalls $
211 solverFailure (isInfixOf "rejecting: ghc-2.0.0 (constraint from non-reinstallable package requires installed instance)")
212 ]
213 , testGroup
214 "reject-unconstrained"
216 onlyConstrained $
220 onlyConstrained $
224 onlyConstrained $
228 onlyConstrained $
230 solverFailure $
231 isInfixOf $
240 ]
241 , testGroup
242 "Cycles"
250 , runTest $ mkTest db15 "cycleThroughSetupDep5" ["E"] (solverSuccess [("C", 2), ("D", 1), ("E", 1)])
253 ]
254 , testGroup
255 "Extensions"
257 , runTest $ mkTestExts [EnableExtension CPP] dbExts1 "unsupportedIndirect" ["B"] anySolverFailure
258 , runTest $ mkTestExts [EnableExtension RankNTypes] dbExts1 "supported" ["A"] (solverSuccess [("A", 1)])
259 , runTest $ mkTestExts (map EnableExtension [CPP, RankNTypes]) dbExts1 "supportedIndirect" ["C"] (solverSuccess [("A", 1), ("B", 1), ("C", 1)])
261 , runTest $ mkTestExts (map EnableExtension [CPP, RankNTypes]) dbExts1 "disabledExtension" ["D"] anySolverFailure
262 , runTest $ mkTestExts (UnknownExtension "custom" : map EnableExtension [CPP, RankNTypes]) dbExts1 "supportedUnknown" ["E"] (solverSuccess [("A", 1), ("B", 1), ("C", 1), ("E", 1)])
263 ]
264 , testGroup
265 "Languages"
267 , runTest $ mkTestLangs [Haskell98, Haskell2010] dbLangs1 "supported" ["A"] (solverSuccess [("A", 1)])
269 , runTest $ mkTestLangs [Haskell98, Haskell2010, UnknownLanguage "Haskell3000"] dbLangs1 "supportedUnknown" ["C"] (solverSuccess [("A", 1), ("B", 1), ("C", 1)])
270 ]
271 , testGroup
272 "Qualified Package Constraints"
278 constraints cs $
284 ]
286 constraints cs $
291 constraints cs $
294 ]
295 , testGroup
296 "Package Preferences"
297 [ runTest $ preferences [ExPkgPref "A" $ mkvrThis 1] $ mkTest db13 "selectPreferredVersionSimple" ["A"] (solverSuccess [("A", 1)])
298 , runTest $ preferences [ExPkgPref "A" $ mkvrOrEarlier 2] $ mkTest db13 "selectPreferredVersionSimple2" ["A"] (solverSuccess [("A", 2)])
299 , runTest
300 $ preferences
303 ]
305 , runTest
306 $ preferences
309 ]
311 , runTest
312 $ preferences
315 ]
317 , runTest
318 $ preferences
321 ]
323 ]
324 , testGroup
325 "Stanza Preferences"
338 ]
339 , testGroup
340 "Buildable Field"
342 , testBuildable "avoid building component with unknown extension" (ExExt (UnknownExtension "unknown"))
343 , testBuildable "avoid building component with unknown language" (ExLang (UnknownLanguage "unknown"))
344 , runTest $ mkTest dbBuildable1 "choose flags that set buildable to false" ["pkg"] (solverSuccess [("flag1-false", 1), ("flag2-true", 1), ("pkg", 1)])
345 , runTest $ mkTest dbBuildable2 "choose version that sets buildable to false" ["A"] (solverSuccess [("A", 1), ("B", 2)])
346 ]
347 , testGroup
348 "Pkg-config dependencies"
351 , runTest $ mkTestPCDepends (Just [("pkgA", "1.0.0"), ("pkgB", "1.0.0")]) dbPC1 "pruneNotFound" ["C"] (solverSuccess [("A", 1), ("B", 1), ("C", 1)])
352 , runTest $ mkTestPCDepends (Just [("pkgA", "1.0.0"), ("pkgB", "2.0.0")]) dbPC1 "chooseNewest" ["C"] (solverSuccess [("A", 1), ("B", 2), ("C", 1)])
355 ]
356 , testGroup
357 "Independent goals"
358 [ runTest $ indep $ mkTest db16 "indepGoals1" ["A", "B"] (solverSuccess [("A", 1), ("B", 1), ("C", 1), ("D", 1), ("D", 2), ("E", 1)])
368 ]
370 testGroup
371 "Backjumping"
381 , runTest $ indep $ mkTest dbBJ8 "bj8" ["A", "B"] (solverSuccess [("A", 1), ("B", 1), ("C", 1)])
382 ]
383 , testGroup
384 "main library dependencies"
392 ]
395 solverFailure (isInfixOf "rejecting: B-1.0.0 (does not contain library, which is required by A)")
397 db =
401 ]
405 ]
406 , testGroup
407 "sub-library dependencies"
411 ]
414 solverFailure $
415 isInfixOf $
416 "rejecting: B-1.0.0 (does not contain library 'sub-lib', which is required by A)"
420 ]
423 solverFailure $
424 isInfixOf $
425 "rejecting: B-1.0.0 (library 'sub-lib' is private, but it is required by A)"
430 `withSubLibrary` exSubLib "sub-lib" [ExFlagged "make-lib-private" (dependencies []) publicDependencies]
431 ]
435 solverFailure $
436 isInfixOf $
437 "rejecting: B-1.0.0 (library 'sub-lib' is private, but it is required by A)"
442 `withSubLibrary` exSubLib "sub-lib" [ExFlagged "make-lib-private" (dependencies []) publicDependencies]
443 ]
451 ]
453 goals =
457 ]
459 goalOrder goals $
461 solverFailure $
462 isInfixOf $
463 "rejecting: C-1.0.0 (requires library 'sub-lib' from B, but the component is private)"
468 ]
476 ]
480 ]
482 testGroup
483 "build-tool-depends"
484 [ runTest $ mkTest dbBuildTools "simple exe dependency" ["A"] (solverSuccess [("A", 1), ("bt-pkg", 2)])
486 disableSolveExecutables $
487 mkTest dbBuildTools "don't install build tool packages in legacy mode" ["A"] (solverSuccess [("A", 1)])
488 , runTest $ mkTest dbBuildTools "flagged exe dependency" ["B"] (solverSuccess [("B", 1), ("bt-pkg", 2)])
490 enableAllTests $
496 disableSolveExecutables $
504 solverFailure (isInfixOf "does not contain executable 'unknown-exe', which is required by F +flagF")
506 enableAllTests $
508 solverFailure (isInfixOf "does not contain executable 'unknown-exe', which is required by G *test")
511 solverFailure $
512 isInfixOf $
513 -- The solver reports the version conflict when a version conflict
514 -- and an executable conflict apply to the same package version.
515 "[__1] rejecting: H:bt-pkg:exe.bt-pkg-4.0.0 (conflict: H => H:bt-pkg:exe.bt-pkg (exe exe1)==3.0.0)\n"
516 ++ "[__1] rejecting: H:bt-pkg:exe.bt-pkg-3.0.0 (does not contain executable 'exe1', which is required by H)\n"
517 ++ "[__1] rejecting: H:bt-pkg:exe.bt-pkg-2.0.0 (conflict: H => H:bt-pkg:exe.bt-pkg (exe exe1)==3.0.0)"
518 , runTest $ chooseExeAfterBuildToolsPackage True "choose exe after choosing its package - success"
519 , runTest $ chooseExeAfterBuildToolsPackage False "choose exe after choosing its package - failure"
520 , runTest $ rejectInstalledBuildToolPackage "reject installed package for build-tool dependency"
521 , runTest $ requireConsistentBuildToolVersions "build tool versions must be consistent within one package"
522 ]
524 testGroup
525 "legacy build-tools"
528 disableSolveExecutables $
529 mkTest dbLegacyBuildTools1 "bt1 - don't install build tool packages in legacy mode" ["A"] (solverSuccess [("A", 1)])
534 disableSolveExecutables $
535 mkTest dbLegacyBuildTools2 "bt2 - don't check for build tool executables in legacy mode" ["A"] (solverSuccess [("A", 1)])
537 , runTest $ mkTest dbLegacyBuildTools4 "bt4" ["C"] (solverSuccess [("A", 1), ("B", 1), ("C", 1), ("alex", 1), ("alex", 2)])
538 , runTest $ mkTest dbLegacyBuildTools5 "bt5" ["B"] (solverSuccess [("A", 1), ("A", 2), ("B", 1), ("alex", 1)])
539 , runTest $ mkTest dbLegacyBuildTools6 "bt6" ["A"] (solverSuccess [("A", 1), ("alex", 1), ("happy", 1)])
540 ]
542 testGroup
543 "internal dependencies"
544 [ runTest $ mkTest dbIssue3775 "issue #3775" ["B"] (solverSuccess [("A", 2), ("B", 2), ("warp", 1)])
545 ]
549 in [ let db = [Right $ exAv "A" 1 [ExFlagged "build-lib" (dependencies []) unbuildableDependencies]]
558 ]
566 ]
570 solverFailure $
571 isInfixOf $
572 "rejecting: B-1.0.0 (library is not buildable in the "
579 ]
589 ]
593 solverFailure $
594 isInfixOf $
595 "rejecting: A:B:exe.B-1.0.0 (executable 'bt' is not "
598 chooseUnbuildableExeAfterBuildToolsPackage
599 "choose unbuildable exe after choosing its package"
600 ]
601 , testGroup
602 "--fine-grained-conflicts"
604 --
605 -- When the solver explores A-4, it finds that it cannot satisfy B's
606 -- dependencies. This allows the solver to skip the subsequent
607 -- versions of A that also depend on B.
608 runTest $
616 ]
617 msg =
630 ]
636 -- dependency:
637 --
638 -- The solver rejects A-4 because its constraint on B excludes B-1.
639 -- Then the solver is able to skip A-3 and A-2 because they also
640 -- exclude B-1, even though they don't have the exact same constraints
641 -- on B.
642 runTest $
649 ]
650 msg =
662 ]
668 -- package, B, before choosing a version for one of its reverse
669 -- dependencies, C. While the solver is exploring the subtree rooted
670 -- at B-3, it finds that C-2's dependency on B conflicts with B-3.
671 -- Then the solver is able to skip C-1, because it also excludes B-3.
672 --
673 -- --fine-grained-conflicts could have a benefit in this case even
674 -- though the solver would have found the conflict between B-3 and C-1
675 -- immediately after trying C-1 anyway. It prevents C-1 from
676 -- introducing any other conflicts which could increase the size of
677 -- the conflict set.
678 runTest $
686 ]
688 expectedMsg =
700 ]
702 goalOrder goals $
707 -- multiple reasons to add a variable to the conflict set. In this
708 -- case, package A conflicts with B and C. The solver should take the
709 -- union of the conflicts and then only skip a version if it does not
710 -- resolve any of the conflicts.
711 --
712 -- The solver rejects A-3 because it can't find consistent versions for
713 -- its two dependencies, B and C. Then it skips A-2 because A-2 also
714 -- depends on B and C. This test ensures that the solver considers
715 -- A-1 even though A-1 only resolves one of the conflicts (A-1 removes
716 -- the dependency on C).
717 runTest $
726 ]
728 msg =
746 ]
748 goalOrder goals $
753 -- that the solver encountered in a subtree. The solver should only
754 -- show the conflicts that are contained in the current conflict set.
755 --
756 -- The goal order forces the solver to try A-4, encounter a conflict
757 -- with B-2, try B-1, and then try C. A-4 conflicts with the only
758 -- version of C, so the solver backjumps with a conflict set of
759 -- {A, C}. When the solver skips the next version of A, the log should
760 -- mention the conflict with C but not B.
761 runTest $
770 ]
772 msg =
786 ]
788 goalOrder goals $
793 -- skipped due to being excluded by one of its reverse dependencies'
794 -- constraints.
795 runTest $
801 ]
802 msg =
806 -- conflict set, with the details of each package's
807 -- conflict:
808 --
809 -- A: A's constraint rejected B-2.
810 -- B: B was rejected by A's B==3 constraint
811 "[__1] rejecting: B-2.0.0 (conflict: A => B==3.0.0)"
813 -- previous conflict set. It also needs to update A's
814 -- entry to say that A also rejected B-1. Otherwise, the
815 -- solver wouldn't know that A-1 could resolve one of
816 -- the conflicts encountered while exploring A-2. The
817 -- solver would skip A-1, even though it leads to the
818 -- solution.
819 "[__1] skipping: B-1.0.0 (has the same characteristics that caused "
827 ]
833 -- skipped due to excluding a version of one of its dependencies.
834 -- This test is similar the previous one, with the goal order reversed.
835 runTest $
841 ]
843 msg =
855 ]
857 goalOrder goals $
861 ]
863 testGroup
864 "Solver log"
866 runTest $
870 p lg =
875 SolverResult p $
879 msg =
880 "After searching the rest of the dependency tree exhaustively, "
900 "Backjump limit reached (currently 1, change with --max-backjumps "
903 , testMinimizeConflictSet
904 "minimize conflict set with --minimize-conflict-set"
905 , testNoMinimizeConflictSet
906 "show original conflict set with --no-minimize-conflict-set"
911 ]
919 ]
923 , testGroup
924 "package versions abbreviation (issue #9559.)"
930 ]
940 ]
951 ]
962 ]
967 ]
968 ]
969 ]
970 where
971 indep = independentGoals
978 {-------------------------------------------------------------------------------
979 Specific example database for the tests
980 -------------------------------------------------------------------------------}
982 db1 :: ExampleDb
983 db1 =
994 ]
996 -- In this example, we _can_ install C and D as independent goals, but we have
997 -- to pick two different versions for B (arbitrarily)
998 db2 :: ExampleDb
999 db2 =
1006 ]
1008 db3 :: ExampleDb
1009 db3 =
1015 ]
1017 -- | Like db3, but the flag picks a different package rather than a
1018 -- different package version
1019 --
1020 -- In db3 we cannot install C and D as independent goals because:
1021 --
1022 -- * The multiple instance restriction says C and D _must_ share B
1023 -- * Since C relies on A-1, C needs B to be compiled with flagB on
1024 -- * Since D relies on A-2, D needs B to be compiled with flagB off
1025 -- * Hence C and D have incompatible requirements on B's flags.
1026 --
1027 -- However, _even_ if we don't check explicitly that we pick the same flag
1028 -- assignment for 0.B and 1.B, we will still detect the problem because
1029 -- 0.B depends on 0.A-1, 1.B depends on 1.A-2, hence we cannot link 0.A to
1030 -- 1.A and therefore we cannot link 0.B to 1.B.
1031 --
1032 -- In db4 the situation however is trickier. We again cannot install
1033 -- packages C and D as independent goals because:
1034 --
1035 -- * As above, the multiple instance restriction says that C and D _must_ share B
1036 -- * Since C relies on Ax-2, it requires B to be compiled with flagB off
1037 -- * Since D relies on Ay-2, it requires B to be compiled with flagB on
1038 -- * Hence C and D have incompatible requirements on B's flags.
1039 --
1040 -- But now this requirement is more indirect. If we only check dependencies
1041 -- we don't see the problem:
1042 --
1043 -- * We link 0.B to 1.B
1044 -- * 0.B relies on Ay-1
1045 -- * 1.B relies on Ax-1
1046 --
1047 -- We will insist that 0.Ay will be linked to 1.Ay, and 0.Ax to 1.Ax, but since
1048 -- we only ever assign to one of these, these constraints are never broken.
1049 db4 :: ExampleDb
1050 db4 =
1058 ]
1060 -- | Simple database containing one package with a manual flag.
1061 dbManualFlags :: ExampleDb
1062 dbManualFlags =
1068 ]
1070 -- | Database containing a setup dependency with a manual flag. A's library and
1071 -- setup script depend on two different versions of B. B's manual flag can be
1072 -- set to different values in the two places where it is used.
1073 dbSetupDepWithManualFlag :: ExampleDb
1074 dbSetupDepWithManualFlag =
1078 declareFlags bFlags $
1079 exAv
1080 "B"
1081 1
1082 [ exFlagged
1083 "flag"
1086 ]
1088 declareFlags bFlags $
1089 exAv
1090 "B"
1091 2
1092 [ exFlagged
1093 "flag"
1096 ]
1101 ]
1103 -- | A database similar to 'dbSetupDepWithManualFlag', except that the library
1104 -- and setup script both depend on B-1. B must be linked because of the Single
1105 -- Instance Restriction, and its flag can only have one value.
1106 dbLinkedSetupDepWithManualFlag :: ExampleDb
1107 dbLinkedSetupDepWithManualFlag =
1111 exAv
1112 "B"
1113 1
1114 [ exFlagged
1115 "flag"
1118 ]
1121 ]
1123 -- | Some tests involving testsuites
1124 --
1125 -- Note that in this test framework test suites are always enabled; if you
1126 -- want to test without test suites just set up a test database without
1127 -- test suites.
1128 --
1129 -- * C depends on A (through its test suite)
1130 -- * D depends on B-2 (through its test suite), but B-2 is unavailable
1131 -- * E depends on A-1 directly and on A through its test suite. We prefer
1132 -- to use A-1 for the test suite in this case.
1133 -- * F depends on A-1 directly and on A-2 through its test suite. In this
1134 -- case we currently fail to install F, although strictly speaking
1135 -- test suites should be considered independent goals.
1136 -- * G is like E, but for version A-2. This means that if we cannot install
1137 -- E and G together, unless we regard them as independent goals.
1138 db5 :: ExampleDb
1139 db5 =
1148 ]
1150 -- Now the _dependencies_ have test suites
1151 --
1153 -- * Installing C is a simple example. C wants version 1 of A, but depends on
1155 -- B, and B's testsuite depends on an any version of A. In this case we prefer
1156 -- to link (if we don't regard test suites as independent goals then of course
1157 -- linking here doesn't even come into it).
1159 -- * Installing [C, D] means that we prefer to link B -- depending on how we
1161 -- set things up, this means that we should also link their test suites.
1162 db6 :: ExampleDb
1163 db6 =
1169 ]
1171 -- | This test checks that the solver can backjump to disable a flag, even if
1172 -- the problematic dependency is also under a test suite. (issue #4390)
1173 --
1174 -- The goal order forces the solver to choose the flag before enabling testing.
1175 -- Previously, the solver couldn't handle this case, because it only tried to
1176 -- disable testing, and when that failed, it backjumped past the flag choice.
1177 -- The solver should also try to set the flag to false, because that avoids the
1178 -- dependency on B.
1180 testTestSuiteWithFlag name =
1181 goalOrder goals $
1182 enableAllTests $
1185 where
1186 db :: ExampleDb
1187 db =
1192 ]
1195 goals =
1200 ]
1202 -- Packages with setup dependencies
1203 --
1204 -- Install..
1206 -- * B: Simple example, just make sure setup deps are taken into account at all
1208 -- * C: Both the package and the setup script depend on any version of A.
1210 -- In this case we prefer to link
1212 -- * D: Variation on C.1 where the package requires a specific (not latest)
1214 -- version but the setup dependency is not fixed. Again, we prefer to
1215 -- link (picking the older version)
1217 -- * E: Variation on C.2 with the setup dependency the more inflexible.
1219 -- Currently, in this case we do not see the opportunity to link because
1220 -- we consider setup dependencies after normal dependencies; we will
1221 -- pick A.2 for E, then realize we cannot link E.setup.A to A.2, and pick
1222 -- A.1 instead. This isn't so easy to fix (if we want to fix it at all);
1223 -- in particular, considering setup dependencies _before_ other deps is
1224 -- not an improvement, because in general we would prefer to link setup
1225 -- setups to package deps, rather than the other way around. (For example,
1226 -- if we change this ordering then the test for D would start to install
1227 -- two versions of A).
1229 -- * F: The package and the setup script depend on different versions of A.
1231 -- This will only work if setup dependencies are considered independent.
1232 db7 :: ExampleDb
1233 db7 =
1241 ]
1243 -- If we install C and D together (not as independent goals), we need to build
1244 -- both B.1 and B.2, both of which depend on A.
1245 db8 :: ExampleDb
1246 db8 =
1252 ]
1254 -- Extended version of `db8` so that we have nested setup dependencies
1255 db9 :: ExampleDb
1256 db9 =
1257 db8
1262 ]
1264 -- Multiple already-installed packages with inter-dependencies, and one package
1265 -- (C) that depends on package A-1 for its setup script and package A-2 as a
1266 -- library dependency.
1267 db10 :: ExampleDb
1268 db10 =
1275 , Left ghc_prim
1276 , Left base
1277 , Left a1
1278 , Left a2
1280 ]
1282 -- | This database tests that a package's setup dependencies are correctly
1283 -- linked when the package is linked. See pull request #3268.
1284 --
1285 -- When A and B are installed as independent goals, their dependencies on C must
1286 -- be linked, due to the single instance restriction. Since C depends on D, 0.D
1287 -- and 1.D must be linked. C also has a setup dependency on D, so 0.C-setup.D
1288 -- and 1.C-setup.D must be linked. However, D's two link groups must remain
1289 -- independent. The solver should be able to choose D-1 for C's library and D-2
1290 -- for C's setup script.
1291 dbSetupDeps :: ExampleDb
1292 dbSetupDeps =
1298 ]
1300 -- | Tests for dealing with base shims
1301 db11 :: ExampleDb
1302 db11 =
1306 , Left base4
1308 ]
1310 -- | Slightly more realistic version of db11 where base-3 depends on syb
1311 -- This means that if a package depends on base-3 and on syb, then they MUST
1312 -- share the version of syb
1313 --
1314 -- * Package A relies on base-3 (which relies on base-4)
1315 -- * Package B relies on base-4
1316 -- * Package C relies on both A and B
1317 -- * Package D relies on base-3 and on syb-2, which is not possible because
1318 -- base-3 has a dependency on syb-1 (non-inheritance of the Base qualifier)
1319 -- * Package E relies on base-4 and on syb-2, which is fine.
1320 db12 :: ExampleDb
1321 db12 =
1326 , Left base4
1327 , Left syb1
1334 ]
1336 -- | A version of db12 where the dependency on base happens via a setup dependency
1337 --
1338 -- * The setup dependency is solved in it's own qualified scope, so should be solved
1339 -- independently of the rest of the build plan.
1340 --
1341 -- * The setup dependency depends on `base-3` and hence `syb1`
1342 --
1343 -- * A depends on `base-4` and `syb-2`, should be fine as the setup stanza should
1344 -- be solved independently.
1345 db12s :: ExampleDb
1346 db12s =
1351 , Left base4
1352 , Left syb1
1357 ]
1359 -- | A version of db11 where the dependency on base happens via a setup dependency
1360 --
1361 -- * The setup dependency is solved in it's own qualified scope, so should be solved
1362 -- independently of the rest of the build plan.
1363 --
1364 -- * The setup dependency depends on `base-3`
1365 --
1366 -- * A depends on `base-4`, should be fine as the setup stanza should
1367 -- be solved independently.
1368 db11s :: ExampleDb
1369 db11s =
1373 , Left base4
1377 ]
1379 -- Works without the base-shimness, choosing different versions of base
1380 db11s2 :: ExampleDb
1381 db11s2 =
1385 , Left base4
1389 ]
1391 dbBase :: ExampleDb
1392 dbBase =
1394 exAv
1395 "base"
1396 1
1401 ]
1403 dbNonupgrade :: ExampleDb
1404 dbNonupgrade =
1412 ]
1414 db13 :: ExampleDb
1415 db13 =
1419 ]
1421 -- | A, B, and C have three different dependencies on D that can be set to
1422 -- different versions with qualified constraints. Each version of D can only
1423 -- be depended upon by one version of A, B, or C, so that the versions of A, B,
1424 -- and C in the install plan indicate which version of D was chosen for each
1425 -- dependency. The one-to-one correspondence between versions of A, B, and C and
1426 -- versions of D also prevents linking, which would complicate the solver's
1427 -- behavior.
1428 dbConstraints :: ExampleDb
1429 dbConstraints =
1435 dbStanzaPreferences1 :: ExampleDb
1436 dbStanzaPreferences1 =
1439 ]
1441 dbStanzaPreferences2 :: ExampleDb
1442 dbStanzaPreferences2 =
1444 ]
1446 -- | This is a test case for a bug in stanza preferences (#3930). The solver
1447 -- should be able to install 'A' by enabling 'flag' and disabling testing. When
1448 -- it tries goals in the specified order and prefers testing, it encounters
1449 -- 'unknown-pkg2'. 'unknown-pkg2' is only introduced by testing and 'flag', so
1450 -- the conflict set should contain both of those variables. Before the fix, it
1451 -- only contained 'flag'. The solver backjumped past the choice to disable
1452 -- testing and failed to find the solution.
1454 testStanzaPreference name =
1456 exAv
1457 "A"
1458 1
1459 [ exFlagged
1460 "flag"
1461 []
1463 ]
1464 `withTest` exTest
1465 "test"
1466 [ exFlagged
1467 "flag"
1469 []
1470 ]
1471 goals =
1475 ]
1477 goalOrder goals $
1482 -- | Database with some cycles
1483 --
1484 -- * Simplest non-trivial cycle: A -> B and B -> A
1485 -- * There is a cycle C -> D -> C, but it can be broken by picking the
1486 -- right flag assignment.
1487 db14 :: ExampleDb
1488 db14 =
1494 ]
1496 -- | Cycles through setup dependencies
1497 --
1498 -- The first cycle is unsolvable: package A has a setup dependency on B,
1499 -- B has a regular dependency on A, and we only have a single version available
1500 -- for both.
1501 --
1502 -- The second cycle can be broken by picking different versions: package C-2.0
1503 -- has a setup dependency on D, and D has a regular dependency on C-*. However,
1504 -- version C-1.0 is already available (perhaps it didn't have this setup dep).
1505 -- Thus, we should be able to break this cycle even if we are installing package
1506 -- E, which explicitly depends on C-2.0.
1507 db15 :: ExampleDb
1508 db15 =
1517 ]
1519 -- | Detect a cycle between a package and its setup script.
1520 --
1521 -- This type of cycle can easily occur when v2-build adds default setup
1522 -- dependencies to packages without custom-setup stanzas. For example, cabal
1523 -- adds 'time' as a setup dependency for 'time'. The solver should detect the
1524 -- cycle when it attempts to link the setup and non-setup instances of the
1525 -- package and then choose a different version for the setup dependency.
1527 issue4161 name =
1528 setVerbose $
1530 SolverResult checkFullLog $
1532 where
1533 db :: ExampleDb
1534 db =
1538 ]
1541 checkFullLog =
1543 isInfixOf $
1544 "rejecting: time:setup.time~>time-2.0.0 (cyclic dependencies; "
1547 -- | Packages pkg-A, pkg-B, and pkg-C form a cycle. The solver should backtrack
1548 -- as soon as it chooses the last package in the cycle, to avoid searching parts
1549 -- of the tree that have no solution. Since there is no way to break the cycle,
1550 -- it should fail with an error message describing the cycle.
1552 testCyclicDependencyErrorMessages name =
1553 goalOrder goals $
1555 SolverResult checkFullLog $
1556 Left checkSummarizedLog
1557 where
1558 db :: ExampleDb
1559 db =
1565 ]
1567 -- The solver should backtrack as soon as pkg-A, pkg-B, and pkg-C form a
1568 -- cycle. It shouldn't try pkg-D or pkg-E.
1570 checkFullLog =
1574 checkSummarizedLog =
1575 isInfixOf "rejecting: pkg-C-1.0.0 (cyclic dependencies; conflict set: pkg-A, pkg-B, pkg-C)"
1577 -- Solve for pkg-D and pkg-E last.
1581 -- | Check that the solver can backtrack after encountering the SIR (issue #2843)
1582 --
1583 -- When A and B are installed as independent goals, the single instance
1584 -- restriction prevents B from depending on C. This database tests that the
1585 -- solver can backtrack after encountering the single instance restriction and
1586 -- choose the only valid flag assignment (-flagA +flagB):
1587 --
1588 -- > flagA flagB B depends on
1589 -- > On _ C-*
1590 -- > Off On E-* <-- only valid flag assignment
1591 -- > Off Off D-2.0, C-*
1592 --
1593 -- Since A depends on C-* and D-1.0, and C-1.0 depends on any version of D,
1594 -- we must build C-1.0 against D-1.0. Since B depends on D-2.0, we cannot have
1595 -- C in the transitive closure of B's dependencies, because that would mean we
1596 -- would need two instances of C: one built against D-1.0 and one built against
1597 -- D-2.0.
1598 db16 :: ExampleDb
1599 db16 =
1602 exAv
1603 "B"
1604 1
1606 , exFlagged
1607 "flagA"
1609 [ exFlagged
1610 "flagB"
1613 ]
1614 ]
1619 ]
1621 -- Try to get the solver to backtrack while satisfying
1622 -- reject-unconstrained-dependencies: both the first and last versions of A
1623 -- require packages outside the closed set, so it will have to try the
1624 -- middle one.
1625 db17 :: ExampleDb
1626 db17 =
1632 ]
1634 -- | This test checks that when the solver discovers a constraint on a
1635 -- package's version after choosing to link that package, it can backtrack to
1636 -- try alternative versions for the linked-to package. See pull request #3327.
1637 --
1638 -- When A and B are installed as independent goals, their dependencies on C
1639 -- must be linked. Since C depends on D, A and B's dependencies on D must also
1640 -- be linked. This test fixes the goal order so that the solver chooses D-2 for
1641 -- both 0.D and 1.D before it encounters the test suites' constraints. The
1642 -- solver must backtrack to try D-1 for both 0.D and 1.D.
1644 testIndepGoals2 name =
1645 goalOrder goals $
1646 independentGoals $
1647 enableAllTests $
1650 where
1651 db :: ExampleDb
1652 db =
1658 ]
1661 goals =
1670 ]
1672 -- | Issue #2834
1673 -- When both A and B are installed as independent goals, their dependencies on
1674 -- C must be linked. The only combination of C's flags that is consistent with
1675 -- A and B's dependencies on D is -flagA +flagB. This database tests that the
1676 -- solver can backtrack to find the right combination of flags (requiring F, but
1677 -- not E or G) and apply it to both 0.C and 1.C.
1678 --
1679 -- > flagA flagB C depends on
1680 -- > On _ D-1, E-*
1681 -- > Off On F-* <-- Only valid choice
1682 -- > Off Off D-2, G-*
1683 --
1684 -- The single instance restriction means we cannot have one instance of C
1685 -- built against D-1 and one instance built against D-2; since A depends on
1686 -- D-1, and B depends on C-2, it is therefore important that C cannot depend
1687 -- on any version of D.
1688 db18 :: ExampleDb
1689 db18 =
1693 exAv
1694 "C"
1695 1
1696 [ exFlagged
1697 "flagA"
1699 [ exFlagged
1700 "flagB"
1703 ]
1704 ]
1710 ]
1712 -- | When both values for flagA introduce package B, the solver should be able
1713 -- to choose B before choosing a value for flagA. It should try to choose a
1714 -- version for B that is in the union of the version ranges required by +flagA
1715 -- and -flagA.
1717 commonDependencyLogMessage name =
1719 solverFailure $
1720 isInfixOf $
1724 where
1725 db :: ExampleDb
1726 db =
1728 exAv
1729 "A"
1730 1
1731 [ exFlagged
1732 "flagA"
1735 ]
1737 ]
1739 -- | Test lifting dependencies out of multiple levels of conditionals.
1741 twoLevelDeepCommonDependencyLogMessage name =
1743 solverFailure $
1744 isInfixOf $
1745 "unknown package: B (dependency of A +/-flagA +/-flagB)"
1746 where
1747 db :: ExampleDb
1748 db =
1750 exAv
1751 "A"
1752 1
1753 [ exFlagged
1754 "flagA"
1755 [ exFlagged
1756 "flagB"
1759 ]
1760 [ exFlagged
1761 "flagB"
1764 ]
1765 ]
1766 ]
1768 -- | Test handling nested conditionals that are controlled by the same flag.
1769 -- The solver should treat flagA as introducing 'unknown' with value true, not
1770 -- both true and false. That means that when +flagA causes a conflict, the
1771 -- solver should try flipping flagA to false to resolve the conflict, rather
1772 -- than backjumping past flagA.
1774 testBackjumpingWithCommonDependency name =
1776 where
1777 db :: ExampleDb
1778 db =
1780 exAv
1781 "A"
1782 1
1783 [ exFlagged
1784 "flagA"
1785 [ exFlagged
1786 "flagA"
1789 ]
1791 ]
1793 ]
1795 -- | Tricky test case with independent goals (issue #2842)
1796 --
1797 -- Suppose we are installing D, E, and F as independent goals:
1798 --
1799 -- * D depends on A-* and C-1, requiring A-1 to be built against C-1
1800 -- * E depends on B-* and C-2, requiring B-1 to be built against C-2
1801 -- * F depends on A-* and B-*; this means we need A-1 and B-1 both to be built
1802 -- against the same version of C, violating the single instance restriction.
1803 --
1804 -- We can visualize this DB as:
1805 --
1806 -- > C-1 C-2
1807 -- > /|\ /|\
1808 -- > / | \ / | \
1809 -- > / | X | \
1810 -- > | | / \ | |
1811 -- > | |/ \| |
1812 -- > | + + |
1813 -- > | | | |
1814 -- > | A B |
1815 -- > \ |\ /| /
1816 -- > \ | \ / | /
1817 -- > \| V |/
1818 -- > D F E
1820 testIndepGoals3 name =
1821 goalOrder goals $
1822 independentGoals $
1824 where
1825 db :: ExampleDb
1826 db =
1834 ]
1837 goals =
1848 ]
1850 -- | This test checks that the solver correctly backjumps when dependencies
1851 -- of linked packages are not linked. It is an example where the conflict set
1852 -- from enforcing the single instance restriction is not sufficient. See pull
1853 -- request #3327.
1854 --
1855 -- When A, B, and C are installed as independent goals with the specified goal
1856 -- order, the first choice that the solver makes for E is 0.E-2. Then, when it
1857 -- chooses dependencies for B and C, it links both 1.E and 2.E to 0.E. Finally,
1858 -- the solver discovers C's test's constraint on E. It must backtrack to try
1859 -- 1.E-1 and then link 2.E to 1.E. Backjumping all the way to 0.E does not lead
1860 -- to a solution, because 0.E's version is constrained by A and cannot be
1861 -- changed.
1863 testIndepGoals4 name =
1864 goalOrder goals $
1865 independentGoals $
1866 enableAllTests $
1869 where
1870 db :: ExampleDb
1871 db =
1878 ]
1881 goals =
1891 ]
1893 -- | Test the trace messages that we get when a package refers to an unknown pkg
1894 --
1895 -- TODO: Currently we don't actually test the trace messages, and this particular
1896 -- test still succeeds. The trace can only be verified by hand.
1897 db21 :: ExampleDb
1898 db21 =
1902 ]
1904 -- | A variant of 'db21', which actually fails.
1905 db22 :: ExampleDb
1906 db22 =
1909 ]
1911 -- | Another test for the unknown package message. This database tests that
1912 -- filtering out redundant conflict set messages in the solver log doesn't
1913 -- interfere with generating a message about a missing package (part of issue
1914 -- #3617). The conflict set for the missing package is {A, B}. That conflict set
1915 -- is propagated up the tree to the level of A. Since the conflict set is the
1916 -- same at both levels, the solver only keeps one of the backjumping messages.
1917 db23 :: ExampleDb
1918 db23 =
1920 ]
1922 -- | Database for (unsuccessfully) trying to expose a bug in the handling
1923 -- of implied linking constraints. The question is whether an implied linking
1924 -- constraint should only have the introducing package in its conflict set,
1925 -- or also its link target.
1926 --
1927 -- It turns out that as long as the Single Instance Restriction is in place,
1928 -- it does not matter, because there will always be an option that is failing
1929 -- due to the SIR, which contains the link target in its conflict set.
1930 --
1931 -- Even if the SIR is not in place, if there is a solution, one will always
1932 -- be found, because without the SIR, linking is always optional, but never
1933 -- necessary.
1935 testIndepGoals5 name fixGoalOrder =
1937 FixedGoalOrder -> goalOrder goals test
1938 DefaultGoalOrder -> test
1939 where
1940 test :: SolverTest
1941 test =
1942 independentGoals $
1944 solverSuccess
1947 db :: ExampleDb
1948 db =
1956 ]
1959 goals =
1968 ]
1970 -- | A simplified version of 'testIndepGoals5'.
1972 testIndepGoals6 name fixGoalOrder =
1974 FixedGoalOrder -> goalOrder goals test
1975 DefaultGoalOrder -> test
1976 where
1977 test :: SolverTest
1978 test =
1979 independentGoals $
1981 solverSuccess
1984 db :: ExampleDb
1985 db =
1992 ]
1995 goals =
2002 ]
2004 dbExts1 :: ExampleDb
2005 dbExts1 =
2011 ]
2013 dbLangs1 :: ExampleDb
2014 dbLangs1 =
2018 ]
2020 -- This test checks how the scope of a constraint interacts with qualified goals.
2021 -- If you specify `A == 2`, that top-level should /not/ apply to an independent goal!
2023 testIndepGoals7 name =
2024 constraints [ExVersionConstraint (scopeToplevel "A") (V.thisVersion (V.mkVersion [2, 0, 0]))] $
2025 independentGoals $
2027 -- The more recent version should be picked by the solver. As said
2028 -- above, the top-level A==2 should not apply to an independent goal.
2031 dbIndepGoals78 :: ExampleDb
2032 dbIndepGoals78 =
2036 ]
2038 -- This test checks how the scope of a constraint interacts with qualified goals.
2039 -- If you specify `any.A == 2`, then that should apply inside an independent goal.
2041 testIndepGoals8 name =
2042 constraints [ExVersionConstraint (ScopeAnyQualifier "A") (V.thisVersion (V.mkVersion [2, 0, 0]))] $
2043 independentGoals $
2047 -- | cabal must set enable-exe to false in order to avoid the unavailable
2048 -- dependency. Flags are true by default. The flag choice causes "pkg" to
2049 -- depend on "false-dep".
2051 testBuildable testName unavailableDep =
2052 runTest $
2054 where
2056 db =
2058 exAv
2059 "pkg"
2060 1
2061 [ exFlagged
2062 "enable-exe"
2065 ]
2066 `withExe` exExe
2067 "exe"
2068 [ unavailableDep
2070 ]
2073 ]
2075 -- | cabal must choose -flag1 +flag2 for "pkg", which requires packages
2076 -- "flag1-false" and "flag2-true".
2077 dbBuildable1 :: ExampleDb
2078 dbBuildable1 =
2080 exAv
2081 "pkg"
2082 1
2085 ]
2086 `withExes` [ exExe
2087 "exe1"
2091 ]
2092 , exExe
2093 "exe2"
2095 , ExFlagged
2096 "flag1"
2099 ]
2100 ]
2105 ]
2107 -- | cabal must pick B-2 to avoid the unknown dependency.
2108 dbBuildable2 :: ExampleDb
2109 dbBuildable2 =
2114 `withExe` exExe
2115 "exe"
2118 ]
2120 ]
2122 -- | Package databases for testing @pkg-config@ dependencies.
2123 -- when no pkgconfig db is present, cabal must pick flag1 false and flag2 true to avoid the pkg dependency.
2124 dbPC1 :: ExampleDb
2125 dbPC1 =
2131 ]
2133 -- | Test for the solver's summarized log. The final conflict set is {A, F},
2134 -- though the goal order forces the solver to find the (avoidable) conflict
2135 -- between B and C first. When the solver reaches the backjump limit, it should
2136 -- only show the log to the first conflict. When the backjump limit is high
2137 -- enough to allow an exhaustive search, the solver should make use of the final
2138 -- conflict set to only show the conflict between A and F in the summarized log.
2140 testSummarizedLog testName mbj expectedMsg =
2141 runTest $
2142 maxBackjumps mbj $
2143 goalOrder goals $
2146 where
2147 db =
2153 ]
2158 dbMinimizeConflictSet :: ExampleDb
2159 dbMinimizeConflictSet =
2166 ]
2168 -- | Test that the solver can find a minimal conflict set with
2169 -- --minimize-conflict-set. In the first run, the goal order causes the solver
2170 -- to find that A-3 conflicts with B, A-2 conflicts with C, and A-1 conflicts
2171 -- with D. The full log should show that the original final conflict set is
2172 -- {A, B, C, D}. Then the solver should be able to reduce the conflict set to
2173 -- {A, D}, since all versions of A conflict with D. The summarized log should
2174 -- only mention A and D.
2176 testMinimizeConflictSet testName =
2177 runTest $
2178 minimizeConflictSet $
2179 goalOrder goals $
2180 setVerbose $
2183 where
2185 checkFullLog =
2186 containsInOrder
2196 ]
2198 expectedMsg =
2210 -- | This test uses the same packages and goal order as testMinimizeConflictSet,
2211 -- but it doesn't set --minimize-conflict-set. The solver should print the
2212 -- original final conflict set and the conflict between A and B. It should also
2213 -- suggest rerunning with --minimize-conflict-set.
2215 testNoMinimizeConflictSet testName =
2216 runTest $
2217 goalOrder goals $
2218 setVerbose $
2221 where
2222 expectedMsg =
2236 {-------------------------------------------------------------------------------
2237 Simple databases for the illustrations for the backjumping blog post
2238 -------------------------------------------------------------------------------}
2240 -- | Motivate conflict sets
2241 dbBJ1a :: ExampleDb
2242 dbBJ1a =
2246 ]
2248 -- | Show that we can skip some decisions
2249 dbBJ1b :: ExampleDb
2250 dbBJ1b =
2256 ]
2258 -- | Motivate why both A and B need to be in the conflict set
2259 dbBJ1c :: ExampleDb
2260 dbBJ1c =
2264 ]
2266 -- | Motivate the need for accumulating conflict sets while we walk the tree
2267 dbBJ2 :: ExampleDb
2268 dbBJ2 =
2274 ]
2276 -- | Motivate the need for `QGoalReason`
2277 dbBJ3 :: ExampleDb
2278 dbBJ3 =
2284 ]
2286 -- | `QGOalReason` not unique
2287 dbBJ4 :: ExampleDb
2288 dbBJ4 =
2292 ]
2294 -- | Flags are represented somewhat strangely in the tree
2295 --
2296 -- This example probably won't be in the blog post itself but as a separate
2297 -- bug report (#3409)
2298 dbBJ5 :: ExampleDb
2299 dbBJ5 =
2304 ]
2306 -- | Conflict sets for cycles
2307 dbBJ6 :: ExampleDb
2308 dbBJ6 =
2313 ]
2315 -- | Conflicts not unique
2316 dbBJ7 :: ExampleDb
2317 dbBJ7 =
2322 ]
2324 -- | Conflict sets for SIR (C shared subgoal of independent goals A, B)
2325 dbBJ8 :: ExampleDb
2326 dbBJ8 =
2330 ]
2332 {-------------------------------------------------------------------------------
2333 Databases for build-tool-depends
2334 -------------------------------------------------------------------------------}
2336 -- | Multiple packages depending on exes from 'bt-pkg'.
2337 dbBuildTools :: ExampleDb
2338 dbBuildTools =
2341 exAv
2342 "B"
2343 1
2344 [ exFlagged
2345 "flagB"
2348 ]
2353 exAv
2354 "F"
2355 1
2356 [ exFlagged
2357 "flagF"
2360 ]
2367 ]
2369 -- The solver should never choose an installed package for a build tool
2370 -- dependency.
2372 rejectInstalledBuildToolPackage name =
2374 solverFailure $
2375 isInfixOf $
2376 "rejecting: A:B:exe.B-1.0.0/installed-1 "
2378 where
2379 db :: ExampleDb
2380 db =
2383 ]
2385 -- | This test forces the solver to choose B as a build-tool dependency before
2386 -- it sees the dependency on executable exe2 from B. The solver needs to check
2387 -- that the version that it already chose for B contains the necessary
2388 -- executable. This order causes a different "missing executable" error message
2389 -- than when the solver checks for the executable in the same step that it
2390 -- chooses the build-tool package.
2391 --
2392 -- This case may become impossible if we ever add the executable name to the
2393 -- build-tool goal qualifier. Then this test would involve two qualified goals
2394 -- for B, one for exe1 and another for exe2.
2396 chooseExeAfterBuildToolsPackage shouldSucceed name =
2397 goalOrder goals $
2399 if shouldSucceed
2401 else
2402 solverFailure $
2403 isInfixOf $
2404 "rejecting: A:+flagA (requires executable 'exe2' from A:B:exe.B, "
2406 where
2407 db :: ExampleDb
2408 db =
2410 exAv
2411 "A"
2412 1
2414 , exFlagged
2415 "flagA"
2418 ]
2422 ]
2425 goals =
2429 ]
2431 -- | Test that when one package depends on two executables from another package,
2432 -- both executables must come from the same instance of that package. We could
2433 -- lift this restriction in the future by adding the executable name to the goal
2434 -- qualifier.
2436 requireConsistentBuildToolVersions name =
2438 solverFailure $
2439 isInfixOf $
2442 where
2443 db :: ExampleDb
2444 db =
2446 exAv
2447 "A"
2448 1
2451 ]
2454 ]
2458 -- | This test is similar to the failure case for
2459 -- chooseExeAfterBuildToolsPackage, except that the build tool is unbuildable
2460 -- instead of missing.
2462 chooseUnbuildableExeAfterBuildToolsPackage name =
2464 goalOrder goals $
2466 solverFailure $
2467 isInfixOf $
2468 "rejecting: A:+use-bt2 (requires executable 'bt2' from A:B:exe.B, but "
2470 where
2471 db :: ExampleDb
2472 db =
2474 exAv
2475 "A"
2476 1
2478 , exFlagged
2479 "use-bt2"
2482 ]
2487 ]
2488 ]
2491 goals =
2495 ]
2497 {-------------------------------------------------------------------------------
2498 Databases for legacy build-tools
2499 -------------------------------------------------------------------------------}
2500 dbLegacyBuildTools1 :: ExampleDb
2501 dbLegacyBuildTools1 =
2504 ]
2506 -- Test that a recognized build tool dependency specifies the name of both the
2507 -- package and the executable. This db has no solution.
2508 dbLegacyBuildTools2 :: ExampleDb
2509 dbLegacyBuildTools2 =
2513 ]
2515 -- Test that build-tools on a random thing doesn't matter (only
2516 -- the ones we recognize need to be in db)
2517 dbLegacyBuildTools3 :: ExampleDb
2518 dbLegacyBuildTools3 =
2520 ]
2522 -- Test that we can solve for different versions of executables
2523 dbLegacyBuildTools4 :: ExampleDb
2524 dbLegacyBuildTools4 =
2530 ]
2532 -- Test that exe is not related to library choices
2533 dbLegacyBuildTools5 :: ExampleDb
2534 dbLegacyBuildTools5 =
2539 ]
2541 -- Test that build-tools on build-tools works
2542 dbLegacyBuildTools6 :: ExampleDb
2543 dbLegacyBuildTools6 =
2547 ]
2549 -- Test that build-depends on library/executable package works.
2550 -- Extracted from https://github.com/haskell/cabal/issues/3775
2551 dbIssue3775 :: ExampleDb
2552 dbIssue3775 =
2555 -- executable!
2558 ]
2560 -- A database where the setup depends on something which has a test stanza, does the
2561 -- test stanza get enabled?
2562 dbSetupStanza :: ExampleDb
2563 dbSetupStanza =
2570 ]
2572 -- With the "top-level" qualifier syntax
2573 setupStanzaTest1 :: SolverTest
2574 setupStanzaTest1 = constraints [ExStanzaConstraint (scopeToplevel "B") [TestStanzas]] $ mkTest dbSetupStanza "setupStanzaTest1" ["A"] (solverSuccess [("A", 1), ("B", 1)])
2576 -- With the "any" qualifier syntax
2577 setupStanzaTest2 :: SolverTest
2578 setupStanzaTest2 =
2580 mkTest
2581 dbSetupStanza
2582 "setupStanzaTest2"
2586 -- | Returns true if the second list contains all elements of the first list, in
2587 -- order.