Home|Differences with the last checks|Previous runs

Differences between b1ed080 and 6ed4e23 (git diff)

Packages now failing:

• acgtk.1.5.1 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.14 had its build status changed: passing to 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
• alcotest-mirage.1.5.0 on 4.10 had its build status changed: passing to failing
• alcotest.0.8.3 on 4.10 had its build status changed: passing to failing
• algaeff.0.1.0 on 4.10 is now installable. Current state is: failing
• alsa.0.3.0 on 4.10 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.09 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.11 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.0.95.2 on 4.08 had its build status changed: passing to failing
• alt-ergo.0.95.2 on 4.10 had its build status changed: passing to 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.14 had its build status changed: passing to failing
• alt-ergo.2.0.0 on 4.08 had its build status changed: passing to failing
• alt-ergo.2.0.0 on 4.09 had its build status changed: passing to failing
• alt-ergo.2.0.0 on 4.10 had its build status changed: passing to failing
• alt-ergo.2.0.0 on 4.14 had its build status changed: passing to failing
• alt-ergo.2.1.0 on 4.09 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.2.0 on 4.08 had its build status changed: passing to failing
• alt-ergo.2.2.0 on 4.09 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.11 had its build status changed: passing to failing
• alt-ergo.2.2.0 on 4.12 had its build status changed: passing to failing
• b0.0.0.2 on 5.1 is now installable. Current state is: failing
• b0.0.0.3 on 5.1 is now installable. Current state is: failing
• b0.0.0.4 on 5.1 is now installable. Current state is: 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.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.14 is now installable. Current state is: failing
• batteries.3.6.0 on 5.1 is now installable. Current state is: failing
• biotk.0.2.0 on 4.14 is now installable. Current state is: failing
• bitmasks.1.4.0 on 5.1 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 4.08 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.11 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 4.12 had its build status changed: passing to failing
• bitwuzla-bin.0.0.0 on 5.0 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 5.1 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
• bonsai.v0.16.0 on 5.0 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.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.14 had its build status changed: not available to failing
• cca.0.4 on 4.11 had its build status changed: passing to failing
• cca.0.4 on 4.12 had its build status changed: passing to failing
• cca.0.4 on 4.14 had its build status changed: not available to 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.14 is now installable. Current state is: failing
• cca.0.6.2 on 4.14 is now installable. Current state is: failing
• cfstream.1.3.1 on 4.14 had its build status changed: not available to failing
• cfstream.1.3.2 on 4.14 is now installable. Current state is: failing
• cfstream.1.3.2 on 5.0 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
• cohttp-async.6.0.0~alpha1 on 4.14 is now installable. Current state is: failing
• cohttp-async.6.0.0~alpha1 on 5.0 is now installable. Current state is: failing
• cohttp-lwt-jsoo.2.1.3 on 4.08 had its build status changed: passing to failing
• combine.0.6 on 5.0 is now installable. Current state is: failing
• combine.0.6 on 5.1 is now installable. Current state is: failing
• conan.0.0.3 on 5.1 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-python-3-7.1.0.0 on 4.08 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.09 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.10 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.11 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.12 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.14 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 5.0 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 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.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.2 on 4.08 had its build status changed: passing to failing
• csvfields.v0.15.0 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.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.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.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
• 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
• docker-api.0.2 on 5.0 is now installable. Current state is: failing
• docker-api.0.2 on 5.1 is now installable. Current state is: failing
• docker-api.0.2.1 on 5.0 is now installable. Current state is: failing
• docker-api.0.2.1 on 5.1 is now installable. Current state is: failing
• docker-api.0.2.2 on 5.0 is now installable. Current state is: failing
• docker-api.0.2.2 on 5.1 is now installable. Current state is: failing
• dolmen.0.1 on 5.0 is now installable. Current state is: failing
• dolmen.0.1 on 5.1 is now installable. Current state is: failing
• dolmen.0.2 on 5.0 is now installable. Current state is: failing
• dolmen.0.2 on 5.1 is now installable. Current state is: failing
• domainslib.0.3.0 on 5.0 is now installable. Current state is: failing
• domainslib.0.3.0 on 5.1 is now installable. Current state is: failing
• domainslib.0.3.1 on 5.0 is now installable. Current state is: failing
• domainslib.0.3.1 on 5.1 is now installable. Current state is: failing
• domainslib.0.4.0 on 5.0 is now installable. Current state is: failing
• domainslib.0.4.0 on 5.1 is now installable. Current state is: failing
• domainslib.0.4.1 on 5.0 is now installable. Current state is: failing
• domainslib.0.4.1 on 5.1 is now installable. Current state is: failing
• duff.0.2 on 5.1 is now installable. Current state is: failing
• duff.0.3 on 5.1 is now installable. Current state is: failing
• duff.0.4 on 5.1 is now installable. Current state is: failing
• duff.0.5 on 5.1 is now installable. Current state is: 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
• 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
• errpy.0.0.8 on 4.08 is now installable. Current state is: failing
• errpy.0.0.8 on 4.09 is now installable. Current state is: failing
• errpy.0.0.8 on 4.10 is now installable. Current state is: failing
• errpy.0.0.8 on 4.11 is now installable. Current state is: failing
• errpy.0.0.8 on 4.12 is now installable. Current state is: failing
• errpy.0.0.8 on 4.14 is now installable. Current state is: failing
• errpy.0.0.8 on 5.0 is now installable. Current state is: failing
• extism-manifest.0.3.0 on 4.14 is now installable. Current state is: failing
• extism-manifest.0.3.0 on 5.0 is now installable. Current state is: failing
• facile.1.1 on 5.0 is now installable. Current state is: failing
• facile.1.1 on 5.1 is now installable. Current state is: failing
• fm-simplex-plugin.1.01 on 4.14 had its build status changed: passing to 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
• 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
• 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
• grenier.0.11 on 5.1 is now installable. Current state is: failing
• grenier.0.12 on 5.1 is now installable. Current state is: failing
• grenier.0.13 on 5.1 is now installable. Current state is: failing
• grenier.0.14 on 5.1 is now installable. Current state is: 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
• hevea.2.25 on 5.0 is now installable. Current state is: failing
• hevea.2.25 on 5.1 is now installable. Current state is: failing
• hevea.2.28 on 5.0 is now installable. Current state is: failing
• hevea.2.28 on 5.1 is now installable. Current state is: failing
• hevea.2.29 on 5.0 is now installable. Current state is: failing
• hevea.2.29 on 5.1 is now installable. Current state is: failing
• hevea.2.32 on 5.0 is now installable. Current state is: failing
• hevea.2.32 on 5.1 is now installable. Current state is: failing
• hevea.2.35 on 5.0 is now installable. Current state is: failing
• hevea.2.35 on 5.1 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.2.0 on 4.08 had its build status changed: passing to failing
• irmin-test.2.2.0 on 4.09 had its build status changed: passing to failing
• irmin-test.2.2.0 on 4.10 had its build status changed: passing to failing
• irmin-test.2.2.0 on 4.11 had its build status changed: passing to failing
• irmin-test.2.2.0 on 4.12 had its build status changed: passing to failing
• irmin-test.2.2.0 on 4.14 had its build status changed: passing to failing
• irmin-test.2.2.0 on 5.0 is now installable. Current state is: failing
• irmin-test.2.2.0 on 5.1 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
• js_of_ocaml-toplevel.3.4.0 on 4.08 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
• jupyter.2.8.2 on 4.14 is now installable. Current state is: failing
• kappa-library.4.1.0 on 4.08 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.09 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.10 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.11 had its build status changed: passing 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
• kind2.1.5.0 on 5.1 is now installable. Current state is: 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to failing
• labltk.8.06.11 on 4.14 had its build status changed: passing to 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
• libssh.0.1 on 4.14 had its build status changed: passing to failing
• lua-ml.0.9 on 5.0 is now installable. Current state is: failing
• lua-ml.0.9 on 5.1 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.14 had its build status changed: passing to 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
• 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 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+6 on 4.09 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.09 had its build status changed: passing to 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
• menhir.20220210 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.14 had its build status changed: passing to 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.08 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.14 had its build status changed: passing to 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.08 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.14 had its build status changed: passing to 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.08 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.14 had its build status changed: passing to 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.08 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.14 had its build status changed: passing to 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.08 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.14 had its build status changed: passing to 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.08 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.14 had its build status changed: passing to 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.08 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.14 had its build status changed: passing to 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.08 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.09 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.10 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.11 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.12 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.14 had its build status changed: passing to 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
• morbig.0.9 on 5.0 is now installable. Current state is: failing
• mosquitto.0.1-0 on 5.0 is now installable. Current state is: failing
• mosquitto.0.1-0 on 5.1 is now installable. Current state is: failing
• multicont.1.0.0~rc.1 on 5.0 is now installable. Current state is: failing
• multicont.1.0.0~rc.1 on 5.1 is now installable. Current state is: failing
• mysql8.1.0 on 4.14 had its build status changed: not available to failing
• mysql8.1.0 on 5.0 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
• 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
• 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 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 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-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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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 had its build status changed: passing to failing
• ocaml-r.0.5.0 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.5.0 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.5.0 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.5.0 on 4.12 had its build status changed: passing to failing
• ocaml-r.0.5.0 on 4.14 had its build status changed: passing to 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
• ocaml-twt.0.93 on 5.0 is now installable. Current state is: failing
• ocaml-twt.0.93 on 5.1 is now installable. Current state is: failing
• ocaml-twt.0.93.2 on 5.0 is now installable. Current state is: failing
• ocaml-twt.0.93.2 on 5.1 is now installable. Current state is: failing
• ocaml-twt.0.94.0 on 5.0 is now installable. Current state is: failing
• ocaml-twt.0.94.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.14 had its build status changed: passing to 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 4.08 had its build status changed: passing to failing
• ocamldsort.0.15.0 on 4.12 had its build status changed: passing to failing
• ocamldsort.0.16.0 on 4.08 had its build status changed: passing to failing
• ocamldsort.0.16.0 on 4.09 had its build status changed: passing to 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
• 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-index.1.3.3 on 5.1 is now installable. Current state is: failing
• ocp-index.1.3.4 on 5.1 is now installable. Current state is: 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
• ocplib-simplex.0.4 on 5.1 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 5.0 is now installable. Current state is: failing
• odepack.0.7 on 5.1 is now installable. Current state is: failing
• ogg.0.6.0 on 4.14 had its build status changed: passing to failing
• ogg.0.7.0 on 4.14 had its build status changed: passing to failing
• ogg.0.7.1 on 4.14 is now installable. Current state is: failing
• ogg.0.7.2 on 4.14 is now installable. Current state is: failing
• olinq.0.1 on 5.0 is now installable. Current state is: failing
• olinq.0.1 on 5.1 is now installable. Current state is: failing
• olinq.0.2 on 5.0 is now installable. Current state is: failing
• olinq.0.2 on 5.1 is now installable. Current state is: failing
• olinq.0.3 on 5.0 is now installable. Current state is: failing
• olinq.0.3 on 5.1 is now installable. Current state is: failing
• ollvm-tapir.0.99.1 on 4.09 had its build status changed: passing to failing
• ollvm-tapir.0.99.1 on 5.1 is now installable. Current state is: failing
• ollvm.0.99 on 4.08 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.14 had its build status changed: passing to failing
• ollvm.0.99 on 5.0 is now installable. Current state is: failing
• opam-depext.1.2.0 on 5.0 is now installable. Current state is: failing
• opam-depext.1.2.0 on 5.1 is now installable. Current state is: 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
• openai.0.0.1 on 4.14 is now installable. Current state is: failing
• openai.0.0.1 on 5.0 is now installable. Current state is: failing
• operf-micro.1.1.1 on 5.0 is now installable. Current state is: failing
• operf-micro.1.1.1 on 5.1 is now installable. Current state is: failing
• oplsr.8.0.1 on 4.14 had its build status changed: not available to failing
• oplsr.8.0.1 on 5.0 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.09 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.14 had its build status changed: passing to failing
• orun.0.0.1 on 5.0 is now installable. Current state is: failing
• orun.0.0.1 on 5.1 is now installable. Current state is: 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
• 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: passing 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: passing 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: passing 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: passing to failing
• pa_ppx_unique.0.07.02 on 4.12 had its build status changed: passing to 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
• 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.5 on 4.11 had its build status changed: passing to failing
• portia.1.5 on 5.0 is now installable. Current state is: failing
• ppx_pbt.0.2.1 on 4.10 had its build status changed: passing to failing
• ppx_pbt.0.2.1 on 4.11 had its build status changed: passing to failing
• ppx_pbt.0.2.1 on 4.12 had its build status changed: passing to 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
• profiler-plugin.1.01 on 4.11 had its build status changed: passing to failing
• profiler-plugin.1.01 on 4.14 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.1 on 5.0 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
• 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.14 had its build status changed: passing to failing
• randoml.0.1.5 on 5.0 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 had its build status changed: passing to 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
• rfsm.1.4.2 on 4.14 had its build status changed: not available to failing
• rfsm.1.5 on 4.14 had its build status changed: not available to failing
• rml.1.09.06 on 5.1 is now installable. Current state is: failing
• rml.1.09.07 on 5.1 is now installable. Current state is: failing
• rmlbuild.0.14.0-00 on 5.0 is now installable. Current state is: failing
• rmlbuild.0.14.0-00 on 5.1 is now installable. Current state is: 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
• 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
• satML-plugin.1.01 on 4.11 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.14 had its build status changed: passing to 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.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.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.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.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
• 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.14 had its build status changed: passing to failing
• stdcompat.16 on 4.08 had its build status changed: passing to failing
• stdcompat.16 on 4.09 had its build status changed: passing to failing
• stdcompat.16 on 4.10 had its build status changed: passing to failing
• stdcompat.16 on 4.11 had its build status changed: passing to failing
• stdcompat.16 on 4.12 had its build status changed: passing to failing
• stdcompat.16 on 4.14 had its build status changed: passing to failing
• stdcompat.17 on 4.08 had its build status changed: passing to failing
• stdcompat.17 on 4.09 had its build status changed: passing to failing
• stdcompat.17 on 4.10 had its build status changed: passing to failing
• stdcompat.17 on 4.11 had its build status changed: passing to failing
• stdcompat.17 on 4.12 had its build status changed: passing to failing
• stdcompat.17 on 4.14 had its build status changed: passing to 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.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 had its build status changed: passing to failing
• stog.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.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.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.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.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.14 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
• tezos-sapling.11.0 on 4.12 had its build status changed: passing to failing
• tezos-sapling.11.0 on 4.14 had its build status changed: not available to failing
• tezos-sapling.11.1 on 4.12 is now installable. Current state is: failing
• tezos-sapling.11.1 on 4.14 is now installable. Current state is: failing
• tezos-sapling.12.0 on 4.12 is now installable. Current state is: failing
• tezos-sapling.12.0 on 4.14 is now installable. Current state is: failing
• tezos-sapling.12.3 on 4.12 is now installable. Current state is: failing
• tezos-sapling.12.3 on 4.14 is now installable. Current state is: failing
• tezos-stdlib-unix.10.2 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.10.2 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.10.2 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.10.2 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.11 had its build status changed: passing to failing
• topiary.0.1.0 on 4.08 is now installable. Current state is: failing
• topiary.0.1.0 on 4.09 is now installable. Current state is: failing
• topiary.0.1.0 on 4.10 is now installable. Current state is: failing
• topiary.0.1.0 on 4.11 is now installable. Current state is: failing
• topiary.0.1.0 on 4.12 is now installable. Current state is: failing
• topiary.0.1.0 on 4.14 is now installable. Current state is: failing
• topiary.0.1.0 on 5.0 is now installable. Current state is: failing
• topiary.0.1.0 on 5.1 is now installable. Current state is: failing
• topiary.0.2.0 on 4.08 is now installable. Current state is: failing
• topiary.0.2.0 on 4.09 is now installable. Current state is: failing
• topiary.0.2.0 on 4.10 is now installable. Current state is: failing
• topiary.0.2.0 on 4.11 is now installable. Current state is: failing
• topiary.0.2.0 on 4.12 is now installable. Current state is: failing
• topiary.0.2.0 on 4.14 is now installable. Current state is: failing
• topiary.0.2.0 on 5.0 is now installable. Current state is: failing
• topiary.0.2.0 on 5.1 is now installable. Current state is: failing
• topiary.0.2.1 on 4.08 is now installable. Current state is: failing
• topiary.0.2.1 on 4.09 is now installable. Current state is: failing
• topiary.0.2.1 on 4.10 is now installable. Current state is: failing
• topiary.0.2.1 on 4.11 is now installable. Current state is: failing
• topiary.0.2.1 on 4.12 is now installable. Current state is: failing
• topiary.0.2.1 on 4.14 is now installable. Current state is: failing
• topiary.0.2.1 on 5.0 is now installable. Current state is: failing
• topiary.0.2.1 on 5.1 is now installable. Current state is: failing
• topiary.0.2.2 on 4.08 is now installable. Current state is: failing
• topiary.0.2.2 on 4.09 is now installable. Current state is: failing
• topiary.0.2.2 on 4.10 is now installable. Current state is: failing
• topiary.0.2.2 on 4.11 is now installable. Current state is: failing
• topiary.0.2.2 on 4.12 is now installable. Current state is: failing
• topiary.0.2.2 on 4.14 is now installable. Current state is: failing
• topiary.0.2.2 on 5.0 is now installable. Current state is: failing
• topiary.0.2.2 on 5.1 is now installable. Current state is: failing
• toplevel_expect_test.v0.15.0 on 5.0 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
• utop.2.10.0 on 5.1 is now installable. Current state is: failing
• utop.2.11.0 on 5.1 is now installable. Current state is: 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
• 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 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.09 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.10 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.11 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.12 had its build status changed: passing to failing
• wamp.0.1 on 4.08 had its build status changed: passing to failing
• wamp.0.1 on 4.09 had its build status changed: passing to failing
• wamp.0.1 on 4.10 had its build status changed: passing to failing
• wamp.0.1 on 4.11 had its build status changed: passing to failing
• wamp.0.1 on 4.12 had its build status changed: passing to failing
• wasm.2.0.0 on 5.0 is now installable. Current state is: failing
• wasm.2.0.0 on 5.1 is now installable. Current state is: failing
• wcs-lib.2017-05-26.05 on 4.08 had its build status changed: passing to failing
• wcs-lib.2017-05-26.05 on 4.09 had its build status changed: passing to failing
• wcs-lib.2017-05-26.05 on 4.10 had its build status changed: passing to failing
• wcs-lib.2017-05-26.05 on 4.11 had its build status changed: passing to failing
• wcs-lib.2017-05-26.05 on 4.12 had its build status changed: passing to failing
• xmldiff.0.6.0 on 5.0 is now installable. Current state is: 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.10.1 on 4.11 is now installable. Current state is: failing
• z3.4.11.0 on 4.11 is now installable. Current state is: failing
• z3.4.8.13 on 4.12 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
• z3.4.8.17 on 4.10 is now installable. Current state is: failing

Packages now partially failing:

• acp4.1.0.1 on 5.1 is now installable. Current state is: partially failing
• acpc.2.0.0 on 5.1 is now installable. Current state is: partially failing
• async_rpc_websocket.v0.16.0 on 4.14 is now installable. Current state is: partially failing
• async_rpc_websocket.v0.16.0 on 5.0 is now installable. Current state is: partially failing
• aws-async.1.2 on 4.14 had its build status changed: not available to partially failing
• aws-async.1.2 on 5.0 is now installable. Current state is: partially failing
• biocaml.0.11.0 on 4.14 had its build status changed: not available to partially failing
• biocaml.0.11.1 on 4.14 had its build status changed: not available to partially failing
• biocaml.0.11.2 on 4.14 is now installable. Current state is: partially failing
• bitcoin-cohttp-async.3.0 on 4.14 is now installable. Current state is: partially failing
• bitcoin-cohttp-async.3.0 on 5.0 is now installable. Current state is: partially failing
• bonsai.v0.16.0 on 4.14 is now installable. Current state is: partially failing
• bst.7.0.1 on 5.1 is now installable. Current state is: partially failing
• carton-git.0.4.4 on 5.1 is now installable. Current state is: partially failing
• carton-git.0.5.0 on 5.1 is now installable. Current state is: partially failing
• carton-git.0.6.0 on 5.1 is now installable. Current state is: partially failing
• carton-lwt.0.4.4 on 5.1 is now installable. Current state is: partially failing
• carton-lwt.0.5.0 on 5.1 is now installable. Current state is: partially failing
• carton-lwt.0.6.0 on 5.1 is now installable. Current state is: partially failing
• carton.0.4.4 on 5.1 is now installable. Current state is: partially failing
• carton.0.5.0 on 5.1 is now installable. Current state is: partially failing
• carton.0.6.0 on 5.1 is now installable. Current state is: 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
• cmon.0.1 on 5.1 is now installable. Current state is: partially failing
• cmon.0.2 on 5.1 is now installable. Current state is: partially failing
• cohttp_async_websocket.v0.16.0 on 4.14 is now installable. Current state is: partially failing
• cohttp_async_websocket.v0.16.0 on 5.0 is now installable. Current state is: partially failing
• cohttp_static_handler.v0.16.0 on 4.14 is now installable. Current state is: partially failing
• cohttp_static_handler.v0.16.0 on 5.0 is now installable. Current state is: partially failing
• conan-cli.0.0.3 on 5.1 is now installable. Current state is: partially failing
• conan-database.0.0.3 on 5.1 is now installable. Current state is: partially failing
• conan-lwt.0.0.3 on 5.1 is now installable. Current state is: partially failing
• conan-unix.0.0.3 on 5.1 is now installable. Current state is: partially failing
• cpm.12.1.2 on 5.1 is now installable. Current state is: partially failing
• cpm.12.2.0 on 5.1 is now installable. Current state is: partially failing
• daft.0.0.4 on 5.1 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 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.09 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.10 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.11 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.12 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.14 had its build status changed: not available to partially failing
• docteur-solo5.0.0.4 on 5.1 is now installable. Current state is: partially failing
• docteur-solo5.0.0.5 on 5.1 is now installable. Current state is: partially failing
• docteur-solo5.0.0.6 on 5.1 is now installable. Current state is: partially failing
• docteur-unix.0.0.5 on 5.1 is now installable. Current state is: partially failing
• docteur-unix.0.0.6 on 5.1 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.14 had its build status changed: not available to partially failing
• docteur.0.0.4 on 5.1 is now installable. Current state is: partially failing
• docteur.0.0.5 on 5.1 is now installable. Current state is: partially failing
• docteur.0.0.6 on 5.1 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
• extism.0.3.0 on 4.14 is now installable. Current state is: partially failing
• extism.0.3.0 on 5.0 is now installable. Current state is: partially failing
• fasmifra.1.0.0 on 5.1 is now installable. Current state is: partially failing
• fasmifra.1.1.0 on 5.1 is now installable. Current state is: partially failing
• fm-simplex-plugin.1.01 on 4.08 had its build status changed: passing to partially failing
• fm-simplex-plugin.1.01 on 4.09 had its build status changed: passing to partially failing
• fm-simplex-plugin.1.01 on 4.10 had its build status changed: passing to partially failing
• fm-simplex-plugin.1.01 on 4.11 had its build status changed: passing to partially failing
• fm-simplex-plugin.1.01 on 4.12 had its build status changed: passing to partially failing
• get_line.7.0.0 on 5.1 is now installable. Current state is: partially failing
• git-kv.0.0.1 on 5.1 is now installable. Current state is: partially failing
• git-kv.0.0.2 on 5.1 is now installable. Current state is: partially failing
• git-kv.0.0.3 on 5.1 is now installable. Current state is: partially failing
• git-mirage.3.13.0 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.10.0 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.10.1 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.11.0 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.12.0 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.13.0 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.9.1 on 5.1 is now installable. Current state is: partially failing
• git-unix.3.13.0 on 5.1 is now installable. Current state is: partially failing
• git.2.1.1 on 5.1 is now installable. Current state is: partially failing
• git.2.1.2 on 5.1 is now installable. Current state is: partially failing
• git.2.1.3 on 5.1 is now installable. Current state is: partially failing
• git.3.10.0 on 5.1 is now installable. Current state is: partially failing
• git.3.10.1 on 5.1 is now installable. Current state is: partially failing
• git.3.11.0 on 5.1 is now installable. Current state is: partially failing
• git.3.12.0 on 5.1 is now installable. Current state is: partially failing
• git.3.13.0 on 5.1 is now installable. Current state is: partially failing
• git.3.9.1 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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
• hts_shrink.2.1.2 on 5.1 is now installable. Current state is: partially failing
• influxdb-async.0.1.0 on 4.14 had its build status changed: not available to partially failing
• influxdb-async.0.1.0 on 5.0 is now installable. Current state is: partially failing
• influxdb-async.0.2.0 on 4.14 had its build status changed: not available to partially failing
• influxdb-async.0.2.0 on 5.0 is now installable. Current state is: partially failing
• influxdb-async.0.3.0 on 4.14 had its build status changed: not available to partially failing
• influxdb-async.0.3.0 on 5.0 is now installable. Current state is: partially failing
• inuit.0.1 on 5.1 is now installable. Current state is: partially failing
• inuit.0.2 on 5.1 is now installable. Current state is: partially failing
• inuit.0.3 on 5.1 is now installable. Current state is: 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-git.2.0.0 on 5.1 is now installable. Current state is: partially failing
• irmin-git.2.2.0 on 5.1 is now installable. Current state is: 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: passing to partially failing
• kappa-agents.4.1.0 on 4.09 had its build status changed: passing to partially failing
• kappa-agents.4.1.0 on 4.10 had its build status changed: passing to partially failing
• kappa-agents.4.1.0 on 4.11 had its build status changed: passing to partially failing
• kappa-binaries.4.1.0 on 4.08 had its build status changed: passing to partially failing
• kappa-binaries.4.1.0 on 4.09 had its build status changed: passing to partially failing
• kappa-binaries.4.1.0 on 4.10 had its build status changed: passing to partially failing
• kappa-binaries.4.1.0 on 4.11 had its build status changed: passing to partially failing
• kappa-server.4.1.0 on 4.08 had its build status changed: passing to partially failing
• kappa-server.4.1.0 on 4.09 had its build status changed: passing to partially failing
• kappa-server.4.1.0 on 4.10 had its build status changed: passing to partially failing
• kappa-server.4.1.0 on 4.11 had its build status changed: passing to partially failing
• lambdapi.2.0.0 on 4.08 is now installable. Current state is: partially failing
• lambdapi.2.0.0 on 4.11 is now installable. Current state is: partially failing
• lambdapi.2.0.0 on 4.12 is now installable. Current state is: partially failing
• lbvs_consent.2.1.1 on 4.14 had its build status changed: not available to partially failing
• lbvs_consent.2.1.2 on 4.14 had its build status changed: not available to partially failing
• lbvs_consent.2.1.3 on 5.0 is now installable. Current state is: partially failing
• lbvs_consent.2.2.0 on 5.0 is now installable. Current state is: partially failing
• line_oriented.1.0.0 on 5.1 is now installable. Current state is: partially failing
• line_oriented.1.2.0 on 5.1 is now installable. Current state is: partially failing
• line_oriented.1.3.0 on 5.1 is now installable. Current state is: partially failing
• magic-trace.1.0.1 on 4.14 is now installable. Current state is: partially failing
• magic-trace.1.0.1 on 5.0 is now installable. Current state is: partially failing
• markdown.0.2.1 on 5.1 is now installable. Current state is: partially failing
• memtrace_viewer.v0.16.0 on 4.14 is now installable. Current state is: partially failing
• memtrace_viewer.v0.16.0 on 5.0 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.14 had its build status changed: not available to partially failing
• metapp.0.4.1 on 4.08 had its build status changed: passing to partially failing
• metapp.0.4.1 on 4.09 had its build status changed: passing to partially failing
• metapp.0.4.1 on 4.10 had its build status changed: passing to partially failing
• metapp.0.4.1 on 4.11 had its build status changed: passing to partially failing
• metapp.0.4.1 on 4.12 had its build status changed: passing to partially failing
• metapp.0.4.1 on 4.14 had its build status changed: not available to partially failing
• metapp.0.4.2 on 4.08 had its build status changed: passing to partially failing
• metapp.0.4.2 on 4.09 had its build status changed: passing to partially failing
• metapp.0.4.2 on 4.10 had its build status changed: passing to partially failing
• metapp.0.4.2 on 4.11 had its build status changed: passing to partially failing
• metapp.0.4.2 on 4.12 had its build status changed: passing to partially failing
• metapp.0.4.2 on 4.14 had its build status changed: not available to 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.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 had its build status changed: passing to partially failing
• metaquot.0.5.0 on 4.09 had its build status changed: passing to partially failing
• metaquot.0.5.0 on 4.10 had its build status changed: passing to partially failing
• metaquot.0.5.0 on 4.11 had its build status changed: passing to partially failing
• metaquot.0.5.0 on 4.12 had its build status changed: passing to 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.14 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to partially failing
• mirage-console-xen-backend.5.0.0 on 4.08 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.09 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.10 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.11 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.12 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.14 had its build status changed: not available to 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.14 had its build status changed: not available to partially failing
• mirage-console-xen.5.0.0 on 4.08 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.09 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.10 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.11 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.12 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.14 had its build status changed: not available to 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.14 is now installable. Current state is: 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to partially failing
• mirage-solo5.0.6.5 on 4.08 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.09 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.10 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.11 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.12 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.14 had its build status changed: not available to 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.14 had its build status changed: not available to partially failing
• mirage-xen.6.0.1 on 4.08 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.09 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.10 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.11 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.12 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.14 had its build status changed: not available to partially failing
• morsmall.0.1 on 5.0 is now installable. Current state is: partially failing
• mutf8.0.1 on 5.1 is now installable. Current state is: partially failing
• mutf8.0.2 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.14 had its build status changed: not available to 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 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.09 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.10 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.11 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.12 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.08 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.09 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.10 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.11 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.12 had its build status changed: passing to 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.14 is now installable. Current state is: partially failing
• ocaml-in-python.0.1.0 on 4.14 is now installable. Current state is: partially failing
• ocaml-markdown.transition on 5.1 is now installable. Current state is: partially failing
• ocaml-option-address-sanitizer.1 on 5.1 is now installable. Current state is: partially failing
• ocaml-top.1.2.0 on 5.1 is now installable. Current state is: partially failing
• ocamlbrowser.4.14.0 on 4.14 is now installable. Current state is: partially failing
• odnnr.2.0.0 on 5.1 is now installable. Current state is: partially failing
• oplsr.2.0.0 on 5.1 is now installable. Current state is: partially failing
• oplsr.5.0.1 on 5.1 is now installable. Current state is: partially failing
• oplsr.8.0.1 on 5.1 is now installable. Current state is: partially failing
• oranger.2.0.1 on 5.1 is now installable. Current state is: partially failing
• oranger.2.0.2 on 5.1 is now installable. Current state is: partially failing
• oranger.2.0.4 on 5.1 is now installable. Current state is: partially failing
• orrandomForest.3.0.0 on 5.1 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 had its build status changed: passing to partially failing
• override.0.4.0 on 4.09 had its build status changed: passing to partially failing
• override.0.4.0 on 4.10 had its build status changed: passing to partially failing
• override.0.4.0 on 4.11 had its build status changed: passing to partially failing
• override.0.4.0 on 4.12 had its build status changed: passing to partially failing
• owl-jupyter.1.0 on 4.14 had its build status changed: not available to 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.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
• pardi.2.0.4 on 5.1 is now installable. Current state is: partially failing
• pardi.3.1.1 on 5.1 is now installable. Current state is: partially failing
• pardi.3.2.0 on 5.1 is now installable. Current state is: partially failing
• pardi.3.2.2 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
• pb-plugin.1.0.0 on 5.1 is now installable. Current state is: partially failing
• phylogenetics.0.2.0 on 4.14 is now installable. Current state is: partially failing
• portia.1.1 on 5.1 is now installable. Current state is: partially failing
• portia.1.3 on 5.1 is now installable. Current state is: partially failing
• portia.1.5 on 5.1 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
• profiler-plugin.1.01 on 4.09 had its build status changed: passing to 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.1 on 5.0 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
• 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
• 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.0.99.1 on 4.08 had its build status changed: passing to partially failing
• satML-plugin.0.99.1 on 4.09 had its build status changed: passing to partially failing
• satML-plugin.0.99.1 on 4.10 had its build status changed: passing to partially failing
• satML-plugin.0.99.1 on 4.11 had its build status changed: passing to partially failing
• satML-plugin.0.99.1 on 4.12 had its build status changed: passing to partially failing
• satML-plugin.0.99.1 on 4.14 had its build status changed: passing to partially failing
• satML-plugin.1.01 on 4.08 had its build status changed: passing to partially failing
• satML-plugin.1.01 on 4.10 had its build status changed: passing to partially failing
• session-cohttp-async.0.4.0 on 4.14 had its build status changed: not available to partially failing
• session-cohttp-async.0.4.1 on 4.14 had its build status changed: not available to partially failing
• session-cohttp-async.0.4.1 on 5.0 is now installable. Current state is: partially failing
• session-cohttp-async.0.5.0 on 4.14 had its build status changed: not available to partially failing
• session-cohttp-async.0.5.0 on 5.0 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.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.09 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
• spirv.1.1.1 on 5.1 is now installable. Current state is: partially failing
• spirv.1.1.2 on 5.1 is now installable. Current state is: partially failing
• stog-writing.0.19.0 on 4.12 had its build status changed: passing to partially failing
• stog_all.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_asy.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_dot.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_extern.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_markdown.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_multi_doc.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_nocaml.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_noexec.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_plugins.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_rdf.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_rel_href.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_server.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
• stog_sitemap.0.20.0 on 4.12 is now installable. Current state is: partially failing
• stog_writing.0.20.0 on 4.12 is now installable. Current state is: partially failing
• sturgeon.0.1 on 5.1 is now installable. Current state is: partially failing
• sturgeon.0.2 on 5.1 is now installable. Current state is: partially failing
• sturgeon.0.3 on 5.1 is now installable. Current state is: partially failing
• sturgeon.0.4 on 5.1 is now installable. Current state is: partially failing
• sturgeon.0.4.2 on 5.1 is now installable. Current state is: partially failing
• tezos-base.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-base.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-base.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-base.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-base.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-base.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-base.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-base.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-base.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-base.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-base.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-base.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base.11.0 on 4.12 had its build status changed: passing to partially failing
• tezos-client-base.11.0 on 4.14 had its build status changed: not available to partially failing
• tezos-client-base.11.1 on 4.12 is now installable. Current state is: partially failing
• tezos-client-base.11.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-base.12.0 on 4.12 is now installable. Current state is: partially failing
• tezos-client-base.12.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-base.12.3 on 4.12 is now installable. Current state is: partially failing
• tezos-client-base.12.3 on 4.14 is now installable. Current state is: partially failing
• tezos-client-commands.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-client-commands.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-commands.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-commands.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-client-commands.11.0 on 4.12 had its build status changed: passing to partially failing
• tezos-client-commands.11.0 on 4.14 had its build status changed: not available to partially failing
• tezos-client-commands.11.1 on 4.12 is now installable. Current state is: partially failing
• tezos-client-commands.11.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-commands.12.0 on 4.12 is now installable. Current state is: partially failing
• tezos-client-commands.12.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-commands.12.3 on 4.12 is now installable. Current state is: partially failing
• tezos-client-commands.12.3 on 4.14 is now installable. Current state is: partially failing
• tezos-crypto.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-environment-structs.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-requester.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-requester.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-requester.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-requester.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-requester.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-requester.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-requester.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-requester.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-requester.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-requester.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-requester.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-requester.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http-client-unix.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http-client.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http-client.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http-client.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http-client.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http-client.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http-client.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http-client.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http-client.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http-client.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http-client.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http-client.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http-client.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http-server.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http-server.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http-server.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http-server.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http-server.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http-server.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http-server.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http-server.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http-server.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http-server.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http-server.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http-server.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-rpc-http.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-rpc-http.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-rpc-http.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-rpc-http.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-sapling.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-sapling.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-sapling.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-sapling.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-sapling.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-sapling.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-sapling.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-sapling.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-sapling.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-sapling.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-sapling.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-sapling.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-shell-services.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-shell-services.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-shell-services.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-shell-services.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-shell-services.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-shell-services.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-shell-services.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-shell-services.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-shell-services.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-shell-services.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-shell-services.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-shell-services.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-signer-backends.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-signer-backends.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-signer-backends.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-signer-backends.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-signer-backends.11.0 on 4.12 had its build status changed: passing to partially failing
• tezos-signer-backends.11.0 on 4.14 had its build status changed: not available to partially failing
• tezos-signer-backends.11.1 on 4.12 is now installable. Current state is: partially failing
• tezos-signer-backends.11.1 on 4.14 is now installable. Current state is: partially failing
• tezos-signer-backends.12.0 on 4.12 is now installable. Current state is: partially failing
• tezos-signer-backends.12.0 on 4.14 is now installable. Current state is: partially failing
• tezos-signer-backends.12.3 on 4.12 is now installable. Current state is: partially failing
• tezos-signer-backends.12.3 on 4.14 is now installable. Current state is: partially failing
• tezos-signer-services.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-signer-services.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-signer-services.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-signer-services.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-signer-services.11.0 on 4.12 had its build status changed: passing to partially failing
• tezos-signer-services.11.0 on 4.14 had its build status changed: not available to partially failing
• tezos-signer-services.11.1 on 4.12 is now installable. Current state is: partially failing
• tezos-signer-services.11.1 on 4.14 is now installable. Current state is: partially failing
• tezos-signer-services.12.0 on 4.12 is now installable. Current state is: partially failing
• tezos-signer-services.12.0 on 4.14 is now installable. Current state is: partially failing
• tezos-signer-services.12.3 on 4.12 is now installable. Current state is: partially failing
• tezos-signer-services.12.3 on 4.14 is now installable. Current state is: partially failing
• tezos-test-services.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-test-services.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-test-services.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-test-services.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-test-services.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-test-services.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-test-services.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-test-services.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-test-services.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-test-services.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-test-services.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-test-services.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-version.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-version.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-version.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-version.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-version.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-version.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-version.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-version.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-version.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-version.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-version.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-version.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-workers.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-workers.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-workers.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-workers.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-workers.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-workers.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-workers.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-workers.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-workers.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-workers.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-workers.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-workers.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos.7.0 on 4.09 had its build status changed: passing to partially failing
• tezos.7.1 on 4.09 had its build status changed: passing to partially failing
• tezos.7.2 on 4.09 had its build status changed: passing to partially failing
• tezos.7.3 on 4.09 had its build status changed: passing to partially failing
• tezos.7.4 on 4.09 had its build status changed: passing to partially failing
• tezos.9.1 on 4.10 had its build status changed: passing to 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
• 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.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
• vcardgen.1.2 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.14 had its build status changed: not available to partially failing
• vhd-format-lwt.0.12.1 on 4.08 had its build status changed: passing to partially failing
• vhd-format-lwt.0.12.1 on 4.09 had its build status changed: passing to partially failing
• vhd-format-lwt.0.12.1 on 4.10 had its build status changed: passing to partially failing
• vhd-format-lwt.0.12.1 on 4.11 had its build status changed: passing to partially failing
• vhd-format-lwt.0.12.1 on 4.12 had its build status changed: passing to partially failing
• vhd-format-lwt.0.12.2 on 4.08 had its build status changed: passing to partially failing
• vhd-format-lwt.0.12.2 on 4.09 had its build status changed: passing to partially failing
• vhd-format-lwt.0.12.2 on 4.10 had its build status changed: passing to partially failing
• vhd-format-lwt.0.12.2 on 4.11 had its build status changed: passing to partially failing
• vhd-format-lwt.0.12.2 on 4.12 had its build status changed: passing to partially failing
• wall.0.4 on 5.1 is now installable. Current state is: partially failing
• wall.0.4.1 on 5.1 is now installable. Current state is: partially failing
• wcs.2017-05-26.05 on 4.08 had its build status changed: passing to partially failing
• wcs.2017-05-26.05 on 4.09 had its build status changed: passing to partially failing
• wcs.2017-05-26.05 on 4.10 had its build status changed: passing to partially failing
• wcs.2017-05-26.05 on 4.11 had its build status changed: passing to partially failing
• wcs.2017-05-26.05 on 4.12 had its build status changed: passing to partially failing
• why3-coq.1.0.0 on 4.08 had its build status changed: passing to partially failing
• why3-coq.1.1.0 on 4.08 had its build status changed: passing to partially failing
• why3-coq.1.1.1 on 4.08 had its build status changed: passing to partially failing
• why3-coq.1.2.0 on 4.08 had its build status changed: passing to partially failing
• why3-coq.1.2.1 on 4.08 had its build status changed: passing to partially failing
• why3-coq.1.2.1 on 4.09 had its build status changed: passing to partially failing
• why3-coq.1.3.0 on 4.08 had its build status changed: passing to partially failing
• why3-coq.1.3.0 on 4.09 had its build status changed: passing to partially failing
• why3-coq.1.3.0 on 4.10 had its build status changed: passing to partially failing
• why3-coq.1.3.0 on 4.11 had its build status changed: passing to partially failing
• why3-coq.1.3.1 on 4.08 had its build status changed: passing to partially failing
• why3-coq.1.3.1 on 4.09 had its build status changed: passing to partially failing
• why3-coq.1.3.1 on 4.10 had its build status changed: passing to partially failing
• why3-coq.1.3.1 on 4.11 had its build status changed: passing to partially failing
• why3-coq.1.3.2 on 4.08 had its build status changed: passing to partially failing
• why3-coq.1.3.2 on 4.09 had its build status changed: passing to partially failing
• why3-coq.1.3.2 on 4.10 had its build status changed: passing to partially failing
• why3-coq.1.3.2 on 4.11 had its build status changed: passing to partially failing
• why3-coq.1.3.3 on 4.08 had its build status changed: passing to partially failing
• why3-coq.1.3.3 on 4.09 had its build status changed: passing to partially failing
• why3-coq.1.3.3 on 4.10 had its build status changed: passing to partially failing
• why3-coq.1.3.3 on 4.11 had its build status changed: passing to partially failing
• z3_tptp.4.10.1 on 4.11 is now installable. Current state is: partially failing
• z3_tptp.4.11.2 on 5.1 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
• z3_tptp.4.8.17 on 4.09 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to 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.14 had its build status changed: not available to partially failing
• zelus-gtk.2.1 on 4.12 had its build status changed: passing to partially failing
• zelus.2.2 on 4.09 had its build status changed: passing to partially failing
• zipperposition-tools.2.1 on 4.11 had its build status changed: passing to partially failing