luet/pkg/solver
Ettore Di Giacinto 40fc948c6e Stabilize tests after changes
With BuildWorld() we get more results back (now we return the whole
model, including the false assertions).

Besides, now solving with BuildWorld() detects an invalid case:
when we supply a provided, the definitionDB shouldn't explictly supply
also the package that has to be provided. This would cause to 'shadow'
packages between repositories.

The test was invalid before, and shouldn't have contained A1. Moved the
test to Pending to inspect it further in subsequent dev iterations
2021-01-11 23:35:18 +01:00
..
benchmark_test.go Add install benchmark test for solver 2020-10-30 22:20:08 +01:00
decoder_test.go Revert "Revert "Stabilize ordering graph"" 2020-11-02 15:43:35 +01:00
decoder.go Bump topsort 2020-11-03 17:20:52 +01:00
parallel_test.go Stabilize tests after changes 2021-01-11 23:35:18 +01:00
parallel.go Use BuildWorld() instead of BuildPartialWorld() in solver.Solve 2021-01-11 20:11:51 +01:00
resolver_test.go Stabilize tests after changes 2021-01-11 23:35:18 +01:00
resolver.go Introduce Packages for []Package 2020-04-04 14:29:08 +02:00
solver_suite_test.go Support logging level and spinner customization 2020-01-01 13:43:22 +01:00
solver_test.go Stabilize tests after changes 2021-01-11 23:35:18 +01:00
solver.go Stabilize tests after changes 2021-01-11 23:35:18 +01:00