anchor.diff:       race_conditions,
        behaviours,
        unmatched_returns,
  -     overspecs,
  -     underspecs,
  -     specdiffs].
  +     underspecs].
  
positive.code:     ec_talk:say("Doing plt for project apps ..."),
      update_dep_plt(Config0, State0, ProjectPlt, AppList),
  
      WarningTypes = Config0:match(plt_warnings, default_warnings()),
      Paths = [filename:join(Path, "ebin") ||
                #app{path=Path} <- AppList],
      Opts = [{analysis_type, succ_typings},
  
negative.code:             useful information. You can get around this by asking the
              dialyzer task to ignore certain applications. Do this in
              your build config with the following entry.  <break>  <break>
              {dialyzer_ignore, [some_app1, some_app2]}.  <break>  <break>
              The downside, of course, is figuring out which apps actually
              have the problem. This task tries to help by printing out a
              list of applications that where under analysis when the blowup
  