opam-health-check diff

Home|Differences with the last checks|Previous runs

Differences between 01c350d and c4b7df5 (git diff)

Packages now failing:

advi.2.0.0 on 5.0 is now installable. Current state is: failing
advi.2.0.0 on 5.1 is now installable. Current state is: failing
ahrocksdb.0.2.2 on 4.08 had its build status changed: passing to failing
ahrocksdb.0.2.2 on 4.09 had its build status changed: passing to failing
ahrocksdb.0.2.2 on 4.10 had its build status changed: passing to failing
ahrocksdb.0.2.2 on 4.11 had its build status changed: passing to failing
ahrocksdb.0.2.2 on 4.12 had its build status changed: passing to failing
ahrocksdb.0.2.2 on 4.13 had its build status changed: passing to failing
ahrocksdb.0.2.2 on 4.14 is now installable. Current state is: failing
ahrocksdb.0.2.2 on 5.0 is now installable. Current state is: failing
ahrocksdb.0.2.2 on 5.1 is now installable. Current state is: failing
alt-ergo-free.2.0.0 on 4.08 had its build status changed: passing to failing
alt-ergo-free.2.0.0 on 4.10 had its build status changed: passing to failing
alt-ergo-free.2.0.0 on 4.12 had its build status changed: passing to failing
alt-ergo-free.2.0.0 on 4.13 had its build status changed: passing to failing
alt-ergo-free.2.0.0 on 4.14 is now installable. Current state is: failing
alt-ergo.1.30 on 4.08 had its build status changed: passing to failing
alt-ergo.1.30 on 4.09 had its build status changed: passing to failing
alt-ergo.1.30 on 4.10 had its build status changed: passing to failing
alt-ergo.1.30 on 4.11 had its build status changed: passing to failing
alt-ergo.1.30 on 4.12 had its build status changed: passing to failing
alt-ergo.1.30 on 4.13 had its build status changed: passing to failing
alt-ergo.1.30 on 4.14 is now installable. Current state is: failing
alt-ergo.2.0.0 on 4.09 had its build status changed: passing to failing
alt-ergo.2.0.0 on 4.11 had its build status changed: passing to failing
alt-ergo.2.0.0 on 4.12 had its build status changed: passing to failing
alt-ergo.2.0.0 on 4.14 is now installable. Current state is: failing
alt-ergo.2.1.0 on 4.08 had its build status changed: passing to failing
alt-ergo.2.1.0 on 4.10 had its build status changed: passing to failing
alt-ergo.2.1.0 on 4.11 had its build status changed: passing to failing
alt-ergo.2.1.0 on 4.12 had its build status changed: passing to failing
alt-ergo.2.1.0 on 4.13 had its build status changed: passing to failing
alt-ergo.2.2.0 on 4.10 had its build status changed: passing to failing
alt-ergo.2.2.0 on 4.12 had its build status changed: passing to failing
alt-ergo.2.2.0 on 4.13 had its build status changed: passing to failing
alt-ergo.2.2.0 on 4.14 is now installable. Current state is: failing
archimedes.0.4.18 on 5.0 is now installable. Current state is: failing
aws-s3-lwt.4.2.0 on 4.08 had its build status changed: passing to failing
aws-s3-lwt.4.2.0 on 4.09 had its build status changed: passing to failing
aws-s3-lwt.4.3.0 on 4.08 had its build status changed: passing to failing
aws-s3-lwt.4.3.0 on 4.09 had its build status changed: passing to failing
bap-ghidra.2.4.0 on 4.08 is now installable. Current state is: failing
bap-ghidra.2.4.0 on 4.09 is now installable. Current state is: failing
bap-ghidra.2.4.0 on 4.10 is now installable. Current state is: failing
bap-ghidra.2.4.0 on 4.11 is now installable. Current state is: failing
bap-ghidra.2.4.0 on 4.12 is now installable. Current state is: failing
bap-ghidra.2.4.0 on 4.13 is now installable. Current state is: failing
bap-ghidra.2.4.0 on 4.14 is now installable. Current state is: failing
bap-ghidra.2.5.0 on 4.08 is now installable. Current state is: failing
bap-ghidra.2.5.0 on 4.09 is now installable. Current state is: failing
bap-ghidra.2.5.0 on 4.10 is now installable. Current state is: failing
bap-ghidra.2.5.0 on 4.11 is now installable. Current state is: failing
bap-ghidra.2.5.0 on 4.12 is now installable. Current state is: failing
bap-ghidra.2.5.0 on 4.13 is now installable. Current state is: failing
bap-ghidra.2.5.0 on 4.14 is now installable. Current state is: failing
binaryen.0.1.0 on 4.08 had its build status changed: passing to failing
binaryen.0.1.0 on 4.09 had its build status changed: passing to failing
binaryen.0.1.0 on 4.10 had its build status changed: passing to failing
binaryen.0.1.0 on 4.11 had its build status changed: passing to failing
binaryen.0.1.0 on 4.12 had its build status changed: passing to failing
binaryen.0.1.0 on 4.13 had its build status changed: passing to failing
binaryen.0.1.0 on 4.14 is now installable. Current state is: failing
binaryen.0.1.0 on 5.0 is now installable. Current state is: failing
binaryen.0.1.0 on 5.1 is now installable. Current state is: failing
binaryen.0.2.1 on 4.08 had its build status changed: passing to failing
binaryen.0.2.1 on 4.09 had its build status changed: passing to failing
binaryen.0.2.1 on 4.10 had its build status changed: passing to failing
binaryen.0.2.1 on 4.11 had its build status changed: passing to failing
binaryen.0.2.1 on 4.12 had its build status changed: passing to failing
binaryen.0.2.1 on 4.13 had its build status changed: passing to failing
binaryen.0.2.1 on 4.14 is now installable. Current state is: failing
binaryen.0.2.1 on 5.0 is now installable. Current state is: failing
binaryen.0.2.1 on 5.1 is now installable. Current state is: failing
binaryen.0.2.2 on 4.08 had its build status changed: passing to failing
binaryen.0.2.2 on 4.09 had its build status changed: passing to failing
binaryen.0.2.2 on 4.10 had its build status changed: passing to failing
binaryen.0.2.2 on 4.11 had its build status changed: passing to failing
binaryen.0.2.2 on 4.12 had its build status changed: passing to failing
binaryen.0.2.2 on 4.13 had its build status changed: passing to failing
binaryen.0.2.2 on 4.14 is now installable. Current state is: failing
binaryen.0.2.2 on 5.0 is now installable. Current state is: failing
binaryen.0.2.2 on 5.1 is now installable. Current state is: failing
binaryen.0.2.3 on 4.08 had its build status changed: passing to failing
binaryen.0.2.3 on 4.09 had its build status changed: passing to failing
binaryen.0.2.3 on 4.10 had its build status changed: passing to failing
binaryen.0.2.3 on 4.11 had its build status changed: passing to failing
binaryen.0.2.3 on 4.12 had its build status changed: passing to failing
binaryen.0.2.3 on 4.13 had its build status changed: passing to failing
binaryen.0.2.3 on 4.14 is now installable. Current state is: failing
binaryen.0.2.3 on 5.0 is now installable. Current state is: failing
binaryen.0.2.3 on 5.1 is now installable. Current state is: failing
binaryen.0.3.0 on 4.08 had its build status changed: passing to failing
binaryen.0.3.0 on 4.09 had its build status changed: passing to failing
binaryen.0.3.0 on 4.10 had its build status changed: passing to failing
binaryen.0.3.0 on 4.11 had its build status changed: passing to failing
bisect.1.3.1 on 5.0 is now installable. Current state is: failing
bitmasks.1.4.0 on 5.1 is now installable. Current state is: failing
bitwuzla-bin.1.0.0 on 4.08 is now installable. Current state is: failing
bitwuzla-bin.1.0.0 on 4.09 is now installable. Current state is: failing
bitwuzla-bin.1.0.0 on 4.10 is now installable. Current state is: failing
bitwuzla-bin.1.0.0 on 4.11 is now installable. Current state is: failing
bitwuzla-bin.1.0.0 on 4.12 is now installable. Current state is: failing
bitwuzla-bin.1.0.0 on 4.13 is now installable. Current state is: failing
bitwuzla-bin.1.0.0 on 4.14 is now installable. Current state is: failing
bitwuzla-bin.1.0.0 on 5.0 is now installable. Current state is: failing
bitwuzla-bin.1.0.0 on 5.1 is now installable. Current state is: failing
blake3.0.1 on 4.14 is now installable. Current state is: failing
blake3.0.1 on 5.0 is now installable. Current state is: failing
blake3.0.1 on 5.1 is now installable. Current state is: failing
calculon.0.3 on 4.08 had its build status changed: passing to failing
calculon.0.3 on 4.09 had its build status changed: passing to failing
calculon.0.3 on 4.10 had its build status changed: passing to failing
calculon.0.3 on 4.11 had its build status changed: passing to failing
calculon.0.4 on 4.08 had its build status changed: passing to failing
calculon.0.4 on 4.09 had its build status changed: passing to failing
calculon.0.4 on 4.10 had its build status changed: passing to failing
calculon.0.4 on 4.11 had its build status changed: passing to failing
camllib.1.3.3 on 5.0 is now installable. Current state is: failing
camllib.1.3.3 on 5.1 is now installable. Current state is: failing
camlmix.1.3.0 on 5.0 is now installable. Current state is: failing
camlmix.1.3.0 on 5.1 is now installable. Current state is: failing
cca.0.1 on 4.11 had its build status changed: passing to failing
cca.0.1 on 4.12 had its build status changed: passing to failing
cca.0.2 on 4.11 had its build status changed: passing to failing
cca.0.2 on 4.12 had its build status changed: passing to failing
cca.0.2 on 4.13 had its build status changed: not available to failing
cca.0.2 on 4.14 is now installable. Current state is: failing
cca.0.4 on 4.11 is now installable. Current state is: failing
cca.0.4 on 4.12 is now installable. Current state is: failing
cca.0.4 on 4.13 is now installable. Current state is: failing
cca.0.4 on 4.14 is now installable. Current state is: failing
cca.0.5 on 4.11 is now installable. Current state is: failing
cca.0.5 on 4.12 is now installable. Current state is: failing
cca.0.5 on 4.13 is now installable. Current state is: failing
cca.0.5 on 4.14 is now installable. Current state is: failing
cca.0.6.2 on 4.14 is now installable. Current state is: failing
cca.0.7 on 4.14 is now installable. Current state is: failing
charrua-unix.1.0.0 on 4.08 had its build status changed: passing to failing
charrua-unix.1.0.0 on 4.09 had its build status changed: passing to failing
charrua-unix.1.0.0 on 4.10 had its build status changed: passing to failing
charrua-unix.1.0.0 on 4.11 had its build status changed: passing to failing
charset.0.1.0 on 5.1 is now installable. Current state is: failing
class_group_vdf.0.0.2 on 4.08 is now installable. Current state is: failing
class_group_vdf.0.0.2 on 4.09 is now installable. Current state is: failing
class_group_vdf.0.0.2 on 4.10 is now installable. Current state is: failing
class_group_vdf.0.0.2 on 4.11 is now installable. Current state is: failing
class_group_vdf.0.0.2 on 4.12 is now installable. Current state is: failing
class_group_vdf.0.0.2 on 4.13 is now installable. Current state is: failing
class_group_vdf.0.0.2 on 4.14 is now installable. Current state is: failing
class_group_vdf.0.0.2 on 5.0 is now installable. Current state is: failing
class_group_vdf.0.0.2 on 5.1 is now installable. Current state is: failing
class_group_vdf.0.0.3 on 4.08 is now installable. Current state is: failing
class_group_vdf.0.0.3 on 4.09 is now installable. Current state is: failing
class_group_vdf.0.0.3 on 4.10 is now installable. Current state is: failing
class_group_vdf.0.0.3 on 4.11 is now installable. Current state is: failing
class_group_vdf.0.0.3 on 4.12 is now installable. Current state is: failing
class_group_vdf.0.0.3 on 4.13 is now installable. Current state is: failing
class_group_vdf.0.0.3 on 4.14 is now installable. Current state is: failing
codept.0.11.0 on 4.08 is now installable. Current state is: failing
codept.0.11.0 on 4.09 is now installable. Current state is: failing
codept.0.11.0 on 4.10 is now installable. Current state is: failing
codept.0.11.0 on 4.11 is now installable. Current state is: failing
codept.0.11.0 on 4.12 is now installable. Current state is: failing
codept.0.11.0 on 4.13 is now installable. Current state is: failing
cohttp-lwt-jsoo.2.1.3 on 4.08 had its build status changed: passing to failing
cohttp-lwt.1.0.0 on 4.08 had its build status changed: passing to failing
cohttp-lwt.1.0.0 on 4.09 had its build status changed: passing to failing
cohttp-lwt.1.0.0 on 4.10 had its build status changed: passing to failing
cohttp-lwt.1.0.0 on 4.11 had its build status changed: passing to failing
cohttp-lwt.1.0.0 on 4.12 had its build status changed: passing to failing
coin.0.1.0 on 4.08 had its build status changed: passing to failing
coin.0.1.1 on 4.08 had its build status changed: passing to failing
conf-libclang.12 on 4.08 had its build status changed: passing to failing
conf-libclang.12 on 4.09 had its build status changed: passing to failing
conf-libclang.12 on 4.10 had its build status changed: passing to failing
conf-libclang.12 on 4.11 had its build status changed: passing to failing
conf-libclang.12 on 4.12 had its build status changed: passing to failing
conf-libclang.12 on 4.13 had its build status changed: passing to failing
conf-libclang.12 on 4.14 is now installable. Current state is: failing
conf-libclang.12 on 5.0 is now installable. Current state is: failing
conf-libclang.12 on 5.1 is now installable. Current state is: failing
conf-libclang.15 on 4.08 is now installable. Current state is: failing
conf-libclang.15 on 4.09 is now installable. Current state is: failing
conf-libclang.15 on 4.10 is now installable. Current state is: failing
conf-libclang.15 on 4.11 is now installable. Current state is: failing
conf-libclang.15 on 4.12 is now installable. Current state is: failing
conf-libclang.15 on 4.13 is now installable. Current state is: failing
conf-libclang.15 on 4.14 is now installable. Current state is: failing
conf-libclang.15 on 5.0 is now installable. Current state is: failing
conf-libclang.15 on 5.1 is now installable. Current state is: failing
conf-trexio.0.1 on 4.08 is now installable. Current state is: failing
conf-trexio.0.1 on 4.09 is now installable. Current state is: failing
conf-trexio.0.1 on 4.10 is now installable. Current state is: failing
conf-trexio.0.1 on 4.11 is now installable. Current state is: failing
conf-trexio.0.1 on 4.12 is now installable. Current state is: failing
conf-trexio.0.1 on 4.13 is now installable. Current state is: failing
conf-trexio.0.1 on 4.14 is now installable. Current state is: failing
conf-trexio.0.1 on 5.0 is now installable. Current state is: failing
conf-trexio.0.1 on 5.1 is now installable. Current state is: failing
config-file.1.1 on 5.0 is now installable. Current state is: failing
config-file.1.2 on 5.0 is now installable. Current state is: failing
config-file.1.2.1 on 5.0 is now installable. Current state is: failing
cryptohash.0.1 on 5.0 is now installable. Current state is: failing
datakit-client-9p.0.12.0 on 4.12 had its build status changed: passing to failing
datakit-client-9p.0.12.0 on 4.13 had its build status changed: not available to failing
datakit-client-9p.0.12.2 on 4.08 had its build status changed: passing to failing
datakit-client-9p.0.12.2 on 4.09 had its build status changed: passing to failing
datakit-client-9p.0.12.2 on 4.10 had its build status changed: passing to failing
datakit-client-9p.0.12.2 on 4.11 had its build status changed: passing to failing
datakit-client-9p.0.12.2 on 4.12 had its build status changed: passing to failing
datakit-client-9p.0.12.2 on 4.13 had its build status changed: not available to failing
datakit-client-9p.0.12.3 on 4.08 had its build status changed: passing to failing
datakit-client-9p.0.12.3 on 4.09 had its build status changed: passing to failing
datakit-client-9p.0.12.3 on 4.10 had its build status changed: passing to failing
datakit-client-9p.0.12.3 on 4.11 had its build status changed: passing to failing
datakit-client-9p.0.12.3 on 4.12 had its build status changed: passing to failing
datakit-client-9p.0.12.3 on 4.13 had its build status changed: not available to failing
datakit-client-9p.1.0.0 on 4.08 had its build status changed: passing to failing
datakit-client-9p.1.0.0 on 4.09 had its build status changed: passing to failing
datakit-client-9p.1.0.0 on 4.10 had its build status changed: passing to failing
datakit-client-9p.1.0.0 on 4.11 had its build status changed: passing to failing
datakit-client-9p.1.0.0 on 4.12 had its build status changed: passing to failing
datakit-client-9p.1.0.0 on 4.13 had its build status changed: not available to failing
datalog.0.1 on 5.1 is now installable. Current state is: failing
datalog.0.2 on 5.1 is now installable. Current state is: failing
datalog.0.3 on 5.1 is now installable. Current state is: failing
datalog.0.3.1 on 5.1 is now installable. Current state is: failing
devkit.0.6 on 4.08 had its build status changed: passing to failing
devkit.0.6 on 4.09 had its build status changed: passing to failing
devkit.0.6 on 4.10 had its build status changed: passing to failing
devkit.0.6 on 4.11 had its build status changed: passing to failing
devkit.0.7 on 4.08 had its build status changed: passing to failing
devkit.0.7 on 4.09 had its build status changed: passing to failing
devkit.0.7 on 4.10 had its build status changed: passing to failing
devkit.0.7 on 4.11 had its build status changed: passing to failing
devkit.1.0 on 4.08 had its build status changed: passing to failing
devkit.1.0 on 4.09 had its build status changed: passing to failing
devkit.1.0 on 4.10 had its build status changed: passing to failing
devkit.1.0 on 4.11 had its build status changed: passing to failing
distributed.0.6.0 on 5.0 is now installable. Current state is: failing
distributed.0.6.0 on 5.1 is now installable. Current state is: failing
dune-release.1.1.0 on 4.08 had its build status changed: passing to failing
dune-release.1.1.0 on 4.09 had its build status changed: passing to failing
dune-release.1.1.0 on 4.10 had its build status changed: passing to failing
dune-release.1.1.0 on 4.11 had its build status changed: passing to failing
dune-release.1.2.0 on 4.08 had its build status changed: passing to failing
dune-release.1.2.0 on 4.09 had its build status changed: passing to failing
dune-release.1.2.0 on 4.10 had its build status changed: passing to failing
dune-release.1.2.0 on 4.11 had its build status changed: passing to failing
easy_logging_yojson.0.4 on 4.08 had its build status changed: passing to failing
easy_logging_yojson.0.4 on 4.09 had its build status changed: passing to failing
easy_logging_yojson.0.4 on 4.10 had its build status changed: passing to failing
easy_logging_yojson.0.4 on 4.11 had its build status changed: passing to failing
easy_logging_yojson.0.4 on 4.12 had its build status changed: passing to failing
easy_logging_yojson.0.5 on 4.08 had its build status changed: passing to failing
easy_logging_yojson.0.5 on 4.09 had its build status changed: passing to failing
easy_logging_yojson.0.5 on 4.10 had its build status changed: passing to failing
easy_logging_yojson.0.5 on 4.11 had its build status changed: passing to failing
easy_logging_yojson.0.5 on 4.12 had its build status changed: passing to failing
easy_logging_yojson.0.5.2 on 4.08 had its build status changed: passing to failing
easy_logging_yojson.0.5.2 on 4.09 had its build status changed: passing to failing
easy_logging_yojson.0.5.2 on 4.10 had its build status changed: passing to failing
easy_logging_yojson.0.5.2 on 4.11 had its build status changed: passing to failing
easy_logging_yojson.0.5.2 on 4.12 had its build status changed: passing to failing
efl.1.12.0 on 4.08 is now installable. Current state is: failing
efl.1.12.0 on 4.09 is now installable. Current state is: failing
efl.1.12.0 on 4.10 is now installable. Current state is: failing
efl.1.12.0 on 4.11 is now installable. Current state is: failing
efl.1.12.0 on 4.12 is now installable. Current state is: failing
efl.1.12.0 on 4.13 is now installable. Current state is: failing
efl.1.12.0 on 4.14 is now installable. Current state is: failing
efl.1.12.0 on 5.0 is now installable. Current state is: failing
efl.1.12.0 on 5.1 is now installable. Current state is: failing
efl.1.13.0 on 4.08 is now installable. Current state is: failing
efl.1.13.0 on 4.09 is now installable. Current state is: failing
efl.1.13.0 on 4.10 is now installable. Current state is: failing
efl.1.13.0 on 4.11 is now installable. Current state is: failing
efl.1.13.0 on 4.12 is now installable. Current state is: failing
efl.1.13.0 on 4.13 is now installable. Current state is: failing
efl.1.13.0 on 4.14 is now installable. Current state is: failing
efl.1.13.0 on 5.0 is now installable. Current state is: failing
efl.1.13.0 on 5.1 is now installable. Current state is: failing
efl.1.17.0 on 4.08 is now installable. Current state is: failing
efl.1.17.0 on 4.09 is now installable. Current state is: failing
efl.1.17.0 on 4.10 is now installable. Current state is: failing
efl.1.17.0 on 4.11 is now installable. Current state is: failing
efl.1.17.0 on 4.12 is now installable. Current state is: failing
efl.1.17.0 on 4.13 is now installable. Current state is: failing
efl.1.17.0 on 4.14 is now installable. Current state is: failing
efl.1.17.0 on 5.0 is now installable. Current state is: failing
efl.1.17.0 on 5.1 is now installable. Current state is: failing
efl.1.18.0 on 4.08 is now installable. Current state is: failing
efl.1.18.0 on 4.09 is now installable. Current state is: failing
efl.1.18.0 on 4.10 is now installable. Current state is: failing
efl.1.18.0 on 4.11 is now installable. Current state is: failing
efl.1.18.0 on 4.12 is now installable. Current state is: failing
efl.1.18.0 on 4.13 is now installable. Current state is: failing
efl.1.18.0 on 4.14 is now installable. Current state is: failing
efl.1.18.0 on 5.0 is now installable. Current state is: failing
efl.1.18.0 on 5.1 is now installable. Current state is: failing
efl.1.19.0 on 4.08 is now installable. Current state is: failing
efl.1.19.0 on 4.09 is now installable. Current state is: failing
efl.1.19.0 on 4.10 is now installable. Current state is: failing
efl.1.19.0 on 4.11 is now installable. Current state is: failing
efl.1.19.0 on 4.12 is now installable. Current state is: failing
efl.1.19.0 on 4.13 is now installable. Current state is: failing
efl.1.19.0 on 4.14 is now installable. Current state is: failing
efl.1.19.0 on 5.0 is now installable. Current state is: failing
efl.1.19.0 on 5.1 is now installable. Current state is: failing
efl.1.20.0 on 4.08 is now installable. Current state is: failing
efl.1.20.0 on 4.09 is now installable. Current state is: failing
efl.1.20.0 on 4.10 is now installable. Current state is: failing
efl.1.20.0 on 4.11 is now installable. Current state is: failing
efl.1.20.0 on 4.12 is now installable. Current state is: failing
efl.1.20.0 on 4.13 is now installable. Current state is: failing
efl.1.20.0 on 4.14 is now installable. Current state is: failing
efl.1.20.0 on 5.0 is now installable. Current state is: failing
efl.1.20.0 on 5.1 is now installable. Current state is: failing
efl.1.22.0 on 4.08 is now installable. Current state is: failing
efl.1.22.0 on 4.09 is now installable. Current state is: failing
efl.1.22.0 on 4.10 is now installable. Current state is: failing
efl.1.22.0 on 4.11 is now installable. Current state is: failing
efl.1.22.0 on 4.12 is now installable. Current state is: failing
efl.1.22.0 on 4.13 is now installable. Current state is: failing
efl.1.22.0 on 4.14 is now installable. Current state is: failing
efl.1.22.0 on 5.0 is now installable. Current state is: failing
efl.1.22.0 on 5.1 is now installable. Current state is: failing
efl.1.24.0 on 4.08 is now installable. Current state is: failing
efl.1.24.0 on 4.09 is now installable. Current state is: failing
efl.1.24.0 on 4.10 is now installable. Current state is: failing
efl.1.24.0 on 4.11 is now installable. Current state is: failing
efl.1.24.0 on 4.12 is now installable. Current state is: failing
efl.1.24.0 on 4.13 is now installable. Current state is: failing
efl.1.24.0 on 4.14 is now installable. Current state is: failing
efl.1.24.0 on 5.0 is now installable. Current state is: failing
efl.1.24.0 on 5.1 is now installable. Current state is: failing
eigen.0.1.4 on 5.1 is now installable. Current state is: failing
eigen.0.1.5 on 5.1 is now installable. Current state is: failing
eliom.6.11.0 on 4.08 had its build status changed: passing to failing
eliom.6.11.0 on 4.09 had its build status changed: passing to failing
eliom.6.11.0 on 4.10 had its build status changed: passing to failing
eliom.6.12.0 on 4.08 had its build status changed: passing to failing
eliom.6.12.0 on 4.09 had its build status changed: passing to failing
eliom.6.12.0 on 4.10 had its build status changed: passing to failing
eliom.6.12.1 on 4.08 had its build status changed: passing to failing
eliom.6.12.1 on 4.09 had its build status changed: passing to failing
eliom.6.12.1 on 4.10 had its build status changed: passing to failing
eliom.6.12.1 on 4.11 had its build status changed: passing to failing
eliom.6.12.4 on 4.08 had its build status changed: passing to failing
eliom.6.12.4 on 4.09 had its build status changed: passing to failing
eliom.6.12.4 on 4.10 had its build status changed: passing to failing
eliom.6.12.4 on 4.11 had its build status changed: passing to failing
eliom.6.13.1 on 4.08 had its build status changed: passing to failing
eliom.6.13.1 on 4.09 had its build status changed: passing to failing
eliom.6.13.1 on 4.10 had its build status changed: passing to failing
eliom.6.13.1 on 4.11 had its build status changed: passing to failing
eliom.7.0.0 on 4.08 had its build status changed: passing to failing
eliom.7.0.0 on 4.09 had its build status changed: passing to failing
eliom.7.0.0 on 4.10 had its build status changed: passing to failing
eliom.7.0.0 on 4.11 had its build status changed: passing to failing
eliom.7.0.0 on 4.12 had its build status changed: passing to failing
eliom.8.4.8 on 4.08 is now installable. Current state is: failing
eliom.8.4.8 on 4.09 is now installable. Current state is: failing
eliom.8.4.8 on 4.10 is now installable. Current state is: failing
eliom.8.4.8 on 4.11 is now installable. Current state is: failing
eliom.8.4.8 on 4.12 is now installable. Current state is: failing
eliom.8.6.0 on 4.08 is now installable. Current state is: failing
eliom.8.6.0 on 4.09 is now installable. Current state is: failing
eliom.8.6.0 on 4.10 is now installable. Current state is: failing
eliom.8.6.0 on 4.11 is now installable. Current state is: failing
eliom.8.6.0 on 4.12 is now installable. Current state is: failing
eliom.8.8.0 on 4.08 is now installable. Current state is: failing
eliom.8.8.0 on 4.09 is now installable. Current state is: failing
eliom.8.8.0 on 4.10 is now installable. Current state is: failing
eliom.8.8.0 on 4.11 is now installable. Current state is: failing
eliom.8.8.0 on 4.12 is now installable. Current state is: failing
eliom.8.8.1 on 4.08 is now installable. Current state is: failing
eliom.8.8.1 on 4.09 is now installable. Current state is: failing
eliom.8.8.1 on 4.10 is now installable. Current state is: failing
eliom.8.8.1 on 4.11 is now installable. Current state is: failing
eliom.8.8.1 on 4.12 is now installable. Current state is: failing
errpy.0.0.7 on 5.1 is now installable. Current state is: failing
errpy.0.0.8 on 5.1 is now installable. Current state is: failing
errpy.0.0.9 on 5.1 is now installable. Current state is: failing
esperanto.0.0.1 on 4.13 is now installable. Current state is: failing
extprot.1.7.0 on 5.0 is now installable. Current state is: failing
format.0.1 on 5.0 is now installable. Current state is: failing
frama-c.22.0 on 4.08 had its build status changed: passing to failing
frama-c.22.0 on 4.09 had its build status changed: passing to failing
frama-c.22.0 on 4.10 had its build status changed: passing to failing
frama-c.22.0 on 4.11 had its build status changed: passing to failing
frama-c.22.0 on 4.12 had its build status changed: passing to failing
frama-c.22.0 on 4.13 had its build status changed: passing to failing
frama-c.22.0 on 4.14 is now installable. Current state is: failing
functoria-runtime.2.0.0 on 4.08 had its build status changed: passing to failing
functoria-runtime.2.0.0 on 4.09 had its build status changed: passing to failing
functoria-runtime.2.0.0 on 4.10 had its build status changed: passing to failing
functoria-runtime.2.0.0 on 4.11 had its build status changed: passing to failing
functoria-runtime.2.1.0 on 4.08 had its build status changed: passing to failing
functoria-runtime.2.1.0 on 4.09 had its build status changed: passing to failing
functoria-runtime.2.1.0 on 4.10 had its build status changed: passing to failing
functoria-runtime.2.1.0 on 4.11 had its build status changed: passing to failing
functoria-runtime.2.2.0 on 4.08 had its build status changed: passing to failing
functoria-runtime.2.2.0 on 4.09 had its build status changed: passing to failing
functoria-runtime.2.2.0 on 4.10 had its build status changed: passing to failing
functoria-runtime.2.2.0 on 4.11 had its build status changed: passing to failing
functoria-runtime.2.2.1 on 4.08 had its build status changed: passing to failing
functoria-runtime.2.2.1 on 4.09 had its build status changed: passing to failing
functoria-runtime.2.2.1 on 4.10 had its build status changed: passing to failing
functoria-runtime.2.2.1 on 4.11 had its build status changed: passing to failing
functory.0.6 on 4.08 had its build status changed: passing to failing
functory.0.6 on 4.12 had its build status changed: passing to failing
gadelac.0.6 on 5.0 is now installable. Current state is: failing
gadelac.0.6 on 5.1 is now installable. Current state is: failing
gammu.0.9.3 on 5.0 is now installable. Current state is: failing
gammu.0.9.3 on 5.1 is now installable. Current state is: failing
gdbprofiler.0.3 on 4.08 had its build status changed: passing to failing
gdbprofiler.0.3 on 4.09 had its build status changed: passing to failing
gdbprofiler.0.3 on 4.10 had its build status changed: passing to failing
gdbprofiler.0.3 on 4.11 had its build status changed: passing to failing
gdbprofiler.0.3 on 4.12 had its build status changed: passing to failing
gemini.0.1 on 4.08 had its build status changed: passing to failing
gemini.0.1 on 4.09 had its build status changed: passing to failing
gemini.0.2.0 on 4.08 had its build status changed: passing to failing
gemini.0.2.0 on 4.09 had its build status changed: passing to failing
genprint.0.3 on 4.08 is now installable. Current state is: failing
genprint.0.3 on 4.09 is now installable. Current state is: failing
genprint.0.3 on 4.10 is now installable. Current state is: failing
git-unix.3.2.0 on 4.08 had its build status changed: passing to failing
git-unix.3.2.0 on 4.09 had its build status changed: passing to failing
git-unix.3.2.0 on 4.10 had its build status changed: passing to failing
git-unix.3.2.0 on 4.11 had its build status changed: passing to failing
git-unix.3.2.0 on 4.12 had its build status changed: passing to failing
git-unix.3.3.0 on 4.08 had its build status changed: passing to failing
git-unix.3.3.0 on 4.09 had its build status changed: passing to failing
git-unix.3.3.0 on 4.10 had its build status changed: passing to failing
git-unix.3.3.0 on 4.11 had its build status changed: passing to failing
git-unix.3.3.0 on 4.12 had its build status changed: passing to failing
git-unix.3.3.1 on 4.08 had its build status changed: passing to failing
git-unix.3.3.1 on 4.09 had its build status changed: passing to failing
git-unix.3.3.1 on 4.10 had its build status changed: passing to failing
git-unix.3.3.1 on 4.11 had its build status changed: passing to failing
git-unix.3.3.1 on 4.12 had its build status changed: passing to failing
git-unix.3.3.2 on 4.08 had its build status changed: passing to failing
git-unix.3.3.2 on 4.09 had its build status changed: passing to failing
git-unix.3.3.2 on 4.10 had its build status changed: passing to failing
git-unix.3.3.2 on 4.11 had its build status changed: passing to failing
git-unix.3.3.2 on 4.12 had its build status changed: passing to failing
git-unix.3.3.3 on 4.08 had its build status changed: passing to failing
git-unix.3.3.3 on 4.09 had its build status changed: passing to failing
git-unix.3.3.3 on 4.10 had its build status changed: passing to failing
git-unix.3.3.3 on 4.11 had its build status changed: passing to failing
git-unix.3.3.3 on 4.12 had its build status changed: passing to failing
graphql.0.1.0 on 4.08 had its build status changed: passing to failing
graphql.0.1.0 on 4.09 had its build status changed: passing to failing
graphql.0.1.0 on 4.10 had its build status changed: passing to failing
graphql.0.1.0 on 4.11 had its build status changed: passing to failing
graphql.0.1.0 on 4.12 had its build status changed: passing to failing
graphql.0.2.0 on 4.08 had its build status changed: passing to failing
graphql.0.2.0 on 4.09 had its build status changed: passing to failing
graphql.0.2.0 on 4.10 had its build status changed: passing to failing
graphql.0.2.0 on 4.11 had its build status changed: passing to failing
graphql.0.2.0 on 4.12 had its build status changed: passing to failing
graphql.0.4.0 on 4.08 had its build status changed: passing to failing
graphql.0.4.0 on 4.09 had its build status changed: passing to failing
graphql.0.4.0 on 4.10 had its build status changed: passing to failing
graphql.0.4.0 on 4.11 had its build status changed: passing to failing
graphql.0.4.0 on 4.12 had its build status changed: passing to failing
graphql.0.5.0 on 4.08 had its build status changed: passing to failing
graphql.0.5.0 on 4.09 had its build status changed: passing to failing
graphql.0.5.0 on 4.10 had its build status changed: passing to failing
graphql.0.5.0 on 4.11 had its build status changed: passing to failing
graphql.0.5.0 on 4.12 had its build status changed: passing to failing
graphql.0.6.0 on 4.08 had its build status changed: passing to failing
graphql.0.6.0 on 4.09 had its build status changed: passing to failing
graphql.0.6.0 on 4.10 had its build status changed: passing to failing
graphql.0.6.0 on 4.11 had its build status changed: passing to failing
graphql.0.6.0 on 4.12 had its build status changed: passing to failing
graphql.0.7.0 on 4.08 had its build status changed: passing to failing
graphql.0.7.0 on 4.09 had its build status changed: passing to failing
graphql.0.7.0 on 4.10 had its build status changed: passing to failing
graphql.0.7.0 on 4.11 had its build status changed: passing to failing
graphql.0.7.0 on 4.12 had its build status changed: passing to failing
graphql.0.8.0 on 4.08 had its build status changed: passing to failing
graphql.0.8.0 on 4.09 had its build status changed: passing to failing
graphql.0.8.0 on 4.10 had its build status changed: passing to failing
graphql.0.8.0 on 4.11 had its build status changed: passing to failing
graphql.0.8.0 on 4.12 had its build status changed: passing to failing
hack_parallel.0.1.1 on 4.08 had its build status changed: passing to failing
hack_parallel.0.1.1 on 4.09 had its build status changed: passing to failing
hacl-star-raw.0.1 on 4.08 had its build status changed: passing to failing
hacl-star-raw.0.1 on 4.10 had its build status changed: passing to failing
hacl-star-raw.0.1 on 4.11 had its build status changed: passing to failing
hacl-star-raw.0.1 on 4.12 had its build status changed: passing to failing
hacl-star-raw.0.1 on 4.13 had its build status changed: passing to failing
hacl-star-raw.0.1 on 4.14 is now installable. Current state is: failing
hacl-star-raw.0.1.1 on 4.08 had its build status changed: passing to failing
hacl-star-raw.0.1.1 on 4.09 had its build status changed: passing to failing
hacl-star-raw.0.1.1 on 4.10 had its build status changed: passing to failing
hacl-star-raw.0.1.1 on 4.11 had its build status changed: passing to failing
hacl-star-raw.0.1.1 on 4.12 had its build status changed: passing to failing
hacl-star-raw.0.1.1 on 4.13 had its build status changed: passing to failing
hacl-star-raw.0.1.1 on 4.14 is now installable. Current state is: failing
hacl-star-raw.0.2.0 on 4.08 had its build status changed: passing to failing
hacl-star-raw.0.2.0 on 4.09 had its build status changed: passing to failing
hacl-star-raw.0.2.0 on 4.10 had its build status changed: passing to failing
hacl-star-raw.0.2.0 on 4.12 had its build status changed: passing to failing
hacl-star-raw.0.2.0 on 4.13 had its build status changed: passing to failing
hacl-star-raw.0.2.0 on 4.14 is now installable. Current state is: failing
hacl-star-raw.0.2.1 on 4.08 had its build status changed: passing to failing
hacl-star-raw.0.2.1 on 4.11 had its build status changed: passing to failing
hacl-star-raw.0.2.1 on 4.12 had its build status changed: passing to failing
hacl-star-raw.0.2.1 on 4.13 had its build status changed: passing to failing
hacl-star-raw.0.2.1 on 4.14 is now installable. Current state is: failing
hacl-star-raw.0.2.2 on 4.08 had its build status changed: passing to failing
hacl-star-raw.0.2.2 on 4.09 had its build status changed: passing to failing
hacl-star-raw.0.2.2 on 4.11 had its build status changed: passing to failing
heptagon.1.03.03 on 5.0 is now installable. Current state is: failing
heptagon.1.03.04 on 5.0 is now installable. Current state is: failing
heptagon.1.04.00 on 5.0 is now installable. Current state is: failing
heptagon.1.05.00 on 5.0 is now installable. Current state is: failing
hlarp.0.0.1 on 4.08 had its build status changed: passing to failing
hlarp.0.0.1 on 4.09 had its build status changed: passing to failing
hlarp.0.0.1 on 4.10 had its build status changed: passing to failing
hlarp.0.0.1 on 4.11 had its build status changed: passing to failing
hlarp.0.0.1 on 4.12 had its build status changed: passing to failing
hlarp.0.0.2 on 4.08 had its build status changed: passing to failing
hlarp.0.0.2 on 4.09 had its build status changed: passing to failing
hlarp.0.0.2 on 4.10 had its build status changed: passing to failing
hlarp.0.0.2 on 4.11 had its build status changed: passing to failing
hlarp.0.0.2 on 4.12 had its build status changed: passing to failing
hweak.1.1 on 5.0 is now installable. Current state is: failing
hweak.1.1 on 5.1 is now installable. Current state is: failing
index.1.2.1 on 4.08 had its build status changed: passing to failing
index.1.2.1 on 4.09 had its build status changed: passing to failing
index.1.2.1 on 4.10 had its build status changed: passing to failing
index.1.2.1 on 4.11 had its build status changed: passing to failing
irmin-test.2.0.0 on 4.08 had its build status changed: passing to failing
irmin-test.2.0.0 on 4.09 had its build status changed: passing to failing
irmin-test.2.0.0 on 4.10 had its build status changed: passing to failing
irmin-test.2.0.0 on 4.11 had its build status changed: passing to failing
irmin-test.2.0.0 on 4.12 had its build status changed: passing to failing
irmin-test.2.0.0 on 4.13 had its build status changed: passing to failing
javalib.3.1 on 5.0 is now installable. Current state is: failing
jhupllib.0.1 on 4.08 had its build status changed: passing to failing
jhupllib.0.1 on 4.09 had its build status changed: passing to failing
jhupllib.0.1.1 on 4.08 had its build status changed: passing to failing
jhupllib.0.1.1 on 4.09 had its build status changed: passing to failing
jhupllib.0.2.1 on 4.08 had its build status changed: passing to failing
jhupllib.0.2.1 on 4.09 had its build status changed: passing to failing
jupyter-kernel.0.4 on 4.08 had its build status changed: passing to failing
jupyter-kernel.0.4 on 4.09 had its build status changed: passing to failing
jupyter-kernel.0.4 on 4.10 had its build status changed: passing to failing
jupyter-kernel.0.4 on 4.11 had its build status changed: passing to failing
kappa-library.4.1.0 on 4.08 had its build status changed: internal failure to failing
kappa-library.4.1.0 on 4.09 had its build status changed: internal failure to failing
kappa-library.4.1.0 on 4.10 had its build status changed: internal failure to failing
kappa-library.4.1.0 on 4.11 had its build status changed: internal failure to failing
key-parsers.0.9.2 on 4.08 had its build status changed: passing to failing
key-parsers.0.9.2 on 4.09 had its build status changed: passing to failing
key-parsers.0.9.2 on 4.10 had its build status changed: passing to failing
key-parsers.0.9.2 on 4.11 had its build status changed: passing to failing
key-parsers.0.9.2 on 4.12 had its build status changed: passing to failing
kinetic-client.0.0.1 on 4.08 had its build status changed: not available to failing
kinetic-client.0.0.1 on 4.09 had its build status changed: not available to failing
kinetic-client.0.0.1 on 4.10 had its build status changed: not available to failing
kinetic-client.0.0.1 on 4.11 had its build status changed: not available to failing
kinetic-client.0.0.1 on 4.12 had its build status changed: not available to failing
kinetic-client.0.0.1 on 4.13 had its build status changed: not available to failing
kinetic-client.0.0.1 on 4.14 is now installable. Current state is: failing
kinetic-client.0.0.9 on 4.08 had its build status changed: not available to failing
kinetic-client.0.0.9 on 4.09 had its build status changed: not available to failing
kinetic-client.0.0.9 on 4.10 had its build status changed: not available to failing
kinetic-client.0.0.9 on 4.11 had its build status changed: not available to failing
kinetic-client.0.0.9 on 4.12 had its build status changed: not available to failing
kinetic-client.0.0.9 on 4.13 had its build status changed: not available to failing
kinetic-client.0.0.9 on 4.14 is now installable. Current state is: failing
labltk.8.06.11 on 4.14 is now installable. Current state is: failing
labltk.8.06.11 on 5.0 is now installable. Current state is: failing
labltk.8.06.11 on 5.1 is now installable. Current state is: failing
labltk.8.06.12 on 4.14 is now installable. Current state is: failing
labltk.8.06.12 on 5.0 is now installable. Current state is: failing
labltk.8.06.12 on 5.1 is now installable. Current state is: failing
lascar.0.5 on 5.0 is now installable. Current state is: failing
learn-ocaml.0.13.0 on 4.12 is now installable. Current state is: failing
learn-ocaml.0.13.1 on 4.12 is now installable. Current state is: failing
learn-ocaml.0.14.0 on 4.12 is now installable. Current state is: failing
learn-ocaml.0.14.1 on 4.12 is now installable. Current state is: failing
learn-ocaml.0.15.0 on 4.12 is now installable. Current state is: failing
libbinaryen.109.0.0 on 4.12 is now installable. Current state is: failing
libbinaryen.109.0.0 on 4.13 is now installable. Current state is: failing
libbinaryen.109.0.0 on 4.14 is now installable. Current state is: failing
libbinaryen.109.0.0 on 5.0 is now installable. Current state is: failing
libbinaryen.109.0.0 on 5.1 is now installable. Current state is: failing
libbinaryen.109.0.1 on 4.12 is now installable. Current state is: failing
libbinaryen.109.0.1 on 4.13 is now installable. Current state is: failing
libbinaryen.109.0.1 on 4.14 is now installable. Current state is: failing
libbinaryen.109.0.1 on 5.0 is now installable. Current state is: failing
libbinaryen.109.0.1 on 5.1 is now installable. Current state is: failing
libbinaryen.110.0.0 on 4.12 is now installable. Current state is: failing
libbinaryen.110.0.0 on 4.13 is now installable. Current state is: failing
libbinaryen.110.0.0 on 4.14 is now installable. Current state is: failing
libbinaryen.110.0.0 on 5.0 is now installable. Current state is: failing
libbinaryen.110.0.0 on 5.1 is now installable. Current state is: failing
libbinaryen.111.0.0 on 4.12 is now installable. Current state is: failing
libbinaryen.111.0.0 on 4.13 is now installable. Current state is: failing
libbinaryen.111.0.0 on 4.14 is now installable. Current state is: failing
libbinaryen.111.0.0 on 5.0 is now installable. Current state is: failing
libbinaryen.111.0.0 on 5.1 is now installable. Current state is: failing
libbinaryen.111.1.0 on 4.12 is now installable. Current state is: failing
libbinaryen.111.1.0 on 4.13 is now installable. Current state is: failing
libbinaryen.111.1.0 on 4.14 is now installable. Current state is: failing
libbinaryen.111.1.0 on 5.0 is now installable. Current state is: failing
libbinaryen.111.1.0 on 5.1 is now installable. Current state is: failing
libssh.0.1 on 4.14 is now installable. Current state is: failing
luv.0.5.0 on 4.08 had its build status changed: passing to failing
luv.0.5.0 on 4.09 had its build status changed: passing to failing
luv.0.5.0 on 4.10 had its build status changed: passing to failing
luv.0.5.0 on 4.11 had its build status changed: passing to failing
luv.0.5.0 on 4.12 had its build status changed: passing to failing
luv.0.5.0 on 4.13 had its build status changed: passing to failing
luv.0.5.0 on 4.14 is now installable. Current state is: failing
luv.0.5.0 on 5.0 is now installable. Current state is: failing
luv.0.5.0 on 5.1 is now installable. Current state is: failing
mariadb.1.1.4 on 4.08 had its build status changed: passing to failing
mariadb.1.1.4 on 4.09 had its build status changed: passing to failing
mariadb.1.1.4 on 4.10 had its build status changed: passing to failing
mariadb.1.1.4 on 4.11 had its build status changed: passing to failing
mariadb.1.1.4 on 4.12 had its build status changed: passing to failing
mariadb.1.1.4 on 4.13 had its build status changed: passing to failing
mccs.1.1+10 on 4.08 had its build status changed: passing to failing
mccs.1.1+10 on 4.09 had its build status changed: passing to failing
mccs.1.1+11 on 4.08 had its build status changed: passing to failing
mccs.1.1+11 on 4.09 had its build status changed: passing to failing
mccs.1.1+11 on 4.10 had its build status changed: passing to failing
mccs.1.1+11 on 4.11 had its build status changed: passing to failing
mccs.1.1+11 on 4.12 had its build status changed: passing to failing
mccs.1.1+11 on 4.13 had its build status changed: passing to failing
mccs.1.1+11 on 4.14 is now installable. Current state is: failing
mccs.1.1+11 on 5.0 is now installable. Current state is: failing
mccs.1.1+11 on 5.1 is now installable. Current state is: failing
mccs.1.1+3 on 4.08 had its build status changed: passing to failing
mccs.1.1+3 on 4.09 had its build status changed: passing to failing
mccs.1.1+4 on 4.08 had its build status changed: passing to failing
mccs.1.1+4 on 4.09 had its build status changed: passing to failing
mccs.1.1+5 on 4.08 had its build status changed: passing to failing
mccs.1.1+5 on 4.09 had its build status changed: passing to failing
mccs.1.1+6 on 4.08 had its build status changed: passing to failing
mccs.1.1+6 on 4.09 had its build status changed: passing to failing
mccs.1.1+8 on 4.08 had its build status changed: passing to failing
mccs.1.1+8 on 4.09 had its build status changed: passing to failing
mccs.1.1+9 on 4.08 had its build status changed: passing to failing
mccs.1.1+9 on 4.09 had its build status changed: passing to failing
mdx.1.7.0 on 4.08 had its build status changed: passing to failing
mdx.1.7.0 on 4.09 had its build status changed: passing to failing
mdx.1.7.0 on 4.10 had its build status changed: passing to failing
mdx.1.7.0 on 4.11 had its build status changed: passing to failing
melange.3.0.0-51 on 5.1 is now installable. Current state is: failing
memtrace.0.1 on 5.0 is now installable. Current state is: failing
memtrace.0.1 on 5.1 is now installable. Current state is: failing
memtrace_viewer.v0.14.0 on 4.11 had its build status changed: passing to failing
memtrace_viewer.v0.14.1 on 4.11 had its build status changed: passing to failing
metapp.0.4.4 on 4.08 is now installable. Current state is: failing
metapp.0.4.4 on 4.09 is now installable. Current state is: failing
metapp.0.4.4 on 4.10 is now installable. Current state is: failing
metapp.0.4.4 on 4.11 is now installable. Current state is: failing
metapp.0.4.4 on 4.12 is now installable. Current state is: failing
metapp.0.4.4 on 4.13 is now installable. Current state is: failing
metapp.0.4.4 on 4.14 is now installable. Current state is: failing
metapp.0.4.4 on 5.0 is now installable. Current state is: failing
metapp.0.4.4 on 5.1 is now installable. Current state is: failing
minios-xen.0.7 on 4.08 had its build status changed: passing to failing
minios-xen.0.7 on 4.09 had its build status changed: passing to failing
minios-xen.0.7 on 4.10 had its build status changed: passing to failing
minios-xen.0.7 on 4.11 had its build status changed: passing to failing
minios-xen.0.7 on 4.12 had its build status changed: passing to failing
minios-xen.0.7 on 4.13 had its build status changed: passing to failing
minios-xen.0.7 on 4.14 is now installable. Current state is: failing
minios-xen.0.7 on 5.0 is now installable. Current state is: failing
minios-xen.0.7 on 5.1 is now installable. Current state is: failing
mirage-block-xen.1.7.0 on 4.08 had its build status changed: passing to failing
mirage-block-xen.1.7.0 on 4.09 had its build status changed: passing to failing
mirage-block-xen.1.7.0 on 4.10 had its build status changed: passing to failing
mirage-block-xen.1.7.0 on 4.11 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.0 on 4.08 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.0 on 4.09 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.0 on 4.10 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.0 on 4.11 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.1 on 4.08 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.1 on 4.09 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.1 on 4.10 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.1 on 4.11 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.2 on 4.08 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.2 on 4.09 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.2 on 4.10 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.2 on 4.11 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.3 on 4.08 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.3 on 4.09 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.3 on 4.10 had its build status changed: passing to failing
mirage-console-xen-backend.2.4.3 on 4.11 had its build status changed: passing to failing
mirage-console-xen-backend.3.0.2 on 4.08 had its build status changed: passing to failing
mirage-console-xen-backend.3.0.2 on 4.09 had its build status changed: passing to failing
mirage-console-xen-backend.3.0.2 on 4.10 had its build status changed: passing to failing
mirage-console-xen-backend.3.0.2 on 4.11 had its build status changed: passing to failing
mirage-console-xen.2.4.2 on 4.08 had its build status changed: passing to failing
mirage-console-xen.2.4.2 on 4.09 had its build status changed: passing to failing
mirage-console-xen.2.4.2 on 4.10 had its build status changed: passing to failing
mirage-console-xen.2.4.2 on 4.11 had its build status changed: passing to failing
mirage-console-xen.2.4.3 on 4.08 had its build status changed: passing to failing
mirage-console-xen.2.4.3 on 4.09 had its build status changed: passing to failing
mirage-console-xen.2.4.3 on 4.10 had its build status changed: passing to failing
mirage-console-xen.2.4.3 on 4.11 had its build status changed: passing to failing
mirage-console-xen.3.0.2 on 4.08 had its build status changed: passing to failing
mirage-console-xen.3.0.2 on 4.09 had its build status changed: passing to failing
mirage-console-xen.3.0.2 on 4.10 had its build status changed: passing to failing
mirage-console-xen.3.0.2 on 4.11 had its build status changed: passing to failing
mirage-fs-unix.1.6.0 on 5.0 is now installable. Current state is: failing
mirage-fs-unix.1.6.0 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.2 on 4.14 is now installable. Current state is: failing
mirage-xen-minios.0.2 on 5.0 is now installable. Current state is: failing
mirage-xen-minios.0.2 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.3 on 4.14 is now installable. Current state is: failing
mirage-xen-minios.0.3 on 5.0 is now installable. Current state is: failing
mirage-xen-minios.0.3 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.4 on 4.14 is now installable. Current state is: failing
mirage-xen-minios.0.4 on 5.0 is now installable. Current state is: failing
mirage-xen-minios.0.4 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.4.1 on 4.14 is now installable. Current state is: failing
mirage-xen-minios.0.4.1 on 5.0 is now installable. Current state is: failing
mirage-xen-minios.0.4.1 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.4.2 on 4.14 is now installable. Current state is: failing
mirage-xen-minios.0.4.2 on 5.0 is now installable. Current state is: failing
mirage-xen-minios.0.4.2 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.5.0 on 4.14 is now installable. Current state is: failing
mirage-xen-minios.0.5.0 on 5.0 is now installable. Current state is: failing
mirage-xen-minios.0.5.0 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.6.0 on 4.14 is now installable. Current state is: failing
mirage-xen-minios.0.6.0 on 5.0 is now installable. Current state is: failing
mirage-xen-minios.0.6.0 on 5.1 is now installable. Current state is: failing
mirage-xen-minios.0.7.0 on 4.14 is now installable. Current state is: failing
mirage-xen-minios.0.7.0 on 5.0 is now installable. Current state is: failing
mirage-xen-minios.0.7.0 on 5.1 is now installable. Current state is: failing
mldonkey.3.1.7-2 on 4.08 had its build status changed: passing to failing
mldonkey.3.1.7-2 on 4.09 had its build status changed: passing to failing
morbig.0.9 on 5.0 is now installable. Current state is: failing
morbig.0.9 on 5.1 is now installable. Current state is: failing
multicont.1.0.2 on 5.1 is now installable. Current state is: failing
mysql8.1.0 on 4.13 had its build status changed: not available to failing
mysql8.1.0 on 4.14 is now installable. Current state is: failing
mysql8.1.0 on 5.0 is now installable. Current state is: failing
mysql8.1.0 on 5.1 is now installable. Current state is: failing
named-pipe.0.4.0 on 4.08 had its build status changed: passing to failing
named-pipe.0.4.0 on 4.09 had its build status changed: passing to failing
named-pipe.0.4.0 on 4.10 had its build status changed: passing to failing
named-pipe.0.4.0 on 4.11 had its build status changed: passing to failing
netchannel.1.10.2 on 4.08 had its build status changed: passing to failing
netchannel.1.10.2 on 4.09 had its build status changed: passing to failing
netchannel.1.10.2 on 4.10 had its build status changed: passing to failing
netchannel.1.10.2 on 4.11 had its build status changed: passing to failing
netchannel.1.11.0 on 4.08 had its build status changed: passing to failing
netchannel.1.11.0 on 4.09 had its build status changed: passing to failing
netchannel.1.11.0 on 4.10 had its build status changed: passing to failing
netchannel.1.11.0 on 4.11 had its build status changed: passing to failing
netchannel.1.12.0 on 4.08 had its build status changed: passing to failing
netchannel.1.12.0 on 4.09 had its build status changed: passing to failing
netchannel.1.12.0 on 4.10 had its build status changed: passing to failing
netchannel.1.12.0 on 4.11 had its build status changed: passing to failing
netchannel.1.13.0 on 4.08 had its build status changed: passing to failing
netchannel.1.13.0 on 4.09 had its build status changed: passing to failing
netchannel.1.13.0 on 4.10 had its build status changed: passing to failing
netchannel.1.13.0 on 4.11 had its build status changed: passing to failing
netchannel.1.13.1 on 4.08 had its build status changed: passing to failing
netchannel.1.13.1 on 4.09 had its build status changed: passing to failing
netchannel.1.13.1 on 4.10 had its build status changed: passing to failing
netchannel.1.13.1 on 4.11 had its build status changed: passing to failing
netkat.0.1 on 4.08 had its build status changed: passing to failing
netkat.0.1 on 4.09 had its build status changed: passing to failing
netkat.0.1 on 4.10 had its build status changed: passing to failing
netkat.0.1 on 4.11 had its build status changed: passing to failing
noCanren.0.3.0 on 4.13 is now installable. Current state is: failing
noCanren.0.3.0~alpha1 on 4.13 is now installable. Current state is: failing
nuscr.1.0.0 on 4.08 had its build status changed: passing to failing
nuscr.1.0.0 on 4.09 had its build status changed: passing to failing
nuscr.1.1.0 on 4.08 had its build status changed: passing to failing
nuscr.1.1.0 on 4.09 had its build status changed: passing to failing
nuscr.1.1.0 on 4.10 had its build status changed: passing to failing
nuscr.1.1.0 on 4.11 had its build status changed: passing to failing
nuscr.1.1.0 on 4.12 had its build status changed: passing to failing
objsize.0.18 on 5.0 is now installable. Current state is: failing
ocaml-makefile.6.37.0 on 4.14 is now installable. Current state is: failing
ocaml-makefile.6.37.0 on 5.0 is now installable. Current state is: failing
ocaml-makefile.6.37.0 on 5.1 is now installable. Current state is: failing
ocaml-makefile.6.38.0 on 4.14 is now installable. Current state is: failing
ocaml-makefile.6.38.0 on 5.0 is now installable. Current state is: failing
ocaml-makefile.6.38.0 on 5.1 is now installable. Current state is: failing
ocaml-makefile.6.39.0 on 4.14 is now installable. Current state is: failing
ocaml-makefile.6.39.0 on 5.0 is now installable. Current state is: failing
ocaml-makefile.6.39.0 on 5.1 is now installable. Current state is: failing
ocaml-protoc-plugin.0.9 on 4.08 had its build status changed: passing to failing
ocaml-protoc-plugin.0.9 on 4.09 had its build status changed: passing to failing
ocaml-protoc-plugin.0.9 on 4.10 had its build status changed: passing to failing
ocaml-protoc-plugin.0.9 on 4.11 had its build status changed: passing to failing
ocaml-r.0.1.0 on 4.08 had its build status changed: passing to failing
ocaml-r.0.1.0 on 4.09 had its build status changed: passing to failing
ocaml-r.0.1.0 on 4.10 had its build status changed: passing to failing
ocaml-r.0.1.0 on 4.11 had its build status changed: passing to failing
ocaml-r.0.1.1 on 4.08 had its build status changed: passing to failing
ocaml-r.0.1.1 on 4.09 had its build status changed: passing to failing
ocaml-r.0.1.1 on 4.10 had its build status changed: passing to failing
ocaml-r.0.1.1 on 4.11 had its build status changed: passing to failing
ocaml-r.0.2.0 on 4.08 had its build status changed: passing to failing
ocaml-r.0.2.0 on 4.09 had its build status changed: passing to failing
ocaml-r.0.2.0 on 4.10 had its build status changed: passing to failing
ocaml-r.0.2.0 on 4.11 had its build status changed: passing to failing
ocaml-r.0.3.0 on 4.08 had its build status changed: passing to failing
ocaml-r.0.3.0 on 4.09 had its build status changed: passing to failing
ocaml-r.0.3.0 on 4.10 had its build status changed: passing to failing
ocaml-r.0.3.0 on 4.11 had its build status changed: passing to failing
ocaml-r.0.3.1 on 4.08 had its build status changed: passing to failing
ocaml-r.0.3.1 on 4.09 had its build status changed: passing to failing
ocaml-r.0.3.1 on 4.10 had its build status changed: passing to failing
ocaml-r.0.3.1 on 4.11 had its build status changed: passing to failing
ocaml-r.0.3.1 on 4.12 had its build status changed: passing to failing
ocaml-r.0.3.1 on 4.13 had its build status changed: passing to failing
ocaml-r.0.3.1 on 4.14 is now installable. Current state is: failing
ocaml-r.0.3.1 on 5.0 is now installable. Current state is: failing
ocaml-r.0.3.1 on 5.1 is now installable. Current state is: failing
ocaml-r.0.4.0 on 4.08 had its build status changed: passing to failing
ocaml-r.0.4.0 on 4.09 had its build status changed: passing to failing
ocaml-r.0.4.0 on 4.10 had its build status changed: passing to failing
ocaml-r.0.4.0 on 4.11 had its build status changed: passing to failing
ocaml-r.0.4.0 on 4.12 had its build status changed: passing to failing
ocaml-r.0.4.0 on 4.13 had its build status changed: passing to failing
ocaml-r.0.4.0 on 4.14 is now installable. Current state is: failing
ocaml-r.0.4.0 on 5.0 is now installable. Current state is: failing
ocaml-r.0.4.0 on 5.1 is now installable. Current state is: failing
ocaml-r.0.5.0 on 4.08 is now installable. Current state is: failing
ocaml-r.0.5.0 on 4.09 is now installable. Current state is: failing
ocaml-r.0.5.0 on 4.10 is now installable. Current state is: failing
ocaml-r.0.5.0 on 4.11 is now installable. Current state is: failing
ocaml-r.0.5.0 on 4.12 is now installable. Current state is: failing
ocaml-r.0.5.0 on 4.13 is now installable. Current state is: failing
ocaml-r.0.5.0 on 4.14 is now installable. Current state is: failing
ocaml-r.0.5.0 on 5.0 is now installable. Current state is: failing
ocaml-r.0.5.0 on 5.1 is now installable. Current state is: failing
ocamldiff.1.1 on 4.08 had its build status changed: passing to failing
ocamldiff.1.1 on 4.09 had its build status changed: passing to failing
ocamldiff.1.1 on 4.10 had its build status changed: passing to failing
ocamldiff.1.1 on 4.11 had its build status changed: passing to failing
ocamldiff.1.1 on 4.12 had its build status changed: passing to failing
ocamldiff.1.1 on 4.13 had its build status changed: passing to failing
ocamldiff.1.1 on 4.14 is now installable. Current state is: failing
ocamldiff.1.1 on 5.0 is now installable. Current state is: failing
ocamldiff.1.1 on 5.1 is now installable. Current state is: failing
ocamldsort.0.15.0 on 5.0 is now installable. Current state is: failing
ocamldsort.0.16.0 on 5.0 is now installable. Current state is: failing
ocamlformat-rpc.0.18.0 on 4.08 had its build status changed: passing to failing
ocamlformat-rpc.0.18.0 on 4.09 had its build status changed: passing to failing
ocamlformat-rpc.0.18.0 on 4.10 had its build status changed: passing to failing
ocamlformat-rpc.0.18.0 on 4.11 had its build status changed: passing to failing
ocamlformat-rpc.0.18.0 on 4.12 had its build status changed: passing to failing
ocamlscript.2.0.2 on 5.0 is now installable. Current state is: failing
ocamlscript.2.0.4 on 5.0 is now installable. Current state is: failing
ocp-index-top.0.4.1 on 4.08 had its build status changed: passing to failing
ocp-index-top.0.4.1 on 4.09 had its build status changed: passing to failing
ocp-index-top.0.4.3 on 4.08 had its build status changed: passing to failing
ocp-index-top.0.4.3 on 4.09 had its build status changed: passing to failing
ocp-index-top.0.5.0 on 4.08 had its build status changed: passing to failing
ocp-index-top.0.5.0 on 4.09 had its build status changed: passing to failing
ocp-pack-split.1.0.1 on 5.0 is now installable. Current state is: failing
ocp-pack-split.1.0.1 on 5.1 is now installable. Current state is: failing
ocplib-simplex.0.3 on 5.1 is now installable. Current state is: failing
ocsigen-start.2.15.1 on 4.08 had its build status changed: passing to failing
ocsigen-start.2.15.1 on 4.09 had its build status changed: passing to failing
ocsigen-start.2.15.1 on 4.10 had its build status changed: passing to failing
ocsigen-start.2.16.0 on 4.08 had its build status changed: passing to failing
ocsigen-start.2.16.0 on 4.09 had its build status changed: passing to failing
ocsigen-start.2.16.0 on 4.10 had its build status changed: passing to failing
ocsigen-start.2.16.1 on 4.08 had its build status changed: passing to failing
ocsigen-start.2.16.1 on 4.09 had its build status changed: passing to failing
ocsigen-start.2.16.1 on 4.10 had its build status changed: passing to failing
odepack.0.6.9 on 4.14 is now installable. Current state is: failing
odepack.0.6.9 on 5.0 is now installable. Current state is: failing
odepack.0.6.9 on 5.1 is now installable. Current state is: failing
odepack.0.7 on 4.14 is now installable. Current state is: failing
odepack.0.7 on 5.0 is now installable. Current state is: failing
odepack.0.7 on 5.1 is now installable. Current state is: failing
odig.0.0.3 on 4.08 had its build status changed: passing to failing
odig.0.0.3 on 4.09 had its build status changed: passing to failing
odig.0.0.3 on 4.10 had its build status changed: passing to failing
odig.0.0.3 on 4.11 had its build status changed: passing to failing
ollvm-tapir.0.99.1 on 5.0 is now installable. Current state is: failing
ollvm.0.99 on 4.09 had its build status changed: passing to failing
ollvm.0.99 on 4.11 had its build status changed: passing to failing
ollvm.0.99 on 4.12 had its build status changed: passing to failing
ollvm.0.99 on 4.13 had its build status changed: passing to failing
openai-gym.0.01 on 4.08 had its build status changed: passing to failing
openai-gym.0.01 on 4.09 had its build status changed: passing to failing
openai-gym.0.01 on 4.10 had its build status changed: passing to failing
openai-gym.0.01 on 4.11 had its build status changed: passing to failing
openai-gym.0.01 on 4.12 had its build status changed: passing to failing
opentelemetry-cohttp-lwt.0.7 on 4.08 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.7 on 4.09 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.7 on 4.10 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.7 on 4.11 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.7 on 4.12 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.7 on 4.13 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.7 on 4.14 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.7 on 5.0 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.7 on 5.1 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.8 on 4.08 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.8 on 4.09 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.8 on 4.10 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.8 on 4.11 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.8 on 4.12 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.8 on 4.13 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.8 on 4.14 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.8 on 5.0 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.8 on 5.1 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.9 on 4.08 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.9 on 4.09 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.9 on 4.10 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.9 on 4.11 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.9 on 4.12 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.9 on 4.13 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.9 on 4.14 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.9 on 5.0 is now installable. Current state is: failing
opentelemetry-cohttp-lwt.0.9 on 5.1 is now installable. Current state is: failing
oplsr.8.0.1 on 4.13 had its build status changed: not available to failing
oplsr.8.0.1 on 4.14 is now installable. Current state is: failing
oplsr.8.0.1 on 5.0 is now installable. Current state is: failing
oplsr.8.0.1 on 5.1 is now installable. Current state is: failing
opsian.0.1 on 5.0 is now installable. Current state is: failing
opsian.0.1 on 5.1 is now installable. Current state is: failing
orun.0.0.1 on 4.08 had its build status changed: passing to failing
orun.0.0.1 on 4.10 had its build status changed: passing to failing
orun.0.0.1 on 4.11 had its build status changed: passing to failing
orun.0.0.1 on 4.12 had its build status changed: passing to failing
orun.0.0.1 on 4.13 had its build status changed: passing to failing
orun.0.0.1 on 4.14 is now installable. Current state is: failing
orun.0.0.1 on 5.1 is now installable. Current state is: failing
owl-symbolic.0.1.0 on 4.08 had its build status changed: passing to failing
owl-symbolic.0.1.0 on 4.09 had its build status changed: passing to failing
owl-symbolic.0.1.0 on 4.10 had its build status changed: passing to failing
owl-symbolic.0.1.0 on 4.11 had its build status changed: passing to failing
owl-symbolic.0.1.0 on 4.12 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.08 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.09 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.10 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.11 had its build status changed: passing to failing
owl-symbolic.0.2.0 on 4.12 had its build status changed: passing to failing
owl-zoo.1.0.2 on 4.10 is now installable. Current state is: failing
owl-zoo.1.0.2 on 4.11 is now installable. Current state is: failing
owl-zoo.1.0.2 on 4.12 is now installable. Current state is: failing
owl-zoo.1.0.2 on 4.13 is now installable. Current state is: failing
pa_comprehension.0.4 on 5.0 is now installable. Current state is: failing
pa_monad_custom.v6.0.0 on 5.0 is now installable. Current state is: failing
pa_ppx_ag.0.07.02 on 4.10 had its build status changed: passing to failing
pa_ppx_ag.0.07.02 on 4.11 had its build status changed: not available to failing
pa_ppx_ag.0.07.02 on 4.12 had its build status changed: passing to failing
pa_ppx_hashcons.0.07.02 on 4.10 had its build status changed: passing to failing
pa_ppx_hashcons.0.07.02 on 4.11 had its build status changed: not available to failing
pa_ppx_hashcons.0.07.02 on 4.12 had its build status changed: passing to failing
pa_ppx_migrate.0.07.02 on 4.10 had its build status changed: passing to failing
pa_ppx_migrate.0.07.02 on 4.11 had its build status changed: not available to failing
pa_ppx_migrate.0.07.02 on 4.12 had its build status changed: passing to failing
pa_ppx_unique.0.07.02 on 4.10 had its build status changed: passing to failing
pa_ppx_unique.0.07.02 on 4.11 had its build status changed: not available to failing
pa_ppx_unique.0.07.02 on 4.12 had its build status changed: passing to failing
pa_qualified.0.5 on 5.0 is now installable. Current state is: failing
pa_qualified.0.6 on 5.0 is now installable. Current state is: failing
pa_where.0.4 on 5.0 is now installable. Current state is: failing
papi.0.1.1 on 4.14 is now installable. Current state is: failing
papi.0.1.1 on 5.0 is now installable. Current state is: failing
papi.0.1.1 on 5.1 is now installable. Current state is: failing
pari-bindings.0.1 on 4.10 is now installable. Current state is: failing
pari-bindings.0.1 on 4.11 is now installable. Current state is: failing
pari-bindings.0.1 on 4.12 is now installable. Current state is: failing
pari-bindings.0.1 on 4.13 is now installable. Current state is: failing
pari-bindings.0.1 on 4.14 is now installable. Current state is: failing
pari-bindings.0.1 on 5.0 is now installable. Current state is: failing
pari-bindings.0.1 on 5.1 is now installable. Current state is: failing
petr4.0.1 on 4.08 had its build status changed: passing to failing
petr4.0.1 on 4.09 had its build status changed: passing to failing
petr4.0.1.1 on 4.08 had its build status changed: passing to failing
petr4.0.1.1 on 4.09 had its build status changed: passing to failing
portia.1.1 on 4.11 had its build status changed: passing to failing
portia.1.1 on 4.14 is now installable. Current state is: failing
portia.1.1 on 5.0 is now installable. Current state is: failing
portia.1.1 on 5.1 is now installable. Current state is: failing
portia.1.3 on 5.0 is now installable. Current state is: failing
portia.1.3 on 5.1 is now installable. Current state is: failing
portia.1.5 on 4.11 had its build status changed: passing to failing
portia.1.5 on 4.14 is now installable. Current state is: failing
portia.1.5 on 5.0 is now installable. Current state is: failing
portia.1.5 on 5.1 is now installable. Current state is: failing
ppx_deriving_encoding.0.2.3 on 4.08 had its build status changed: passing to failing
ppx_deriving_encoding.0.2.3 on 4.09 had its build status changed: passing to failing
ppx_deriving_encoding.0.2.3 on 4.10 had its build status changed: passing to failing
ppx_deriving_encoding.0.2.3 on 4.11 had its build status changed: passing to failing
ppx_deriving_encoding.0.2.3 on 4.12 had its build status changed: passing to failing
ppx_deriving_encoding.0.2.3 on 4.13 had its build status changed: not available to failing
ppx_deriving_encoding.0.2.3 on 4.14 is now installable. Current state is: failing
ppx_deriving_encoding.0.2.3 on 5.0 is now installable. Current state is: failing
ppx_deriving_encoding.0.2.3 on 5.1 is now installable. Current state is: failing
ppx_pbt.0.2.1 on 4.10 is now installable. Current state is: failing
ppx_pbt.0.2.1 on 4.11 is now installable. Current state is: failing
ppx_pbt.0.2.1 on 4.12 is now installable. Current state is: failing
ppx_pbt.0.2.1 on 4.13 is now installable. Current state is: failing
prof_spacetime.0.3.0 on 4.08 had its build status changed: passing to failing
prof_spacetime.0.3.0 on 4.09 had its build status changed: passing to failing
prof_spacetime.0.3.0 on 4.10 had its build status changed: passing to failing
prof_spacetime.0.3.0 on 4.11 had its build status changed: passing to failing
protocol-9p.1.0.0 on 5.0 is now installable. Current state is: failing
protocol-9p.1.0.0 on 5.1 is now installable. Current state is: failing
protocol-9p.1.0.1 on 5.0 is now installable. Current state is: failing
protocol-9p.1.0.1 on 5.1 is now installable. Current state is: failing
proverif.1.98 on 5.0 is now installable. Current state is: failing
proverif.1.98 on 5.1 is now installable. Current state is: failing
proverif.1.98pl1 on 5.0 is now installable. Current state is: failing
proverif.1.98pl1 on 5.1 is now installable. Current state is: failing
proverif.2.00 on 5.0 is now installable. Current state is: failing
proverif.2.00 on 5.1 is now installable. Current state is: failing
pythonlib.v0.15.1 on 5.1 is now installable. Current state is: failing
radare2.0.0.2 on 4.08 had its build status changed: passing to failing
radare2.0.0.2 on 4.09 had its build status changed: passing to failing
radare2.0.0.2 on 4.10 had its build status changed: passing to failing
radare2.0.0.2 on 4.11 had its build status changed: passing to failing
radare2.0.0.2 on 4.12 had its build status changed: passing to failing
radare2.0.0.2 on 4.13 had its build status changed: passing to failing
radare2.0.0.2 on 4.14 is now installable. Current state is: failing
randoml.0.1.5 on 5.0 is now installable. Current state is: failing
randoml.0.1.5 on 5.1 is now installable. Current state is: failing
rdf.0.11.0 on 4.08 had its build status changed: passing to failing
rdf.0.11.0 on 4.09 had its build status changed: passing to failing
rdf.0.11.0 on 4.10 had its build status changed: passing to failing
rdf.0.12.0 on 4.12 is now installable. Current state is: failing
reason.3.5.0 on 4.08 had its build status changed: passing to failing
reason.3.5.2 on 4.08 had its build status changed: passing to failing
reason.3.5.2 on 4.09 had its build status changed: passing to failing
records.0.6.0 on 4.08 had its build status changed: passing to failing
rosetta.0.1.0 on 4.08 had its build status changed: passing to failing
rosetta.0.1.0 on 4.09 had its build status changed: passing to failing
rosetta.0.1.0 on 4.10 had its build status changed: passing to failing
rosetta.0.1.0 on 4.11 had its build status changed: passing to failing
rotor.0.1 on 4.08 had its build status changed: internal failure to failing
rpclib.6.0.0 on 4.08 had its build status changed: passing to failing
rpclib.6.0.0 on 4.09 had its build status changed: passing to failing
rtop.3.6.2 on 4.08 had its build status changed: passing to failing
rtop.3.6.2 on 4.09 had its build status changed: passing to failing
rtop.3.6.2 on 4.10 had its build status changed: passing to failing
rtop.3.6.2 on 4.11 had its build status changed: passing to failing
rtop.3.7.0 on 4.08 had its build status changed: passing to failing
rtop.3.7.0 on 4.09 had its build status changed: passing to failing
rtop.3.7.0 on 4.10 had its build status changed: passing to failing
rtop.3.7.0 on 4.11 had its build status changed: passing to failing
rtop.3.7.0 on 4.12 had its build status changed: passing to failing
sanlock.0.0.9 on 4.08 had its build status changed: passing to failing
sanlock.0.0.9 on 4.09 had its build status changed: passing to failing
sanlock.0.0.9 on 4.10 had its build status changed: passing to failing
sanlock.0.0.9 on 4.11 had its build status changed: passing to failing
sanlock.0.0.9 on 4.12 had its build status changed: passing to failing
scid.1.0 on 5.0 is now installable. Current state is: failing
scid.1.0 on 5.1 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.5 on 4.08 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.5 on 4.09 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.5 on 4.10 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.5 on 4.11 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.5 on 4.12 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.5 on 4.13 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.5 on 4.14 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.5 on 5.0 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.5 on 5.1 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.6 on 4.08 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.6 on 4.09 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.6 on 4.10 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.6 on 4.11 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.6 on 4.12 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.6 on 4.13 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.6 on 4.14 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.6 on 5.0 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.7 on 4.08 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.7 on 4.09 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.7 on 4.10 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.7 on 4.11 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.7 on 4.12 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.7 on 4.13 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.7 on 4.14 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.7 on 5.0 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.8 on 4.08 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.8 on 4.09 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.8 on 4.10 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.8 on 4.11 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.8 on 4.12 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.8 on 4.13 had its build status changed: passing to failing
solo5-bindings-hvt.0.6.8 on 4.14 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.8 on 5.0 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 4.08 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 4.09 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 4.10 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 4.11 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 4.12 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 4.13 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 4.14 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 5.0 is now installable. Current state is: failing
solo5-bindings-hvt.0.6.9 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.5 on 4.08 had its build status changed: passing to failing
solo5-bindings-muen.0.6.5 on 4.09 had its build status changed: passing to failing
solo5-bindings-muen.0.6.5 on 4.10 had its build status changed: passing to failing
solo5-bindings-muen.0.6.5 on 4.11 had its build status changed: passing to failing
solo5-bindings-muen.0.6.5 on 4.12 had its build status changed: passing to failing
solo5-bindings-muen.0.6.5 on 4.13 had its build status changed: passing to failing
solo5-bindings-muen.0.6.5 on 4.14 is now installable. Current state is: failing
solo5-bindings-muen.0.6.5 on 5.0 is now installable. Current state is: failing
solo5-bindings-muen.0.6.5 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.6 on 4.08 had its build status changed: passing to failing
solo5-bindings-muen.0.6.6 on 4.09 had its build status changed: passing to failing
solo5-bindings-muen.0.6.6 on 4.10 had its build status changed: passing to failing
solo5-bindings-muen.0.6.6 on 4.11 had its build status changed: passing to failing
solo5-bindings-muen.0.6.6 on 4.12 had its build status changed: passing to failing
solo5-bindings-muen.0.6.6 on 4.13 had its build status changed: passing to failing
solo5-bindings-muen.0.6.6 on 4.14 is now installable. Current state is: failing
solo5-bindings-muen.0.6.6 on 5.0 is now installable. Current state is: failing
solo5-bindings-muen.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.7 on 4.08 had its build status changed: passing to failing
solo5-bindings-muen.0.6.7 on 4.09 had its build status changed: passing to failing
solo5-bindings-muen.0.6.7 on 4.10 had its build status changed: passing to failing
solo5-bindings-muen.0.6.7 on 4.11 had its build status changed: passing to failing
solo5-bindings-muen.0.6.7 on 4.12 had its build status changed: passing to failing
solo5-bindings-muen.0.6.7 on 4.13 had its build status changed: passing to failing
solo5-bindings-muen.0.6.7 on 4.14 is now installable. Current state is: failing
solo5-bindings-muen.0.6.7 on 5.0 is now installable. Current state is: failing
solo5-bindings-muen.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.8 on 4.08 had its build status changed: passing to failing
solo5-bindings-muen.0.6.8 on 4.09 had its build status changed: passing to failing
solo5-bindings-muen.0.6.8 on 4.10 had its build status changed: passing to failing
solo5-bindings-muen.0.6.8 on 4.11 had its build status changed: passing to failing
solo5-bindings-muen.0.6.8 on 4.12 had its build status changed: passing to failing
solo5-bindings-muen.0.6.8 on 4.13 had its build status changed: passing to failing
solo5-bindings-muen.0.6.8 on 4.14 is now installable. Current state is: failing
solo5-bindings-muen.0.6.8 on 5.0 is now installable. Current state is: failing
solo5-bindings-muen.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 4.08 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 4.09 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 4.10 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 4.11 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 4.12 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 4.13 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 4.14 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 5.0 is now installable. Current state is: failing
solo5-bindings-muen.0.6.9 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.5 on 4.08 had its build status changed: passing to failing
solo5-bindings-spt.0.6.5 on 4.09 had its build status changed: passing to failing
solo5-bindings-spt.0.6.5 on 4.10 had its build status changed: passing to failing
solo5-bindings-spt.0.6.5 on 4.11 had its build status changed: passing to failing
solo5-bindings-spt.0.6.5 on 4.12 had its build status changed: passing to failing
solo5-bindings-spt.0.6.5 on 4.13 had its build status changed: passing to failing
solo5-bindings-spt.0.6.5 on 4.14 is now installable. Current state is: failing
solo5-bindings-spt.0.6.5 on 5.0 is now installable. Current state is: failing
solo5-bindings-spt.0.6.5 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.6 on 4.08 had its build status changed: passing to failing
solo5-bindings-spt.0.6.6 on 4.09 had its build status changed: passing to failing
solo5-bindings-spt.0.6.6 on 4.10 had its build status changed: passing to failing
solo5-bindings-spt.0.6.6 on 4.11 had its build status changed: passing to failing
solo5-bindings-spt.0.6.6 on 4.12 had its build status changed: passing to failing
solo5-bindings-spt.0.6.6 on 4.13 had its build status changed: passing to failing
solo5-bindings-spt.0.6.6 on 4.14 is now installable. Current state is: failing
solo5-bindings-spt.0.6.6 on 5.0 is now installable. Current state is: failing
solo5-bindings-spt.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.7 on 4.08 had its build status changed: passing to failing
solo5-bindings-spt.0.6.7 on 4.09 had its build status changed: passing to failing
solo5-bindings-spt.0.6.7 on 4.10 had its build status changed: passing to failing
solo5-bindings-spt.0.6.7 on 4.11 had its build status changed: passing to failing
solo5-bindings-spt.0.6.7 on 4.12 had its build status changed: passing to failing
solo5-bindings-spt.0.6.7 on 4.13 had its build status changed: passing to failing
solo5-bindings-spt.0.6.7 on 4.14 is now installable. Current state is: failing
solo5-bindings-spt.0.6.7 on 5.0 is now installable. Current state is: failing
solo5-bindings-spt.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.8 on 4.08 had its build status changed: passing to failing
solo5-bindings-spt.0.6.8 on 4.09 had its build status changed: passing to failing
solo5-bindings-spt.0.6.8 on 4.10 had its build status changed: passing to failing
solo5-bindings-spt.0.6.8 on 4.11 had its build status changed: passing to failing
solo5-bindings-spt.0.6.8 on 4.12 had its build status changed: passing to failing
solo5-bindings-spt.0.6.8 on 4.13 had its build status changed: passing to failing
solo5-bindings-spt.0.6.8 on 4.14 is now installable. Current state is: failing
solo5-bindings-spt.0.6.8 on 5.0 is now installable. Current state is: failing
solo5-bindings-spt.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 4.08 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 4.09 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 4.10 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 4.11 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 4.12 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 4.13 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 4.14 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 5.0 is now installable. Current state is: failing
solo5-bindings-spt.0.6.9 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.5 on 4.08 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.5 on 4.09 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.5 on 4.10 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.5 on 4.11 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.5 on 4.12 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.5 on 4.13 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.5 on 4.14 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.5 on 5.0 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.5 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.6 on 4.08 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.6 on 4.09 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.6 on 4.10 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.6 on 4.11 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.6 on 4.12 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.6 on 4.13 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.6 on 4.14 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.6 on 5.0 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.7 on 4.08 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.7 on 4.09 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.7 on 4.10 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.7 on 4.11 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.7 on 4.12 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.7 on 4.13 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.7 on 4.14 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.7 on 5.0 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.8 on 4.08 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.8 on 4.09 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.8 on 4.10 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.8 on 4.11 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.8 on 4.12 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.8 on 4.13 had its build status changed: passing to failing
solo5-bindings-virtio.0.6.8 on 4.14 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.8 on 5.0 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 4.08 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 4.09 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 4.10 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 4.11 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 4.12 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 4.13 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 4.14 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 5.0 is now installable. Current state is: failing
solo5-bindings-virtio.0.6.9 on 5.1 is now installable. Current state is: failing
solo5-bindings-xen.0.6.6 on 4.08 had its build status changed: passing to failing
solo5-bindings-xen.0.6.6 on 4.09 had its build status changed: passing to failing
solo5-bindings-xen.0.6.6 on 4.10 had its build status changed: passing to failing
solo5-bindings-xen.0.6.6 on 4.11 had its build status changed: passing to failing
solo5-bindings-xen.0.6.6 on 4.12 had its build status changed: passing to failing
solo5-bindings-xen.0.6.6 on 4.13 had its build status changed: passing to failing
solo5-bindings-xen.0.6.6 on 4.14 is now installable. Current state is: failing
solo5-bindings-xen.0.6.6 on 5.0 is now installable. Current state is: failing
solo5-bindings-xen.0.6.6 on 5.1 is now installable. Current state is: failing
solo5-bindings-xen.0.6.7 on 4.08 had its build status changed: passing to failing
solo5-bindings-xen.0.6.7 on 4.09 had its build status changed: passing to failing
solo5-bindings-xen.0.6.7 on 4.10 had its build status changed: passing to failing
solo5-bindings-xen.0.6.7 on 4.11 had its build status changed: passing to failing
solo5-bindings-xen.0.6.7 on 4.12 had its build status changed: passing to failing
solo5-bindings-xen.0.6.7 on 4.13 had its build status changed: passing to failing
solo5-bindings-xen.0.6.7 on 4.14 is now installable. Current state is: failing
solo5-bindings-xen.0.6.7 on 5.0 is now installable. Current state is: failing
solo5-bindings-xen.0.6.7 on 5.1 is now installable. Current state is: failing
solo5-bindings-xen.0.6.8 on 4.08 had its build status changed: passing to failing
solo5-bindings-xen.0.6.8 on 4.09 had its build status changed: passing to failing
solo5-bindings-xen.0.6.8 on 4.10 had its build status changed: passing to failing
solo5-bindings-xen.0.6.8 on 4.11 had its build status changed: passing to failing
solo5-bindings-xen.0.6.8 on 4.12 had its build status changed: passing to failing
solo5-bindings-xen.0.6.8 on 4.13 had its build status changed: passing to failing
solo5-bindings-xen.0.6.8 on 4.14 is now installable. Current state is: failing
solo5-bindings-xen.0.6.8 on 5.0 is now installable. Current state is: failing
solo5-bindings-xen.0.6.8 on 5.1 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 4.08 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 4.09 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 4.10 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 4.11 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 4.12 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 4.13 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 4.14 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 5.0 is now installable. Current state is: failing
solo5-bindings-xen.0.6.9 on 5.1 is now installable. Current state is: failing
solo5-cross-aarch64.0.7.1 on 4.09 is now installable. Current state is: failing
solo5-cross-aarch64.0.7.1 on 4.13 is now installable. Current state is: failing
solo5.0.7.0 on 4.08 is now installable. Current state is: failing
solo5.0.7.0 on 4.09 is now installable. Current state is: failing
solo5.0.7.0 on 4.10 is now installable. Current state is: failing
solo5.0.7.0 on 4.11 is now installable. Current state is: failing
solo5.0.7.0 on 4.12 is now installable. Current state is: failing
solo5.0.7.0 on 4.13 is now installable. Current state is: failing
solo5.0.7.0 on 4.14 is now installable. Current state is: failing
solo5.0.7.0 on 5.0 is now installable. Current state is: failing
solo5.0.7.0 on 5.1 is now installable. Current state is: failing
solo5.0.7.1 on 4.08 is now installable. Current state is: failing
solo5.0.7.1 on 4.09 is now installable. Current state is: failing
solo5.0.7.1 on 4.10 is now installable. Current state is: failing
solo5.0.7.1 on 4.11 is now installable. Current state is: failing
solo5.0.7.1 on 4.12 is now installable. Current state is: failing
solo5.0.7.1 on 4.13 is now installable. Current state is: failing
solo5.0.7.1 on 4.14 is now installable. Current state is: failing
solo5.0.7.1 on 5.0 is now installable. Current state is: failing
solo5.0.7.1 on 5.1 is now installable. Current state is: failing
srt.0.2.0 on 4.08 is now installable. Current state is: failing
srt.0.2.0 on 4.09 is now installable. Current state is: failing
srt.0.2.0 on 4.10 is now installable. Current state is: failing
srt.0.2.0 on 4.11 is now installable. Current state is: failing
srt.0.2.0 on 4.12 is now installable. Current state is: failing
srt.0.2.0 on 4.13 is now installable. Current state is: failing
srt.0.2.0 on 4.14 is now installable. Current state is: failing
srt.0.2.0 on 5.0 is now installable. Current state is: failing
srt.0.2.0 on 5.1 is now installable. Current state is: failing
srt.0.2.1 on 4.08 is now installable. Current state is: failing
srt.0.2.1 on 4.09 is now installable. Current state is: failing
srt.0.2.1 on 4.10 is now installable. Current state is: failing
srt.0.2.1 on 4.11 is now installable. Current state is: failing
srt.0.2.1 on 4.12 is now installable. Current state is: failing
srt.0.2.1 on 4.13 is now installable. Current state is: failing
srt.0.2.1 on 4.14 is now installable. Current state is: failing
srt.0.2.1 on 5.0 is now installable. Current state is: failing
srt.0.2.1 on 5.1 is now installable. Current state is: failing
stdcompat.0 on 5.0 is now installable. Current state is: failing
stdcompat.0 on 5.1 is now installable. Current state is: failing
stdcompat.1 on 5.0 is now installable. Current state is: failing
stdcompat.1 on 5.1 is now installable. Current state is: failing
stdcompat.10 on 4.08 had its build status changed: passing to failing
stdcompat.10 on 4.09 had its build status changed: passing to failing
stdcompat.11 on 4.08 had its build status changed: passing to failing
stdcompat.11 on 4.09 had its build status changed: passing to failing
stdcompat.12 on 4.08 had its build status changed: passing to failing
stdcompat.12 on 4.09 had its build status changed: passing to failing
stdcompat.12 on 4.10 had its build status changed: passing to failing
stdcompat.13 on 4.08 had its build status changed: passing to failing
stdcompat.13 on 4.09 had its build status changed: passing to failing
stdcompat.13 on 4.10 had its build status changed: passing to failing
stdcompat.14 on 4.08 had its build status changed: passing to failing
stdcompat.14 on 4.09 had its build status changed: passing to failing
stdcompat.14 on 4.10 had its build status changed: passing to failing
stdcompat.14 on 4.11 had its build status changed: passing to failing
stdcompat.15 on 4.08 had its build status changed: passing to failing
stdcompat.15 on 4.09 had its build status changed: passing to failing
stdcompat.15 on 4.10 had its build status changed: passing to failing
stdcompat.15 on 4.11 had its build status changed: passing to failing
stdcompat.15 on 4.12 had its build status changed: passing to failing
stdcompat.15 on 4.13 had its build status changed: passing to failing
stdcompat.15 on 4.14 is now installable. Current state is: failing
stdcompat.16 on 4.08 is now installable. Current state is: failing
stdcompat.16 on 4.09 is now installable. Current state is: failing
stdcompat.16 on 4.10 is now installable. Current state is: failing
stdcompat.16 on 4.11 is now installable. Current state is: failing
stdcompat.16 on 4.12 is now installable. Current state is: failing
stdcompat.16 on 4.13 is now installable. Current state is: failing
stdcompat.16 on 4.14 is now installable. Current state is: failing
stdcompat.17 on 4.08 is now installable. Current state is: failing
stdcompat.17 on 4.09 is now installable. Current state is: failing
stdcompat.17 on 4.10 is now installable. Current state is: failing
stdcompat.17 on 4.11 is now installable. Current state is: failing
stdcompat.17 on 4.12 is now installable. Current state is: failing
stdcompat.17 on 4.13 is now installable. Current state is: failing
stdcompat.17 on 4.14 is now installable. Current state is: failing
stdcompat.18 on 4.08 is now installable. Current state is: failing
stdcompat.18 on 4.09 is now installable. Current state is: failing
stdcompat.18 on 4.10 is now installable. Current state is: failing
stdcompat.18 on 4.11 is now installable. Current state is: failing
stdcompat.18 on 4.12 is now installable. Current state is: failing
stdcompat.18 on 4.13 is now installable. Current state is: failing
stdcompat.18 on 4.14 is now installable. Current state is: failing
stdcompat.7 on 4.08 had its build status changed: passing to failing
stdcompat.9 on 4.08 had its build status changed: passing to failing
stog.0.19.0 on 4.12 is now installable. Current state is: failing
stog_rdf.0.20.0 on 4.12 is now installable. Current state is: failing
stog_server.0.20.0 on 4.12 is now installable. Current state is: failing
sundialsml.5.8.0p0 on 4.08 is now installable. Current state is: failing
sundialsml.5.8.0p0 on 4.09 is now installable. Current state is: failing
sundialsml.5.8.0p0 on 4.10 is now installable. Current state is: failing
sundialsml.5.8.0p0 on 4.11 is now installable. Current state is: failing
sundialsml.5.8.0p0 on 4.12 is now installable. Current state is: failing
sundialsml.5.8.0p0 on 4.13 is now installable. Current state is: failing
sundialsml.6.0.0p0 on 4.08 is now installable. Current state is: failing
sundialsml.6.0.0p0 on 4.09 is now installable. Current state is: failing
sundialsml.6.0.0p0 on 4.10 is now installable. Current state is: failing
sundialsml.6.0.0p0 on 4.11 is now installable. Current state is: failing
sundialsml.6.0.0p0 on 4.12 is now installable. Current state is: failing
sundialsml.6.0.0p0 on 4.13 is now installable. Current state is: failing
sundialsml.6.1.0p0 on 4.08 is now installable. Current state is: failing
sundialsml.6.1.0p0 on 4.09 is now installable. Current state is: failing
sundialsml.6.1.0p0 on 4.10 is now installable. Current state is: failing
sundialsml.6.1.0p0 on 4.11 is now installable. Current state is: failing
sundialsml.6.1.0p0 on 4.12 is now installable. Current state is: failing
sundialsml.6.1.0p0 on 4.13 is now installable. Current state is: failing
sundialsml.6.1.1p0 on 4.08 is now installable. Current state is: failing
sundialsml.6.1.1p0 on 4.09 is now installable. Current state is: failing
sundialsml.6.1.1p0 on 4.10 is now installable. Current state is: failing
sundialsml.6.1.1p0 on 4.11 is now installable. Current state is: failing
sundialsml.6.1.1p0 on 4.12 is now installable. Current state is: failing
sundialsml.6.1.1p0 on 4.13 is now installable. Current state is: failing
sundialsml.6.1.1p1 on 4.08 is now installable. Current state is: failing
sundialsml.6.1.1p1 on 4.09 is now installable. Current state is: failing
sundialsml.6.1.1p1 on 4.10 is now installable. Current state is: failing
sundialsml.6.1.1p1 on 4.11 is now installable. Current state is: failing
sundialsml.6.1.1p1 on 4.12 is now installable. Current state is: failing
sundialsml.6.1.1p1 on 4.13 is now installable. Current state is: failing
sundialsml.6.1.1p1 on 4.14 is now installable. Current state is: failing
systemverilog.0.0.1 on 5.1 is now installable. Current state is: failing
tcpip.4.0.0 on 4.08 had its build status changed: passing to failing
tcpip.4.0.0 on 4.09 had its build status changed: passing to failing
tcpip.4.0.0 on 4.10 had its build status changed: passing to failing
tcpip.4.0.0 on 4.11 had its build status changed: passing to failing
tidy.1-4.9.30-0.1.1 on 4.08 had its build status changed: internal failure to failing
tidy.1-4.9.30-0.1.1 on 4.09 had its build status changed: internal failure to failing
torch.0.10 on 4.08 had its build status changed: passing to failing
torch.0.10 on 4.09 had its build status changed: passing to failing
torch.0.10 on 4.10 had its build status changed: passing to failing
torch.0.10 on 4.11 had its build status changed: passing to failing
torch.0.10 on 4.12 had its build status changed: passing to failing
torch.0.10 on 4.13 had its build status changed: not available to failing
torch.0.10 on 4.14 is now installable. Current state is: failing
torch.0.10 on 5.0 is now installable. Current state is: failing
torch.0.10 on 5.1 is now installable. Current state is: failing
torch.0.11 on 4.08 had its build status changed: passing to failing
torch.0.11 on 4.09 had its build status changed: passing to failing
torch.0.11 on 4.10 had its build status changed: passing to failing
torch.0.11 on 4.11 had its build status changed: passing to failing
torch.0.11 on 4.12 had its build status changed: passing to failing
torch.0.11 on 4.13 had its build status changed: not available to failing
torch.0.11 on 4.14 is now installable. Current state is: failing
torch.0.11 on 5.0 is now installable. Current state is: failing
torch.0.11 on 5.1 is now installable. Current state is: failing
torch.0.12 on 4.08 had its build status changed: passing to failing
torch.0.12 on 4.09 had its build status changed: passing to failing
torch.0.12 on 4.10 had its build status changed: passing to failing
torch.0.12 on 4.11 had its build status changed: passing to failing
torch.0.12 on 4.12 had its build status changed: passing to failing
torch.0.12 on 4.13 had its build status changed: not available to failing
torch.0.12 on 4.14 is now installable. Current state is: failing
torch.0.12 on 5.0 is now installable. Current state is: failing
torch.0.12 on 5.1 is now installable. Current state is: failing
torch.0.13 on 4.08 is now installable. Current state is: failing
torch.0.13 on 4.09 is now installable. Current state is: failing
torch.0.13 on 4.10 is now installable. Current state is: failing
torch.0.13 on 4.11 is now installable. Current state is: failing
torch.0.13 on 4.12 is now installable. Current state is: failing
torch.0.13 on 4.13 is now installable. Current state is: failing
torch.0.13 on 4.14 is now installable. Current state is: failing
torch.0.13 on 5.0 is now installable. Current state is: failing
torch.0.13 on 5.1 is now installable. Current state is: failing
tplib.1.3 on 5.0 is now installable. Current state is: failing
tplib.1.3 on 5.1 is now installable. Current state is: failing
tuareg.2.0.10 on 4.08 had its build status changed: passing to failing
tuareg.2.0.10 on 4.09 had its build status changed: passing to failing
tuareg.2.0.10 on 4.10 had its build status changed: passing to failing
tuareg.2.0.10 on 4.11 had its build status changed: passing to failing
tuareg.2.0.10 on 4.12 had its build status changed: passing to failing
tuareg.2.0.10 on 4.13 had its build status changed: passing to failing
tuareg.2.0.10 on 4.14 is now installable. Current state is: failing
tuareg.2.0.10 on 5.0 is now installable. Current state is: failing
tuareg.2.0.10 on 5.1 is now installable. Current state is: failing
tuareg.2.0.7 on 4.08 had its build status changed: passing to failing
tuareg.2.0.7 on 4.09 had its build status changed: passing to failing
tuareg.2.0.7 on 4.10 had its build status changed: passing to failing
tuareg.2.0.7 on 4.11 had its build status changed: passing to failing
tuareg.2.0.7 on 4.12 had its build status changed: passing to failing
tuareg.2.0.7 on 4.13 had its build status changed: passing to failing
tuareg.2.0.7 on 4.14 is now installable. Current state is: failing
tuareg.2.0.7 on 5.0 is now installable. Current state is: failing
tuareg.2.0.7 on 5.1 is now installable. Current state is: failing
tuareg.2.1.0 on 4.11 had its build status changed: passing to failing
tuareg.2.1.0 on 4.12 had its build status changed: passing to failing
tuareg.2.1.0 on 4.13 had its build status changed: passing to failing
tuareg.2.1.0 on 4.14 is now installable. Current state is: failing
tuareg.2.1.0 on 5.0 is now installable. Current state is: failing
type_conv.113.00.02 on 5.0 is now installable. Current state is: failing
uri.1.9.7 on 4.12 had its build status changed: passing to failing
uuuu.0.1.0 on 4.08 had its build status changed: passing to failing
uuuu.0.1.1 on 4.08 had its build status changed: passing to failing
uwt.0.3.0 on 4.08 had its build status changed: passing to failing
uwt.0.3.0 on 4.09 had its build status changed: passing to failing
uwt.0.3.0 on 4.10 had its build status changed: passing to failing
uwt.0.3.0 on 4.11 had its build status changed: passing to failing
uwt.0.3.0.2 on 4.08 had its build status changed: passing to failing
uwt.0.3.0.2 on 4.09 had its build status changed: passing to failing
uwt.0.3.0.2 on 4.10 had its build status changed: passing to failing
uwt.0.3.0.2 on 4.11 had its build status changed: passing to failing
uwt.0.3.2 on 4.08 had its build status changed: passing to failing
uwt.0.3.2 on 4.09 had its build status changed: passing to failing
uwt.0.3.2 on 4.10 had its build status changed: passing to failing
uwt.0.3.2 on 4.11 had its build status changed: passing to failing
uwt.0.3.3 on 4.08 had its build status changed: passing to failing
uwt.0.3.3 on 4.09 had its build status changed: passing to failing
uwt.0.3.3 on 4.10 had its build status changed: passing to failing
uwt.0.3.3 on 4.11 had its build status changed: passing to failing
vcaml.v0.16.0 on 5.1 is now installable. Current state is: failing
vhd-format.0.12.0 on 4.08 had its build status changed: passing to failing
vhd-format.0.12.0 on 4.09 had its build status changed: passing to failing
vhd-format.0.12.0 on 4.10 had its build status changed: passing to failing
vhd-format.0.12.0 on 4.11 had its build status changed: passing to failing
vhd-format.0.12.0 on 4.12 had its build status changed: passing to failing
vhd-format.0.12.1 on 4.08 is now installable. Current state is: failing
vhd-format.0.12.1 on 4.09 is now installable. Current state is: failing
vhd-format.0.12.1 on 4.10 is now installable. Current state is: failing
vhd-format.0.12.1 on 4.11 is now installable. Current state is: failing
vhd-format.0.12.1 on 4.12 is now installable. Current state is: failing
volt.1.4 on 5.0 is now installable. Current state is: failing
yaml.0.2.1 on 4.08 had its build status changed: passing to failing
yaml.0.2.1 on 4.09 had its build status changed: passing to failing
yaml.0.2.1 on 4.10 had its build status changed: passing to failing
yaml.0.2.1 on 4.11 had its build status changed: passing to failing
yuscii.0.2.0 on 4.08 had its build status changed: passing to failing
yuscii.0.2.0 on 4.09 had its build status changed: passing to failing
yuscii.0.2.0 on 4.10 had its build status changed: passing to failing
yuscii.0.2.0 on 4.11 had its build status changed: passing to failing
z3.4.12.2 on 4.08 is now installable. Current state is: failing
z3.4.12.2 on 4.09 is now installable. Current state is: failing
z3.4.12.2 on 4.10 is now installable. Current state is: failing
z3.4.12.2 on 4.11 is now installable. Current state is: failing
z3.4.12.2 on 4.12 is now installable. Current state is: failing
z3.4.12.2 on 4.13 is now installable. Current state is: failing
z3.4.12.2 on 4.14 is now installable. Current state is: failing
z3.4.12.2 on 5.0 is now installable. Current state is: failing
z3.4.12.2 on 5.1 is now installable. Current state is: failing
z3.4.8.14 on 5.0 is now installable. Current state is: failing
z3.4.8.14 on 5.1 is now installable. Current state is: failing

Packages now partially failing:

binaryen.0.19.0 on 4.12 is now installable. Current state is: partially failing
binaryen.0.19.0 on 4.13 is now installable. Current state is: partially failing
binaryen.0.19.0 on 4.14 is now installable. Current state is: partially failing
binaryen.0.19.0 on 5.0 is now installable. Current state is: partially failing
binaryen.0.19.0 on 5.1 is now installable. Current state is: partially failing
binaryen.0.20.0 on 4.12 is now installable. Current state is: partially failing
binaryen.0.20.0 on 4.13 is now installable. Current state is: partially failing
binaryen.0.20.0 on 4.14 is now installable. Current state is: partially failing
binaryen.0.20.0 on 5.0 is now installable. Current state is: partially failing
binaryen.0.20.1 on 4.12 is now installable. Current state is: partially failing
binaryen.0.20.1 on 4.13 is now installable. Current state is: partially failing
binaryen.0.20.1 on 4.14 is now installable. Current state is: partially failing
binaryen.0.20.1 on 5.0 is now installable. Current state is: partially failing
binaryen.0.21.0 on 4.12 is now installable. Current state is: partially failing
binaryen.0.21.0 on 4.13 is now installable. Current state is: partially failing
binaryen.0.21.0 on 4.14 is now installable. Current state is: partially failing
binaryen.0.21.0 on 5.0 is now installable. Current state is: partially failing
binaryen.0.21.0 on 5.1 is now installable. Current state is: partially failing
clangml-transforms.0.26 on 4.08 had its build status changed: passing to partially failing
clangml-transforms.0.26 on 4.09 had its build status changed: passing to partially failing
clangml-transforms.0.26 on 4.10 had its build status changed: passing to partially failing
clangml-transforms.0.26 on 4.11 had its build status changed: passing to partially failing
clangml-transforms.0.26 on 4.12 had its build status changed: not available to partially failing
clangml-transforms.0.26 on 4.13 had its build status changed: not available to partially failing
clangml-transforms.0.26 on 4.14 is now installable. Current state is: partially failing
clangml-transforms.0.26 on 5.0 is now installable. Current state is: partially failing
clangml.4.0.0 on 4.08 had its build status changed: failing to partially failing
clangml.4.0.0 on 4.09 had its build status changed: failing to partially failing
clangml.4.0.1 on 4.10 had its build status changed: failing to partially failing
clangml.4.0.1 on 4.11 had its build status changed: failing to partially failing
clangml.4.1.0 on 4.08 had its build status changed: failing to partially failing
clangml.4.1.0 on 4.09 had its build status changed: failing to partially failing
clangml.4.1.0 on 4.10 had its build status changed: failing to partially failing
clangml.4.1.0 on 4.11 had its build status changed: failing to partially failing
clangml.4.2.0 on 4.08 had its build status changed: failing to partially failing
clangml.4.2.0 on 4.09 had its build status changed: failing to partially failing
clangml.4.2.0 on 4.10 had its build status changed: failing to partially failing
clangml.4.2.0 on 4.11 had its build status changed: failing to partially failing
clangml.4.3.0 on 4.08 had its build status changed: failing to partially failing
clangml.4.3.0 on 4.09 had its build status changed: failing to partially failing
clangml.4.3.0 on 4.10 had its build status changed: failing to partially failing
clangml.4.3.0 on 4.11 had its build status changed: failing to partially failing
clangml.4.4.0 on 4.08 had its build status changed: passing to partially failing
clangml.4.4.0 on 4.09 had its build status changed: passing to partially failing
clangml.4.4.0 on 4.10 had its build status changed: passing to partially failing
clangml.4.4.0 on 4.11 had its build status changed: passing to partially failing
clangml.4.4.0 on 4.12 had its build status changed: passing to partially failing
clangml.4.4.0 on 4.13 had its build status changed: not available to partially failing
clangml.4.5.0 on 4.08 is now installable. Current state is: partially failing
clangml.4.5.0 on 4.09 is now installable. Current state is: partially failing
clangml.4.5.0 on 4.10 is now installable. Current state is: partially failing
clangml.4.5.0 on 4.11 is now installable. Current state is: partially failing
clangml.4.5.0 on 4.12 is now installable. Current state is: partially failing
clangml.4.5.0 on 4.13 is now installable. Current state is: partially failing
clangml.4.5.0 on 4.14 is now installable. Current state is: partially failing
clangml.4.7.0 on 4.08 is now installable. Current state is: partially failing
clangml.4.7.0 on 4.09 is now installable. Current state is: partially failing
clangml.4.7.0 on 4.10 is now installable. Current state is: partially failing
clangml.4.7.0 on 4.11 is now installable. Current state is: partially failing
clangml.4.7.0 on 4.12 is now installable. Current state is: partially failing
clangml.4.7.0 on 4.13 is now installable. Current state is: partially failing
clangml.4.7.0 on 4.14 is now installable. Current state is: partially failing
clangml.4.7.0 on 5.0 is now installable. Current state is: partially failing
clangml.4.8.0 on 4.08 is now installable. Current state is: partially failing
clangml.4.8.0 on 4.09 is now installable. Current state is: partially failing
clangml.4.8.0 on 4.10 is now installable. Current state is: partially failing
clangml.4.8.0 on 4.11 is now installable. Current state is: partially failing
clangml.4.8.0 on 4.12 is now installable. Current state is: partially failing
clangml.4.8.0 on 4.13 is now installable. Current state is: partially failing
clangml.4.8.0 on 4.14 is now installable. Current state is: partially failing
clangml.4.8.0 on 5.0 is now installable. Current state is: partially failing
distributed-lwt.0.2.0 on 5.0 is now installable. Current state is: partially failing
distributed-lwt.0.2.0 on 5.1 is now installable. Current state is: partially failing
distributed-uwt.0.1.0 on 4.08 had its build status changed: passing to partially failing
distributed-uwt.0.1.0 on 4.09 had its build status changed: passing to partially failing
distributed-uwt.0.1.0 on 4.10 had its build status changed: passing to partially failing
distributed-uwt.0.1.0 on 4.11 had its build status changed: passing to partially failing
distributed-uwt.0.2.0 on 4.08 had its build status changed: passing to partially failing
distributed-uwt.0.2.0 on 4.09 had its build status changed: passing to partially failing
distributed-uwt.0.2.0 on 4.10 had its build status changed: passing to partially failing
distributed-uwt.0.2.0 on 4.11 had its build status changed: passing to partially failing
docteur-solo5.0.0.2 on 4.08 is now installable. Current state is: partially failing
docteur-solo5.0.0.2 on 4.09 is now installable. Current state is: partially failing
docteur-solo5.0.0.2 on 4.10 is now installable. Current state is: partially failing
docteur-solo5.0.0.2 on 4.11 is now installable. Current state is: partially failing
docteur-solo5.0.0.2 on 4.12 is now installable. Current state is: partially failing
docteur-solo5.0.0.2 on 4.13 is now installable. Current state is: partially failing
docteur-solo5.0.0.2 on 4.14 is now installable. Current state is: partially failing
docteur.0.0.1 on 4.08 had its build status changed: passing to partially failing
docteur.0.0.1 on 4.09 had its build status changed: passing to partially failing
docteur.0.0.1 on 4.10 had its build status changed: passing to partially failing
docteur.0.0.1 on 4.11 had its build status changed: passing to partially failing
docteur.0.0.1 on 4.12 had its build status changed: passing to partially failing
docteur.0.0.1 on 4.13 had its build status changed: not available to partially failing
docteur.0.0.1 on 4.14 is now installable. Current state is: partially failing
dyntype.0.9.0 on 5.0 is now installable. Current state is: partially failing
elasticsearch-cli.0.4 on 4.08 had its build status changed: passing to partially failing
elasticsearch-cli.0.4 on 4.09 had its build status changed: passing to partially failing
elasticsearch-cli.0.4 on 4.10 had its build status changed: passing to partially failing
elasticsearch-cli.0.4 on 4.11 had its build status changed: passing to partially failing
fm-simplex-plugin.1.30 on 4.08 had its build status changed: passing to partially failing
fm-simplex-plugin.1.30 on 4.09 had its build status changed: passing to partially failing
fm-simplex-plugin.1.30 on 4.10 had its build status changed: passing to partially failing
fm-simplex-plugin.1.30 on 4.11 had its build status changed: passing to partially failing
fm-simplex-plugin.1.30 on 4.12 had its build status changed: passing to partially failing
fm-simplex-plugin.1.30 on 4.13 had its build status changed: passing to partially failing
fm-simplex-plugin.1.30 on 4.14 is now installable. Current state is: partially failing
frama-c-metacsl.0.1 on 4.08 had its build status changed: passing to partially failing
frama-c-metacsl.0.1 on 4.09 had its build status changed: passing to partially failing
frama-c-metacsl.0.1 on 4.10 had its build status changed: passing to partially failing
frama-c-metacsl.0.1 on 4.11 had its build status changed: passing to partially failing
frama-c-metacsl.0.1 on 4.12 had its build status changed: passing to partially failing
frama-c-metacsl.0.1 on 4.13 had its build status changed: passing to partially failing
frama-c-metacsl.0.1 on 4.14 is now installable. Current state is: partially failing
frama-clang.0.0.14 on 4.11 is now installable. Current state is: partially failing
frama-clang.0.0.14 on 4.12 is now installable. Current state is: partially failing
frama-clang.0.0.14 on 4.13 is now installable. Current state is: partially failing
frama-clang.0.0.14 on 4.14 is now installable. Current state is: partially failing
frama-clang.0.0.14 on 5.0 is now installable. Current state is: partially failing
frama-clang.0.0.14 on 5.1 is now installable. Current state is: partially failing
frama-clang.0.0.15 on 4.13 is now installable. Current state is: partially failing
frama-clang.0.0.15 on 4.14 is now installable. Current state is: partially failing
frama-clang.0.0.15 on 5.0 is now installable. Current state is: partially failing
frama-clang.0.0.15 on 5.1 is now installable. Current state is: partially failing
github-jsoo.4.1.0 on 4.08 had its build status changed: passing to partially failing
github-jsoo.4.2.0 on 4.08 had its build status changed: passing to partially failing
gmp-freestanding.6.1.2-2 on 4.08 had its build status changed: passing to partially failing
gmp-freestanding.6.1.2-2 on 4.09 had its build status changed: passing to partially failing
gmp-freestanding.6.1.2-2 on 4.10 had its build status changed: passing to partially failing
gmp-freestanding.6.1.2-2 on 4.11 had its build status changed: passing to partially failing
gmp-freestanding.6.1.2-2 on 4.12 had its build status changed: passing to partially failing
gmp-freestanding.6.1.2-2 on 4.13 had its build status changed: not available to partially failing
gmp-freestanding.6.1.2-2 on 4.14 is now installable. Current state is: partially failing
gmp-freestanding.6.2.0 on 4.08 had its build status changed: passing to partially failing
gmp-freestanding.6.2.0 on 4.09 had its build status changed: passing to partially failing
gmp-freestanding.6.2.0 on 4.10 had its build status changed: passing to partially failing
gmp-freestanding.6.2.0 on 4.11 had its build status changed: passing to partially failing
gmp-freestanding.6.2.0 on 4.12 had its build status changed: passing to partially failing
gmp-freestanding.6.2.0 on 4.13 had its build status changed: not available to partially failing
gmp-freestanding.6.2.0 on 4.14 is now installable. Current state is: partially failing
gmp-freestanding.6.2.1 on 4.08 had its build status changed: passing to partially failing
gmp-freestanding.6.2.1 on 4.09 had its build status changed: passing to partially failing
gmp-freestanding.6.2.1 on 4.10 had its build status changed: passing to partially failing
gmp-freestanding.6.2.1 on 4.11 had its build status changed: passing to partially failing
gmp-freestanding.6.2.1 on 4.12 had its build status changed: passing to partially failing
gmp-freestanding.6.2.1 on 4.13 had its build status changed: not available to partially failing
gmp-freestanding.6.2.1 on 4.14 is now installable. Current state is: partially failing
graphql-async.0.1.0 on 4.08 had its build status changed: passing to partially failing
graphql-async.0.1.0 on 4.09 had its build status changed: passing to partially failing
graphql-async.0.1.0 on 4.10 had its build status changed: passing to partially failing
graphql-async.0.1.0 on 4.11 had its build status changed: passing to partially failing
graphql-async.0.1.0 on 4.12 had its build status changed: passing to partially failing
graphql-async.0.8.0 on 4.08 had its build status changed: passing to partially failing
graphql-async.0.8.0 on 4.09 had its build status changed: passing to partially failing
graphql-async.0.8.0 on 4.10 had its build status changed: passing to partially failing
graphql-async.0.8.0 on 4.11 had its build status changed: passing to partially failing
graphql-async.0.8.0 on 4.12 had its build status changed: passing to partially failing
graphql-lwt.0.1.0 on 4.08 had its build status changed: passing to partially failing
graphql-lwt.0.1.0 on 4.09 had its build status changed: passing to partially failing
graphql-lwt.0.1.0 on 4.10 had its build status changed: passing to partially failing
graphql-lwt.0.1.0 on 4.11 had its build status changed: passing to partially failing
graphql-lwt.0.1.0 on 4.12 had its build status changed: passing to partially failing
graphql-lwt.0.6.0 on 4.08 had its build status changed: passing to partially failing
graphql-lwt.0.6.0 on 4.09 had its build status changed: passing to partially failing
graphql-lwt.0.6.0 on 4.10 had its build status changed: passing to partially failing
graphql-lwt.0.6.0 on 4.11 had its build status changed: passing to partially failing
graphql-lwt.0.6.0 on 4.12 had its build status changed: passing to partially failing
graphql-lwt.0.7.0 on 4.08 had its build status changed: passing to partially failing
graphql-lwt.0.7.0 on 4.09 had its build status changed: passing to partially failing
graphql-lwt.0.7.0 on 4.10 had its build status changed: passing to partially failing
graphql-lwt.0.7.0 on 4.11 had its build status changed: passing to partially failing
graphql-lwt.0.7.0 on 4.12 had its build status changed: passing to partially failing
graphql-lwt.0.8.0 on 4.08 had its build status changed: passing to partially failing
graphql-lwt.0.8.0 on 4.09 had its build status changed: passing to partially failing
graphql-lwt.0.8.0 on 4.10 had its build status changed: passing to partially failing
graphql-lwt.0.8.0 on 4.11 had its build status changed: passing to partially failing
graphql-lwt.0.8.0 on 4.12 had its build status changed: passing to partially failing
hacl-star.0.1 on 4.09 had its build status changed: passing to partially failing
hacl-star.0.1 on 4.10 had its build status changed: passing to partially failing
hacl-star.0.1 on 4.11 had its build status changed: passing to partially failing
hacl-star.0.1 on 4.12 had its build status changed: passing to partially failing
hacl-star.0.1 on 4.13 had its build status changed: passing to partially failing
hacl-star.0.1.1 on 4.08 had its build status changed: passing to partially failing
hacl-star.0.1.1 on 4.09 had its build status changed: passing to partially failing
hacl-star.0.1.1 on 4.11 had its build status changed: passing to partially failing
hacl-star.0.1.1 on 4.14 is now installable. Current state is: partially failing
hacl-star.0.2.0 on 4.08 had its build status changed: passing to partially failing
hacl-star.0.2.0 on 4.09 had its build status changed: passing to partially failing
hacl-star.0.2.0 on 4.10 had its build status changed: passing to partially failing
hacl-star.0.2.0 on 4.11 had its build status changed: passing to partially failing
hacl-star.0.2.0 on 4.12 had its build status changed: passing to partially failing
hacl-star.0.2.0 on 4.13 had its build status changed: passing to partially failing
hacl-star.0.2.1 on 4.08 had its build status changed: passing to partially failing
hacl-star.0.2.1 on 4.09 had its build status changed: passing to partially failing
hacl-star.0.2.1 on 4.10 had its build status changed: passing to partially failing
hacl-star.0.2.1 on 4.11 had its build status changed: passing to partially failing
hacl-star.0.2.1 on 4.14 is now installable. Current state is: partially failing
hacl-star.0.2.2 on 4.08 had its build status changed: passing to partially failing
hacl-star.0.2.2 on 4.09 had its build status changed: passing to partially failing
hacl-star.0.2.2 on 4.10 had its build status changed: passing to partially failing
hacl-star.0.2.2 on 4.11 had its build status changed: passing to partially failing
hacl-star.0.2.2 on 4.12 had its build status changed: passing to partially failing
hacl-star.0.2.2 on 4.13 had its build status changed: passing to partially failing
irmin-containers.2.3.0 on 4.08 had its build status changed: passing to partially failing
irmin-containers.2.3.0 on 4.09 had its build status changed: passing to partially failing
irmin-containers.2.3.0 on 4.10 had its build status changed: passing to partially failing
irmin-containers.2.3.0 on 4.11 had its build status changed: passing to partially failing
irmin-mirage-git.2.3.0 on 4.08 had its build status changed: passing to partially failing
irmin-mirage-git.2.3.0 on 4.09 had its build status changed: passing to partially failing
irmin-mirage-git.2.3.0 on 4.10 had its build status changed: passing to partially failing
irmin-mirage-git.2.3.0 on 4.11 had its build status changed: passing to partially failing
irmin-pack.2.0.0 on 4.08 had its build status changed: passing to partially failing
irmin-pack.2.0.0 on 4.09 had its build status changed: passing to partially failing
irmin-pack.2.0.0 on 4.10 had its build status changed: passing to partially failing
irmin-pack.2.0.0 on 4.11 had its build status changed: passing to partially failing
irmin-pack.2.1.0 on 4.08 had its build status changed: passing to partially failing
irmin-pack.2.1.0 on 4.09 had its build status changed: passing to partially failing
irmin-pack.2.1.0 on 4.10 had its build status changed: passing to partially failing
irmin-pack.2.1.0 on 4.11 had its build status changed: passing to partially failing
irmin-pack.2.2.0 on 4.08 had its build status changed: passing to partially failing
irmin-pack.2.2.0 on 4.09 had its build status changed: passing to partially failing
irmin-pack.2.2.0 on 4.10 had its build status changed: passing to partially failing
irmin-pack.2.2.0 on 4.11 had its build status changed: passing to partially failing
irmin-unix.2.3.0 on 4.08 had its build status changed: passing to partially failing
irmin-unix.2.3.0 on 4.09 had its build status changed: passing to partially failing
irmin-unix.2.3.0 on 4.10 had its build status changed: passing to partially failing
irmin-unix.2.3.0 on 4.11 had its build status changed: passing to partially failing
kappa-agents.4.1.0 on 4.08 had its build status changed: internal failure to partially failing
kappa-agents.4.1.0 on 4.09 had its build status changed: internal failure to partially failing
kappa-agents.4.1.0 on 4.10 had its build status changed: internal failure to partially failing
kappa-agents.4.1.0 on 4.11 had its build status changed: internal failure to partially failing
kappa-binaries.4.1.0 on 4.08 had its build status changed: internal failure to partially failing
kappa-binaries.4.1.0 on 4.09 had its build status changed: internal failure to partially failing
kappa-binaries.4.1.0 on 4.10 had its build status changed: internal failure to partially failing
kappa-binaries.4.1.0 on 4.11 had its build status changed: internal failure to partially failing
kappa-server.4.1.0 on 4.08 had its build status changed: internal failure to partially failing
kappa-server.4.1.0 on 4.09 had its build status changed: internal failure to partially failing
kappa-server.4.1.0 on 4.10 had its build status changed: internal failure to partially failing
kappa-server.4.1.0 on 4.11 had its build status changed: internal failure to partially failing
lambdapi.2.0.0 on 4.10 is now installable. Current state is: partially failing
lambdapi.2.0.0 on 4.12 is now installable. Current state is: partially failing
lambdapi.2.0.0 on 4.13 is now installable. Current state is: partially failing
links-mysql.0.9.8 on 4.14 is now installable. Current state is: partially failing
links-mysql.0.9.8 on 5.0 is now installable. Current state is: partially failing
links-mysql.0.9.8 on 5.1 is now installable. Current state is: partially failing
melange-atdgen-codec-runtime.3.0.0 on 5.1 is now installable. Current state is: partially failing
melange-fest.0.1.0 on 5.1 is now installable. Current state is: partially failing
melange-fetch.0.1.0 on 5.1 is now installable. Current state is: partially failing
melange-jest.0.1.1 on 5.1 is now installable. Current state is: partially failing
melange-json.1.1.0 on 5.1 is now installable. Current state is: partially failing
melange-moment.0.3.0 on 5.1 is now installable. Current state is: partially failing
melange-numeral.0.0.1 on 5.1 is now installable. Current state is: partially failing
melange-webapi.0.21.0 on 5.1 is now installable. Current state is: partially failing
memcad.1.1.0 on 4.08 is now installable. Current state is: partially failing
memcad.1.1.0 on 4.09 is now installable. Current state is: partially failing
memcad.1.1.0 on 4.10 is now installable. Current state is: partially failing
memcad.1.1.0 on 4.11 is now installable. Current state is: partially failing
memcad.1.1.0 on 4.12 is now installable. Current state is: partially failing
memcad.1.1.0 on 4.13 is now installable. Current state is: partially failing
memcad.1.1.0 on 4.14 is now installable. Current state is: partially failing
metapp.0.1.0 on 4.08 had its build status changed: passing to partially failing
metapp.0.1.0 on 4.09 had its build status changed: passing to partially failing
metapp.0.1.0 on 4.10 had its build status changed: passing to partially failing
metapp.0.2.0 on 4.08 had its build status changed: passing to partially failing
metapp.0.2.0 on 4.09 had its build status changed: passing to partially failing
metapp.0.2.0 on 4.10 had its build status changed: passing to partially failing
metapp.0.2.0 on 4.11 had its build status changed: passing to partially failing
metapp.0.3.0 on 4.08 had its build status changed: passing to partially failing
metapp.0.3.0 on 4.09 had its build status changed: passing to partially failing
metapp.0.3.0 on 4.10 had its build status changed: passing to partially failing
metapp.0.3.0 on 4.11 had its build status changed: passing to partially failing
metapp.0.4.0 on 4.08 had its build status changed: passing to partially failing
metapp.0.4.0 on 4.09 had its build status changed: passing to partially failing
metapp.0.4.0 on 4.10 had its build status changed: passing to partially failing
metapp.0.4.0 on 4.11 had its build status changed: passing to partially failing
metapp.0.4.0 on 4.12 had its build status changed: passing to partially failing
metapp.0.4.0 on 4.13 had its build status changed: not available to partially failing
metapp.0.4.0 on 4.14 is now installable. Current state is: partially failing
metapp.0.4.1 on 4.08 is now installable. Current state is: partially failing
metapp.0.4.1 on 4.09 is now installable. Current state is: partially failing
metapp.0.4.1 on 4.10 is now installable. Current state is: partially failing
metapp.0.4.1 on 4.11 is now installable. Current state is: partially failing
metapp.0.4.1 on 4.12 is now installable. Current state is: partially failing
metapp.0.4.1 on 4.13 is now installable. Current state is: partially failing
metapp.0.4.1 on 4.14 is now installable. Current state is: partially failing
metapp.0.4.2 on 4.08 is now installable. Current state is: partially failing
metapp.0.4.2 on 4.09 is now installable. Current state is: partially failing
metapp.0.4.2 on 4.10 is now installable. Current state is: partially failing
metapp.0.4.2 on 4.11 is now installable. Current state is: partially failing
metapp.0.4.2 on 4.12 is now installable. Current state is: partially failing
metapp.0.4.2 on 4.13 is now installable. Current state is: partially failing
metapp.0.4.2 on 4.14 is now installable. Current state is: partially failing
metapp.0.4.3 on 4.08 is now installable. Current state is: partially failing
metapp.0.4.3 on 4.09 is now installable. Current state is: partially failing
metapp.0.4.3 on 4.10 is now installable. Current state is: partially failing
metapp.0.4.3 on 4.11 is now installable. Current state is: partially failing
metapp.0.4.3 on 4.12 is now installable. Current state is: partially failing
metapp.0.4.3 on 4.13 is now installable. Current state is: partially failing
metapp.0.4.3 on 4.14 is now installable. Current state is: partially failing
metaquot.0.1.0 on 4.08 had its build status changed: passing to partially failing
metaquot.0.1.0 on 4.09 had its build status changed: passing to partially failing
metaquot.0.1.0 on 4.10 had its build status changed: passing to partially failing
metaquot.0.2.0 on 4.08 had its build status changed: passing to partially failing
metaquot.0.2.0 on 4.09 had its build status changed: passing to partially failing
metaquot.0.2.0 on 4.10 had its build status changed: passing to partially failing
metaquot.0.2.0 on 4.11 had its build status changed: passing to partially failing
metaquot.0.3.0 on 4.08 had its build status changed: passing to partially failing
metaquot.0.3.0 on 4.09 had its build status changed: passing to partially failing
metaquot.0.3.0 on 4.10 had its build status changed: passing to partially failing
metaquot.0.3.0 on 4.11 had its build status changed: passing to partially failing
metaquot.0.4.0 on 4.08 had its build status changed: passing to partially failing
metaquot.0.4.0 on 4.09 had its build status changed: passing to partially failing
metaquot.0.4.0 on 4.10 had its build status changed: passing to partially failing
metaquot.0.4.0 on 4.11 had its build status changed: passing to partially failing
metaquot.0.4.0 on 4.12 had its build status changed: passing to partially failing
metaquot.0.5.0 on 4.08 is now installable. Current state is: partially failing
metaquot.0.5.0 on 4.09 is now installable. Current state is: partially failing
metaquot.0.5.0 on 4.10 is now installable. Current state is: partially failing
metaquot.0.5.0 on 4.11 is now installable. Current state is: partially failing
metaquot.0.5.0 on 4.12 is now installable. Current state is: partially failing
metaquot.0.5.0 on 4.13 is now installable. Current state is: partially failing
metaquot.0.5.1 on 4.08 is now installable. Current state is: partially failing
metaquot.0.5.1 on 4.09 is now installable. Current state is: partially failing
metaquot.0.5.1 on 4.10 is now installable. Current state is: partially failing
metaquot.0.5.1 on 4.11 is now installable. Current state is: partially failing
metaquot.0.5.1 on 4.12 is now installable. Current state is: partially failing
metaquot.0.5.1 on 4.13 is now installable. Current state is: partially failing
metaquot.0.5.1 on 4.14 is now installable. Current state is: partially failing
metaquot.0.5.2 on 4.08 is now installable. Current state is: partially failing
metaquot.0.5.2 on 4.09 is now installable. Current state is: partially failing
metaquot.0.5.2 on 4.10 is now installable. Current state is: partially failing
metaquot.0.5.2 on 4.11 is now installable. Current state is: partially failing
metaquot.0.5.2 on 4.12 is now installable. Current state is: partially failing
metaquot.0.5.2 on 4.13 is now installable. Current state is: partially failing
metaquot.0.5.2 on 4.14 is now installable. Current state is: partially failing
metaquot.0.5.2 on 5.0 is now installable. Current state is: partially failing
metaquot.0.5.2 on 5.1 is now installable. Current state is: partially failing
mirage-block-solo5.0.6.0 on 4.08 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.0 on 4.09 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.0 on 4.10 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.0 on 4.11 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.0 on 4.12 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.0 on 4.13 had its build status changed: not available to partially failing
mirage-block-solo5.0.6.0 on 4.14 is now installable. Current state is: partially failing
mirage-block-solo5.0.6.1 on 4.08 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.1 on 4.09 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.1 on 4.10 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.1 on 4.11 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.1 on 4.12 had its build status changed: passing to partially failing
mirage-block-solo5.0.6.1 on 4.13 had its build status changed: not available to partially failing
mirage-block-solo5.0.6.1 on 4.14 is now installable. Current state is: partially failing
mirage-block-solo5.0.6.2 on 4.08 is now installable. Current state is: partially failing
mirage-block-solo5.0.6.2 on 4.09 is now installable. Current state is: partially failing
mirage-block-solo5.0.6.2 on 4.10 is now installable. Current state is: partially failing
mirage-block-solo5.0.6.2 on 4.11 is now installable. Current state is: partially failing
mirage-block-solo5.0.6.2 on 4.12 is now installable. Current state is: partially failing
mirage-block-solo5.0.6.2 on 4.13 is now installable. Current state is: partially failing
mirage-block-solo5.0.6.2 on 4.14 is now installable. Current state is: partially failing
mirage-block-xen.2.0.0 on 4.08 had its build status changed: passing to partially failing
mirage-block-xen.2.0.0 on 4.09 had its build status changed: passing to partially failing
mirage-block-xen.2.0.0 on 4.10 had its build status changed: passing to partially failing
mirage-block-xen.2.0.0 on 4.11 had its build status changed: passing to partially failing
mirage-block-xen.2.0.0 on 4.12 had its build status changed: passing to partially failing
mirage-block-xen.2.0.0 on 4.13 had its build status changed: not available to partially failing
mirage-block-xen.2.0.0 on 4.14 is now installable. Current state is: partially failing
mirage-console-solo5.0.6.0 on 4.08 had its build status changed: passing to partially failing
mirage-console-solo5.0.6.0 on 4.09 had its build status changed: passing to partially failing
mirage-console-solo5.0.6.0 on 4.10 had its build status changed: passing to partially failing
mirage-console-solo5.0.6.0 on 4.11 had its build status changed: passing to partially failing
mirage-console-solo5.0.6.0 on 4.12 had its build status changed: passing to partially failing
mirage-console-solo5.0.6.0 on 4.13 had its build status changed: not available to partially failing
mirage-console-solo5.0.6.0 on 4.14 is now installable. Current state is: partially failing
mirage-console-xen-backend.4.0.0 on 4.08 had its build status changed: passing to partially failing
mirage-console-xen-backend.4.0.0 on 4.09 had its build status changed: passing to partially failing
mirage-console-xen-backend.4.0.0 on 4.10 had its build status changed: passing to partially failing
mirage-console-xen-backend.4.0.0 on 4.11 had its build status changed: passing to partially failing
mirage-console-xen-backend.4.0.0 on 4.12 had its build status changed: passing to partially failing
mirage-console-xen-backend.4.0.0 on 4.13 had its build status changed: not available to partially failing
mirage-console-xen-backend.4.0.0 on 4.14 is now installable. Current state is: partially failing
mirage-console-xen-backend.5.0.0 on 4.08 is now installable. Current state is: partially failing
mirage-console-xen-backend.5.0.0 on 4.09 is now installable. Current state is: partially failing
mirage-console-xen-backend.5.0.0 on 4.10 is now installable. Current state is: partially failing
mirage-console-xen-backend.5.0.0 on 4.11 is now installable. Current state is: partially failing
mirage-console-xen-backend.5.0.0 on 4.12 is now installable. Current state is: partially failing
mirage-console-xen-backend.5.0.0 on 4.13 is now installable. Current state is: partially failing
mirage-console-xen-backend.5.0.0 on 4.14 is now installable. Current state is: partially failing
mirage-console-xen.4.0.0 on 4.08 had its build status changed: passing to partially failing
mirage-console-xen.4.0.0 on 4.09 had its build status changed: passing to partially failing
mirage-console-xen.4.0.0 on 4.10 had its build status changed: passing to partially failing
mirage-console-xen.4.0.0 on 4.11 had its build status changed: passing to partially failing
mirage-console-xen.4.0.0 on 4.12 had its build status changed: passing to partially failing
mirage-console-xen.4.0.0 on 4.13 had its build status changed: not available to partially failing
mirage-console-xen.4.0.0 on 4.14 is now installable. Current state is: partially failing
mirage-console-xen.5.0.0 on 4.08 is now installable. Current state is: partially failing
mirage-console-xen.5.0.0 on 4.09 is now installable. Current state is: partially failing
mirage-console-xen.5.0.0 on 4.10 is now installable. Current state is: partially failing
mirage-console-xen.5.0.0 on 4.11 is now installable. Current state is: partially failing
mirage-console-xen.5.0.0 on 4.12 is now installable. Current state is: partially failing
mirage-console-xen.5.0.0 on 4.13 is now installable. Current state is: partially failing
mirage-console-xen.5.0.0 on 4.14 is now installable. Current state is: partially failing
mirage-monitoring.0.0.1 on 4.11 is now installable. Current state is: partially failing
mirage-monitoring.0.0.1 on 4.12 is now installable. Current state is: partially failing
mirage-monitoring.0.0.1 on 4.13 is now installable. Current state is: partially failing
mirage-monitoring.0.0.1 on 4.14 is now installable. Current state is: partially failing
mirage-nat.2.0.0 on 4.08 had its build status changed: passing to partially failing
mirage-nat.2.0.0 on 4.09 had its build status changed: passing to partially failing
mirage-nat.2.0.0 on 4.10 had its build status changed: passing to partially failing
mirage-nat.2.0.0 on 4.11 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.0 on 4.08 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.0 on 4.09 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.0 on 4.10 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.0 on 4.11 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.0 on 4.12 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.0 on 4.13 had its build status changed: not available to partially failing
mirage-net-solo5.0.6.0 on 4.14 is now installable. Current state is: partially failing
mirage-net-solo5.0.6.1 on 4.08 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.1 on 4.09 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.1 on 4.10 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.1 on 4.11 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.1 on 4.12 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.1 on 4.13 had its build status changed: not available to partially failing
mirage-net-solo5.0.6.1 on 4.14 is now installable. Current state is: partially failing
mirage-net-solo5.0.6.2 on 4.08 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.2 on 4.09 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.2 on 4.10 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.2 on 4.11 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.2 on 4.12 had its build status changed: passing to partially failing
mirage-net-solo5.0.6.2 on 4.13 had its build status changed: not available to partially failing
mirage-net-solo5.0.6.2 on 4.14 is now installable. Current state is: partially failing
mirage-net-xen.1.10.2 on 4.08 had its build status changed: passing to partially failing
mirage-net-xen.1.10.2 on 4.09 had its build status changed: passing to partially failing
mirage-net-xen.1.10.2 on 4.10 had its build status changed: passing to partially failing
mirage-net-xen.1.10.2 on 4.11 had its build status changed: passing to partially failing
mirage-net-xen.1.11.0 on 4.08 had its build status changed: passing to partially failing
mirage-net-xen.1.11.0 on 4.09 had its build status changed: passing to partially failing
mirage-net-xen.1.11.0 on 4.10 had its build status changed: passing to partially failing
mirage-net-xen.1.11.0 on 4.11 had its build status changed: passing to partially failing
mirage-net-xen.1.12.0 on 4.08 had its build status changed: passing to partially failing
mirage-net-xen.1.12.0 on 4.09 had its build status changed: passing to partially failing
mirage-net-xen.1.12.0 on 4.10 had its build status changed: passing to partially failing
mirage-net-xen.1.12.0 on 4.11 had its build status changed: passing to partially failing
mirage-net-xen.1.13.0 on 4.08 had its build status changed: passing to partially failing
mirage-net-xen.1.13.0 on 4.09 had its build status changed: passing to partially failing
mirage-net-xen.1.13.0 on 4.10 had its build status changed: passing to partially failing
mirage-net-xen.1.13.0 on 4.11 had its build status changed: passing to partially failing
mirage-net-xen.1.13.1 on 4.08 had its build status changed: passing to partially failing
mirage-net-xen.1.13.1 on 4.09 had its build status changed: passing to partially failing
mirage-net-xen.1.13.1 on 4.10 had its build status changed: passing to partially failing
mirage-net-xen.1.13.1 on 4.11 had its build status changed: passing to partially failing
mirage-net-xen.2.0.0 on 4.08 had its build status changed: passing to partially failing
mirage-net-xen.2.0.0 on 4.09 had its build status changed: passing to partially failing
mirage-net-xen.2.0.0 on 4.10 had its build status changed: passing to partially failing
mirage-net-xen.2.0.0 on 4.11 had its build status changed: passing to partially failing
mirage-net-xen.2.0.0 on 4.12 had its build status changed: passing to partially failing
mirage-net-xen.2.0.0 on 4.13 had its build status changed: not available to partially failing
mirage-net-xen.2.0.0 on 4.14 is now installable. Current state is: partially failing
mirage-solo5.0.6.0 on 4.08 had its build status changed: passing to partially failing
mirage-solo5.0.6.0 on 4.09 had its build status changed: passing to partially failing
mirage-solo5.0.6.1 on 4.08 had its build status changed: passing to partially failing
mirage-solo5.0.6.1 on 4.09 had its build status changed: passing to partially failing
mirage-solo5.0.6.2 on 4.08 had its build status changed: passing to partially failing
mirage-solo5.0.6.2 on 4.09 had its build status changed: passing to partially failing
mirage-solo5.0.6.2 on 4.10 had its build status changed: passing to partially failing
mirage-solo5.0.6.2 on 4.11 had its build status changed: passing to partially failing
mirage-solo5.0.6.2 on 4.12 had its build status changed: passing to partially failing
mirage-solo5.0.6.2 on 4.13 had its build status changed: not available to partially failing
mirage-solo5.0.6.2 on 4.14 is now installable. Current state is: partially failing
mirage-solo5.0.6.3 on 4.08 had its build status changed: passing to partially failing
mirage-solo5.0.6.3 on 4.09 had its build status changed: passing to partially failing
mirage-solo5.0.6.3 on 4.10 had its build status changed: passing to partially failing
mirage-solo5.0.6.3 on 4.11 had its build status changed: passing to partially failing
mirage-solo5.0.6.3 on 4.12 had its build status changed: passing to partially failing
mirage-solo5.0.6.3 on 4.13 had its build status changed: not available to partially failing
mirage-solo5.0.6.3 on 4.14 is now installable. Current state is: partially failing
mirage-solo5.0.6.4 on 4.08 had its build status changed: passing to partially failing
mirage-solo5.0.6.4 on 4.09 had its build status changed: passing to partially failing
mirage-solo5.0.6.4 on 4.10 had its build status changed: passing to partially failing
mirage-solo5.0.6.4 on 4.11 had its build status changed: passing to partially failing
mirage-solo5.0.6.4 on 4.12 had its build status changed: passing to partially failing
mirage-solo5.0.6.4 on 4.13 had its build status changed: not available to partially failing
mirage-solo5.0.6.4 on 4.14 is now installable. Current state is: partially failing
mirage-solo5.0.6.5 on 4.08 is now installable. Current state is: partially failing
mirage-solo5.0.6.5 on 4.09 is now installable. Current state is: partially failing
mirage-solo5.0.6.5 on 4.10 is now installable. Current state is: partially failing
mirage-solo5.0.6.5 on 4.11 is now installable. Current state is: partially failing
mirage-solo5.0.6.5 on 4.12 is now installable. Current state is: partially failing
mirage-solo5.0.6.5 on 4.13 is now installable. Current state is: partially failing
mirage-solo5.0.6.5 on 4.14 is now installable. Current state is: partially failing
mirage-xen.6.0.0 on 4.08 had its build status changed: passing to partially failing
mirage-xen.6.0.0 on 4.09 had its build status changed: passing to partially failing
mirage-xen.6.0.0 on 4.10 had its build status changed: passing to partially failing
mirage-xen.6.0.0 on 4.11 had its build status changed: passing to partially failing
mirage-xen.6.0.0 on 4.12 had its build status changed: passing to partially failing
mirage-xen.6.0.0 on 4.13 had its build status changed: not available to partially failing
mirage-xen.6.0.0 on 4.14 is now installable. Current state is: partially failing
mirage-xen.6.0.1 on 4.08 is now installable. Current state is: partially failing
mirage-xen.6.0.1 on 4.09 is now installable. Current state is: partially failing
mirage-xen.6.0.1 on 4.10 is now installable. Current state is: partially failing
mirage-xen.6.0.1 on 4.11 is now installable. Current state is: partially failing
mirage-xen.6.0.1 on 4.12 is now installable. Current state is: partially failing
mirage-xen.6.0.1 on 4.13 is now installable. Current state is: partially failing
mirage-xen.6.0.1 on 4.14 is now installable. Current state is: partially failing
morsmall.0.1 on 5.0 is now installable. Current state is: partially failing
morsmall.0.1 on 5.1 is now installable. Current state is: partially failing
netchannel.2.0.0 on 4.08 had its build status changed: passing to partially failing
netchannel.2.0.0 on 4.09 had its build status changed: passing to partially failing
netchannel.2.0.0 on 4.10 had its build status changed: passing to partially failing
netchannel.2.0.0 on 4.11 had its build status changed: passing to partially failing
netchannel.2.0.0 on 4.12 had its build status changed: passing to partially failing
netchannel.2.0.0 on 4.13 had its build status changed: not available to partially failing
netchannel.2.0.0 on 4.14 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.0 on 4.08 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.0 on 4.09 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.0 on 4.10 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.2 on 4.08 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.2 on 4.09 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.2 on 4.10 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.2 on 4.11 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.3 on 4.08 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.3 on 4.09 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.3 on 4.10 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.3 on 4.11 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.4 on 4.08 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.4 on 4.09 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.4 on 4.10 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.4 on 4.11 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.4 on 4.12 had its build status changed: passing to partially failing
ocaml-freestanding.0.6.5 on 4.08 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.5 on 4.09 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.5 on 4.10 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.5 on 4.11 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.5 on 4.12 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.5 on 4.13 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.6 on 4.08 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.6 on 4.09 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.6 on 4.10 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.6 on 4.11 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.6 on 4.12 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.6 on 4.13 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.7 on 4.08 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.7 on 4.09 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.7 on 4.10 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.7 on 4.11 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.7 on 4.12 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.7 on 4.13 is now installable. Current state is: partially failing
ocaml-freestanding.0.6.7 on 4.14 is now installable. Current state is: partially failing
ocamlbrowser.4.14.0 on 4.14 is now installable. Current state is: partially failing
ocsigen-start.2.11.0 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.12.0 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.13.0 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.15.0 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.15.2 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.18.0 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.18.0 on 4.09 had its build status changed: passing to partially failing
ocsigen-start.2.18.0 on 4.10 had its build status changed: passing to partially failing
ocsigen-start.2.18.0 on 4.11 had its build status changed: passing to partially failing
ocsigen-start.2.19.2 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.19.2 on 4.09 had its build status changed: passing to partially failing
ocsigen-start.2.19.2 on 4.10 had its build status changed: passing to partially failing
ocsigen-start.2.19.2 on 4.11 had its build status changed: passing to partially failing
ocsigen-start.2.19.3 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.19.3 on 4.09 had its build status changed: passing to partially failing
ocsigen-start.2.19.3 on 4.10 had its build status changed: passing to partially failing
ocsigen-start.2.19.3 on 4.11 had its build status changed: passing to partially failing
ocsigen-start.2.21.1 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.21.1 on 4.09 had its build status changed: passing to partially failing
ocsigen-start.2.21.1 on 4.10 had its build status changed: passing to partially failing
ocsigen-start.2.21.1 on 4.11 had its build status changed: passing to partially failing
ocsigen-start.2.3.0 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.4.0 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.7.0 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.9.1 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.2.9.2 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.4.0.0 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.4.0.0 on 4.09 had its build status changed: passing to partially failing
ocsigen-start.4.0.0 on 4.10 had its build status changed: passing to partially failing
ocsigen-start.4.0.0 on 4.11 had its build status changed: passing to partially failing
ocsigen-start.4.0.1 on 4.08 had its build status changed: passing to partially failing
ocsigen-start.4.0.1 on 4.09 had its build status changed: passing to partially failing
ocsigen-start.4.0.1 on 4.10 had its build status changed: passing to partially failing
ocsigen-start.4.0.1 on 4.11 had its build status changed: passing to partially failing
ocveralls.0.1.0 on 5.0 is now installable. Current state is: partially failing
ocveralls.0.2.0 on 5.0 is now installable. Current state is: partially failing
ocveralls.0.2.1 on 5.0 is now installable. Current state is: partially failing
ocveralls.0.3.0 on 5.0 is now installable. Current state is: partially failing
ocveralls.0.3.1 on 5.0 is now installable. Current state is: partially failing
ocveralls.0.3.2 on 5.0 is now installable. Current state is: partially failing
ocveralls.0.3.3 on 5.0 is now installable. Current state is: partially failing
ocveralls.0.3.4 on 5.0 is now installable. Current state is: partially failing
orm.0.7.0 on 5.0 is now installable. Current state is: partially failing
orm.0.7.1 on 5.0 is now installable. Current state is: partially failing
override.0.3.0 on 4.08 had its build status changed: passing to partially failing
override.0.3.0 on 4.09 had its build status changed: passing to partially failing
override.0.3.0 on 4.10 had its build status changed: passing to partially failing
override.0.3.0 on 4.11 had its build status changed: passing to partially failing
override.0.4.0 on 4.08 is now installable. Current state is: partially failing
override.0.4.0 on 4.09 is now installable. Current state is: partially failing
override.0.4.0 on 4.10 is now installable. Current state is: partially failing
override.0.4.0 on 4.11 is now installable. Current state is: partially failing
override.0.4.0 on 4.12 is now installable. Current state is: partially failing
override.0.4.0 on 4.13 is now installable. Current state is: partially failing
owl-ode-sundials.0.5.0 on 4.10 is now installable. Current state is: partially failing
owl-ode-sundials.0.5.0 on 4.11 is now installable. Current state is: partially failing
owl-ode-sundials.0.5.0 on 4.12 is now installable. Current state is: partially failing
owl-ode-sundials.0.5.0 on 4.13 is now installable. Current state is: partially failing
owl-ode-sundials.0.5.0 on 4.14 is now installable. Current state is: partially failing
owl-top.1.0.2 on 4.10 is now installable. Current state is: partially failing
owl-top.1.0.2 on 4.11 is now installable. Current state is: partially failing
owl-top.1.0.2 on 4.12 is now installable. Current state is: partially failing
owl-top.1.0.2 on 4.13 is now installable. Current state is: partially failing
pa_solution.0.5 on 5.0 is now installable. Current state is: partially failing
pa_solution.0.6 on 5.0 is now installable. Current state is: partially failing
pa_solution.0.7 on 5.0 is now installable. Current state is: partially failing
pancake.2.0.1 on 5.1 is now installable. Current state is: partially failing
pari.0.1 on 4.10 is now installable. Current state is: partially failing
pari.0.1 on 4.11 is now installable. Current state is: partially failing
pari.0.1 on 4.12 is now installable. Current state is: partially failing
pari.0.1 on 4.13 is now installable. Current state is: partially failing
pari.0.1 on 4.14 is now installable. Current state is: partially failing
pari.0.1 on 5.0 is now installable. Current state is: partially failing
pari.0.1 on 5.1 is now installable. Current state is: partially failing
pattern.0.2.0 on 4.08 had its build status changed: passing to partially failing
pattern.0.2.0 on 4.09 had its build status changed: passing to partially failing
pattern.0.2.0 on 4.10 had its build status changed: passing to partially failing
pattern.0.2.0 on 4.11 had its build status changed: passing to partially failing
pattern.0.3.2 on 4.08 is now installable. Current state is: partially failing
pattern.0.3.2 on 4.09 is now installable. Current state is: partially failing
pattern.0.3.2 on 4.10 is now installable. Current state is: partially failing
pattern.0.3.2 on 4.11 is now installable. Current state is: partially failing
pattern.0.3.2 on 4.12 is now installable. Current state is: partially failing
pattern.0.3.2 on 4.13 is now installable. Current state is: partially failing
pattern.0.3.2 on 4.14 is now installable. Current state is: partially failing
pattern.0.3.2 on 5.0 is now installable. Current state is: partially failing
ppx_deriving_rpc.6.0.0 on 4.08 had its build status changed: passing to partially failing
ppx_deriving_rpc.6.0.0 on 4.09 had its build status changed: passing to partially failing
ppx_pbt.0.1.0 on 4.10 is now installable. Current state is: partially failing
ppx_pbt.0.1.0 on 4.11 is now installable. Current state is: partially failing
ppx_pbt.0.1.0 on 4.12 is now installable. Current state is: partially failing
ppx_pbt.0.1.0 on 4.13 is now installable. Current state is: partially failing
profiler-plugin.1.30 on 4.08 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.09 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.10 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.11 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.12 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.13 had its build status changed: passing to partially failing
profiler-plugin.1.30 on 4.14 is now installable. Current state is: partially failing
protocol-9p-tool.0.11.0 on 4.08 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.0 on 4.09 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.0 on 4.10 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.0 on 4.11 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.1 on 4.08 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.1 on 4.09 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.1 on 4.10 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.1 on 4.11 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.2 on 4.08 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.2 on 4.09 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.2 on 4.10 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.2 on 4.11 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.3 on 4.08 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.3 on 4.09 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.3 on 4.10 had its build status changed: passing to partially failing
protocol-9p-tool.0.11.3 on 4.11 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.0 on 4.08 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.0 on 4.09 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.0 on 4.10 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.0 on 4.11 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.1 on 4.08 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.1 on 4.09 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.1 on 4.10 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.1 on 4.11 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.2 on 4.08 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.2 on 4.09 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.2 on 4.10 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.2 on 4.11 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.3 on 4.08 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.3 on 4.09 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.3 on 4.10 had its build status changed: passing to partially failing
protocol-9p-unix.0.11.3 on 4.11 had its build status changed: passing to partially failing
protocol-9p-unix.0.12.0 on 4.08 had its build status changed: passing to partially failing
protocol-9p-unix.0.12.0 on 4.09 had its build status changed: passing to partially failing
protocol-9p-unix.0.12.0 on 4.10 had its build status changed: passing to partially failing
protocol-9p-unix.0.12.0 on 4.11 had its build status changed: passing to partially failing
protocol-9p-unix.1.0.0 on 5.0 is now installable. Current state is: partially failing
protocol-9p-unix.1.0.0 on 5.1 is now installable. Current state is: partially failing
protocol-9p-unix.1.0.1 on 5.0 is now installable. Current state is: partially failing
protocol-9p-unix.1.0.1 on 5.1 is now installable. Current state is: partially failing
protocol-9p.0.11.0 on 4.08 had its build status changed: passing to partially failing
protocol-9p.0.11.0 on 4.09 had its build status changed: passing to partially failing
protocol-9p.0.11.0 on 4.10 had its build status changed: passing to partially failing
protocol-9p.0.11.0 on 4.11 had its build status changed: passing to partially failing
protocol-9p.0.11.1 on 4.08 had its build status changed: passing to partially failing
protocol-9p.0.11.1 on 4.09 had its build status changed: passing to partially failing
protocol-9p.0.11.1 on 4.10 had its build status changed: passing to partially failing
protocol-9p.0.11.1 on 4.11 had its build status changed: passing to partially failing
protocol-9p.0.11.2 on 4.08 had its build status changed: passing to partially failing
protocol-9p.0.11.2 on 4.09 had its build status changed: passing to partially failing
protocol-9p.0.11.2 on 4.10 had its build status changed: passing to partially failing
protocol-9p.0.11.2 on 4.11 had its build status changed: passing to partially failing
protocol-9p.0.11.3 on 4.08 had its build status changed: passing to partially failing
protocol-9p.0.11.3 on 4.09 had its build status changed: passing to partially failing
protocol-9p.0.11.3 on 4.10 had its build status changed: passing to partially failing
protocol-9p.0.11.3 on 4.11 had its build status changed: passing to partially failing
protocol-9p.0.12.0 on 4.08 had its build status changed: passing to partially failing
protocol-9p.0.12.0 on 4.09 had its build status changed: passing to partially failing
protocol-9p.0.12.0 on 4.10 had its build status changed: passing to partially failing
protocol-9p.0.12.0 on 4.11 had its build status changed: passing to partially failing
pyast.0.1.0 on 4.08 is now installable. Current state is: partially failing
pyast.0.1.0 on 4.09 is now installable. Current state is: partially failing
pyast.0.1.0 on 4.10 is now installable. Current state is: partially failing
pyast.0.1.0 on 4.11 is now installable. Current state is: partially failing
pyast.0.1.0 on 4.12 is now installable. Current state is: partially failing
pyast.0.1.0 on 4.13 is now installable. Current state is: partially failing
pyast.0.1.0 on 4.14 is now installable. Current state is: partially failing
pyast.0.1.0 on 5.0 is now installable. Current state is: partially failing
pyast.0.1.0 on 5.1 is now installable. Current state is: partially failing
pyast.0.1.1 on 4.08 is now installable. Current state is: partially failing
pyast.0.1.1 on 4.09 is now installable. Current state is: partially failing
pyast.0.1.1 on 4.10 is now installable. Current state is: partially failing
pyast.0.1.1 on 4.11 is now installable. Current state is: partially failing
pyast.0.1.1 on 4.12 is now installable. Current state is: partially failing
pyast.0.1.1 on 4.13 is now installable. Current state is: partially failing
pyast.0.1.1 on 4.14 is now installable. Current state is: partially failing
pyast.0.1.1 on 5.0 is now installable. Current state is: partially failing
pyast.0.1.1 on 5.1 is now installable. Current state is: partially failing
pyast.0.2.0 on 4.08 is now installable. Current state is: partially failing
pyast.0.2.0 on 4.09 is now installable. Current state is: partially failing
pyast.0.2.0 on 4.10 is now installable. Current state is: partially failing
pyast.0.2.0 on 4.11 is now installable. Current state is: partially failing
pyast.0.2.0 on 4.12 is now installable. Current state is: partially failing
pyast.0.2.0 on 4.13 is now installable. Current state is: partially failing
pyast.0.2.0 on 4.14 is now installable. Current state is: partially failing
pyast.0.2.0 on 5.0 is now installable. Current state is: partially failing
pyast.0.2.0 on 5.1 is now installable. Current state is: partially failing
reason-react-ppx.0.13.0 on 5.1 is now installable. Current state is: partially failing
refl.0.1.0 on 4.08 had its build status changed: passing to partially failing
refl.0.1.0 on 4.09 had its build status changed: passing to partially failing
refl.0.1.0 on 4.10 had its build status changed: passing to partially failing
refl.0.1.0 on 4.11 had its build status changed: passing to partially failing
refl.0.2.0 on 4.08 had its build status changed: passing to partially failing
refl.0.2.0 on 4.09 had its build status changed: passing to partially failing
refl.0.2.0 on 4.10 had its build status changed: passing to partially failing
refl.0.2.0 on 4.11 had its build status changed: passing to partially failing
refl.0.2.1 on 4.08 had its build status changed: passing to partially failing
refl.0.2.1 on 4.09 had its build status changed: passing to partially failing
refl.0.2.1 on 4.10 had its build status changed: passing to partially failing
refl.0.2.1 on 4.11 had its build status changed: passing to partially failing
refl.0.3.0 on 4.08 had its build status changed: passing to partially failing
refl.0.3.0 on 4.09 had its build status changed: passing to partially failing
refl.0.3.0 on 4.10 had its build status changed: passing to partially failing
refl.0.3.0 on 4.11 had its build status changed: passing to partially failing
refl.0.4.1 on 4.08 is now installable. Current state is: partially failing
refl.0.4.1 on 4.09 is now installable. Current state is: partially failing
refl.0.4.1 on 4.10 is now installable. Current state is: partially failing
refl.0.4.1 on 4.11 is now installable. Current state is: partially failing
refl.0.4.1 on 4.12 is now installable. Current state is: partially failing
refl.0.4.1 on 4.13 is now installable. Current state is: partially failing
refl.0.4.1 on 4.14 is now installable. Current state is: partially failing
refl.0.4.1 on 5.0 is now installable. Current state is: partially failing
refl.0.4.1 on 5.1 is now installable. Current state is: partially failing
rfsm.1.4.2 on 5.0 is now installable. Current state is: partially failing
rfsm.1.5 on 5.0 is now installable. Current state is: partially failing
rpclib-async.6.0.0 on 4.08 had its build status changed: passing to partially failing
rpclib-async.6.0.0 on 4.09 had its build status changed: passing to partially failing
rpclib-lwt.6.0.0 on 4.08 had its build status changed: passing to partially failing
rpclib-lwt.6.0.0 on 4.09 had its build status changed: passing to partially failing
satML-plugin.1.30 on 4.08 had its build status changed: passing to partially failing
satML-plugin.1.30 on 4.09 had its build status changed: passing to partially failing
satML-plugin.1.30 on 4.10 had its build status changed: passing to partially failing
satML-plugin.1.30 on 4.11 had its build status changed: passing to partially failing
satML-plugin.1.30 on 4.12 had its build status changed: passing to partially failing
satML-plugin.1.30 on 4.13 had its build status changed: passing to partially failing
satML-plugin.1.30 on 4.14 is now installable. Current state is: partially failing
server-reason-react.0.1.0 on 5.1 is now installable. Current state is: partially failing
server-reason-react.0.2.0 on 5.1 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.0 on 4.08 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.0 on 4.09 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.0 on 4.10 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.0 on 4.11 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.0 on 4.12 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.0 on 4.13 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.0 on 4.14 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.0 on 5.0 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.0 on 5.1 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.1 on 4.08 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.1 on 4.10 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.1 on 4.11 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.1 on 4.12 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.1 on 4.14 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.1 on 5.0 is now installable. Current state is: partially failing
solo5-cross-aarch64.0.7.1 on 5.1 is now installable. Current state is: partially failing
stog_all.0.20.0 on 4.12 is now installable. Current state is: partially failing
stog_server_multi.0.20.0 on 4.12 is now installable. Current state is: partially failing
stone.0.5.1 on 5.0 is now installable. Current state is: partially failing
traverse.0.1.0 on 4.08 had its build status changed: passing to partially failing
traverse.0.1.0 on 4.09 had its build status changed: passing to partially failing
traverse.0.1.0 on 4.10 had its build status changed: passing to partially failing
traverse.0.2.0 on 4.08 had its build status changed: passing to partially failing
traverse.0.2.0 on 4.09 had its build status changed: passing to partially failing
traverse.0.2.0 on 4.10 had its build status changed: passing to partially failing
traverse.0.2.0 on 4.11 had its build status changed: passing to partially failing
traverse.0.3.0 on 4.08 had its build status changed: passing to partially failing
traverse.0.3.0 on 4.09 had its build status changed: passing to partially failing
traverse.0.3.0 on 4.10 had its build status changed: passing to partially failing
traverse.0.3.0 on 4.11 had its build status changed: passing to partially failing
traverse.0.3.0 on 4.12 had its build status changed: passing to partially failing
traverse.0.3.0 on 4.13 had its build status changed: not available to partially failing
traverse.0.3.0 on 4.14 is now installable. Current state is: partially failing
traverse.0.3.0 on 5.0 is now installable. Current state is: partially failing
traverse.0.3.0 on 5.1 is now installable. Current state is: partially failing
trexio.2.2.0 on 4.08 is now installable. Current state is: partially failing
trexio.2.2.0 on 4.09 is now installable. Current state is: partially failing
trexio.2.2.0 on 4.10 is now installable. Current state is: partially failing
trexio.2.2.0 on 4.11 is now installable. Current state is: partially failing
trexio.2.2.0 on 4.12 is now installable. Current state is: partially failing
trexio.2.2.0 on 4.13 is now installable. Current state is: partially failing
trexio.2.2.0 on 4.14 is now installable. Current state is: partially failing
trexio.2.2.0 on 5.0 is now installable. Current state is: partially failing
trexio.2.2.0 on 5.1 is now installable. Current state is: partially failing
vchan-xen.6.0.0 on 4.08 had its build status changed: passing to partially failing
vchan-xen.6.0.0 on 4.09 had its build status changed: passing to partially failing
vchan-xen.6.0.0 on 4.10 had its build status changed: passing to partially failing
vchan-xen.6.0.0 on 4.11 had its build status changed: passing to partially failing
vchan-xen.6.0.0 on 4.12 had its build status changed: passing to partially failing
vchan-xen.6.0.0 on 4.13 had its build status changed: not available to partially failing
vchan-xen.6.0.0 on 4.14 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.1 on 4.08 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.1 on 4.09 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.1 on 4.10 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.1 on 4.11 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.1 on 4.12 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.2 on 4.08 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.2 on 4.09 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.2 on 4.10 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.2 on 4.11 is now installable. Current state is: partially failing
vhd-format-lwt.0.12.2 on 4.12 is now installable. Current state is: partially failing
z3_tptp.4.8.14 on 5.0 is now installable. Current state is: partially failing
z3_tptp.4.8.14 on 5.1 is now installable. Current state is: partially failing
zarith-freestanding.1.10 on 4.08 had its build status changed: passing to partially failing
zarith-freestanding.1.10 on 4.09 had its build status changed: passing to partially failing
zarith-freestanding.1.10 on 4.10 had its build status changed: passing to partially failing
zarith-freestanding.1.10 on 4.11 had its build status changed: passing to partially failing
zarith-freestanding.1.10 on 4.12 had its build status changed: passing to partially failing
zarith-freestanding.1.10 on 4.13 had its build status changed: not available to partially failing
zarith-freestanding.1.10 on 4.14 is now installable. Current state is: partially failing
zarith-freestanding.1.11 on 4.08 had its build status changed: passing to partially failing
zarith-freestanding.1.11 on 4.09 had its build status changed: passing to partially failing
zarith-freestanding.1.11 on 4.10 had its build status changed: passing to partially failing
zarith-freestanding.1.11 on 4.11 had its build status changed: passing to partially failing
zarith-freestanding.1.11 on 4.12 had its build status changed: passing to partially failing
zarith-freestanding.1.11 on 4.13 had its build status changed: not available to partially failing
zarith-freestanding.1.11 on 4.14 is now installable. Current state is: partially failing
zarith-freestanding.1.12 on 4.08 had its build status changed: passing to partially failing
zarith-freestanding.1.12 on 4.09 had its build status changed: passing to partially failing
zarith-freestanding.1.12 on 4.10 had its build status changed: passing to partially failing
zarith-freestanding.1.12 on 4.11 had its build status changed: passing to partially failing
zarith-freestanding.1.12 on 4.12 had its build status changed: passing to partially failing
zarith-freestanding.1.12 on 4.13 had its build status changed: not available to partially failing
zarith-freestanding.1.12 on 4.14 is now installable. Current state is: partially failing
zarith-freestanding.1.7-1 on 4.08 had its build status changed: passing to partially failing
zarith-freestanding.1.7-1 on 4.09 had its build status changed: passing to partially failing
zarith-freestanding.1.7-1 on 4.10 had its build status changed: passing to partially failing
zarith-freestanding.1.7-1 on 4.11 had its build status changed: passing to partially failing
zarith-freestanding.1.7-1 on 4.12 had its build status changed: passing to partially failing
zarith-freestanding.1.7-1 on 4.13 had its build status changed: not available to partially failing
zarith-freestanding.1.7-1 on 4.14 is now installable. Current state is: partially failing
zarith-freestanding.1.7-2 on 4.08 had its build status changed: passing to partially failing
zarith-freestanding.1.7-2 on 4.09 had its build status changed: passing to partially failing
zarith-freestanding.1.7-2 on 4.10 had its build status changed: passing to partially failing
zarith-freestanding.1.7-2 on 4.11 had its build status changed: passing to partially failing
zarith-freestanding.1.7-2 on 4.12 had its build status changed: passing to partially failing
zarith-freestanding.1.7-2 on 4.13 had its build status changed: not available to partially failing
zarith-freestanding.1.7-2 on 4.14 is now installable. Current state is: partially failing
zarith-freestanding.1.9.1 on 4.08 had its build status changed: passing to partially failing
zarith-freestanding.1.9.1 on 4.09 had its build status changed: passing to partially failing
zarith-freestanding.1.9.1 on 4.10 had its build status changed: passing to partially failing
zarith-freestanding.1.9.1 on 4.11 had its build status changed: passing to partially failing
zarith-freestanding.1.9.1 on 4.12 had its build status changed: passing to partially failing
zarith-freestanding.1.9.1 on 4.13 had its build status changed: not available to partially failing
zarith-freestanding.1.9.1 on 4.14 is now installable. Current state is: partially failing

Packages now not available:

0install-gtk.2.15.2 on 4.05 is not available anymore. Previous state was: passing
0install-gtk.2.15.2 on 4.06 is not available anymore. Previous state was: passing
0install-gtk.2.15.2 on 4.07 is not available anymore. Previous state was: passing
0install-gtk.2.16 on 4.05 is not available anymore. Previous state was: passing
0install-gtk.2.16 on 4.06 is not available anymore. Previous state was: passing
0install-gtk.2.16 on 4.07 is not available anymore. Previous state was: passing
0install.2.10 on 4.02 is not available anymore. Previous state was: failing
0install.2.10 on 4.03 is not available anymore. Previous state was: failing
0install.2.10 on 4.04 is not available anymore. Previous state was: failing
0install.2.10 on 4.05 is not available anymore. Previous state was: failing
0install.2.11 on 4.02 is not available anymore. Previous state was: failing
0install.2.11 on 4.03 is not available anymore. Previous state was: failing
0install.2.11 on 4.04 is not available anymore. Previous state was: failing
0install.2.11 on 4.05 is not available anymore. Previous state was: failing
0install.2.12 on 4.02 is not available anymore. Previous state was: failing
0install.2.12 on 4.03 is not available anymore. Previous state was: failing
0install.2.12 on 4.04 is not available anymore. Previous state was: failing
0install.2.12 on 4.05 is not available anymore. Previous state was: failing
0install.2.12.1 on 4.02 is not available anymore. Previous state was: failing
0install.2.12.1 on 4.03 is not available anymore. Previous state was: internal failure
0install.2.12.1 on 4.04 is not available anymore. Previous state was: failing
0install.2.12.1 on 4.05 is not available anymore. Previous state was: failing
0install.2.12.3 on 4.02 is not available anymore. Previous state was: passing
0install.2.12.3 on 4.03 is not available anymore. Previous state was: passing
0install.2.12.3 on 4.04 is not available anymore. Previous state was: passing
0install.2.12.3 on 4.05 is not available anymore. Previous state was: passing
0install.2.12.3 on 4.06 is not available anymore. Previous state was: passing
0install.2.14 on 4.03 is not available anymore. Previous state was: passing
0install.2.14 on 4.04 is not available anymore. Previous state was: passing
0install.2.14 on 4.05 is not available anymore. Previous state was: passing
0install.2.14 on 4.06 is not available anymore. Previous state was: passing
0install.2.14 on 4.07 is not available anymore. Previous state was: passing
0install.2.14.1 on 4.03 is not available anymore. Previous state was: passing
0install.2.14.1 on 4.04 is not available anymore. Previous state was: passing
0install.2.14.1 on 4.05 is not available anymore. Previous state was: passing
0install.2.14.1 on 4.06 is not available anymore. Previous state was: passing
0install.2.14.1 on 4.07 is not available anymore. Previous state was: passing
0install.2.15.1 on 4.05 is not available anymore. Previous state was: passing
0install.2.15.1 on 4.06 is not available anymore. Previous state was: passing
0install.2.15.1 on 4.07 is not available anymore. Previous state was: passing
0install.2.15.2 on 4.05 is not available anymore. Previous state was: passing
0install.2.15.2 on 4.06 is not available anymore. Previous state was: passing
0install.2.15.2 on 4.07 is not available anymore. Previous state was: passing
0install.2.16 on 4.05 is not available anymore. Previous state was: passing
0install.2.16 on 4.06 is not available anymore. Previous state was: passing
0install.2.16 on 4.07 is not available anymore. Previous state was: passing
0install.2.6.2 on 4.02 is not available anymore. Previous state was: failing
0install.2.6.2 on 4.03 is not available anymore. Previous state was: failing
0install.2.6.2 on 4.04 is not available anymore. Previous state was: failing
0install.2.6.2 on 4.05 is not available anymore. Previous state was: failing
0install.2.9.1 on 4.02 is not available anymore. Previous state was: failing
0install.2.9.1 on 4.03 is not available anymore. Previous state was: failing
0install.2.9.1 on 4.04 is not available anymore. Previous state was: failing
0install.2.9.1 on 4.05 is not available anymore. Previous state was: failing
ANSITerminal.0.6 on 4.02 is not available anymore. Previous state was: passing
ANSITerminal.0.6 on 4.03 is not available anymore. Previous state was: passing
ANSITerminal.0.6 on 4.04 is not available anymore. Previous state was: passing
ANSITerminal.0.6.2 on 4.02 is not available anymore. Previous state was: passing
ANSITerminal.0.6.2 on 4.03 is not available anymore. Previous state was: passing
ANSITerminal.0.6.2 on 4.04 is not available anymore. Previous state was: passing
ANSITerminal.0.6.3 on 4.02 is not available anymore. Previous state was: passing
ANSITerminal.0.6.3 on 4.03 is not available anymore. Previous state was: passing
ANSITerminal.0.6.3 on 4.04 is not available anymore. Previous state was: passing
ANSITerminal.0.6.4 on 4.02 is not available anymore. Previous state was: passing
ANSITerminal.0.6.4 on 4.03 is not available anymore. Previous state was: passing
ANSITerminal.0.6.4 on 4.04 is not available anymore. Previous state was: passing
ANSITerminal.0.6.5 on 4.02 is not available anymore. Previous state was: passing
ANSITerminal.0.6.5 on 4.03 is not available anymore. Previous state was: passing
ANSITerminal.0.6.5 on 4.04 is not available anymore. Previous state was: passing
ANSITerminal.0.7 on 4.02 is not available anymore. Previous state was: passing
ANSITerminal.0.7 on 4.03 is not available anymore. Previous state was: passing
ANSITerminal.0.7 on 4.04 is not available anymore. Previous state was: passing
ANSITerminal.0.7 on 4.05 is not available anymore. Previous state was: passing
ANSITerminal.0.7 on 4.06 is not available anymore. Previous state was: passing
ANSITerminal.0.7 on 4.07 is not available anymore. Previous state was: passing
ANSITerminal.0.8 on 4.02 is not available anymore. Previous state was: passing
ANSITerminal.0.8 on 4.03 is not available anymore. Previous state was: passing
ANSITerminal.0.8 on 4.04 is not available anymore. Previous state was: passing
ANSITerminal.0.8 on 4.05 is not available anymore. Previous state was: passing
ANSITerminal.0.8 on 4.06 is not available anymore. Previous state was: passing
ANSITerminal.0.8 on 4.07 is not available anymore. Previous state was: passing
ANSITerminal.0.8.1 on 4.02 is not available anymore. Previous state was: passing
ANSITerminal.0.8.1 on 4.03 is not available anymore. Previous state was: passing
ANSITerminal.0.8.1 on 4.04 is not available anymore. Previous state was: passing
ANSITerminal.0.8.1 on 4.05 is not available anymore. Previous state was: passing
ANSITerminal.0.8.1 on 4.06 is not available anymore. Previous state was: passing
ANSITerminal.0.8.1 on 4.07 is not available anymore. Previous state was: passing
ANSITerminal.0.8.2 on 4.02 is not available anymore. Previous state was: passing
ANSITerminal.0.8.2 on 4.03 is not available anymore. Previous state was: passing
ANSITerminal.0.8.2 on 4.04 is not available anymore. Previous state was: passing
ANSITerminal.0.8.2 on 4.05 is not available anymore. Previous state was: passing
ANSITerminal.0.8.2 on 4.06 is not available anymore. Previous state was: passing
ANSITerminal.0.8.2 on 4.07 is not available anymore. Previous state was: passing
BetterErrors.0.0.1 on 4.02 is not available anymore. Previous state was: passing
BetterErrors.0.0.1 on 4.03 is not available anymore. Previous state was: passing
BetterErrors.0.0.1 on 4.04 is not available anymore. Previous state was: passing
BetterErrors.0.0.1 on 4.05 is not available anymore. Previous state was: passing
BetterErrors.0.0.1 on 4.06 is not available anymore. Previous state was: passing
BetterErrors.0.0.1 on 4.07 is not available anymore. Previous state was: passing
CamlGI.0.6 on 4.02 is not available anymore. Previous state was: passing
CamlGI.0.6 on 4.03 is not available anymore. Previous state was: passing
CamlGI.0.6 on 4.04 is not available anymore. Previous state was: passing
CamlGI.0.6 on 4.05 is not available anymore. Previous state was: passing
Camldiets.0.2 on 4.02 is not available anymore. Previous state was: passing
Camldiets.0.2 on 4.03 is not available anymore. Previous state was: passing
Camldiets.0.2 on 4.04 is not available anymore. Previous state was: passing
DrawGrammar.0.1.0 on 4.02 is not available anymore. Previous state was: partially failing
DrawGrammar.0.1.0 on 4.03 is not available anymore. Previous state was: partially failing
DrawGrammar.0.1.0 on 4.04 is not available anymore. Previous state was: partially failing
DrawGrammar.0.1.0 on 4.05 is not available anymore. Previous state was: partially failing
DrawGrammar.0.2.0 on 4.02 is not available anymore. Previous state was: partially failing
DrawGrammar.0.2.0 on 4.03 is not available anymore. Previous state was: partially failing
DrawGrammar.0.2.0 on 4.04 is not available anymore. Previous state was: partially failing
DrawGrammar.0.2.0 on 4.05 is not available anymore. Previous state was: partially failing
DrawGrammar.0.2.1 on 4.02 is not available anymore. Previous state was: passing
DrawGrammar.0.2.1 on 4.03 is not available anymore. Previous state was: passing
DrawGrammar.0.2.1 on 4.04 is not available anymore. Previous state was: passing
DrawGrammar.0.2.1 on 4.05 is not available anymore. Previous state was: passing
DrawGrammar.0.2.1 on 4.06 is not available anymore. Previous state was: passing
DrawGrammar.0.2.1 on 4.07 is not available anymore. Previous state was: passing
DrawGrammar.0.2.2 on 4.02 is not available anymore. Previous state was: passing
DrawGrammar.0.2.2 on 4.03 is not available anymore. Previous state was: passing
DrawGrammar.0.2.2 on 4.04 is not available anymore. Previous state was: passing
DrawGrammar.0.2.2 on 4.05 is not available anymore. Previous state was: passing
DrawGrammar.0.2.2 on 4.06 is not available anymore. Previous state was: passing
DrawGrammar.0.2.2 on 4.07 is not available anymore. Previous state was: passing
FrontC.3.4 on 4.02 is not available anymore. Previous state was: passing
FrontC.3.4 on 4.03 is not available anymore. Previous state was: passing
FrontC.3.4 on 4.04 is not available anymore. Previous state was: passing
FrontC.3.4 on 4.05 is not available anymore. Previous state was: passing
FrontC.3.4.1 on 4.02 is not available anymore. Previous state was: passing
FrontC.3.4.1 on 4.03 is not available anymore. Previous state was: passing
FrontC.3.4.1 on 4.04 is not available anymore. Previous state was: passing
FrontC.3.4.1 on 4.05 is not available anymore. Previous state was: passing
FrontC.3.4.1 on 4.06 is not available anymore. Previous state was: passing
FrontC.3.4.1 on 4.07 is not available anymore. Previous state was: passing
FrontC.3.4.2 on 4.02 is not available anymore. Previous state was: passing
FrontC.3.4.2 on 4.03 is not available anymore. Previous state was: passing
FrontC.3.4.2 on 4.04 is not available anymore. Previous state was: passing
FrontC.3.4.2 on 4.05 is not available anymore. Previous state was: passing
FrontC.3.4.2 on 4.06 is not available anymore. Previous state was: passing
FrontC.3.4.2 on 4.07 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.02 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.03 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.04 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.05 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.06 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.07 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.08 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.09 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.10 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.11 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.12 is not available anymore. Previous state was: passing
FrontC.3.4.3 on 4.13 is not available anymore. Previous state was: passing
General.0.1.0 on 4.02 is not available anymore. Previous state was: failing
General.0.1.0 on 4.03 is not available anymore. Previous state was: failing
General.0.1.0 on 4.04 is not available anymore. Previous state was: failing
General.0.1.0 on 4.05 is not available anymore. Previous state was: failing
General.0.2.0 on 4.02 is not available anymore. Previous state was: failing
General.0.2.0 on 4.03 is not available anymore. Previous state was: failing
General.0.2.0 on 4.04 is not available anymore. Previous state was: failing
General.0.2.0 on 4.05 is not available anymore. Previous state was: failing
General.0.4.0 on 4.02 is not available anymore. Previous state was: passing
General.0.4.0 on 4.03 is not available anymore. Previous state was: passing
General.0.4.0 on 4.04 is not available anymore. Previous state was: passing
General.0.4.0 on 4.05 is not available anymore. Previous state was: passing
General.0.4.0 on 4.06 is not available anymore. Previous state was: passing
General.0.5.0 on 4.02 is not available anymore. Previous state was: passing
General.0.5.0 on 4.03 is not available anymore. Previous state was: passing
General.0.5.0 on 4.04 is not available anymore. Previous state was: passing
General.0.5.0 on 4.05 is not available anymore. Previous state was: passing
General.0.5.0 on 4.06 is not available anymore. Previous state was: passing
General.0.6.0 on 4.02 is not available anymore. Previous state was: passing
General.0.6.0 on 4.03 is not available anymore. Previous state was: passing
General.0.6.0 on 4.04 is not available anymore. Previous state was: passing
General.0.6.0 on 4.05 is not available anymore. Previous state was: passing
General.0.6.0 on 4.06 is not available anymore. Previous state was: passing
General.0.6.0 on 4.07 is not available anymore. Previous state was: passing
General.0.7.0 on 4.02 is not available anymore. Previous state was: passing
General.0.7.0 on 4.03 is not available anymore. Previous state was: passing
General.0.7.0 on 4.04 is not available anymore. Previous state was: passing
General.0.7.0 on 4.05 is not available anymore. Previous state was: passing
General.0.7.0 on 4.06 is not available anymore. Previous state was: passing
General.0.7.0 on 4.07 is not available anymore. Previous state was: passing
ISO8601.0.1.2 on 4.02 is not available anymore. Previous state was: passing
ISO8601.0.1.2 on 4.03 is not available anymore. Previous state was: passing
ISO8601.0.1.2 on 4.04 is not available anymore. Previous state was: passing
ISO8601.0.1.2 on 4.05 is not available anymore. Previous state was: passing
ISO8601.0.1.2 on 4.06 is not available anymore. Previous state was: passing
ISO8601.0.1.2 on 4.07 is not available anymore. Previous state was: passing
ISO8601.0.2.0 on 4.02 is not available anymore. Previous state was: passing
ISO8601.0.2.0 on 4.03 is not available anymore. Previous state was: passing
ISO8601.0.2.0 on 4.04 is not available anymore. Previous state was: passing
ISO8601.0.2.0 on 4.05 is not available anymore. Previous state was: passing
ISO8601.0.2.0 on 4.06 is not available anymore. Previous state was: passing
ISO8601.0.2.0 on 4.07 is not available anymore. Previous state was: passing
ISO8601.0.2.2 on 4.02 is not available anymore. Previous state was: passing
ISO8601.0.2.2 on 4.03 is not available anymore. Previous state was: passing
ISO8601.0.2.2 on 4.04 is not available anymore. Previous state was: passing
ISO8601.0.2.2 on 4.05 is not available anymore. Previous state was: passing
ISO8601.0.2.2 on 4.06 is not available anymore. Previous state was: passing
ISO8601.0.2.2 on 4.07 is not available anymore. Previous state was: passing
ISO8601.0.2.3 on 4.02 is not available anymore. Previous state was: passing
ISO8601.0.2.3 on 4.03 is not available anymore. Previous state was: passing
ISO8601.0.2.3 on 4.04 is not available anymore. Previous state was: passing
ISO8601.0.2.3 on 4.05 is not available anymore. Previous state was: passing
ISO8601.0.2.3 on 4.06 is not available anymore. Previous state was: passing
ISO8601.0.2.3 on 4.07 is not available anymore. Previous state was: passing
ISO8601.0.2.4 on 4.02 is not available anymore. Previous state was: passing
ISO8601.0.2.4 on 4.03 is not available anymore. Previous state was: passing
ISO8601.0.2.4 on 4.04 is not available anymore. Previous state was: passing
ISO8601.0.2.4 on 4.05 is not available anymore. Previous state was: passing
ISO8601.0.2.4 on 4.06 is not available anymore. Previous state was: passing
ISO8601.0.2.4 on 4.07 is not available anymore. Previous state was: passing
ISO8601.0.2.5 on 4.02 is not available anymore. Previous state was: passing
ISO8601.0.2.5 on 4.03 is not available anymore. Previous state was: passing
ISO8601.0.2.5 on 4.04 is not available anymore. Previous state was: passing
ISO8601.0.2.5 on 4.05 is not available anymore. Previous state was: passing
ISO8601.0.2.5 on 4.06 is not available anymore. Previous state was: passing
ISO8601.0.2.5 on 4.07 is not available anymore. Previous state was: passing
ISO8601.0.2.6 on 4.02 is not available anymore. Previous state was: passing
ISO8601.0.2.6 on 4.03 is not available anymore. Previous state was: passing
ISO8601.0.2.6 on 4.04 is not available anymore. Previous state was: passing
ISO8601.0.2.6 on 4.05 is not available anymore. Previous state was: passing
ISO8601.0.2.6 on 4.06 is not available anymore. Previous state was: passing
ISO8601.0.2.6 on 4.07 is not available anymore. Previous state was: passing
JsOfOCairo.0.1.0 on 4.02 is not available anymore. Previous state was: passing
JsOfOCairo.0.1.0 on 4.03 is not available anymore. Previous state was: passing
JsOfOCairo.0.1.0 on 4.04 is not available anymore. Previous state was: passing
JsOfOCairo.1.0.0 on 4.02 is not available anymore. Previous state was: passing
JsOfOCairo.1.0.0 on 4.03 is not available anymore. Previous state was: passing
JsOfOCairo.1.0.0 on 4.04 is not available anymore. Previous state was: passing
JsOfOCairo.1.0.0 on 4.05 is not available anymore. Previous state was: passing
JsOfOCairo.1.0.1 on 4.02 is not available anymore. Previous state was: partially failing
JsOfOCairo.1.0.1 on 4.03 is not available anymore. Previous state was: partially failing
JsOfOCairo.1.0.1 on 4.04 is not available anymore. Previous state was: partially failing
JsOfOCairo.1.0.1 on 4.05 is not available anymore. Previous state was: partially failing
JsOfOCairo.1.0.1 on 4.06 is not available anymore. Previous state was: partially failing
JsOfOCairo.1.0.1 on 4.07 is not available anymore. Previous state was: partially failing
JsOfOCairo.1.1.1 on 4.02 is not available anymore. Previous state was: passing
JsOfOCairo.1.1.1 on 4.03 is not available anymore. Previous state was: passing
JsOfOCairo.1.1.1 on 4.04 is not available anymore. Previous state was: passing
JsOfOCairo.1.1.1 on 4.05 is not available anymore. Previous state was: passing
JsOfOCairo.1.1.1 on 4.06 is not available anymore. Previous state was: passing
JsOfOCairo.1.1.1 on 4.07 is not available anymore. Previous state was: passing
JsOfOCairo.2.0.0 on 4.02 is not available anymore. Previous state was: passing
JsOfOCairo.2.0.0 on 4.03 is not available anymore. Previous state was: passing
JsOfOCairo.2.0.0 on 4.04 is not available anymore. Previous state was: passing
JsOfOCairo.2.0.0 on 4.05 is not available anymore. Previous state was: passing
JsOfOCairo.2.0.0 on 4.06 is not available anymore. Previous state was: passing
JsOfOCairo.2.0.0 on 4.07 is not available anymore. Previous state was: passing
KaSim.3.5.150925 on 4.02 is not available anymore. Previous state was: internal failure
KaSim.3.5.150925 on 4.03 is not available anymore. Previous state was: internal failure
KaSim.3.5.150925 on 4.04 is not available anymore. Previous state was: internal failure
KaSim.3.5.150925 on 4.05 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.02 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.03 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.04 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.05 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.06 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.07 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.08 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.09 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.10 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.11 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.12 is not available anymore. Previous state was: internal failure
KaSim.4.0.0 on 4.13 is not available anymore. Previous state was: internal failure
OCanren-ppx.0.1.0 on 4.07 is not available anymore. Previous state was: passing
TCSLib.0.1 on 4.03 is not available anymore. Previous state was: passing
TCSLib.0.1 on 4.04 is not available anymore. Previous state was: passing
TCSLib.0.1 on 4.05 is not available anymore. Previous state was: passing
TCSLib.0.1 on 4.06 is not available anymore. Previous state was: passing
TCSLib.0.1 on 4.07 is not available anymore. Previous state was: passing
TCSLib.0.2 on 4.03 is not available anymore. Previous state was: passing
TCSLib.0.2 on 4.04 is not available anymore. Previous state was: passing
TCSLib.0.2 on 4.05 is not available anymore. Previous state was: passing
TCSLib.0.2 on 4.06 is not available anymore. Previous state was: passing
TCSLib.0.2 on 4.07 is not available anymore. Previous state was: passing
TCSLib.0.3 on 4.03 is not available anymore. Previous state was: passing
TCSLib.0.3 on 4.04 is not available anymore. Previous state was: passing
TCSLib.0.3 on 4.05 is not available anymore. Previous state was: passing
TCSLib.0.3 on 4.06 is not available anymore. Previous state was: passing
TCSLib.0.3 on 4.07 is not available anymore. Previous state was: passing
aacplus.0.2.1 on 4.02 is not available anymore. Previous state was: internal failure
aacplus.0.2.1 on 4.03 is not available anymore. Previous state was: internal failure
aacplus.0.2.1 on 4.04 is not available anymore. Previous state was: internal failure
aacplus.0.2.1 on 4.05 is not available anymore. Previous state was: internal failure
aacplus.0.2.1 on 4.06 is not available anymore. Previous state was: internal failure
aacplus.0.2.1 on 4.07 is not available anymore. Previous state was: internal failure
aacplus.0.2.2 on 4.02 is not available anymore. Previous state was: internal failure
aacplus.0.2.2 on 4.03 is not available anymore. Previous state was: internal failure
aacplus.0.2.2 on 4.04 is not available anymore. Previous state was: internal failure
aacplus.0.2.2 on 4.05 is not available anymore. Previous state was: internal failure
aacplus.0.2.2 on 4.06 is not available anymore. Previous state was: internal failure
aacplus.0.2.2 on 4.07 is not available anymore. Previous state was: internal failure
abella.2.0.2 on 4.02 is not available anymore. Previous state was: passing
abella.2.0.2 on 4.03 is not available anymore. Previous state was: passing
abella.2.0.2 on 4.04 is not available anymore. Previous state was: passing
abella.2.0.2 on 4.05 is not available anymore. Previous state was: passing
abella.2.0.2 on 4.06 is not available anymore. Previous state was: passing
abella.2.0.2 on 4.07 is not available anymore. Previous state was: passing
abella.2.0.3 on 4.02 is not available anymore. Previous state was: passing
abella.2.0.3 on 4.03 is not available anymore. Previous state was: passing
abella.2.0.3 on 4.04 is not available anymore. Previous state was: passing
abella.2.0.3 on 4.05 is not available anymore. Previous state was: passing
abella.2.0.3 on 4.06 is not available anymore. Previous state was: passing
abella.2.0.3 on 4.07 is not available anymore. Previous state was: passing
abella.2.0.4 on 4.02 is not available anymore. Previous state was: passing
abella.2.0.4 on 4.03 is not available anymore. Previous state was: passing
abella.2.0.4 on 4.04 is not available anymore. Previous state was: passing
abella.2.0.4 on 4.05 is not available anymore. Previous state was: passing
abella.2.0.4 on 4.06 is not available anymore. Previous state was: passing
abella.2.0.4 on 4.07 is not available anymore. Previous state was: passing
abella.2.0.5 on 4.02 is not available anymore. Previous state was: passing
abella.2.0.5 on 4.03 is not available anymore. Previous state was: passing
abella.2.0.5 on 4.04 is not available anymore. Previous state was: passing
abella.2.0.5 on 4.05 is not available anymore. Previous state was: passing
abella.2.0.5 on 4.06 is not available anymore. Previous state was: passing
abella.2.0.5 on 4.07 is not available anymore. Previous state was: passing
abella.2.0.6 on 4.02 is not available anymore. Previous state was: passing
abella.2.0.6 on 4.03 is not available anymore. Previous state was: passing
abella.2.0.6 on 4.04 is not available anymore. Previous state was: passing
abella.2.0.6 on 4.05 is not available anymore. Previous state was: passing
abella.2.0.6 on 4.06 is not available anymore. Previous state was: passing
abella.2.0.6 on 4.07 is not available anymore. Previous state was: passing
abella.2.0.7 on 4.02 is not available anymore. Previous state was: passing
abella.2.0.7 on 4.03 is not available anymore. Previous state was: passing
abella.2.0.7 on 4.04 is not available anymore. Previous state was: passing
abella.2.0.7 on 4.05 is not available anymore. Previous state was: passing
abella.2.0.7 on 4.06 is not available anymore. Previous state was: passing
abella.2.0.7 on 4.07 is not available anymore. Previous state was: passing
abt.0.0.3 on 4.02 is not available anymore. Previous state was: passing
abt.0.0.3 on 4.03 is not available anymore. Previous state was: passing
abt.0.0.3 on 4.04 is not available anymore. Previous state was: passing
acgtk.1.3.0 on 4.03 is not available anymore. Previous state was: passing
acgtk.1.3.0 on 4.04 is not available anymore. Previous state was: passing
acgtk.1.3.0 on 4.05 is not available anymore. Previous state was: passing
acgtk.1.3.1 on 4.03 is not available anymore. Previous state was: passing
acgtk.1.3.1 on 4.04 is not available anymore. Previous state was: passing
acgtk.1.3.1 on 4.05 is not available anymore. Previous state was: passing
acgtk.1.3.2 on 4.03 is not available anymore. Previous state was: partially failing
acgtk.1.3.2 on 4.04 is not available anymore. Previous state was: partially failing
acgtk.1.3.2 on 4.05 is not available anymore. Previous state was: partially failing
acgtk.1.3.3 on 4.03 is not available anymore. Previous state was: partially failing
acgtk.1.3.3 on 4.04 is not available anymore. Previous state was: partially failing
acgtk.1.3.3 on 4.05 is not available anymore. Previous state was: partially failing
acgtk.1.4.0 on 4.03 is not available anymore. Previous state was: passing
acgtk.1.4.0 on 4.04 is not available anymore. Previous state was: passing
acgtk.1.4.0 on 4.05 is not available anymore. Previous state was: passing
acgtk.1.5.0 on 4.03 is not available anymore. Previous state was: passing
acgtk.1.5.0 on 4.04 is not available anymore. Previous state was: passing
acgtk.1.5.0 on 4.05 is not available anymore. Previous state was: passing
acgtk.1.5.0 on 4.06 is not available anymore. Previous state was: passing
acgtk.1.5.0 on 4.07 is not available anymore. Previous state was: passing
acgtk.1.5.1 on 4.05 is not available anymore. Previous state was: passing
acgtk.1.5.1 on 4.06 is not available anymore. Previous state was: passing
acgtk.1.5.1 on 4.07 is not available anymore. Previous state was: passing
acgtk.1.5.2 on 4.05 is not available anymore. Previous state was: passing
acgtk.1.5.2 on 4.06 is not available anymore. Previous state was: passing
acgtk.1.5.2 on 4.07 is not available anymore. Previous state was: passing
acme.0.1 on 4.02 is not available anymore. Previous state was: passing
acme.0.1 on 4.03 is not available anymore. Previous state was: passing
acme.0.1 on 4.04 is not available anymore. Previous state was: passing
acme.0.1 on 4.05 is not available anymore. Previous state was: passing
acpc.1.0 on 4.02 is not available anymore. Previous state was: passing
acpc.1.0 on 4.03 is not available anymore. Previous state was: passing
acpc.1.0 on 4.04 is not available anymore. Previous state was: passing
acpc.1.0 on 4.05 is not available anymore. Previous state was: passing
acpc.1.1 on 4.02 is not available anymore. Previous state was: passing
acpc.1.1 on 4.03 is not available anymore. Previous state was: passing
acpc.1.1 on 4.04 is not available anymore. Previous state was: passing
acpc.1.1 on 4.05 is not available anymore. Previous state was: passing
acpc.1.1.1 on 4.02 is not available anymore. Previous state was: passing
acpc.1.1.1 on 4.03 is not available anymore. Previous state was: passing
acpc.1.1.1 on 4.04 is not available anymore. Previous state was: passing
acpc.1.1.1 on 4.05 is not available anymore. Previous state was: passing
acpc.1.1.1 on 4.06 is not available anymore. Previous state was: passing
acpc.1.1.1 on 4.07 is not available anymore. Previous state was: passing
acpc.1.2 on 4.02 is not available anymore. Previous state was: passing
acpc.1.2 on 4.03 is not available anymore. Previous state was: passing
acpc.1.2 on 4.04 is not available anymore. Previous state was: passing
acpc.1.2 on 4.05 is not available anymore. Previous state was: passing
acpc.1.2.1 on 4.02 is not available anymore. Previous state was: passing
acpc.1.2.1 on 4.03 is not available anymore. Previous state was: passing
acpc.1.2.1 on 4.04 is not available anymore. Previous state was: passing
acpc.1.2.1 on 4.05 is not available anymore. Previous state was: passing
acpc.1.2.2 on 4.02 is not available anymore. Previous state was: passing
acpc.1.2.2 on 4.03 is not available anymore. Previous state was: passing
acpc.1.2.2 on 4.04 is not available anymore. Previous state was: passing
acpc.1.2.2 on 4.05 is not available anymore. Previous state was: passing
acpc.1.2.3 on 4.02 is not available anymore. Previous state was: passing
acpc.1.2.3 on 4.03 is not available anymore. Previous state was: passing
acpc.1.2.3 on 4.04 is not available anymore. Previous state was: passing
acpc.1.2.3 on 4.05 is not available anymore. Previous state was: passing
acpc.1.2.3 on 4.06 is not available anymore. Previous state was: passing
acpc.1.2.3 on 4.07 is not available anymore. Previous state was: passing
aez.0.3 on 4.02 is not available anymore. Previous state was: passing
aez.0.3 on 4.03 is not available anymore. Previous state was: passing
aez.0.3 on 4.04 is not available anymore. Previous state was: passing
aez.0.3 on 4.05 is not available anymore. Previous state was: passing
aez.0.3 on 4.06 is not available anymore. Previous state was: passing
aez.0.3 on 4.07 is not available anymore. Previous state was: passing
afl-persistent.1.0 on 4.05 is not available anymore. Previous state was: passing
afl-persistent.1.0 on 4.06 is not available anymore. Previous state was: passing
afl-persistent.1.0 on 4.07 is not available anymore. Previous state was: passing
afl-persistent.1.1 on 4.05 is not available anymore. Previous state was: passing
afl-persistent.1.1 on 4.06 is not available anymore. Previous state was: passing
afl-persistent.1.1 on 4.07 is not available anymore. Previous state was: passing
afl-persistent.1.2 on 4.02 is not available anymore. Previous state was: passing
afl-persistent.1.2 on 4.03 is not available anymore. Previous state was: passing
afl-persistent.1.2 on 4.04 is not available anymore. Previous state was: passing
afl-persistent.1.2 on 4.05 is not available anymore. Previous state was: passing
afl-persistent.1.2 on 4.06 is not available anymore. Previous state was: passing
afl-persistent.1.2 on 4.07 is not available anymore. Previous state was: passing
afl-persistent.1.3 on 4.02 is not available anymore. Previous state was: passing
afl-persistent.1.3 on 4.03 is not available anymore. Previous state was: passing
afl-persistent.1.3 on 4.04 is not available anymore. Previous state was: passing
afl-persistent.1.3 on 4.05 is not available anymore. Previous state was: passing
afl-persistent.1.3 on 4.06 is not available anymore. Previous state was: passing
afl-persistent.1.3 on 4.07 is not available anymore. Previous state was: passing
afl.2.52b on 4.02 is not available anymore. Previous state was: passing
afl.2.52b on 4.03 is not available anymore. Previous state was: passing
afl.2.52b on 4.04 is not available anymore. Previous state was: passing
afl.2.52b on 4.05 is not available anymore. Previous state was: passing
afl.2.52b on 4.06 is not available anymore. Previous state was: passing
afl.2.52b on 4.07 is not available anymore. Previous state was: passing
ago.0.1 on 4.02 is not available anymore. Previous state was: passing
ago.0.1 on 4.03 is not available anymore. Previous state was: passing
ago.0.1 on 4.04 is not available anymore. Previous state was: passing
ago.0.1 on 4.05 is not available anymore. Previous state was: passing
ago.0.1 on 4.06 is not available anymore. Previous state was: passing
ago.0.1 on 4.07 is not available anymore. Previous state was: passing
ago.0.2 on 4.02 is not available anymore. Previous state was: passing
ago.0.2 on 4.03 is not available anymore. Previous state was: passing
ago.0.2 on 4.04 is not available anymore. Previous state was: passing
ago.0.2 on 4.05 is not available anymore. Previous state was: passing
ago.0.2 on 4.06 is not available anymore. Previous state was: passing
ago.0.2 on 4.07 is not available anymore. Previous state was: passing
ago.0.3 on 4.02 is not available anymore. Previous state was: passing
ago.0.3 on 4.03 is not available anymore. Previous state was: passing
ago.0.3 on 4.04 is not available anymore. Previous state was: passing
ago.0.3 on 4.05 is not available anymore. Previous state was: passing
ago.0.3 on 4.06 is not available anymore. Previous state was: passing
ago.0.3 on 4.07 is not available anymore. Previous state was: passing
ago.0.4 on 4.02 is not available anymore. Previous state was: passing
ago.0.4 on 4.03 is not available anymore. Previous state was: passing
ago.0.4 on 4.04 is not available anymore. Previous state was: passing
ago.0.4 on 4.05 is not available anymore. Previous state was: passing
ago.0.4 on 4.06 is not available anymore. Previous state was: passing
ago.0.4 on 4.07 is not available anymore. Previous state was: passing
agrep.1.0 on 4.02 is not available anymore. Previous state was: passing
agrep.1.0 on 4.03 is not available anymore. Previous state was: passing
agrep.1.0 on 4.04 is not available anymore. Previous state was: passing
agrep.1.0 on 4.05 is not available anymore. Previous state was: passing
agrid.0.1 on 4.05 is not available anymore. Previous state was: passing
agrid.0.1 on 4.06 is not available anymore. Previous state was: passing
agrid.0.1 on 4.07 is not available anymore. Previous state was: passing
ahrocksdb.0.2.0 on 4.06 is not available anymore. Previous state was: internal failure
ahrocksdb.0.2.0 on 4.07 is not available anymore. Previous state was: internal failure
ahrocksdb.0.2.1 on 4.06 is not available anymore. Previous state was: internal failure
ahrocksdb.0.2.1 on 4.07 is not available anymore. Previous state was: internal failure
ahrocksdb.0.2.2 on 4.06 is not available anymore. Previous state was: passing
ahrocksdb.0.2.2 on 4.07 is not available anymore. Previous state was: passing
aifad.2.0.7 on 4.02 is not available anymore. Previous state was: passing
aifad.2.0.7 on 4.03 is not available anymore. Previous state was: passing
aifad.2.0.7 on 4.04 is not available anymore. Previous state was: passing
aifad.2.0.7 on 4.05 is not available anymore. Previous state was: passing
aifad.2.0.8 on 4.02 is not available anymore. Previous state was: passing
aifad.2.0.8 on 4.03 is not available anymore. Previous state was: passing
aifad.2.0.8 on 4.04 is not available anymore. Previous state was: passing
aifad.2.0.8 on 4.05 is not available anymore. Previous state was: passing
aifad.2.1.0 on 4.04 is not available anymore. Previous state was: passing
aifad.2.1.0 on 4.05 is not available anymore. Previous state was: passing
aifad.2.1.0 on 4.06 is not available anymore. Previous state was: passing
aifad.2.1.0 on 4.07 is not available anymore. Previous state was: passing
aifad.2.2.1 on 4.04 is not available anymore. Previous state was: passing
aifad.2.2.1 on 4.05 is not available anymore. Previous state was: passing
aifad.2.2.1 on 4.06 is not available anymore. Previous state was: passing
aifad.2.2.1 on 4.07 is not available anymore. Previous state was: passing
aifad.2.2.2 on 4.04 is not available anymore. Previous state was: passing
aifad.2.2.2 on 4.05 is not available anymore. Previous state was: passing
aifad.2.2.2 on 4.06 is not available anymore. Previous state was: passing
aifad.2.2.2 on 4.07 is not available anymore. Previous state was: passing
aio.0.0.3 on 4.02 is not available anymore. Previous state was: passing
aio.0.0.3 on 4.03 is not available anymore. Previous state was: passing
aio.0.0.3 on 4.04 is not available anymore. Previous state was: passing
aio.0.0.3 on 4.05 is not available anymore. Previous state was: passing
aio.0.0.3 on 4.06 is not available anymore. Previous state was: passing
aio.0.0.3 on 4.07 is not available anymore. Previous state was: passing
alba.0.4.0 on 4.03 is not available anymore. Previous state was: passing
alba.0.4.0 on 4.04 is not available anymore. Previous state was: passing
alba.0.4.0 on 4.05 is not available anymore. Previous state was: passing
alba.0.4.0 on 4.06 is not available anymore. Previous state was: passing
alba.0.4.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.0.8.2 on 4.03 is not available anymore. Previous state was: passing
alcotest-async.0.8.2 on 4.04 is not available anymore. Previous state was: passing
alcotest-async.0.8.2 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.0.8.2 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.0.8.2 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.0.8.5 on 4.03 is not available anymore. Previous state was: passing
alcotest-async.0.8.5 on 4.04 is not available anymore. Previous state was: passing
alcotest-async.0.8.5 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.0.8.5 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.0.8.5 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.1.0.0 on 4.03 is not available anymore. Previous state was: passing
alcotest-async.1.0.0 on 4.04 is not available anymore. Previous state was: passing
alcotest-async.1.0.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.1.0.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.1.0.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.1.0.1 on 4.03 is not available anymore. Previous state was: passing
alcotest-async.1.0.1 on 4.04 is not available anymore. Previous state was: passing
alcotest-async.1.0.1 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.1.0.1 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.1.0.1 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.1.1.0 on 4.03 is not available anymore. Previous state was: passing
alcotest-async.1.1.0 on 4.04 is not available anymore. Previous state was: passing
alcotest-async.1.1.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.1.1.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.1.1.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.1.2.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.1.2.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.1.2.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.1.2.1 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.1.2.1 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.1.2.1 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.1.2.2 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.1.2.2 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.1.2.2 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.1.2.3 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.1.2.3 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.1.2.3 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.1.3.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.1.3.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.1.3.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-async.1.4.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-async.1.4.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-async.1.4.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.0 on 4.02 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.0 on 4.03 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.0 on 4.04 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.5 on 4.02 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.5 on 4.03 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.5 on 4.04 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.5 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.5 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.0.8.5 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.0 on 4.03 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.0 on 4.04 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.1 on 4.03 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.1 on 4.04 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.1 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.1 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.1.0.1 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.1.1.0 on 4.03 is not available anymore. Previous state was: passing
alcotest-lwt.1.1.0 on 4.04 is not available anymore. Previous state was: passing
alcotest-lwt.1.1.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.1.1.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.1.1.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.1 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.1 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.1 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.2 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.2 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.2 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.3 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.3 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.1.2.3 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.1.3.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.1.3.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.1.3.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-lwt.1.4.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-lwt.1.4.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-lwt.1.4.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.1 on 4.05 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.1 on 4.06 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.1 on 4.07 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.2 on 4.05 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.2 on 4.06 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.2 on 4.07 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.3 on 4.05 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.3 on 4.06 is not available anymore. Previous state was: passing
alcotest-mirage.1.2.3 on 4.07 is not available anymore. Previous state was: passing
alcotest-mirage.1.3.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-mirage.1.3.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-mirage.1.3.0 on 4.07 is not available anymore. Previous state was: passing
alcotest-mirage.1.4.0 on 4.05 is not available anymore. Previous state was: passing
alcotest-mirage.1.4.0 on 4.06 is not available anymore. Previous state was: passing
alcotest-mirage.1.4.0 on 4.07 is not available anymore. Previous state was: passing
alcotest.0.1.0 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.1.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.1.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.1.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.2.0 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.2.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.2.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.2.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.3.0 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.3.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.3.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.3.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.3.1 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.3.1 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.3.1 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.3.1 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.3.2 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.3.2 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.3.2 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.3.2 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.3.3 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.3.3 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.3.3 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.3.3 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.4.0 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.4.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.4.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.4.1 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.1 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.4.1 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.4.1 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.4.10 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.10 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.4.10 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.4.10 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.4.11 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.11 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.4.11 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.4.11 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.4.2 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.2 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.4.2 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.4.2 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.4.3 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.3 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.4.3 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.4.3 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.4.4 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.4 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.4.4 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.4.4 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.4.5 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.5 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.4.5 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.4.5 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.4.6 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.7 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.8 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.4.9 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.5.0 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.5.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.5.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.5.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.5.0 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.6.0 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.6.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.6.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.6.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.6.0 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.7.0 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.7.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.7.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.7.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.7.0 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.7.1 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.7.1 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.7.1 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.7.1 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.7.1 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.7.2 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.7.2 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.7.2 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.7.2 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.7.2 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.8.0 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.8.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.8.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.8.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.8.0 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.8.0 on 4.07 is not available anymore. Previous state was: passing
alcotest.0.8.1 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.8.1 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.8.1 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.8.1 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.8.1 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.8.1 on 4.07 is not available anymore. Previous state was: passing
alcotest.0.8.3 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.8.3 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.8.3 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.8.3 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.8.3 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.8.3 on 4.07 is not available anymore. Previous state was: passing
alcotest.0.8.4 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.8.4 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.8.4 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.8.4 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.8.4 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.8.4 on 4.07 is not available anymore. Previous state was: passing
alcotest.0.8.5 on 4.02 is not available anymore. Previous state was: passing
alcotest.0.8.5 on 4.03 is not available anymore. Previous state was: passing
alcotest.0.8.5 on 4.04 is not available anymore. Previous state was: passing
alcotest.0.8.5 on 4.05 is not available anymore. Previous state was: passing
alcotest.0.8.5 on 4.06 is not available anymore. Previous state was: passing
alcotest.0.8.5 on 4.07 is not available anymore. Previous state was: passing
alcotest.1.0.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.1.0.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.1.0.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.1.0.0 on 4.06 is not available anymore. Previous state was: passing
alcotest.1.0.0 on 4.07 is not available anymore. Previous state was: passing
alcotest.1.0.1 on 4.03 is not available anymore. Previous state was: passing
alcotest.1.0.1 on 4.04 is not available anymore. Previous state was: passing
alcotest.1.0.1 on 4.05 is not available anymore. Previous state was: passing
alcotest.1.0.1 on 4.06 is not available anymore. Previous state was: passing
alcotest.1.0.1 on 4.07 is not available anymore. Previous state was: passing
alcotest.1.1.0 on 4.03 is not available anymore. Previous state was: passing
alcotest.1.1.0 on 4.04 is not available anymore. Previous state was: passing
alcotest.1.1.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.1.1.0 on 4.06 is not available anymore. Previous state was: passing
alcotest.1.1.0 on 4.07 is not available anymore. Previous state was: passing
alcotest.1.2.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.1.2.0 on 4.06 is not available anymore. Previous state was: passing
alcotest.1.2.0 on 4.07 is not available anymore. Previous state was: passing
alcotest.1.2.1 on 4.05 is not available anymore. Previous state was: passing
alcotest.1.2.1 on 4.06 is not available anymore. Previous state was: passing
alcotest.1.2.1 on 4.07 is not available anymore. Previous state was: passing
alcotest.1.2.2 on 4.05 is not available anymore. Previous state was: passing
alcotest.1.2.2 on 4.06 is not available anymore. Previous state was: passing
alcotest.1.2.2 on 4.07 is not available anymore. Previous state was: passing
alcotest.1.2.3 on 4.05 is not available anymore. Previous state was: passing
alcotest.1.2.3 on 4.06 is not available anymore. Previous state was: passing
alcotest.1.2.3 on 4.07 is not available anymore. Previous state was: passing
alcotest.1.3.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.1.3.0 on 4.06 is not available anymore. Previous state was: passing
alcotest.1.3.0 on 4.07 is not available anymore. Previous state was: passing
alcotest.1.4.0 on 4.05 is not available anymore. Previous state was: passing
alcotest.1.4.0 on 4.06 is not available anymore. Previous state was: passing
alcotest.1.4.0 on 4.07 is not available anymore. Previous state was: passing
aliases.0.0.5 on 4.02 is not available anymore. Previous state was: passing
aliases.0.0.5 on 4.03 is not available anymore. Previous state was: passing
aliases.0.0.5 on 4.04 is not available anymore. Previous state was: passing
aliases.0.0.5 on 4.05 is not available anymore. Previous state was: passing
aliases.0.0.5 on 4.06 is not available anymore. Previous state was: passing
aliases.0.0.5 on 4.07 is not available anymore. Previous state was: passing
alphaCaml.20061214 on 4.02 is not available anymore. Previous state was: passing
alphaCaml.20061214 on 4.03 is not available anymore. Previous state was: passing
alphaCaml.20061214 on 4.04 is not available anymore. Previous state was: passing
alphaCaml.20061214 on 4.05 is not available anymore. Previous state was: passing
alsa.0.2.1 on 4.02 is not available anymore. Previous state was: failing
alsa.0.2.1 on 4.03 is not available anymore. Previous state was: failing
alsa.0.2.2 on 4.02 is not available anymore. Previous state was: failing
alsa.0.2.2 on 4.03 is not available anymore. Previous state was: failing
alsa.0.2.3 on 4.02 is not available anymore. Previous state was: passing
alsa.0.2.3 on 4.03 is not available anymore. Previous state was: passing
alsa.0.2.3 on 4.04 is not available anymore. Previous state was: passing
alsa.0.2.3 on 4.05 is not available anymore. Previous state was: passing
alsa.0.2.3 on 4.06 is not available anymore. Previous state was: passing
alsa.0.2.3 on 4.07 is not available anymore. Previous state was: passing
alsa.0.3.0 on 4.02 is not available anymore. Previous state was: passing
alsa.0.3.0 on 4.03 is not available anymore. Previous state was: passing
alsa.0.3.0 on 4.04 is not available anymore. Previous state was: passing
alsa.0.3.0 on 4.05 is not available anymore. Previous state was: passing
alsa.0.3.0 on 4.06 is not available anymore. Previous state was: passing
alsa.0.3.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-free.2.0.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-free.2.0.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-free.2.0.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-free.2.0.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-free.2.2.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-free.2.2.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-free.2.2.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-free.2.2.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.1 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.1 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.1 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.1 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.2 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.2 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.2 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.2 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.3 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.3 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.3 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-lib.2.3.3 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-lib.2.4.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-lib.2.4.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-lib.2.4.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-lib.2.4.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.1 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.1 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.1 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.1 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.2 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.2 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.2 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.2 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.3 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.3 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.3 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.3.3 on 4.07 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.4.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.4.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.4.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo-parsers.2.4.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.0.95.2 on 4.02 is not available anymore. Previous state was: passing
alt-ergo.0.95.2 on 4.03 is not available anymore. Previous state was: passing
alt-ergo.0.95.2 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.0.95.2 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.0.95.2 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.0.95.2 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.0.99.1 on 4.02 is not available anymore. Previous state was: passing
alt-ergo.0.99.1 on 4.03 is not available anymore. Previous state was: passing
alt-ergo.0.99.1 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.0.99.1 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.0.99.1 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.0.99.1 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.1.01 on 4.02 is not available anymore. Previous state was: passing
alt-ergo.1.01 on 4.03 is not available anymore. Previous state was: passing
alt-ergo.1.01 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.1.01 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.1.01 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.1.01 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.1.30 on 4.02 is not available anymore. Previous state was: passing
alt-ergo.1.30 on 4.03 is not available anymore. Previous state was: passing
alt-ergo.1.30 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.1.30 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.1.30 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.1.30 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.2.0.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.2.0.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.2.0.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.2.0.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.2.1.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.2.1.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.2.1.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.2.1.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.2.2.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.2.2.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.2.2.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.2.2.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.2.3.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.2.3.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.2.3.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.2.3.0 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.2.3.1 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.2.3.1 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.2.3.1 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.2.3.1 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.2.3.2 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.2.3.2 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.2.3.2 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.2.3.2 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.2.3.3 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.2.3.3 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.2.3.3 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.2.3.3 on 4.07 is not available anymore. Previous state was: passing
alt-ergo.2.4.0 on 4.04 is not available anymore. Previous state was: passing
alt-ergo.2.4.0 on 4.05 is not available anymore. Previous state was: passing
alt-ergo.2.4.0 on 4.06 is not available anymore. Previous state was: passing
alt-ergo.2.4.0 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.02 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.03 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.04 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.05 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.06 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.08 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.09 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.10 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.11 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.12 is not available anymore. Previous state was: passing
altgr-ergo.0.95.2 on 4.13 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.02 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.03 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.04 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.05 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.06 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.08 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.09 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.10 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.11 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.12 is not available anymore. Previous state was: passing
altgr-ergo.0.99.1 on 4.13 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.02 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.03 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.04 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.05 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.06 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.08 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.09 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.10 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.11 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.12 is not available anymore. Previous state was: passing
altgr-ergo.1.01 on 4.13 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.02 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.03 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.04 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.05 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.06 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.08 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.09 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.10 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.11 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.12 is not available anymore. Previous state was: passing
altgr-ergo.1.30 on 4.13 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.04 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.05 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.06 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.08 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.09 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.10 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.11 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.12 is not available anymore. Previous state was: passing
altgr-ergo.2.3.0 on 4.13 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.04 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.05 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.06 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.08 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.09 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.10 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.11 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.12 is not available anymore. Previous state was: passing
altgr-ergo.2.3.1 on 4.13 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.04 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.05 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.06 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.08 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.09 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.10 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.11 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.12 is not available anymore. Previous state was: passing
altgr-ergo.2.3.2 on 4.13 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.04 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.05 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.06 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.08 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.09 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.10 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.11 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.12 is not available anymore. Previous state was: passing
altgr-ergo.2.3.3 on 4.13 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.04 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.05 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.06 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.07 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.08 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.09 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.10 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.11 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.12 is not available anymore. Previous state was: passing
altgr-ergo.2.4.0 on 4.13 is not available anymore. Previous state was: passing
amf.0.1.0 on 4.03 is not available anymore. Previous state was: failing
amf.0.1.0 on 4.04 is not available anymore. Previous state was: passing
amf.0.1.0 on 4.05 is not available anymore. Previous state was: passing
amf.0.1.2 on 4.04 is not available anymore. Previous state was: passing
amf.0.1.2 on 4.05 is not available anymore. Previous state was: passing
amf.0.1.2 on 4.06 is not available anymore. Previous state was: passing
amf.0.1.2 on 4.07 is not available anymore. Previous state was: passing
amqp-client-async.2.0.0 on 4.04 is not available anymore. Previous state was: failing
amqp-client-async.2.0.0 on 4.05 is not available anymore. Previous state was: failing
amqp-client-async.2.0.0 on 4.06 is not available anymore. Previous state was: failing
amqp-client-async.2.0.1 on 4.04 is not available anymore. Previous state was: failing
amqp-client-async.2.0.1 on 4.05 is not available anymore. Previous state was: failing
amqp-client-async.2.0.1 on 4.06 is not available anymore. Previous state was: failing
amqp-client-async.2.0.2 on 4.04 is not available anymore. Previous state was: passing
amqp-client-async.2.0.2 on 4.05 is not available anymore. Previous state was: passing
amqp-client-async.2.0.2 on 4.06 is not available anymore. Previous state was: passing
amqp-client-async.2.0.3 on 4.04 is not available anymore. Previous state was: passing
amqp-client-async.2.0.3 on 4.05 is not available anymore. Previous state was: passing
amqp-client-async.2.0.3 on 4.06 is not available anymore. Previous state was: passing
amqp-client-async.2.0.3 on 4.07 is not available anymore. Previous state was: passing
amqp-client-async.2.1.0 on 4.04 is not available anymore. Previous state was: passing
amqp-client-async.2.1.0 on 4.05 is not available anymore. Previous state was: passing
amqp-client-async.2.1.0 on 4.06 is not available anymore. Previous state was: passing
amqp-client-async.2.1.0 on 4.07 is not available anymore. Previous state was: passing
amqp-client-async.2.2.0 on 4.04 is not available anymore. Previous state was: passing
amqp-client-async.2.2.0 on 4.05 is not available anymore. Previous state was: passing
amqp-client-async.2.2.0 on 4.06 is not available anymore. Previous state was: passing
amqp-client-async.2.2.0 on 4.07 is not available anymore. Previous state was: passing
amqp-client-async.2.2.1 on 4.04 is not available anymore. Previous state was: passing
amqp-client-async.2.2.1 on 4.05 is not available anymore. Previous state was: passing
amqp-client-async.2.2.1 on 4.06 is not available anymore. Previous state was: passing
amqp-client-async.2.2.1 on 4.07 is not available anymore. Previous state was: passing
amqp-client-async.2.2.2 on 4.04 is not available anymore. Previous state was: passing
amqp-client-async.2.2.2 on 4.05 is not available anymore. Previous state was: passing
amqp-client-async.2.2.2 on 4.06 is not available anymore. Previous state was: passing
amqp-client-async.2.2.2 on 4.07 is not available anymore. Previous state was: passing
amqp-client-lwt.2.0.0 on 4.04 is not available anymore. Previous state was: failing
amqp-client-lwt.2.0.0 on 4.05 is not available anymore. Previous state was: failing
amqp-client-lwt.2.0.0 on 4.06 is not available anymore. Previous state was: failing
amqp-client-lwt.2.0.1 on 4.04 is not available anymore. Previous state was: failing
amqp-client-lwt.2.0.1 on 4.05 is not available anymore. Previous state was: failing
amqp-client-lwt.2.0.1 on 4.06 is not available anymore. Previous state was: failing
amqp-client-lwt.2.0.2 on 4.04 is not available anymore. Previous state was: passing
amqp-client-lwt.2.0.2 on 4.05 is not available anymore. Previous state was: passing
amqp-client-lwt.2.0.2 on 4.06 is not available anymore. Previous state was: passing
amqp-client-lwt.2.0.3 on 4.04 is not available anymore. Previous state was: passing
amqp-client-lwt.2.0.3 on 4.05 is not available anymore. Previous state was: passing
amqp-client-lwt.2.0.3 on 4.06 is not available anymore. Previous state was: passing
amqp-client-lwt.2.0.3 on 4.07 is not available anymore. Previous state was: passing
amqp-client-lwt.2.1.0 on 4.04 is not available anymore. Previous state was: passing
amqp-client-lwt.2.1.0 on 4.05 is not available anymore. Previous state was: passing
amqp-client-lwt.2.1.0 on 4.06 is not available anymore. Previous state was: passing
amqp-client-lwt.2.1.0 on 4.07 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.0 on 4.04 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.0 on 4.05 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.0 on 4.06 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.0 on 4.07 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.1 on 4.04 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.1 on 4.05 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.1 on 4.06 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.1 on 4.07 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.2 on 4.04 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.2 on 4.05 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.2 on 4.06 is not available anymore. Previous state was: passing
amqp-client-lwt.2.2.2 on 4.07 is not available anymore. Previous state was: passing
amqp-client.0.2.0 on 4.02 is not available anymore. Previous state was: failing
amqp-client.0.9.0 on 4.02 is not available anymore. Previous state was: passing
amqp-client.1.0.0 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.0.1 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.0.1 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.0.1 on 4.05 is not available anymore. Previous state was: failing
amqp-client.1.0.2 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.0.2 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.0.2 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.0.3 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.0.3 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.0.3 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.0.3 on 4.06 is not available anymore. Previous state was: passing
amqp-client.1.0.3 on 4.07 is not available anymore. Previous state was: passing
amqp-client.1.0.4 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.0.4 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.0.4 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.0.4 on 4.06 is not available anymore. Previous state was: passing
amqp-client.1.0.4 on 4.07 is not available anymore. Previous state was: passing
amqp-client.1.0.5 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.0.5 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.0.5 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.0.5 on 4.06 is not available anymore. Previous state was: passing
amqp-client.1.0.5 on 4.07 is not available anymore. Previous state was: passing
amqp-client.1.0.6 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.0.6 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.0.6 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.0.6 on 4.06 is not available anymore. Previous state was: passing
amqp-client.1.0.6 on 4.07 is not available anymore. Previous state was: passing
amqp-client.1.1.0 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.1.0 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.1.0 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.1.0 on 4.06 is not available anymore. Previous state was: passing
amqp-client.1.1.0 on 4.07 is not available anymore. Previous state was: passing
amqp-client.1.1.1 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.1.1 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.1.1 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.1.2 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.1.2 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.1.2 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.1.2 on 4.06 is not available anymore. Previous state was: passing
amqp-client.1.1.2 on 4.07 is not available anymore. Previous state was: passing
amqp-client.1.1.3 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.1.3 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.1.3 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.1.3 on 4.06 is not available anymore. Previous state was: passing
amqp-client.1.1.3 on 4.07 is not available anymore. Previous state was: passing
amqp-client.1.1.4 on 4.03 is not available anymore. Previous state was: passing
amqp-client.1.1.4 on 4.04 is not available anymore. Previous state was: passing
amqp-client.1.1.4 on 4.05 is not available anymore. Previous state was: passing
amqp-client.1.1.4 on 4.06 is not available anymore. Previous state was: passing
amqp-client.1.1.4 on 4.07 is not available anymore. Previous state was: passing
amqp-client.2.0.0 on 4.04 is not available anymore. Previous state was: passing
amqp-client.2.0.0 on 4.05 is not available anymore. Previous state was: passing
amqp-client.2.0.0 on 4.06 is not available anymore. Previous state was: passing
amqp-client.2.0.0 on 4.07 is not available anymore. Previous state was: passing
amqp-client.2.0.1 on 4.04 is not available anymore. Previous state was: passing
amqp-client.2.0.1 on 4.05 is not available anymore. Previous state was: passing
amqp-client.2.0.1 on 4.06 is not available anymore. Previous state was: passing
amqp-client.2.0.1 on 4.07 is not available anymore. Previous state was: passing
amqp-client.2.0.2 on 4.04 is not available anymore. Previous state was: passing
amqp-client.2.0.2 on 4.05 is not available anymore. Previous state was: passing
amqp-client.2.0.2 on 4.06 is not available anymore. Previous state was: passing
amqp-client.2.0.2 on 4.07 is not available anymore. Previous state was: passing
amqp-client.2.0.3 on 4.04 is not available anymore. Previous state was: passing
amqp-client.2.0.3 on 4.05 is not available anymore. Previous state was: passing
amqp-client.2.0.3 on 4.06 is not available anymore. Previous state was: passing
amqp-client.2.0.3 on 4.07 is not available anymore. Previous state was: passing
amqp-client.2.1.0 on 4.04 is not available anymore. Previous state was: passing
amqp-client.2.1.0 on 4.05 is not available anymore. Previous state was: passing
amqp-client.2.1.0 on 4.06 is not available anymore. Previous state was: passing
amqp-client.2.1.0 on 4.07 is not available anymore. Previous state was: passing
amqp-client.2.2.0 on 4.04 is not available anymore. Previous state was: passing
amqp-client.2.2.0 on 4.05 is not available anymore. Previous state was: passing
amqp-client.2.2.0 on 4.06 is not available anymore. Previous state was: passing
amqp-client.2.2.0 on 4.07 is not available anymore. Previous state was: passing
amqp-client.2.2.1 on 4.04 is not available anymore. Previous state was: passing
amqp-client.2.2.1 on 4.05 is not available anymore. Previous state was: passing
amqp-client.2.2.1 on 4.06 is not available anymore. Previous state was: passing
amqp-client.2.2.1 on 4.07 is not available anymore. Previous state was: passing
amqp-client.2.2.2 on 4.04 is not available anymore. Previous state was: passing
amqp-client.2.2.2 on 4.05 is not available anymore. Previous state was: passing
amqp-client.2.2.2 on 4.06 is not available anymore. Previous state was: passing
amqp-client.2.2.2 on 4.07 is not available anymore. Previous state was: passing
ancient.0.9.0 on 4.02 is not available anymore. Previous state was: internal failure
ancient.0.9.1 on 4.03 is not available anymore. Previous state was: passing
ancient.0.9.1 on 4.04 is not available anymore. Previous state was: passing
ancient.0.9.1 on 4.05 is not available anymore. Previous state was: passing
ancient.0.9.1 on 4.06 is not available anymore. Previous state was: passing
ancient.0.9.1 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.10.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-async.0.10.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.10.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.10.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.10.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.11.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-async.0.11.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.11.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.11.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.11.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.11.1 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.11.1 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.11.1 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.11.1 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.11.2 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.11.2 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.11.2 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.11.2 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.12.1 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.12.1 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.12.1 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.12.1 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.13.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.13.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.13.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.13.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.14.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.14.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.14.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.14.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.14.1 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.14.1 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.14.1 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.14.1 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.15.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.15.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.15.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.15.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.6.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-async.0.6.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.6.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.6.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.7.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-async.0.7.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.7.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.7.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.7.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.8.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-async.0.8.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.8.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.8.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.8.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.8.1 on 4.03 is not available anymore. Previous state was: passing
angstrom-async.0.8.1 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.8.1 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.8.1 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.8.1 on 4.07 is not available anymore. Previous state was: passing
angstrom-async.0.9.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-async.0.9.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-async.0.9.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-async.0.9.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-async.0.9.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.10.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.10.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.10.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.10.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.10.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.1 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.1 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.1 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.1 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.1 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.2 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.2 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.2 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.2 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.11.2 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.12.1 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.12.1 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.12.1 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.12.1 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.12.1 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.13.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.13.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.13.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.13.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.13.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.1 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.1 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.1 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.1 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.14.1 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.15.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.15.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.15.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.15.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.15.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.6.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.6.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.6.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.7.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.7.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.7.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.1 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.1 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.1 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.1 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.8.1 on 4.07 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.9.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.9.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.9.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.9.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-lwt-unix.0.9.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-unix.0.10.0 on 4.03 is not available anymore. Previous state was: passing
angstrom-unix.0.10.0 on 4.04 is not available anymore. Previous state was: passing
angstrom-unix.0.10.0 on 4.05 is not available anymore. Previous state was: passing
angstrom-unix.0.10.0 on 4.06 is not available anymore. Previous state was: passing
angstrom-unix.0.10.0 on 4.07 is not available anymore. Previous state was: passing
angstrom-unix.0.11.0 on 4.03 is not available anymore. Previous state was: