This project is mirrored from Pull mirroring updated .
  1. 30 Jul, 2016 1 commit
    • kristenk's avatar
      Avoid filtering the solver log before 'showMessages'. · f2d02983
      kristenk authored
      Previously, the solver filtered out redundant backjumping messages twice, once
      in 'Log.logToProgress' and again in 'Message.showMessages. However,
      'showMessages' relied on the backjumping messages to determine where to insert
      messages about missing packages. This led to missing "unknown package" messages
      (part of issue #3617).
      This commit removes the filtering in 'logToProgress', because it was redundant.
  2. 28 Jul, 2016 2 commits
  3. 27 Jul, 2016 5 commits
  4. 26 Jul, 2016 20 commits
  5. 25 Jul, 2016 12 commits
    • ttuegel's avatar
      Merge pull request #3610 from ttuegel/lbi-coverage · f9e74632
      ttuegel authored
      LocalBuildInfo: combine profiling settings, track program coverage
    • Duncan Coutts's avatar
      More windows fixes · e80316be
      Duncan Coutts authored
    • Duncan Coutts's avatar
      Fix name shaddowing issue in Graph tests · 35bc4bc7
      Duncan Coutts authored
    • Edward Z. Yang's avatar
      Try to fix Windows build again. · fa44f19f
      Edward Z. Yang authored and Duncan Coutts's avatar Duncan Coutts committed
      Signed-off-by: default avatarEdward Z. Yang <>
    • Duncan Coutts's avatar
      Remove the now-unused InstallPlan type args for result and failure · 0bb80be2
      Duncan Coutts authored
      These were used previously for the Installed and Failed package states,
      but these states are now gone.
      Importantly this now means that we can have a serialisable InstallPlan
      without the failure types having to be serialisable. This means we can
      use things like SomeException which is not serialisable. Since the
      traversal is done separately, the result of the traversal contains the
      failure values, but this result set does not have to be serialised.
    • Duncan Coutts's avatar
      Remove the now unused PlanPackage states · 7cb0844b
      Duncan Coutts authored
      We now just have the initial states, PreExisting and Configured. The
      Processing, Installed and Failed states are gone. We now do traversals
      separately from the InstallPlan, so we no longer need these states.
    • Duncan Coutts's avatar
      Rename the new InstallPlan.{ready,completed,failed} · 86853416
      Duncan Coutts authored
      Rename from prime' versions to the normal names, now that the old ones
      have been removed.
    • Duncan Coutts's avatar
      Remove the old InstallPlan.ready · f28cf318
      Duncan Coutts authored
      There were two uses other than excuteInstallPlan. The new ready impl can
      be used in both these cases, allowing the old one to be removed.
    • Duncan Coutts's avatar
      Remove a number of now-unused InstallPlan operations · 713af703
      Duncan Coutts authored
      These were the primitives used by executeInstallPlan to change the
      package states to Processing, Installed, Failed etc.
      The 'ready' is still used in a couple other places, so those need to be
      modified before the old 'ready' can be removed.
    • Duncan Coutts's avatar
      Convert the old install code to use InstallPlan.execute · 448714b8
      Duncan Coutts authored
      Redefine the local executeInstallPlan util in terms of
      InstallPlan.execute. Of course now executeInstallPlan returns
      BuildResults instead of an upated InstallPlan. This requires changes in
      all the code that looks at the result of the build execution, including
      console error reporting, build reports, symlinks etc.
    • Duncan Coutts's avatar
      Convert new-build to use InstallPlan.execute · 97cff5c0
      Duncan Coutts authored
      Eliminate the local executeInstallPlan. The main change is that the new
      execute returns BuildResults instead of an upated InstallPlan. This has
      a few knock-on conseuqnces for the code that looks at the result of the
      build execution.
      Currently we don't actually do that much with the results in the
      new-build code path (though we should) so there's less disruption than
      one might imagine. The biggest change is in the integration tests which
      do inspect the execution result to check things worked or didn't work as
      The equivalent change for the old build code path will be more
      disruptive since it does a lot of stuff with the execution results.
    • Duncan Coutts's avatar
      Add InstallPlan.execute plus tests · 31be24fa
      Duncan Coutts authored
      This is intended to replace a couple existing executeInstallPlan
      The tests check that execute visits packages in reverse topological
      order, for both serial and parallel job control. There's also a check
      that serial execute and executionOrder use exactly the same order.