Home|Differences with the last checks|Previous runs

Differences between 064e616 and 256625c (git diff)

Packages now failing:

• 0install-gtk.2.15.2 on 4.07 had its build status changed: passing to failing
• ANSITerminal.0.8.2 on 4.07 had its build status changed: passing to failing
• DAGaml.0.01 on 4.08 had its build status changed: passing to failing
• DAGaml.0.01 on 4.13 had its build status changed: passing to failing
• apron.20151015 on 4.02 had its build status changed: passing to failing
• bap-byteweight-frontend.1.0.0 on 4.04 had its build status changed: partially failing to failing
• coq.8.13.2 on 4.09 had its build status changed: passing to failing
• coq.8.14.0 on 4.06 had its build status changed: passing to failing
• coq.8.14.0 on 4.08 had its build status changed: passing to failing
• coq.8.14.0 on 4.13 had its build status changed: passing to failing
• coq.8.14.1 on 4.05 had its build status changed: passing to failing
• coq.8.14.1 on 4.06 had its build status changed: passing to failing
• coq.8.6 on 4.02 had its build status changed: passing to failing
• coq.8.6.1 on 4.05 had its build status changed: passing to failing
• coq.8.7.1 on 4.03 had its build status changed: passing to failing
• coq.8.7.1 on 4.09 had its build status changed: passing to failing
• coq.8.7.1+1 on 4.02 had its build status changed: passing to failing
• coq.8.7.1+1 on 4.09 had its build status changed: passing to failing
• coq.8.7.1+2 on 4.03 had its build status changed: passing to failing
• depyt.0.1.0 on 4.04 had its build status changed: internal failure to failing
• depyt.0.1.0 on 4.06 had its build status changed: internal failure to failing
• devkit.0.7 on 4.10 had its build status changed: internal failure to failing
• devkit.1.0 on 4.07 had its build status changed: internal failure to failing
• disml.0.2.5 on 4.04 had its build status changed: internal failure to failing
• disml.0.2.5 on 4.06 had its build status changed: internal failure to failing
• disml.0.2.5 on 4.07 had its build status changed: internal failure to failing
• earley.3.0.0 on 5.1 had its build status changed: passing to failing
• herelib.109.35.02 on 4.02 had its build status changed: passing to failing
• hkdf.1.0.4 on 4.02 had its build status changed: not available to failing
• merlin.2.5.0 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.02 had its build status changed: internal failure to failing
• mirage-xen-minios.0.4.1 on 4.04 had its build status changed: internal failure to failing
• mirage-xen-minios.0.7.0 on 4.07 had its build status changed: internal failure to failing
• nbd.0.9.0 on 4.03 had its build status changed: internal failure to failing
• nottui.0.1 on 5.1 had its build status changed: passing to failing
• nottui.0.2 on 5.1 had its build status changed: passing to failing
• nottui.0.3 on 5.1 had its build status changed: passing to failing
• owl.0.3.0 on 4.05 had its build status changed: passing to failing
• ppx_expect.113.33.00 on 4.02 had its build status changed: partially failing to failing
• ppx_test.1.2.0 on 4.02 had its build status changed: passing to failing
• riakc_ppx.3.1.1 on 4.04 had its build status changed: internal failure to failing
• riakc_ppx.3.1.3 on 4.02 had its build status changed: internal failure to failing
• riakc_ppx.3.1.4 on 4.02 had its build status changed: internal failure to failing
• riakc_ppx.3.1.4 on 4.04 had its build status changed: internal failure to failing
• solo5-bindings-hvt.0.6.6 on 4.11 had its build status changed: internal failure to failing
• solo5-bindings-hvt.0.6.9 on 4.08 had its build status changed: internal failure to failing
• tezos-proxy-server-config.13.0 on 4.12 had its build status changed: passing to failing
• tezos-proxy.9.2 on 4.12 had its build status changed: not available to failing
• tezos-proxy.9.7 on 4.12 had its build status changed: not available to failing

Packages now partially failing:

• confero.0.1.1 on 5.1 had its build status changed: passing to partially failing
• cow.2.4.0 on 5.1 had its build status changed: passing to partially failing
• docfd.0.3.3 on 5.1 is now installable. Current state is: partially failing
• docteur-solo5.0.0.4 on 5.1 had its build status changed: not available to partially failing
• docteur-solo5.0.0.5 on 5.1 had its build status changed: not available to partially failing
• docteur-unix.0.0.5 on 5.1 had its build status changed: not available to partially failing
• docteur.0.0.4 on 5.1 had its build status changed: not available to partially failing
• docteur.0.0.5 on 5.1 had its build status changed: not available to partially failing
• git-kv.0.0.1 on 5.1 had its build status changed: not available to partially failing
• git-mirage.3.13.0 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.13.0 on 5.1 is now installable. Current state is: partially failing
• git-unix.3.13.0 on 5.1 is now installable. Current state is: partially failing
• git.3.13.0 on 5.1 is now installable. Current state is: partially failing
• mirage.4.3.6 on 5.1 is now installable. Current state is: partially failing
• nottui-lwt.0.1 on 5.1 had its build status changed: passing to partially failing
• nottui-lwt.0.2 on 5.1 had its build status changed: passing to partially failing
• nottui-lwt.0.3 on 5.1 had its build status changed: passing to partially failing
• nottui-pretty.0.1 on 5.1 had its build status changed: passing to partially failing
• nottui-pretty.0.2 on 5.1 had its build status changed: passing to partially failing
• nottui-pretty.0.3 on 5.1 had its build status changed: passing to partially failing
• pareto.0.3 on 4.13 had its build status changed: passing to partially failing
• ppx_bin_prot.113.24.00 on 4.02 had its build status changed: passing to partially failing
• prob-cache.1.1.0 on 4.02 had its build status changed: internal failure to partially failing
• prob-cache.1.1.0 on 4.04 had its build status changed: internal failure to partially failing
• progress.0.2.1 on 5.1 had its build status changed: passing to partially failing
• z3_tptp.4.10.1 on 4.12 had its build status changed: passing to partially failing
• z3_tptp.4.10.2 on 4.09 had its build status changed: passing to partially failing
• z3_tptp.4.11.2 on 4.12 had its build status changed: passing to partially failing
• z3_tptp.4.9.1 on 4.11 had its build status changed: passing to partially failing
• zarith_stubs_js.v0.14.0 on 4.05 had its build status changed: passing to partially failing

Packages now not available:

• opam-sync-github-prs.1.0.0 on 4.03 had its build status changed: internal failure to not available
• zarith-freestanding.1.4.1 on 4.13 had its build status changed: internal failure to not available
• zarith-freestanding.1.6 on 5.0 had its build status changed: internal failure to not available
• zarith-freestanding.1.7-1 on 4.02 had its build status changed: internal failure to not available
• zarith-freestanding.1.7-1 on 5.1 had its build status changed: internal failure to not available

Packages now failing with an internal failure:

• altgr-ergo.2.4.2 on 4.09 had its build status changed: passing to internal failure
• angstrom-async.0.8.0 on 4.06 had its build status changed: passing to internal failure
• bap-elf.1.0.0 on 4.04 had its build status changed: partially failing to internal failure
• bap-elf.1.5.0 on 4.05 had its build status changed: passing to internal failure
• bap-elf.1.6.0 on 4.07 had its build status changed: passing to internal failure
• bap-elf.2.0.0 on 4.05 had its build status changed: passing to internal failure
• bap-elf.2.0.0 on 4.06 had its build status changed: passing to internal failure
• bap-elf.2.1.0 on 4.07 had its build status changed: passing to internal failure
• bap-elf.2.1.0 on 4.08 had its build status changed: passing to internal failure
• bap-elf.2.2.0 on 4.08 had its build status changed: passing to internal failure
• bap-elf.2.2.0 on 4.09 had its build status changed: passing to internal failure
• bap-elf.2.4.0 on 4.08 had its build status changed: passing to internal failure
• bap-elf.2.4.0 on 4.09 had its build status changed: passing to internal failure
• bap.0.9.8 on 4.02 had its build status changed: partially failing to internal failure
• bitcoinml.0.4.1 on 4.10 had its build status changed: passing to internal failure
• bitcoinml.0.4.1 on 4.12 had its build status changed: passing to internal failure
• bitstring.3.0.0 on 4.02 had its build status changed: passing to internal failure
• bitstring.3.0.0 on 4.04 had its build status changed: passing to internal failure
• bitstring.3.0.0 on 4.06 had its build status changed: passing to internal failure
• bitstring.3.0.0 on 4.07 had its build status changed: passing to internal failure
• bitstring.3.1.0 on 4.05 had its build status changed: passing to internal failure
• bitstring.3.1.1 on 4.02 had its build status changed: passing to internal failure
• bitstring.3.1.1 on 4.06 had its build status changed: passing to internal failure
• bt.0.2 on 4.02 had its build status changed: partially failing to internal failure
• decoders-ezjsonm.0.1.0 on 4.11 had its build status changed: passing to internal failure
• dht.0.1.3 on 4.02 had its build status changed: failing to internal failure
• leaflet.0.1 on 4.08 had its build status changed: passing to internal failure
• leaflet.0.1 on 4.09 had its build status changed: passing to internal failure
• leaflet.0.1 on 4.11 had its build status changed: passing to internal failure
• luv.0.5.1 on 4.14 had its build status changed: passing to internal failure
• minicli.3.0.0 on 4.04 had its build status changed: passing to internal failure
• mirage-console-unix.0.9.9 on 4.02 had its build status changed: passing to internal failure
• mirage-nat.2.0.0 on 4.09 had its build status changed: passing to internal failure
• mirage-net-xen.2.1.2 on 4.08 had its build status changed: passing to internal failure
• mirage-qubes.0.8.1 on 4.09 had its build status changed: passing to internal failure
• monorobot.0.1 on 4.10 had its build status changed: passing to internal failure
• nbd.0.9.0 on 4.04 had its build status changed: failing to internal failure
• not-ocamlfind.0.07.01 on 4.09 had its build status changed: passing to internal failure
• oasis2opam.0.8 on 4.03 had its build status changed: passing to internal failure
• obeam.0.0.3 on 4.05 had its build status changed: passing to internal failure
• obeam.0.0.3 on 4.11 had its build status changed: passing to internal failure
• obeam.0.0.4 on 4.09 had its build status changed: passing to internal failure
• obeam.0.1.0 on 4.04 had its build status changed: passing to internal failure
• obeam.0.1.1 on 4.06 had its build status changed: passing to internal failure
• obeam.0.1.1 on 4.10 had its build status changed: passing to internal failure
• obeam.0.1.1 on 4.11 had its build status changed: passing to internal failure
• obeam.0.1.2 on 4.09 had its build status changed: passing to internal failure
• obeam.0.1.3 on 4.08 had its build status changed: passing to internal failure
• obeam.0.1.3 on 4.12 had its build status changed: passing to internal failure
• obeam.0.1.4 on 4.10 had its build status changed: passing to internal failure
• obeam.0.1.5 on 4.07 had its build status changed: passing to internal failure
• obeam.0.1.5 on 4.08 had its build status changed: passing to internal failure
• obeam.0.1.5 on 4.12 had its build status changed: passing to internal failure
• obelisk.0.1.0 on 5.0 had its build status changed: passing to internal failure
• ocsigen-start.6.0.1 on 4.12 had its build status changed: passing to internal failure
• opam-sync-github-prs.1.0.0 on 4.04 had its build status changed: not available to internal failure
• opentelemetry.0.2 on 4.05 had its build status changed: not available to internal failure
• orakuda.1.1.0 on 4.03 had its build status changed: partially failing to internal failure
• orakuda.1.1.1 on 4.02 had its build status changed: partially failing to internal failure
• osdp.0.5.4 on 4.02 had its build status changed: passing to internal failure
• pixel_pusher.1.0 on 4.08 had its build status changed: passing to internal failure
• pixel_pusher.1.1 on 4.09 had its build status changed: passing to internal failure
• pla.1.4 on 4.11 had its build status changed: passing to internal failure
• prob-cache.1.0.0 on 4.02 had its build status changed: partially failing to internal failure
• riakc_ppx.3.1.1 on 4.02 had its build status changed: failing to internal failure
• toml.2.1.0 on 4.05 had its build status changed: passing to internal failure
• ws.0.1 on 4.12 had its build status changed: passing to internal failure
• zarith_stubs_js.v0.12.0 on 4.03 had its build status changed: not available to internal failure

Packages now passing:

• antic.0.2.3 on 4.10 is now installable. Current state is: passing
• antic.0.2.3 on 4.11 is now installable. Current state is: passing
• antic.0.2.3 on 4.12 is now installable. Current state is: passing
• antic.0.2.3 on 4.13 is now installable. Current state is: passing
• antic.0.2.3 on 4.14 is now installable. Current state is: passing
• antic.0.2.3 on 5.0 is now installable. Current state is: passing
• antic.0.2.3 on 5.1 is now installable. Current state is: passing
• arb.0.2.3 on 4.10 is now installable. Current state is: passing
• arb.0.2.3 on 4.11 is now installable. Current state is: passing
• arb.0.2.3 on 4.12 is now installable. Current state is: passing
• arb.0.2.3 on 4.13 is now installable. Current state is: passing
• arb.0.2.3 on 4.14 is now installable. Current state is: passing
• arb.0.2.3 on 5.0 is now installable. Current state is: passing
• arb.0.2.3 on 5.1 is now installable. Current state is: passing
• bap-abi.1.3.0 on 4.02 had its build status changed: partially failing to passing
• bap-beagle.1.2.0 on 4.04 had its build status changed: internal failure to passing
• bap-elf.1.6.0 on 4.04 had its build status changed: internal failure to passing
• bap-elf.1.6.0 on 4.05 had its build status changed: internal failure to passing
• bap-elf.1.6.0 on 4.06 had its build status changed: internal failure to passing
• bap-elf.2.0.0 on 4.04 had its build status changed: internal failure to passing
• bap-elf.2.1.0 on 4.09 had its build status changed: internal failure to passing
• bap-elf.2.3.0 on 4.09 had its build status changed: internal failure to passing
• bap-elf.2.4.0 on 4.10 had its build status changed: internal failure to passing
• bap-elf.2.4.0 on 4.11 had its build status changed: internal failure to passing
• bap-mc.1.0.0 on 4.02 had its build status changed: partially failing to passing
• bencode.1.0.2 on 4.14 had its build status changed: internal failure to passing
• bitstring.3.0.0 on 4.03 had its build status changed: internal failure to passing
• bitstring.3.0.0 on 4.05 had its build status changed: internal failure to passing
• bitstring.3.0.0 on 4.09 had its build status changed: internal failure to passing
• bitstring.3.0.0 on 4.11 had its build status changed: internal failure to passing
• bitstring.3.0.0 on 4.12 had its build status changed: internal failure to passing
• bitstring.3.1.0 on 4.07 had its build status changed: internal failure to passing
• bitstring.3.1.0 on 4.12 had its build status changed: internal failure to passing
• bitstring.3.1.1 on 4.03 had its build status changed: internal failure to passing
• bitstring.3.1.1 on 4.04 had its build status changed: internal failure to passing
• bitstring.3.1.1 on 4.10 had its build status changed: internal failure to passing
• bogue-tutorials.0.1.0 on 4.08 is now installable. Current state is: passing
• bogue-tutorials.0.1.0 on 4.09 is now installable. Current state is: passing
• bogue-tutorials.0.1.0 on 4.10 is now installable. Current state is: passing
• bogue-tutorials.0.1.0 on 4.11 is now installable. Current state is: passing
• bogue-tutorials.0.1.0 on 4.12 is now installable. Current state is: passing
• bogue-tutorials.0.1.0 on 4.13 is now installable. Current state is: passing
• bogue-tutorials.0.1.0 on 4.14 is now installable. Current state is: passing
• bogue-tutorials.0.1.0 on 5.0 is now installable. Current state is: passing
• bogue-tutorials.0.1.0 on 5.1 is now installable. Current state is: passing
• calcium.0.2.3 on 4.10 is now installable. Current state is: passing
• calcium.0.2.3 on 4.11 is now installable. Current state is: passing
• calcium.0.2.3 on 4.12 is now installable. Current state is: passing
• calcium.0.2.3 on 4.13 is now installable. Current state is: passing
• calcium.0.2.3 on 4.14 is now installable. Current state is: passing
• calcium.0.2.3 on 5.0 is now installable. Current state is: passing
• calcium.0.2.3 on 5.1 is now installable. Current state is: passing
• camlp5-buildscripts.0.02 on 4.10 is now installable. Current state is: passing
• camlp5-buildscripts.0.02 on 4.11 is now installable. Current state is: passing
• camlp5-buildscripts.0.02 on 4.12 is now installable. Current state is: passing
• camlp5-buildscripts.0.02 on 4.13 is now installable. Current state is: passing
• camlp5-buildscripts.0.02 on 4.14 is now installable. Current state is: passing
• camlp5-buildscripts.0.02 on 5.0 is now installable. Current state is: passing
• camlp5-buildscripts.0.02 on 5.1 is now installable. Current state is: passing
• captureio.0.1.1 on 4.04 had its build status changed: internal failure to passing
• cca.0.7 on 4.14 is now installable. Current state is: passing
• chamo.4.0 on 4.12 is now installable. Current state is: passing
• chamo.4.0 on 4.13 is now installable. Current state is: passing
• chamo.4.0 on 4.14 is now installable. Current state is: passing
• chamo.4.0 on 5.0 is now installable. Current state is: passing
• cid.0.1.0 on 4.08 is now installable. Current state is: passing
• cid.0.1.0 on 4.09 is now installable. Current state is: passing
• cid.0.1.0 on 4.10 is now installable. Current state is: passing
• cid.0.1.0 on 4.11 is now installable. Current state is: passing
• cid.0.1.0 on 4.12 is now installable. Current state is: passing
• cid.0.1.0 on 4.13 is now installable. Current state is: