ocaml-opam / opam-rt Goto Github PK

take any local git repository:

• initialize an OPAM instance using the repository
• for each of the commits: revert to that commit, opam update and check that the file are indeed the same ones

from @avsm

Louis, can we add a Core upgrade test to opam-rt? Do an installation
from an older snapshot of opam-repository, and attempt an upgrade. It
would probably need a "exit on brute-force" environment variable for
the solver though.

Definitely. I'll add that. Probably by packing two snapshots of the repo, and playing the upgrade. It will show how easy it is to get in trouble, solver-wise. If finding two relevant snapshots turns out to be difficult (which would be a good thing) we can ask the people who had the problem the timestamps of their upgrades to replay the same scenario.

take two copy of a local git repositories:

• initialize an OPAM instance with these 2 repositories
• choose randomly two commits, and checkout the two repositories to these commits
• compute (independently of OPAM) the correct package priorities
• compute (independently of OPAM) the expected OPAM global state
• check that this is indeed the current state of OPAM
• and do this again, and again, for various combinations of the commits

• install a dev package
• modify the url file of the package
• check that opam update resets the dev cache and deletes any archive file

• install a dev package
• update the package repository
• check that opam update detects the update

• Pin a package to a given path
• Install the package
• Update the pinned path

Since the file opam.install does not contain a META file but opam-lib.install does, the library will be known as opam-lib to ocamlfind. I believe that the first line of the Makefile must be fixed.