Home|Differences with the last checks|Previous runs

Differences between b1ed080 and a4349cb (git diff)

Packages now failing:

• advi.2.0.0 on 4.14 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.08 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.09 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.10 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.11 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.12 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.13 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 4.14 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
• alt-ergo-free.2.0.0 on 4.08 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.09 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.10 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.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-free.2.0.0 on 4.13 had its build status changed: passing to failing
• alt-ergo-free.2.0.0 on 4.14 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.0 on 4.08 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.0 on 4.09 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.0 on 4.10 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.0 on 4.11 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.0 on 4.12 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.0 on 4.13 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.0 on 4.14 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.1 on 4.08 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.1 on 4.09 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.1 on 4.10 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.1 on 4.11 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.1 on 4.12 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.1 on 4.13 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.1 on 4.14 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.2 on 4.08 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.2 on 4.09 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.2 on 4.10 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.2 on 4.11 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.2 on 4.12 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.2 on 4.13 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.2 on 4.14 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.3 on 4.08 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.3 on 4.09 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.3 on 4.10 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.3 on 4.11 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.3 on 4.12 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.3 on 4.13 had its build status changed: passing to failing
• alt-ergo-parsers.2.3.3 on 4.14 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.0 on 4.08 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.0 on 4.09 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.0 on 4.10 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.0 on 4.11 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.0 on 4.12 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.0 on 4.13 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.0 on 4.14 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.1 on 4.08 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.1 on 4.09 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.1 on 4.10 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.1 on 4.11 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.1 on 4.12 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.1 on 4.13 had its build status changed: passing to failing
• alt-ergo-parsers.2.4.1 on 4.14 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.13 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.12 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.10 had its build status changed: passing to failing
• alt-ergo.2.1.0 on 4.11 had its build status changed: passing to failing
• alt-ergo.2.1.0 on 4.12 had its build status changed: passing to failing
• alt-ergo.2.1.0 on 4.13 had its build status changed: passing to failing
• alt-ergo.2.2.0 on 4.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.11 had its build status changed: passing to failing
• alt-ergo.2.2.0 on 4.14 had its build status changed: passing to failing
• aws-s3-lwt.4.2.0 on 4.08 had its build status changed: passing to failing
• aws-s3-lwt.4.2.0 on 4.09 had its build status changed: passing to failing
• aws-s3-lwt.4.3.0 on 4.08 had its build status changed: passing to failing
• aws-s3-lwt.4.3.0 on 4.09 had its build status changed: passing to failing
• balancer.1.0 on 4.08 had its build status changed: passing to failing
• balancer.1.0 on 4.09 had its build status changed: passing to failing
• balancer.1.0 on 4.10 had its build status changed: passing to failing
• balancer.1.0 on 4.11 had its build status changed: passing to failing
• balancer.1.0 on 4.12 had its build status changed: passing to failing
• balancer.1.0 on 4.13 had its build status changed: passing to failing
• balancer.1.0 on 4.14 had its build status changed: passing to failing
• bap-ghidra.2.4.0 on 4.08 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.09 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.10 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.11 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.12 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.13 is now installable. Current state is: failing
• bap-ghidra.2.4.0 on 4.14 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.08 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.09 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.10 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.11 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.12 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.13 is now installable. Current state is: failing
• bap-ghidra.2.5.0 on 4.14 is now installable. Current state is: failing
• beluga.1.0 on 4.08 had its build status changed: passing to failing
• beluga.1.0 on 4.09 had its build status changed: passing to failing
• beluga.1.0 on 4.10 had its build status changed: passing to failing
• beluga.1.0 on 4.11 had its build status changed: passing to failing
• beluga.1.0 on 4.12 had its build status changed: passing to failing
• beluga.1.0 on 4.13 had its build status changed: passing to failing
• beluga.1.0 on 4.14 had its build status changed: not available to failing
• beluga.1.1 on 4.14 is now installable. Current state is: failing
• beluga.1.1 on 5.0 is now installable. Current state is: failing
• beluga.1.1 on 5.1 is now installable. Current state is: failing
• beluga.1.1.1 on 4.14 is now installable. Current state is: failing
• beluga.1.1.1 on 5.0 is now installable. Current state is: failing
• beluga.1.1.1 on 5.1 is now installable. Current state is: failing
• binaryen.0.1.0 on 4.08 had its build status changed: passing to failing
• binaryen.0.1.0 on 4.09 had its build status changed: passing to failing
• binaryen.0.1.0 on 4.10 had its build status changed: passing to failing
• binaryen.0.1.0 on 4.11 had its build status changed: passing to failing
• binaryen.0.1.0 on 4.12 had its build status changed: passing to failing
• binaryen.0.1.0 on 4.13 had its build status changed: passing to failing
• binaryen.0.1.0 on 4.14 had its build status changed: passing to failing
• binaryen.0.1.0 on 5.0 is now installable. Current state is: failing
• binaryen.0.1.0 on 5.1 is now installable. Current state is: failing
• binaryen.0.2.1 on 4.08 had its build status changed: passing to failing
• binaryen.0.2.1 on 4.09 had its build status changed: passing to failing
• binaryen.0.2.1 on 4.10 had its build status changed: passing to failing
• binaryen.0.2.1 on 4.11 had its build status changed: passing to failing
• binaryen.0.2.1 on 4.12 had its build status changed: passing to failing
• binaryen.0.2.1 on 4.13 had its build status changed: passing to failing
• binaryen.0.2.1 on 4.14 had its build status changed: passing to failing
• binaryen.0.2.1 on 5.0 is now installable. Current state is: failing
• binaryen.0.2.1 on 5.1 is now installable. Current state is: failing
• binaryen.0.2.2 on 4.08 had its build status changed: passing to failing
• binaryen.0.2.2 on 4.09 had its build status changed: passing to failing
• binaryen.0.2.2 on 4.10 had its build status changed: passing to failing
• binaryen.0.2.2 on 4.11 had its build status changed: passing to failing
• binaryen.0.2.2 on 4.12 had its build status changed: passing to failing
• binaryen.0.2.2 on 4.13 had its build status changed: passing to failing
• binaryen.0.2.2 on 4.14 had its build status changed: passing to failing
• binaryen.0.2.2 on 5.0 is now installable. Current state is: failing
• binaryen.0.2.2 on 5.1 is now installable. Current state is: failing
• binaryen.0.2.3 on 4.08 had its build status changed: passing to failing
• binaryen.0.2.3 on 4.09 had its build status changed: passing to failing
• binaryen.0.2.3 on 4.10 had its build status changed: passing to failing
• binaryen.0.2.3 on 4.11 had its build status changed: passing to failing
• binaryen.0.2.3 on 4.12 had its build status changed: passing to failing
• binaryen.0.2.3 on 4.13 had its build status changed: passing to failing
• binaryen.0.2.3 on 4.14 had its build status changed: passing to failing
• binaryen.0.2.3 on 5.0 is now installable. Current state is: failing
• binaryen.0.2.3 on 5.1 is now installable. Current state is: failing
• binaryen.0.3.0 on 4.08 had its build status changed: passing to failing
• binaryen.0.3.0 on 4.09 had its build status changed: passing to failing
• binaryen.0.3.0 on 4.10 had its build status changed: passing to failing
• binaryen.0.3.0 on 4.11 had its build status changed: passing to failing
• bitmasks.1.4.0 on 5.1 is now installable. Current state is: failing
• bitwuzla-bin.1.0.0 on 4.08 had its build status changed: passing to failing
• bitwuzla-bin.1.0.0 on 4.09 had its build status changed: passing to failing
• bitwuzla-bin.1.0.0 on 4.10 had its build status changed: passing to failing
• bitwuzla-bin.1.0.0 on 4.11 had its build status changed: passing to failing
• bitwuzla-bin.1.0.0 on 4.12 had its build status changed: passing to failing
• bitwuzla-bin.1.0.0 on 4.13 had its build status changed: passing to failing
• bitwuzla-bin.1.0.0 on 4.14 had its build status changed: passing to failing
• bitwuzla-bin.1.0.0 on 5.0 is now installable. Current state is: failing
• bitwuzla-bin.1.0.0 on 5.1 is now installable. Current state is: failing
• bitwuzla.1.0.0 on 4.08 had its build status changed: passing to failing
• bitwuzla.1.0.0 on 4.09 had its build status changed: passing to failing
• bitwuzla.1.0.0 on 4.10 had its build status changed: passing to failing
• bitwuzla.1.0.0 on 4.11 had its build status changed: passing to failing
• bitwuzla.1.0.0 on 4.12 had its build status changed: passing to failing
• bitwuzla.1.0.0 on 4.13 had its build status changed: passing to failing
• bitwuzla.1.0.0 on 4.14 had its build status changed: passing to failing
• bitwuzla.1.0.0 on 5.0 is now installable. Current state is: failing
• bitwuzla.1.0.0 on 5.1 is now installable. Current state is: failing
• bitwuzla.1.0.1 on 4.08 is now installable. Current state is: failing
• bitwuzla.1.0.1 on 4.09 is now installable. Current state is: failing
• bitwuzla.1.0.1 on 4.10 is now installable. Current state is: failing
• bitwuzla.1.0.1 on 4.11 is now installable. Current state is: failing
• bitwuzla.1.0.1 on 4.12 is now installable. Current state is: failing
• bitwuzla.1.0.1 on 4.13 is now installable. Current state is: failing
• bitwuzla.1.0.1 on 4.14 is now installable. Current state is: failing
• bitwuzla.1.0.1 on 5.0 is now installable. Current state is: failing
• bitwuzla.1.0.1 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
• boltzgen.0.9 on 5.0 is now installable. Current state is: failing
• boltzgen.0.9 on 5.1 is now installable. Current state is: failing
• boltzgen.0.9.2 on 5.0 is now installable. Current state is: failing
• boltzgen.0.9.2 on 5.1 is now installable. Current state is: failing
• boltzgen.0.9.3 on 5.0 is now installable. Current state is: failing
• boltzgen.0.9.3 on 5.1 is now installable. Current state is: 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
• camlp4.4.08+1 on 4.08 had its build status changed: passing to failing
• camlp4.4.09+1 on 4.09 had its build status changed: passing to failing
• camlp4.4.10+1 on 4.10 had its build status changed: passing to failing
• camlp4.4.11+1 on 4.11 had its build status changed: passing to failing
• camlp4.4.12+1 on 4.12 had its build status changed: passing to failing
• camlp4.4.13+1 on 4.13 had its build status changed: passing to failing
• camlp4.4.14+1 on 4.14 is now installable. Current state is: failing
• camlp4.5.0 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-lwt-jsoo.2.1.3 on 4.08 had its build status changed: passing to failing
• cohttp-lwt.1.0.0 on 4.08 had its build status changed: passing to failing
• cohttp-lwt.1.0.0 on 4.09 had its build status changed: passing to failing
• cohttp-lwt.1.0.0 on 4.10 had its build status changed: passing to failing
• cohttp-lwt.1.0.0 on 4.11 had its build status changed: passing to failing
• cohttp-lwt.1.0.0 on 4.12 had its build status changed: passing to failing
• conex-mirage-crypto.0.11.1 on 4.08 had its build status changed: passing to failing
• conex-mirage-crypto.0.11.1 on 4.09 had its build status changed: passing to failing
• conex-mirage-crypto.0.11.1 on 4.10 had its build status changed: passing to failing
• conex-mirage-crypto.0.11.1 on 4.11 had its build status changed: passing to failing
• conex-mirage-crypto.0.11.1 on 4.12 had its build status changed: passing to failing
• conex-mirage-crypto.0.11.1 on 4.13 had its build status changed: passing to failing
• conex-mirage-crypto.0.11.1 on 4.14 had its build status changed: passing to failing
• conex-mirage-crypto.0.11.1 on 5.0 is now installable. Current state is: failing
• conex-mirage-crypto.0.11.1 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-libclang.15 on 4.08 is now installable. Current state is: failing
• conf-libclang.15 on 4.09 is now installable. Current state is: failing
• conf-libclang.15 on 4.10 is now installable. Current state is: failing
• conf-libclang.15 on 4.11 is now installable. Current state is: failing
• conf-libclang.15 on 4.12 is now installable. Current state is: failing
• conf-libclang.15 on 4.13 is now installable. Current state is: failing
• conf-libclang.15 on 4.14 is now installable. Current state is: failing
• conf-libclang.15 on 5.0 is now installable. Current state is: failing
• conf-libclang.15 on 5.1 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.08 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.09 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.10 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.11 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.12 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.13 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.14 is now installable. Current state is: failing
• conf-trexio.0.1 on 5.0 is now installable. Current state is: failing
• conf-trexio.0.1 on 5.1 is now installable. Current state is: failing
• cppffigen.0.002 on 4.12 is now installable. Current state is: failing
• cppffigen.0.002 on 4.13 is now installable. Current state is: failing
• cppffigen.0.002 on 4.14 is now installable. Current state is: failing
• cppffigen.0.002 on 5.0 is now installable. Current state is: failing
• cppffigen.0.002 on 5.1 is now installable. Current state is: failing
• datakit-client-9p.0.12.0 on 4.12 had its build status changed: passing to failing
• datakit-client-9p.0.12.0 on 4.13 had its build status changed: 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.2 on 4.13 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.0.12.3 on 4.13 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
• datakit-client-9p.1.0.0 on 4.13 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
• dedukti.2.6.0 on 4.08 had its build status changed: passing to failing
• dedukti.2.6.0 on 4.09 had its build status changed: passing to failing
• dedukti.2.6.0 on 4.10 had its build status changed: passing to failing
• dedukti.2.6.0 on 4.11 had its build status changed: passing to failing
• dedukti.2.6.0 on 4.12 had its build status changed: passing to failing
• dedukti.2.6.0 on 4.13 had its build status changed: passing to failing
• dedukti.2.6.0 on 4.14 had its build status changed: passing to failing
• dedukti.2.6.0 on 5.0 is now installable. Current state is: failing
• dedukti.2.6.0 on 5.1 is now installable. Current state is: 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
• 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
• eliom.8.4.8 on 4.08 had its build status changed: passing to failing
• eliom.8.4.8 on 4.09 had its build status changed: passing to failing
• eliom.8.4.8 on 4.10 had its build status changed: passing to failing
• eliom.8.4.8 on 4.11 had its build status changed: passing to failing
• eliom.8.4.8 on 4.12 had its build status changed: passing to failing
• eliom.8.6.0 on 4.08 had its build status changed: passing to failing
• eliom.8.6.0 on 4.09 had its build status changed: passing to failing
• eliom.8.6.0 on 4.10 had its build status changed: passing to failing
• eliom.8.6.0 on 4.11 had its build status changed: passing to failing
• eliom.8.8.0 on 4.08 had its build status changed: passing to failing
• eliom.8.8.0 on 4.09 had its build status changed: passing to failing
• eliom.8.8.0 on 4.10 had its build status changed: passing to failing
• eliom.8.8.0 on 4.11 had its build status changed: passing to failing
• eliom.8.8.0 on 4.12 had its build status changed: passing to failing
• eliom.8.8.1 on 4.08 had its build status changed: passing to failing
• eliom.8.8.1 on 4.09 had its build status changed: passing to failing
• eliom.8.8.1 on 4.10 had its build status changed: passing to failing
• eliom.8.8.1 on 4.11 had its build status changed: passing to failing
• eliom.8.8.1 on 4.12 had its build status changed: passing to failing
• errpy.0.0.7 on 5.1 is now installable. Current state is: failing
• errpy.0.0.8 on 5.1 is now installable. Current state is: failing
• errpy.0.0.9 on 5.1 is now installable. Current state is: failing
• frenetic.5.0.5 on 4.11 had its build status changed: passing to failing
• frenetic.5.0.5 on 4.12 had its build status changed: passing to failing
• frenetic.5.0.5 on 4.13 had its build status changed: passing to failing
• frenetic.5.0.5 on 4.14 had its build status changed: not available 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
• gpx.1.0 on 4.08 had its build status changed: passing to failing
• gpx.1.0 on 4.09 had its build status changed: passing to failing
• gpx.1.0 on 4.10 had its build status changed: passing to failing
• gpx.1.0 on 4.11 had its build status changed: passing to failing
• gpx.1.0 on 4.12 had its build status changed: passing to failing
• gpx.1.0 on 4.13 had its build status changed: passing to failing
• gpx.1.0 on 4.14 had its build status changed: passing to failing
• gpx.1.0 on 5.0 is now installable. Current state is: failing
• gpx.1.0 on 5.1 is now installable. Current state is: failing
• gpx.1.0.1 on 4.08 had its build status changed: passing to failing
• gpx.1.0.1 on 4.09 had its build status changed: passing to failing
• gpx.1.0.1 on 4.10 had its build status changed: passing to failing
• gpx.1.0.1 on 4.11 had its build status changed: passing to failing
• gpx.1.0.1 on 4.12 had its build status changed: passing to failing
• gpx.1.0.1 on 4.13 had its build status changed: passing to failing
• gpx.1.0.1 on 4.14 had its build status changed: passing to failing
• gpx.1.0.1 on 5.0 is now installable. Current state is: failing
• gpx.1.0.1 on 5.1 is now installable. Current state is: failing
• gpx.1.0.2 on 4.08 had its build status changed: passing to failing
• gpx.1.0.2 on 4.09 had its build status changed: passing to failing
• gpx.1.0.2 on 4.10 had its build status changed: passing to failing
• gpx.1.0.2 on 4.11 had its build status changed: passing to failing
• gpx.1.0.2 on 4.12 had its build status changed: passing to failing
• gpx.1.0.2 on 4.13 had its build status changed: passing to failing
• gpx.1.0.2 on 4.14 had its build status changed: passing to failing
• gpx.1.0.2 on 5.0 is now installable. Current state is: failing
• gpx.1.0.2 on 5.1 is now installable. Current state is: failing
• gpx.1.1.0 on 4.08 had its build status changed: passing to failing
• gpx.1.1.0 on 4.09 had its build status changed: passing to failing
• gpx.1.1.0 on 4.10 had its build status changed: passing to failing
• gpx.1.1.0 on 4.11 had its build status changed: passing to failing
• gpx.1.1.0 on 4.12 had its build status changed: passing to failing
• gpx.1.1.0 on 4.13 had its build status changed: passing to failing
• gpx.1.1.0 on 4.14 had its build status changed: passing to failing
• gpx.1.1.0 on 5.0 is now installable. Current state is: failing
• gpx.1.1.0 on 5.1 is now installable. Current state is: failing
• gpx.1.1.1 on 4.08 had its build status changed: passing to failing
• gpx.1.1.1 on 4.09 had its build status changed: passing to failing
• gpx.1.1.1 on 4.10 had its build status changed: passing to failing
• gpx.1.1.1 on 4.11 had its build status changed: passing to failing
• gpx.1.1.1 on 4.12 had its build status changed: passing to failing
• gpx.1.1.1 on 4.13 had its build status changed: passing to failing
• gpx.1.1.1 on 4.14 had its build status changed: passing to failing
• gpx.1.1.1 on 5.0 is now installable. Current state is: failing
• gpx.1.1.1 on 5.1 is now installable. Current state is: failing
• graphql.0.1.0 on 4.08 had its build status changed: passing to failing
• graphql.0.1.0 on 4.09 had its build status changed: passing to failing
• graphql.0.1.0 on 4.10 had its build status changed: passing to failing
• graphql.0.1.0 on 4.11 had its build status changed: passing to failing
• graphql.0.1.0 on 4.12 had its build status changed: passing to failing
• graphql.0.2.0 on 4.08 had its build status changed: passing to failing
• graphql.0.2.0 on 4.09 had its build status changed: passing to failing
• graphql.0.2.0 on 4.10 had its build status changed: passing to failing
• graphql.0.2.0 on 4.11 had its build status changed: passing to failing
• graphql.0.2.0 on 4.12 had its build status changed: passing to failing
• graphql.0.4.0 on 4.08 had its build status changed: passing to failing
• graphql.0.4.0 on 4.09 had its build status changed: passing to failing
• graphql.0.4.0 on 4.10 had its build status changed: passing to failing
• graphql.0.4.0 on 4.11 had its build status changed: passing to failing
• graphql.0.4.0 on 4.12 had its build status changed: passing to failing
• graphql.0.5.0 on 4.08 had its build status changed: passing to failing
• graphql.0.5.0 on 4.09 had its build status changed: passing to failing
• graphql.0.5.0 on 4.10 had its build status changed: passing to failing
• graphql.0.5.0 on 4.11 had its build status changed: passing to failing
• graphql.0.5.0 on 4.12 had its build status changed: passing to failing
• graphql.0.6.0 on 4.08 had its build status changed: passing to failing
• graphql.0.6.0 on 4.09 had its build status changed: passing to failing
• graphql.0.6.0 on 4.10 had its build status changed: passing to failing
• graphql.0.6.0 on 4.11 had its build status changed: passing to failing
• graphql.0.6.0 on 4.12 had its build status changed: passing to failing
• graphql.0.7.0 on 4.08 had its build status changed: passing to failing
• graphql.0.7.0 on 4.09 had its build status changed: passing to failing
• graphql.0.7.0 on 4.10 had its build status changed: passing to failing
• graphql.0.7.0 on 4.11 had its build status changed: passing to failing
• graphql.0.7.0 on 4.12 had its build status changed: passing to failing
• graphql.0.8.0 on 4.08 had its build status changed: passing to failing
• graphql.0.8.0 on 4.09 had its build status changed: passing to failing
• graphql.0.8.0 on 4.10 had its build status changed: passing to failing
• graphql.0.8.0 on 4.11 had its build status changed: passing to failing
• graphql.0.8.0 on 4.12 had its build status changed: passing to failing
• hack_parallel.0.1.1 on 4.08 had its build status changed: passing to failing
• hack_parallel.0.1.1 on 4.09 had its build status changed: passing to failing
• hacl-star-raw.0.1 on 4.08 had its build status changed: passing to failing
• hacl-star-raw.0.1 on 4.10 had its build status changed: passing to failing
• hacl-star-raw.0.1 on 4.13 had its build status changed: passing to failing
• hacl-star-raw.0.1 on 4.14 had its build status changed: passing to failing
• hacl-star-raw.0.1.1 on 4.08 had its build status changed: passing to failing
• hacl-star-raw.0.1.1 on 4.09 had its build status changed: passing to failing
• hacl-star-raw.0.1.1 on 4.10 had its build status changed: passing to failing
• hacl-star-raw.0.1.1 on 4.11 had its build status changed: passing to failing
• hacl-star-raw.0.1.1 on 4.12 had its build status changed: passing to failing
• hacl-star-raw.0.1.1 on 4.13 had its build status changed: passing to failing
• hacl-star-raw.0.1.1 on 4.14 had its build status changed: passing to failing
• hacl-star-raw.0.2.0 on 4.08 had its build status changed: passing to failing
• hacl-star-raw.0.2.0 on 4.09 had its build status changed: passing to failing
• hacl-star-raw.0.2.0 on 4.11 had its build status changed: passing to failing
• hacl-star-raw.0.2.0 on 4.13 had its build status changed: passing to failing
• hacl-star-raw.0.2.0 on 4.14 had its build status changed: passing to failing
• hacl-star-raw.0.2.1 on 4.08 had its build status changed: passing to failing
• hacl-star-raw.0.2.1 on 4.09 had its build status changed: passing to failing
• hacl-star-raw.0.2.1 on 4.10 had its build status changed: passing to failing
• hacl-star-raw.0.2.1 on 4.11 had its build status changed: passing to failing
• hacl-star-raw.0.2.1 on 4.12 had its build status changed: passing to failing
• hacl-star-raw.0.2.1 on 4.13 had its build status changed: passing to failing
• hacl-star-raw.0.2.1 on 4.14 had its build status changed: passing to failing
• hacl-star-raw.0.2.2 on 4.08 had its build status changed: passing to failing
• hacl-star-raw.0.2.2 on 4.10 had its build status changed: passing to failing
• hacl-star-raw.0.2.2 on 4.12 had its build status changed: passing to failing
• hacl-star-raw.0.2.2 on 4.13 had its build status changed: passing to failing
• hacl-star-raw.0.2.2 on 4.14 had its build status changed: passing to failing
• hlarp.0.0.1 on 4.08 had its build status changed: passing to failing
• hlarp.0.0.1 on 4.09 had its build status changed: passing to failing
• hlarp.0.0.1 on 4.10 had its build status changed: passing to failing
• hlarp.0.0.1 on 4.11 had its build status changed: passing to failing
• hlarp.0.0.1 on 4.12 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.08 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.09 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.10 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.11 had its build status changed: passing to failing
• hlarp.0.0.2 on 4.12 had its build status changed: passing to failing
• hweak.1.1 on 5.0 is now installable. Current state is: failing
• hweak.1.1 on 5.1 is now installable. Current state is: failing
• index.1.2.1 on 4.08 had its build status changed: passing to failing
• index.1.2.1 on 4.09 had its build status changed: passing to failing
• index.1.2.1 on 4.10 had its build status changed: passing to failing
• index.1.2.1 on 4.11 had its build status changed: passing to failing
• irmin-test.2.0.0 on 4.08 had its build status changed: passing to failing
• irmin-test.2.0.0 on 4.09 had its build status changed: passing to failing
• irmin-test.2.0.0 on 4.10 had its build status changed: passing to failing
• irmin-test.2.0.0 on 4.11 had its build status changed: passing to failing
• irmin-test.2.0.0 on 4.12 had its build status changed: passing to failing
• irmin-test.2.0.0 on 4.13 had its build status changed: passing to failing
• jhupllib.0.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
• jupyter-kernel.0.4 on 4.08 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.09 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.10 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.11 had its build status changed: passing to failing
• kappa-library.4.1.0 on 4.08 had its build status changed: 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
• kinetic-client.0.0.1 on 4.08 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.09 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.10 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.11 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.12 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.13 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.14 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.13 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
• lambda.0.1.7 on 4.08 had its build status changed: passing to failing
• lambda.0.1.7 on 4.09 had its build status changed: passing to failing
• lambda.0.1.7 on 4.10 had its build status changed: passing to failing
• lambda.0.1.7 on 4.11 had its build status changed: passing to failing
• lambda.0.1.7 on 4.12 had its build status changed: passing to failing
• lambda.0.1.7 on 4.13 had its build status changed: passing to failing
• lambda.0.1.7 on 4.14 had its build status changed: passing to failing
• lambda.0.1.7 on 5.0 is now installable. Current state is: failing
• lambda.0.1.7 on 5.1 is now installable. Current state is: failing
• lbvs_consent.2.1.3 on 5.0 is now installable. Current state is: failing
• lbvs_consent.2.1.3 on 5.1 is now installable. Current state is: failing
• lbvs_consent.2.2.0 on 5.0 is now installable. Current state is: failing
• lbvs_consent.2.2.0 on 5.1 is now installable. Current state is: failing
• lem.2020-06-03 on 4.08 had its build status changed: passing to failing
• lem.2020-06-03 on 4.09 had its build status changed: passing to failing
• lem.2020-06-03 on 4.10 had its build status changed: passing to failing
• lem.2020-06-03 on 4.11 had its build status changed: passing to failing
• lem.2020-06-03 on 4.12 had its build status changed: passing to failing
• lem.2020-06-03 on 4.13 had its build status changed: passing to failing
• lem.2020-06-03 on 4.14 had its build status changed: passing to failing
• lem.2022-12-10 on 4.08 is now installable. Current state is: failing
• lem.2022-12-10 on 4.09 is now installable. Current state is: failing
• lem.2022-12-10 on 4.10 is now installable. Current state is: failing
• lem.2022-12-10 on 4.11 is now installable. Current state is: failing
• lem.2022-12-10 on 4.12 is now installable. Current state is: failing
• lem.2022-12-10 on 4.13 is now installable. Current state is: failing
• lem.2022-12-10 on 4.14 is now installable. Current state is: failing
• lem.2022-12-10 on 5.0 is now installable. Current state is: failing
• lem.2022-12-10 on 5.1 is now installable. Current state is: failing
• libbinaryen.109.0.0 on 4.12 is now installable. Current state is: failing
• libbinaryen.109.0.0 on 4.13 is now installable. Current state is: failing
• libbinaryen.109.0.0 on 4.14 is now installable. Current state is: failing
• libbinaryen.109.0.0 on 5.0 is now installable. Current state is: failing
• libbinaryen.109.0.0 on 5.1 is now installable. Current state is: failing
• libbinaryen.109.0.1 on 4.12 is now installable. Current state is: failing
• libbinaryen.109.0.1 on 4.13 is now installable. Current state is: failing
• libbinaryen.109.0.1 on 4.14 is now installable. Current state is: failing
• libbinaryen.109.0.1 on 5.0 is now installable. Current state is: failing
• libbinaryen.109.0.1 on 5.1 is now installable. Current state is: failing
• libbinaryen.110.0.0 on 4.12 is now installable. Current state is: failing
• libbinaryen.110.0.0 on 4.13 is now installable. Current state is: failing
• libbinaryen.110.0.0 on 4.14 is now installable. Current state is: failing
• libbinaryen.110.0.0 on 5.0 is now installable. Current state is: failing
• libbinaryen.110.0.0 on 5.1 is now installable. Current state is: failing
• libbinaryen.111.0.0 on 4.12 is now installable. Current state is: failing
• libbinaryen.111.0.0 on 4.13 is now installable. Current state is: failing
• libbinaryen.111.0.0 on 4.14 is now installable. Current state is: failing
• libbinaryen.111.0.0 on 5.0 is now installable. Current state is: failing
• libbinaryen.111.0.0 on 5.1 is now installable. Current state is: failing
• libbinaryen.111.1.0 on 4.12 is now installable. Current state is: failing
• libbinaryen.111.1.0 on 4.13 is now installable. Current state is: failing
• libbinaryen.111.1.0 on 4.14 is now installable. Current state is: failing
• libbinaryen.111.1.0 on 5.0 is now installable. Current state is: failing
• libbinaryen.111.1.0 on 5.1 is now installable. Current state is: failing
• libssh.0.1 on 4.14 had its build status changed: passing to failing
• lustre-v6.6.101.7 on 4.08 had its build status changed: passing to failing
• lustre-v6.6.101.7 on 4.09 had its build status changed: passing to failing
• lustre-v6.6.101.7 on 4.10 had its build status changed: passing to failing
• lustre-v6.6.101.7 on 4.11 had its build status changed: passing to failing
• luv.0.5.0 on 4.08 had its build status changed: passing to failing
• luv.0.5.0 on 4.09 had its build status changed: passing to failing
• luv.0.5.0 on 4.10 had its build status changed: passing to failing
• luv.0.5.0 on 4.11 had its build status changed: passing to failing
• luv.0.5.0 on 4.12 had its build status changed: passing to failing
• luv.0.5.0 on 4.13 had its build status changed: passing to failing
• luv.0.5.0 on 4.14 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
• mariadb.1.1.4 on 4.08 had its build status changed: passing to failing
• mariadb.1.1.4 on 4.09 had its build status changed: passing to failing
• mariadb.1.1.4 on 4.10 had its build status changed: passing to failing
• mariadb.1.1.4 on 4.11 had its build status changed: passing to failing
• mariadb.1.1.4 on 4.12 had its build status changed: passing to failing
• mariadb.1.1.4 on 4.13 had its build status changed: passing to failing
• mccs.1.1+10 on 4.09 had its build status changed: passing to failing
• mccs.1.1+11 on 4.08 had its build status changed: passing to failing
• mccs.1.1+11 on 4.13 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
• md2mld.0.5.1 on 4.08 had its build status changed: passing to failing
• md2mld.0.5.1 on 4.09 had its build status changed: passing to failing
• md2mld.0.5.1 on 4.10 had its build status changed: passing to failing
• md2mld.0.5.1 on 4.11 had its build status changed: passing to failing
• md2mld.0.5.1 on 4.12 had its build status changed: passing to failing
• md2mld.0.5.1 on 4.13 had its build status changed: passing to failing
• md2mld.0.5.1 on 4.14 had its build status changed: passing to failing
• md2mld.0.5.1 on 5.0 is now installable. Current state is: failing
• md2mld.0.5.1 on 5.1 is now installable. Current state is: failing
• md2mld.0.6 on 4.08 is now installable. Current state is: failing
• md2mld.0.6 on 4.09 is now installable. Current state is: failing
• md2mld.0.6 on 4.10 is now installable. Current state is: failing
• md2mld.0.6 on 4.11 is now installable. Current state is: failing
• md2mld.0.6 on 4.12 is now installable. Current state is: failing
• md2mld.0.6 on 4.13 is now installable. Current state is: failing
• md2mld.0.6 on 4.14 is now installable. Current state is: failing
• md2mld.0.6 on 5.0 is now installable. Current state is: failing
• md2mld.0.6 on 5.1 is now installable. Current state is: failing
• mdx.1.11.0 on 4.08 had its build status changed: passing to failing
• mdx.1.11.0 on 4.09 had its build status changed: passing to failing
• mdx.1.11.0 on 4.10 had its build status changed: passing to failing
• mdx.1.11.0 on 4.11 had its build status changed: passing to failing
• mdx.1.11.0 on 4.12 had its build status changed: passing to failing
• mdx.1.11.0 on 4.13 had its build status changed: passing to failing
• melange.1.0.0 on 5.0 is now installable. Current state is: failing
• melange.1.0.0 on 5.1 is now installable. Current state is: failing
• memtrace.0.1 on 5.0 is now installable. Current state is: failing
• memtrace.0.1 on 5.1 is now installable. Current state is: failing
• memtrace_viewer.v0.14.0 on 4.11 had its build status changed: passing to failing
• memtrace_viewer.v0.14.1 on 4.11 had its build status changed: passing to failing
• minios-xen.0.7 on 4.08 had its build status changed: passing to failing
• minios-xen.0.7 on 4.09 had its build status changed: passing to failing
• minios-xen.0.7 on 4.10 had its build status changed: passing to failing
• minios-xen.0.7 on 4.11 had its build status changed: passing to failing
• minios-xen.0.7 on 4.12 had its build status changed: passing to failing
• minios-xen.0.7 on 4.13 had its build status changed: passing to failing
• minios-xen.0.7 on 4.14 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-qubes.0.6 on 4.08 had its build status changed: passing to failing
• mirage-qubes.0.6 on 4.09 had its build status changed: passing to failing
• mirage-qubes.0.6 on 4.10 had its build status changed: passing to failing
• mirage-qubes.0.6 on 4.11 had its build status changed: passing to 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.13 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.13 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.13 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.13 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.13 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.13 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.13 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.13 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
• morbig.0.9 on 5.1 is now installable. Current state is: failing
• morsmall.0.2.0 on 4.08 had its build status changed: passing to failing
• morsmall.0.2.0 on 4.09 had its build status changed: passing to failing
• morsmall.0.2.0 on 4.10 had its build status changed: passing to failing
• morsmall.0.2.0 on 4.11 had its build status changed: passing to failing
• morsmall.0.2.0 on 4.12 had its build status changed: passing to failing
• morsmall.0.2.0 on 4.13 had its build status changed: passing to failing
• morsmall.0.2.0 on 4.14 had its build status changed: not available to failing
• morsmall.0.2.0 on 5.0 is now installable. Current state is: failing
• morsmall.0.2.0 on 5.1 is now installable. Current state is: failing
• mrmime.0.3.0 on 4.08 had its build status changed: passing to failing
• mrmime.0.3.0 on 4.09 had its build status changed: passing to failing
• mrmime.0.3.0 on 4.10 had its build status changed: passing to failing
• mrmime.0.3.0 on 4.11 had its build status changed: passing to failing
• mrmime.0.3.0 on 4.12 had its build status changed: passing to failing
• mrmime.0.3.0 on 4.13 had its build status changed: passing to failing
• mrmime.0.3.0 on 4.14 had its build status changed: passing to failing
• mrmime.0.3.0 on 5.0 is now installable. Current state is: failing
• mrmime.0.3.0 on 5.1 is now installable. Current state is: failing
• msat.0.5 on 4.08 had its build status changed: passing to failing
• msat.0.5 on 4.09 had its build status changed: passing to failing
• msat.0.5 on 4.10 had its build status changed: passing to failing
• msat.0.5 on 4.11 had its build status changed: passing to failing
• msat.0.5 on 4.12 had its build status changed: passing to failing
• msat.0.5 on 4.13 had its build status changed: passing to failing
• msat.0.5 on 4.14 had its build status changed: passing to failing
• msat.0.5.1 on 4.08 had its build status changed: passing to failing
• msat.0.5.1 on 4.09 had its build status changed: passing to failing
• msat.0.5.1 on 4.10 had its build status changed: passing to failing
• msat.0.5.1 on 4.11 had its build status changed: passing to failing
• msat.0.5.1 on 4.12 had its build status changed: passing to failing
• msat.0.5.1 on 4.13 had its build status changed: passing to failing
• msat.0.5.1 on 4.14 had its build status changed: passing to failing
• msat.0.6 on 4.08 had its build status changed: passing to failing
• msat.0.6 on 4.09 had its build status changed: passing to failing
• msat.0.6 on 4.10 had its build status changed: passing to failing
• msat.0.6 on 4.11 had its build status changed: passing to failing
• msat.0.6 on 4.12 had its build status changed: passing to failing
• msat.0.6 on 4.13 had its build status changed: passing to failing
• msat.0.6 on 4.14 had its build status changed: passing to 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
• mysql8.1.0 on 5.1 is now installable. Current state is: failing
• mysql_protocol.3.0.1 on 4.09 had its build status changed: passing to failing
• mysql_protocol.3.0.1 on 4.10 had its build status changed: passing to failing
• mysql_protocol.3.0.1 on 4.11 had its build status changed: passing to failing
• mysql_protocol.3.0.1 on 4.12 had its build status changed: passing to failing
• mysql_protocol.3.0.1 on 4.13 had its build status changed: passing to failing
• mysql_protocol.3.0.1 on 4.14 had its build status changed: not available to failing
• mysql_protocol.3.0.1 on 5.0 is now installable. Current state is: failing
• mysql_protocol.3.0.1 on 5.1 is now installable. Current state is: failing
• mysql_protocol.3.0.2 on 4.09 is now installable. Current state is: failing
• mysql_protocol.3.0.2 on 4.10 is now installable. Current state is: failing
• mysql_protocol.3.0.2 on 4.11 is now installable. Current state is: failing
• mysql_protocol.3.0.2 on 4.12 is now installable. Current state is: failing
• mysql_protocol.3.0.2 on 4.13 is now installable. Current state is: failing
• mysql_protocol.3.0.2 on 4.14 is now installable. Current state is: failing
• mysql_protocol.3.0.2 on 5.0 is now installable. Current state is: failing
• mysql_protocol.3.0.2 on 5.1 is now installable. Current state is: failing
• mysql_protocol.3.0.3 on 4.09 is now installable. Current state is: failing
• mysql_protocol.3.0.3 on 4.10 is now installable. Current state is: failing
• mysql_protocol.3.0.3 on 4.11 is now installable. Current state is: failing
• mysql_protocol.3.0.3 on 4.12 is now installable. Current state is: failing
• mysql_protocol.3.0.3 on 4.13 is now installable. Current state is: failing
• mysql_protocol.3.0.3 on 4.14 is now installable. Current state is: failing
• mysql_protocol.3.0.3 on 5.0 is now installable. Current state is: failing
• mysql_protocol.3.0.3 on 5.1 is now installable. Current state is: failing
• named-pipe.0.4.0 on 4.08 had its build status changed: passing to failing
• named-pipe.0.4.0 on 4.09 had its build status changed: passing to failing
• named-pipe.0.4.0 on 4.10 had its build status changed: passing to failing
• named-pipe.0.4.0 on 4.11 had its build status changed: passing to failing
• nbd.3.0.0 on 4.08 had its build status changed: passing to failing
• nbd.3.0.0 on 4.09 had its build status changed: passing to failing
• nbd.3.0.0 on 4.10 had its build status changed: passing to failing
• nbd.3.0.0 on 4.11 had its build status changed: passing to failing
• netchannel.1.10.2 on 4.08 had its build status changed: passing to failing
• netchannel.1.10.2 on 4.09 had its build status changed: passing to failing
• netchannel.1.10.2 on 4.10 had its build status changed: passing to failing
• netchannel.1.10.2 on 4.11 had its build status changed: passing to failing
• netchannel.1.11.0 on 4.08 had its build status changed: passing to failing
• netchannel.1.11.0 on 4.09 had its build status changed: passing to failing
• netchannel.1.11.0 on 4.10 had its build status changed: passing to failing
• netchannel.1.11.0 on 4.11 had its build status changed: passing to failing
• netchannel.1.12.0 on 4.08 had its build status changed: passing to failing
• netchannel.1.12.0 on 4.09 had its build status changed: passing to failing
• netchannel.1.12.0 on 4.10 had its build status changed: passing to failing
• netchannel.1.12.0 on 4.11 had its build status changed: passing to failing
• netchannel.1.13.0 on 4.08 had its build status changed: passing to failing
• netchannel.1.13.0 on 4.09 had its build status changed: passing to failing
• netchannel.1.13.0 on 4.10 had its build status changed: passing to failing
• netchannel.1.13.0 on 4.11 had its build status changed: passing to failing
• netchannel.1.13.1 on 4.08 had its build status changed: passing to failing
• netchannel.1.13.1 on 4.09 had its build status changed: passing to failing
• netchannel.1.13.1 on 4.10 had its build status changed: passing to failing
• netchannel.1.13.1 on 4.11 had its build status changed: passing to failing
• netkat.0.1 on 4.08 had its build status changed: passing to failing
• netkat.0.1 on 4.09 had its build status changed: passing to failing
• netkat.0.1 on 4.10 had its build status changed: passing to failing
• netkat.0.1 on 4.11 had its build status changed: passing to failing
• noCanren.0.3.0 on 4.13 is now installable. Current state is: failing
• noCanren.0.3.0~alpha1 on 4.13 is now installable. Current state is: failing
• nuscr.1.0.0 on 4.08 had its build status changed: passing to failing
• nuscr.1.0.0 on 4.09 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.08 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.09 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.10 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.11 had its build status changed: passing to failing
• nuscr.1.1.0 on 4.12 had its build status changed: passing to failing
• obuild.0.1.10 on 4.08 had its build status changed: passing to failing
• obuild.0.1.10 on 4.09 had its build status changed: passing to failing
• obuild.0.1.10 on 4.10 had its build status changed: passing to failing
• obuild.0.1.10 on 4.11 had its build status changed: passing to failing
• obuild.0.1.10 on 4.12 had its build status changed: passing to failing
• obuild.0.1.10 on 4.13 had its build status changed: passing to failing
• obuild.0.1.10 on 4.14 had its build status changed: passing to failing
• obuild.0.1.9 on 4.08 had its build status changed: passing to failing
• obuild.0.1.9 on 4.09 had its build status changed: passing to failing
• obuild.0.1.9 on 4.10 had its build status changed: passing to failing
• obuild.0.1.9 on 4.11 had its build status changed: passing to failing
• obuild.0.1.9 on 4.12 had its build status changed: passing to failing
• obuild.0.1.9 on 4.13 had its build status changed: passing to failing
• obuild.0.1.9 on 4.14 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-protoc.1.2.6 on 4.08 had its build status changed: passing to failing
• ocaml-protoc.1.2.6 on 4.09 had its build status changed: passing to failing
• ocaml-protoc.1.2.6 on 4.10 had its build status changed: passing to failing
• ocaml-protoc.1.2.6 on 4.11 had its build status changed: passing to failing
• ocaml-protoc.1.2.6 on 4.12 had its build status changed: passing to failing
• ocaml-protoc.1.2.6 on 4.13 had its build status changed: passing to failing
• ocaml-protoc.1.2.6 on 4.14 had its build status changed: not available to failing
• ocaml-r.0.1.0 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.1.0 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.1.1 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.2.0 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.3.0 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.08 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.09 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.10 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.11 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.12 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.13 had its build status changed: passing to failing
• ocaml-r.0.3.1 on 4.14 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.13 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.13 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
• ocamldiff.1.1 on 4.08 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.09 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.10 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.11 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.12 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.13 had its build status changed: passing to failing
• ocamldiff.1.1 on 4.14 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
• 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
• ocamlnet.4.1.6 on 4.08 had its build status changed: passing to failing
• ocamlnet.4.1.6 on 4.09 had its build status changed: passing to failing
• ocamlnet.4.1.7 on 4.08 had its build status changed: passing to failing
• ocamlnet.4.1.7 on 4.09 had its build status changed: passing to failing
• ocamlnet.4.1.7 on 4.10 had its build status changed: passing to failing
• ocamlnet.4.1.8 on 4.08 had its build status changed: passing to failing
• ocamlnet.4.1.8 on 4.09 had its build status changed: passing to failing
• ocamlnet.4.1.8 on 4.10 had its build status changed: passing to failing
• ocamlnet.4.1.8 on 4.11 had its build status changed: passing to failing
• ocamlnet.4.1.8 on 4.12 had its build status changed: passing to failing
• ocamlnet.4.1.8 on 4.13 had its build status changed: passing to failing
• ocamlnet.4.1.8 on 4.14 had its build status changed: passing to failing
• ocamlnet.4.1.9 on 4.08 had its build status changed: passing to failing
• ocamlnet.4.1.9 on 4.09 had its build status changed: passing to failing
• ocamlnet.4.1.9 on 4.10 had its build status changed: passing to failing
• ocamlnet.4.1.9 on 4.11 had its build status changed: passing to failing
• ocamlnet.4.1.9 on 4.12 had its build status changed: passing to failing
• ocamlnet.4.1.9 on 4.13 had its build status changed: passing to failing
• ocamlnet.4.1.9 on 4.14 had its build status changed: passing to failing
• ocamlnet.4.1.9-1 on 4.08 had its build status changed: passing to failing
• ocamlnet.4.1.9-1 on 4.09 had its build status changed: passing to failing
• ocamlnet.4.1.9-1 on 4.10 had its build status changed: passing to failing
• ocamlnet.4.1.9-1 on 4.11 had its build status changed: passing to failing
• ocamlnet.4.1.9-1 on 4.12 had its build status changed: passing to failing
• ocamlnet.4.1.9-1 on 4.13 had its build status changed: passing to failing
• ocamlnet.4.1.9-1 on 4.14 had its build status changed: passing to failing
• ocamlnet.4.1.9-2 on 4.08 is now installable. Current state is: failing
• ocamlnet.4.1.9-2 on 4.09 is now installable. Current state is: failing
• ocamlnet.4.1.9-2 on 4.10 is now installable. Current state is: failing
• ocamlnet.4.1.9-2 on 4.11 is now installable. Current state is: failing
• ocamlnet.4.1.9-2 on 4.12 is now installable. Current state is: failing
• ocamlnet.4.1.9-2 on 4.13 is now installable. Current state is: failing
• ocamlnet.4.1.9-2 on 4.14 is now installable. Current state is: failing
• ocamlrss.2.0 on 4.08 had its build status changed: passing to failing
• ocamlrss.2.0 on 4.09 had its build status changed: passing to failing
• ocamlrss.2.0 on 4.10 had its build status changed: passing to failing
• ocamlrss.2.0 on 4.11 had its build status changed: passing to failing
• ocamlrss.2.0 on 4.12 had its build status changed: passing to failing
• ocamlrss.2.0 on 4.13 had its build status changed: passing to failing
• ocamlrss.2.0 on 4.14 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-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
• octez-smart-rollup-client-PtMumbai.16.0 on 4.11 is now installable. Current state is: failing
• octez-smart-rollup-client-PtMumbai.16.1 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
• ollvm-tapir.0.99.1 on 4.08 had its build status changed: passing to failing
• ollvm-tapir.0.99.1 on 4.09 had its build status changed: passing to failing
• ollvm-tapir.0.99.1 on 4.10 had its build status changed: passing to failing
• ollvm-tapir.0.99.1 on 4.11 had its build status changed: passing to failing
• ollvm-tapir.0.99.1 on 4.12 had its build status changed: passing to failing
• ollvm-tapir.0.99.1 on 4.13 had its build status changed: passing to failing
• ollvm-tapir.0.99.1 on 4.14 had its build status changed: passing to failing
• ollvm-tapir.0.99.1 on 5.0 is now installable. Current state is: 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.09 had its build status changed: passing to failing
• ollvm.0.99 on 4.10 had its build status changed: passing to failing
• ollvm.0.99 on 4.11 had its build status changed: passing to failing
• ollvm.0.99 on 4.12 had its build status changed: passing to failing
• ollvm.0.99 on 4.13 had its build status changed: passing to failing
• 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
• ollvm.0.99 on 5.1 is now installable. Current state is: failing
• opam-build.0.1.0 on 4.08 had its build status changed: passing to failing
• opam-build.0.1.0 on 4.09 had its build status changed: passing to failing
• opam-build.0.1.0 on 4.10 had its build status changed: passing to failing
• opam-build.0.1.0 on 4.11 had its build status changed: passing to failing
• opam-build.0.1.0 on 4.12 had its build status changed: passing to failing
• opam-build.0.1.0 on 4.13 had its build status changed: passing to failing
• opam-build.0.1.0 on 4.14 had its build status changed: passing to failing
• opam-build.0.1.0 on 5.0 is now installable. Current state is: failing
• opam-build.0.1.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
• opentelemetry-cohttp-lwt.0.6 on 4.08 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.6 on 4.09 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.6 on 4.10 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.6 on 4.11 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.6 on 4.12 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.6 on 4.13 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.6 on 4.14 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.6 on 5.0 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.6 on 5.1 is now installable. Current state is: failing
• oplsr.8.0.1 on 4.13 had its build status changed: not available to failing
• oplsr.8.0.1 on 4.14 had its build status changed: not available to failing
• oplsr.8.0.1 on 5.0 is now installable. Current state is: failing
• oplsr.8.0.1 on 5.1 is now installable. Current state is: failing
• opsian.0.1 on 5.0 is now installable. Current state is: failing
• opsian.0.1 on 5.1 is now installable. Current state is: failing
• orun.0.0.1 on 4.08 had its build status changed: passing to failing
• orun.0.0.1 on 4.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.13 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
• ostap.0.5 on 4.10 had its build status changed: passing to failing
• ostap.0.5 on 4.11 had its build status changed: passing to failing
• ostap.0.5 on 4.12 had its build status changed: passing to failing
• ostap.0.5 on 4.13 had its build status changed: passing to failing
• ostap.0.5 on 4.14 had its build status changed: not available to failing
• ott.0.27 on 4.08 had its build status changed: passing to failing
• ott.0.27 on 4.09 had its build status changed: passing to failing
• ott.0.27 on 4.10 had its build status changed: passing to failing
• ott.0.27 on 4.11 had its build status changed: passing to failing
• ott.0.27 on 4.12 had its build status changed: passing to failing
• ott.0.27 on 4.13 had its build status changed: passing to failing
• ott.0.27 on 4.14 had its build status changed: passing to failing
• ott.0.31 on 4.08 had its build status changed: passing to failing
• ott.0.31 on 4.09 had its build status changed: passing to failing
• ott.0.31 on 4.10 had its build status changed: passing to failing
• ott.0.31 on 4.11 had its build status changed: passing to failing
• ott.0.31 on 4.12 had its build status changed: passing to failing
• ott.0.31 on 4.13 had its build status changed: passing to failing
• ott.0.31 on 4.14 had its build status changed: passing to failing
• ott.0.32 on 4.08 is now installable. Current state is: failing
• ott.0.32 on 4.09 is now installable. Current state is: failing
• ott.0.32 on 4.10 is now installable. Current state is: failing
• ott.0.32 on 4.11 is now installable. Current state is: failing
• ott.0.32 on 4.12 is now installable. Current state is: failing
• ott.0.32 on 4.13 is now installable. Current state is: failing
• ott.0.32 on 4.14 is now installable. Current state is: failing
• ott.0.33 on 4.08 is now installable. Current state is: failing
• ott.0.33 on 4.09 is now installable. Current state is: failing
• ott.0.33 on 4.10 is now installable. Current state is: failing
• ott.0.33 on 4.11 is now installable. Current state is: failing
• ott.0.33 on 4.12 is now installable. Current state is: failing
• ott.0.33 on 4.13 is now installable. Current state is: failing
• ott.0.33 on 4.14 is now installable. Current state is: failing
• ott.0.33 on 5.0 is now installable. Current state is: failing
• ott.0.33 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
• owl-zoo.1.0.2 on 4.13 is now installable. Current state is: failing
• pa_ppx.0.03 on 4.11 had its build status changed: passing to failing
• pa_ppx.0.07.02 on 4.10 had its build status changed: passing to failing
• pa_ppx.0.08 on 4.10 had its build status changed: passing to failing
• pa_ppx.0.08 on 4.11 had its build status changed: passing to failing
• pa_ppx.0.08 on 4.12 had its build status changed: passing to failing
• pa_ppx.0.08 on 4.13 had its build status changed: passing to failing
• pa_ppx.0.09 on 4.10 is now installable. Current state is: failing
• pa_ppx.0.09 on 4.11 is now installable. Current state is: failing
• pa_ppx.0.09 on 4.12 is now installable. Current state is: failing
• pa_ppx.0.09 on 4.13 is now installable. Current state is: failing
• pa_ppx.0.09 on 4.14 is now installable. Current state is: failing
• pa_ppx.0.10 on 4.10 is now installable. Current state is: failing
• pa_ppx.0.10 on 4.11 is now installable. Current state is: failing
• pa_ppx.0.10 on 4.12 is now installable. Current state is: failing
• pa_ppx.0.10 on 4.13 is now installable. Current state is: failing
• pa_ppx.0.10 on 4.14 is now installable. Current state is: failing
• pa_ppx.0.10 on 5.0 is now installable. Current state is: failing
• pa_ppx.0.11 on 4.10 is now installable. Current state is: failing
• pa_ppx.0.11 on 4.11 is now installable. Current state is: failing
• pa_ppx.0.11 on 4.12 is now installable. Current state is: failing
• pa_ppx.0.11 on 4.13 is now installable. Current state is: failing
• pa_ppx.0.11 on 4.14 is now installable. Current state is: failing
• pa_ppx.0.11 on 5.0 is now installable. Current state is: failing
• pa_ppx.0.12 on 4.10 is now installable. Current state is: failing
• pa_ppx.0.12 on 4.11 is now installable. Current state is: failing
• pa_ppx.0.12 on 4.12 is now installable. Current state is: failing
• pa_ppx.0.12 on 4.13 is now installable. Current state is: failing
• pa_ppx.0.12 on 4.14 is now installable. Current state is: failing
• pa_ppx.0.12 on 5.0 is now installable. Current state is: failing
• pa_ppx.0.13 on 4.10 is now installable. Current state is: failing
• pa_ppx.0.13 on 4.11 is now installable. Current state is: failing
• pa_ppx.0.13 on 4.12 is now installable. Current state is: failing
• pa_ppx.0.13 on 4.13 is now installable. Current state is: failing
• pa_ppx.0.13 on 4.14 is now installable. Current state is: failing
• pa_ppx.0.13 on 5.0 is now installable. Current state is: failing
• pa_ppx.0.13 on 5.1 is now installable. Current state is: failing
• pa_ppx.0.14 on 4.12 is now installable. Current state is: failing
• pa_ppx.0.14 on 4.13 is now installable. Current state is: failing
• pa_ppx.0.14 on 4.14 is now installable. Current state is: failing
• pa_ppx.0.14 on 5.0 is now installable. Current state is: failing
• pa_ppx.0.14 on 5.1 is now installable. Current state is: failing
• papi.0.1.1 on 5.0 is now installable. Current state is: failing
• papi.0.1.1 on 5.1 is now installable. Current state is: failing
• 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
• piaf.0.1.0 on 4.08 had its build status changed: passing to failing
• piaf.0.1.0 on 4.09 had its build status changed: passing to failing
• piaf.0.1.0 on 4.10 had its build status changed: passing to failing
• piaf.0.1.0 on 4.11 had its build status changed: passing to failing
• piaf.0.1.0 on 4.12 had its build status changed: passing to failing
• piaf.0.1.0 on 4.13 had its build status changed: passing to failing
• piaf.0.1.0 on 4.14 had its build status changed: passing to failing
• pkcs11-driver.1.0.1 on 5.1 is now installable. Current state is: failing
• portia.1.1 on 4.14 had its build status changed: not available to failing
• portia.1.1 on 5.0 is now installable. Current state is: failing
• portia.1.1 on 5.1 is now installable. Current state is: failing
• portia.1.3 on 4.10 had its build status changed: passing to failing
• portia.1.3 on 4.12 had its build status changed: passing to failing
• portia.1.3 on 4.14 had its build status changed: not available to failing
• portia.1.3 on 5.0 is now installable. Current state is: failing
• portia.1.3 on 5.1 is now installable. Current state is: failing
• portia.1.5 on 4.09 had its build status changed: passing to failing
• portia.1.5 on 4.13 had its build status changed: not available to failing
• portia.1.5 on 5.0 is now installable. Current state is: failing
• portia.1.5 on 5.1 is now installable. Current state is: failing
• posix-semaphore.0.3.0-0 on 4.08 had its build status changed: passing to failing
• posix-semaphore.0.3.0-0 on 4.09 had its build status changed: passing to failing
• posix-semaphore.0.3.0-0 on 4.10 had its build status changed: passing to failing
• posix-semaphore.0.3.0-0 on 4.11 had its build status changed: passing to failing
• posix-semaphore.0.3.0-0 on 4.12 had its build status changed: passing to failing
• posix-semaphore.0.3.0-0 on 4.13 had its build status changed: passing to failing
• posix-semaphore.0.3.0-0 on 4.14 had its build status changed: passing to failing
• posix-semaphore.0.4.0-0 on 4.08 had its build status changed: passing to failing
• posix-semaphore.0.4.0-0 on 4.09 had its build status changed: passing to failing
• posix-semaphore.0.4.0-0 on 4.10 had its build status changed: passing to failing
• posix-semaphore.0.4.0-0 on 4.11 had its build status changed: passing to failing
• posix-semaphore.0.4.0-0 on 4.12 had its build status changed: passing to failing
• posix-semaphore.0.4.0-0 on 4.13 had its build status changed: passing to failing
• posix-semaphore.0.4.0-0 on 4.14 had its build status changed: passing to failing
• posix-semaphore.0.5.0-0 on 4.08 had its build status changed: passing to failing
• posix-semaphore.0.5.0-0 on 4.09 had its build status changed: passing to failing
• posix-semaphore.0.5.0-0 on 4.10 had its build status changed: passing to failing
• posix-semaphore.0.5.0-0 on 4.11 had its build status changed: passing to failing
• posix-semaphore.0.5.0-0 on 4.12 had its build status changed: passing to failing
• posix-semaphore.0.5.0-0 on 4.13 had its build status changed: passing to failing
• posix-semaphore.0.5.0-0 on 4.14 had its build status changed: passing to failing
• ppx_cstubs.0.7.0 on 5.1 is now installable. Current state is: failing
• ppx_gen_rec.2.0.0 on 4.08 had its build status changed: passing to failing
• ppx_gen_rec.2.0.0 on 4.09 had its build status changed: passing to failing
• ppx_gen_rec.2.0.0 on 4.10 had its build status changed: passing to failing
• ppx_gen_rec.2.0.0 on 4.11 had its build status changed: passing to failing
• ppx_gen_rec.2.0.0 on 4.12 had its build status changed: passing to failing
• ppx_gen_rec.2.0.0 on 4.13 had its build status changed: passing to failing
• ppx_gen_rec.2.0.0 on 4.14 had its build status changed: not available to failing
• ppx_gen_rec.2.0.0 on 5.0 is now installable. Current state is: failing
• ppx_gen_rec.2.0.0 on 5.1 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
• ppx_pbt.0.2.1 on 4.13 had its build status changed: passing to failing
• ppxx.2.5.0 on 5.1 is now installable. Current state is: failing
• prof_spacetime.0.3.0 on 4.08 had its build status changed: passing to failing
• prof_spacetime.0.3.0 on 4.09 had its build status changed: passing to failing
• prof_spacetime.0.3.0 on 4.10 had its build status changed: passing to failing
• prof_spacetime.0.3.0 on 4.11 had its build status changed: passing to failing
• protocol-9p.1.0.0 on 5.0 is now installable. Current state is: failing
• protocol-9p.1.0.0 on 5.1 is now installable. Current state is: failing
• protocol-9p.1.0.1 on 5.0 is now installable. Current state is: failing
• protocol-9p.1.0.1 on 5.1 is now installable. Current state is: failing
• proverif.2.00 on 4.08 had its build status changed: passing to failing
• proverif.2.00 on 4.09 had its build status changed: passing to failing
• proverif.2.00 on 4.10 had its build status changed: passing to failing
• proverif.2.00 on 4.11 had its build status changed: passing to failing
• proverif.2.00 on 4.12 had its build status changed: passing to failing
• proverif.2.00 on 4.13 had its build status changed: passing to failing
• proverif.2.00 on 4.14 had its build status changed: passing to failing
• proverif.2.00 on 5.0 is now installable. Current state is: failing
• proverif.2.00 on 5.1 is now installable. Current state is: failing
• pythonlib.v0.15.1 on 5.1 is now installable. Current state is: failing
• radare2.0.0.2 on 4.08 had its build status changed: passing to failing
• radare2.0.0.2 on 4.09 had its build status changed: passing to failing
• radare2.0.0.2 on 4.10 had its build status changed: passing to failing
• radare2.0.0.2 on 4.11 had its build status changed: passing to failing
• radare2.0.0.2 on 4.12 had its build status changed: passing to failing
• radare2.0.0.2 on 4.13 had its build status changed: passing to failing
• radare2.0.0.2 on 4.14 had its build status changed: passing to failing
• randoml.0.1.5 on 5.0 is now installable. Current state is: failing
• randoml.0.1.5 on 5.1 is now installable. Current state is: failing
• rdf.0.11.0 on 4.08 had its build status changed: passing to failing
• rdf.0.11.0 on 4.09 had its build status changed: passing to failing
• rdf.0.11.0 on 4.10 had its build status changed: passing to failing
• rdf.0.12.0 on 4.12 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
• 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
• 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
• sanlock.0.0.9 on 4.08 had its build status changed: passing to failing
• sanlock.0.0.9 on 4.09 had its build status changed: passing to failing
• sanlock.0.0.9 on 4.10 had its build status changed: passing to failing
• sanlock.0.0.9 on 4.11 had its build status changed: passing to failing
• sanlock.0.0.9 on 4.12 had its build status changed: passing to failing
• satML-plugin.1.01 on 4.09 had its build status changed: passing to failing
• scid.1.0 on 5.0 is now installable. Current state is: failing
• scid.1.0 on 5.1 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.5 on 4.08 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.09 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.10 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.11 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.12 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.13 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.14 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.13 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.13 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.13 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.13 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-hvt.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.5 on 4.08 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.09 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.10 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.11 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.12 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.13 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.14 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.13 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.13 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.13 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.13 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-muen.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.5 on 4.08 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.09 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.10 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.11 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.12 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.13 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.14 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.13 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.13 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.13 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.13 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-spt.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.5 on 4.08 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.09 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.10 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.11 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.12 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.13 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.14 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.13 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.13 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.13 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.13 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-virtio.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.6 on 4.08 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.09 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.10 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.11 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.12 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.13 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.14 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.13 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.13 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.13 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 4.14 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 5.0 is now installable. Current state is: failing
• solo5-bindings-xen.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5.0.7.0 on 4.08 is now installable. Current state is: failing
• solo5.0.7.0 on 4.09 is now installable. Current state is: failing
• solo5.0.7.0 on 4.10 is now installable. Current state is: failing
• solo5.0.7.0 on 4.11 is now installable. Current state is: failing
• solo5.0.7.0 on 4.12 is now installable. Current state is: failing
• solo5.0.7.0 on 4.13 is now installable. Current state is: failing
• solo5.0.7.0 on 4.14 is now installable. Current state is: failing
• solo5.0.7.0 on 5.0 is now installable. Current state is: failing
• solo5.0.7.0 on 5.1 is now installable. Current state is: failing
• solo5.0.7.1 on 4.08 is now installable. Current state is: failing
• solo5.0.7.1 on 4.09 is now installable. Current state is: failing
• solo5.0.7.1 on 4.10 is now installable. Current state is: failing
• solo5.0.7.1 on 4.11 is now installable. Current state is: failing
• solo5.0.7.1 on 4.12 is now installable. Current state is: failing
• solo5.0.7.1 on 4.13 is now installable. Current state is: failing
• solo5.0.7.1 on 4.14 is now installable. Current state is: failing
• solo5.0.7.1 on 5.0 is now installable. Current state is: failing
• solo5.0.7.1 on 5.1 is now installable. Current state is: failing
• srt.0.2.0 on 4.08 had its build status changed: passing to failing
• srt.0.2.0 on 4.09 had its build status changed: passing to failing
• srt.0.2.0 on 4.10 had its build status changed: passing to failing
• srt.0.2.0 on 4.11 had its build status changed: passing to failing
• srt.0.2.0 on 4.12 had its build status changed: passing to failing
• srt.0.2.0 on 4.13 had its build status changed: passing to failing
• srt.0.2.0 on 4.14 had its build status changed: passing to failing
• srt.0.2.0 on 5.0 is now installable. Current state is: failing
• srt.0.2.0 on 5.1 is now installable. Current state is: failing
• srt.0.2.1 on 4.08 is now installable. Current state is: failing
• srt.0.2.1 on 4.09 is now installable. Current state is: failing
• srt.0.2.1 on 4.10 is now installable. Current state is: failing
• srt.0.2.1 on 4.11 is now installable. Current state is: failing
• srt.0.2.1 on 4.12 is now installable. Current state is: failing
• srt.0.2.1 on 4.13 is now installable. Current state is: failing
• srt.0.2.1 on 4.14 is now installable. Current state is: failing
• srt.0.2.1 on 5.0 is now installable. Current state is: failing
• srt.0.2.1 on 5.1 is now installable. Current state is: failing
• srt.0.2.2 on 4.08 is now installable. Current state is: failing
• srt.0.2.2 on 4.09 is now installable. Current state is: failing
• srt.0.2.2 on 4.10 is now installable. Current state is: failing
• srt.0.2.2 on 4.11 is now installable. Current state is: failing
• srt.0.2.2 on 4.12 is now installable. Current state is: failing
• srt.0.2.2 on 4.13 is now installable. Current state is: failing
• srt.0.2.2 on 4.14 is now installable. Current state is: failing
• srt.0.2.2 on 5.0 is now installable. Current state is: failing
• srt.0.2.2 on 5.1 is now installable. Current state is: failing
• srt.0.3.0 on 4.08 is now installable. Current state is: failing
• srt.0.3.0 on 4.09 is now installable. Current state is: failing
• srt.0.3.0 on 4.10 is now installable. Current state is: failing
• srt.0.3.0 on 4.11 is now installable. Current state is: failing
• srt.0.3.0 on 4.12 is now installable. Current state is: failing
• srt.0.3.0 on 4.13 is now installable. Current state is: failing
• srt.0.3.0 on 4.14 is now installable. Current state is: failing
• srt.0.3.0 on 5.0 is now installable. Current state is: failing
• srt.0.3.0 on 5.1 is now installable. Current state is: failing
• statverif.1.97pl1.1 on 4.08 had its build status changed: passing to failing
• statverif.1.97pl1.1 on 4.09 had its build status changed: passing to failing
• statverif.1.97pl1.1 on 4.10 had its build status changed: passing to failing
• statverif.1.97pl1.1 on 4.11 had its build status changed: passing to failing
• statverif.1.97pl1.1 on 4.12 had its build status changed: passing to failing
• statverif.1.97pl1.1 on 4.13 had its build status changed: passing to failing
• statverif.1.97pl1.1 on 4.14 had its build status changed: passing to failing
• statverif.1.97pl1.2 on 4.08 had its build status changed: passing to failing
• statverif.1.97pl1.2 on 4.09 had its build status changed: passing to failing
• statverif.1.97pl1.2 on 4.10 had its build status changed: passing to failing
• statverif.1.97pl1.2 on 4.11 had its build status changed: passing to failing
• statverif.1.97pl1.2 on 4.12 had its build status changed: passing to failing
• statverif.1.97pl1.2 on 4.13 had its build status changed: passing to failing
• statverif.1.97pl1.2 on 4.14 had its build status changed: passing to failing
• stdcompat.0 on 5.0 is now installable. Current state is: failing
• stdcompat.0 on 5.1 is now installable. Current state is: failing
• stdcompat.1 on 5.0 is now installable. Current state is: failing
• stdcompat.1 on 5.1 is now installable. Current state is: failing
• stdcompat.10 on 4.08 had its build status changed: passing to failing
• stdcompat.10 on 4.09 had its build status changed: passing to failing
• stdcompat.11 on 4.08 had its build status changed: passing to failing
• stdcompat.11 on 4.09 had its build status changed: passing to failing
• stdcompat.12 on 4.08 had its build status changed: passing to failing
• stdcompat.12 on 4.09 had its build status changed: passing to failing
• stdcompat.12 on 4.10 had its build status changed: passing to failing
• stdcompat.13 on 4.08 had its build status changed: passing to failing
• stdcompat.13 on 4.09 had its build status changed: passing to failing
• stdcompat.13 on 4.10 had its build status changed: passing to failing
• stdcompat.14 on 4.08 had its build status changed: passing to failing
• stdcompat.14 on 4.09 had its build status changed: passing to failing
• stdcompat.14 on 4.10 had its build status changed: passing to failing
• stdcompat.14 on 4.11 had its build status changed: passing to failing
• stdcompat.15 on 4.08 had its build status changed: passing to failing
• stdcompat.15 on 4.09 had its build status changed: passing to failing
• stdcompat.15 on 4.10 had its build status changed: passing to failing
• stdcompat.15 on 4.11 had its build status changed: passing to failing
• stdcompat.15 on 4.12 had its build status changed: passing to failing
• stdcompat.15 on 4.13 had its build status changed: passing to failing
• stdcompat.15 on 4.14 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.13 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.13 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.13 is now installable. Current state is: failing
• stdcompat.18 on 4.14 is now installable. Current state is: failing
• stdcompat.7 on 4.08 had its build status changed: passing to failing
• stdcompat.9 on 4.08 had its build status changed: passing to failing
• stog.0.20.0 on 4.12 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.08 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.09 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.10 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.11 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.12 is now installable. Current state is: failing
• sundialsml.5.8.0p0 on 4.13 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.08 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.09 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.10 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.11 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.12 is now installable. Current state is: failing
• sundialsml.6.0.0p0 on 4.13 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.08 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.09 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.10 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.11 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.12 is now installable. Current state is: failing
• sundialsml.6.1.0p0 on 4.13 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.08 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.09 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.10 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.11 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.12 is now installable. Current state is: failing
• sundialsml.6.1.1p0 on 4.13 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.08 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.09 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.10 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.11 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.12 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.13 is now installable. Current state is: failing
• sundialsml.6.1.1p1 on 4.14 is now installable. Current state is: failing
• systemverilog.0.0.1 on 5.1 is now installable. Current state is: failing
• tcpip.4.0.0 on 4.08 had its build status changed: passing to failing
• tcpip.4.0.0 on 4.09 had its build status changed: passing to failing
• tcpip.4.0.0 on 4.10 had its build status changed: passing to failing
• tcpip.4.0.0 on 4.11 had its build status changed: passing to failing
• tezos-rpc-http-server.17.3 on 4.14 is now installable. Current state is: failing
• tezos-sapling.10.2 on 4.08 had its build status changed: passing to failing
• tezos-sapling.10.2 on 4.09 had its build status changed: passing to failing
• tezos-sapling.10.2 on 4.10 had its build status changed: passing to failing
• tezos-sapling.10.2 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.13 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.13 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.13 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.13 is now installable. Current state is: failing
• tls.0.10.2 on 4.08 had its build status changed: passing to failing
• tls.0.10.2 on 4.09 had its build status changed: passing to failing
• tls.0.10.2 on 4.10 had its build status changed: passing to failing
• tls.0.10.2 on 4.11 had its build status changed: passing to failing
• tls.0.10.3 on 4.08 had its build status changed: passing to failing
• tls.0.10.3 on 4.09 had its build status changed: passing to failing
• tls.0.10.3 on 4.10 had its build status changed: passing to failing
• tls.0.10.3 on 4.11 had its build status changed: passing to failing
• tls.0.10.4 on 4.08 had its build status changed: passing to failing
• tls.0.10.4 on 4.09 had its build status changed: passing to failing
• tls.0.10.4 on 4.10 had its build status changed: passing to failing
• tls.0.10.4 on 4.11 had its build status changed: passing to failing
• tls.0.10.5 on 4.08 had its build status changed: passing to failing
• tls.0.10.5 on 4.09 had its build status changed: passing to failing
• tls.0.10.5 on 4.10 had its build status changed: passing to failing
• tls.0.10.5 on 4.11 had its build status changed: passing to failing
• tls.0.10.6 on 4.08 had its build status changed: passing to failing
• tls.0.10.6 on 4.09 had its build status changed: passing to failing
• tls.0.10.6 on 4.10 had its build status changed: passing to failing
• tls.0.10.6 on 4.11 had its build status changed: passing to failing
• toc.0.1.0 on 4.08 is now installable. Current state is: failing
• toc.0.1.0 on 4.09 is now installable. Current state is: failing
• toc.0.1.0 on 4.10 is now installable. Current state is: failing
• toc.0.1.0 on 4.11 is now installable. Current state is: failing
• toc.0.1.0 on 4.12 is now installable. Current state is: failing
• toc.0.1.0 on 4.13 is now installable. Current state is: failing
• toc.0.1.0 on 4.14 is now installable. Current state is: failing
• toc.0.1.0 on 5.0 is now installable. Current state is: failing
• toc.0.1.0 on 5.1 is now installable. Current state is: failing
• torch.0.10 on 4.08 had its build status changed: passing to failing
• torch.0.10 on 4.09 had its build status changed: passing to failing
• torch.0.10 on 4.10 had its build status changed: passing to failing
• torch.0.10 on 4.11 had its build status changed: passing to failing
• torch.0.10 on 4.12 had its build status changed: passing to failing
• torch.0.10 on 4.13 had its build status changed: passing to failing
• torch.0.10 on 4.14 had its build status changed: not available to failing
• torch.0.10 on 5.0 is now installable. Current state is: failing
• torch.0.10 on 5.1 is now installable. Current state is: failing
• torch.0.11 on 4.08 had its build status changed: passing to failing
• torch.0.11 on 4.09 had its build status changed: passing to failing
• torch.0.11 on 4.10 had its build status changed: passing to failing
• torch.0.11 on 4.11 had its build status changed: passing to failing
• torch.0.11 on 4.12 had its build status changed: passing to failing
• torch.0.11 on 4.13 had its build status changed: passing to failing
• torch.0.11 on 4.14 had its build status changed: not available to failing
• torch.0.11 on 5.0 is now installable. Current state is: failing
• torch.0.11 on 5.1 is now installable. Current state is: failing
• torch.0.12 on 4.08 had its build status changed: passing to failing
• torch.0.12 on 4.09 had its build status changed: passing to failing
• torch.0.12 on 4.10 had its build status changed: passing to failing
• torch.0.12 on 4.11 had its build status changed: passing to failing
• torch.0.12 on 4.12 had its build status changed: passing to failing
• torch.0.12 on 4.13 had its build status changed: passing to failing
• torch.0.12 on 4.14 had its build status changed: not available to failing
• torch.0.12 on 5.0 is now installable. Current state is: failing
• torch.0.12 on 5.1 is now installable. Current state is: failing
• torch.0.13 on 4.08 had its build status changed: passing to failing
• torch.0.13 on 4.09 had its build status changed: passing to failing
• torch.0.13 on 4.10 had its build status changed: passing to failing
• torch.0.13 on 4.11 had its build status changed: passing to failing
• torch.0.13 on 4.12 had its build status changed: passing to failing
• torch.0.13 on 4.13 had its build status changed: passing to failing
• torch.0.13 on 4.14 had its build status changed: not available to failing
• torch.0.13 on 5.0 is now installable. Current state is: failing
• torch.0.13 on 5.1 is now installable. Current state is: failing
• tplib.1.3 on 5.0 is now installable. Current state is: failing
• tplib.1.3 on 5.1 is now installable. Current state is: failing
• tsdl-image.0.1.2 on 4.08 had its build status changed: passing to failing
• tsdl-image.0.1.2 on 4.09 had its build status changed: passing to failing
• tsdl-image.0.1.2 on 4.10 had its build status changed: passing to failing
• tsdl-image.0.1.2 on 4.11 had its build status changed: passing to failing
• tsdl-image.0.1.2 on 4.12 had its build status changed: passing to failing
• tsdl-image.0.1.2 on 4.13 had its build status changed: passing to failing
• tsdl-image.0.1.2 on 4.14 had its build status changed: passing to failing
• tsdl-image.0.2.0 on 4.08 had its build status changed: passing to failing
• tsdl-image.0.2.0 on 4.09 had its build status changed: passing to failing
• tsdl-image.0.2.0 on 4.10 had its build status changed: passing to failing
• tsdl-image.0.2.0 on 4.11 had its build status changed: passing to failing
• tsdl-image.0.2.0 on 4.12 had its build status changed: passing to failing
• tsdl-image.0.2.0 on 4.13 had its build status changed: passing to failing
• tsdl.0.9.1 on 4.08 had its build status changed: passing to failing
• tsdl.0.9.1 on 4.09 had its build status changed: passing to failing
• tsdl.0.9.1 on 4.10 had its build status changed: passing to failing
• tsdl.0.9.1 on 4.11 had its build status changed: passing to failing
• tsdl.0.9.1 on 4.12 had its build status changed: passing to failing
• tsdl.0.9.1 on 4.13 had its build status changed: passing to failing
• tsdl.0.9.2 on 4.08 had its build status changed: passing to failing
• tsdl.0.9.2 on 4.09 had its build status changed: passing to failing
• tsdl.0.9.2 on 4.10 had its build status changed: passing to failing
• tsdl.0.9.2 on 4.11 had its build status changed: passing to failing
• tsdl.0.9.2 on 4.12 had its build status changed: passing to failing
• tsdl.0.9.2 on 4.13 had its build status changed: passing to failing
• tsdl.0.9.3 on 4.08 had its build status changed: passing to failing
• tsdl.0.9.3 on 4.09 had its build status changed: passing to failing
• tsdl.0.9.3 on 4.10 had its build status changed: passing to failing
• tsdl.0.9.3 on 4.11 had its build status changed: passing to failing
• tsdl.0.9.3 on 4.12 had its build status changed: passing to failing
• tsdl.0.9.3 on 4.13 had its build status changed: passing to failing
• tsdl.0.9.4 on 4.08 had its build status changed: passing to failing
• tsdl.0.9.4 on 4.09 had its build status changed: passing to failing
• tsdl.0.9.4 on 4.10 had its build status changed: passing to failing
• tsdl.0.9.4 on 4.11 had its build status changed: passing to failing
• tsdl.0.9.4 on 4.12 had its build status changed: passing to failing
• tsdl.0.9.4 on 4.13 had its build status changed: passing to failing
• tsdl.0.9.5 on 4.08 had its build status changed: passing to failing
• tsdl.0.9.5 on 4.09 had its build status changed: passing to failing
• tsdl.0.9.5 on 4.10 had its build status changed: passing to failing
• tsdl.0.9.5 on 4.11 had its build status changed: passing to failing
• tsdl.0.9.5 on 4.12 had its build status changed: passing to failing
• tsdl.0.9.5 on 4.13 had its build status changed: passing to failing
• tsdl.0.9.6 on 4.08 had its build status changed: passing to failing
• tsdl.0.9.6 on 4.09 had its build status changed: passing to failing
• tsdl.0.9.6 on 4.10 had its build status changed: passing to failing
• tsdl.0.9.6 on 4.11 had its build status changed: passing to failing
• tsdl.0.9.6 on 4.12 had its build status changed: passing to failing
• tsdl.0.9.6 on 4.13 had its build status changed: passing to failing
• tuareg.2.0.10 on 4.08 had its build status changed: passing to failing
• tuareg.2.0.10 on 4.09 had its build status changed: passing to failing
• tuareg.2.0.10 on 4.10 had its build status changed: passing to failing
• tuareg.2.0.10 on 4.11 had its build status changed: passing to failing
• tuareg.2.0.10 on 4.12 had its build status changed: passing to failing
• tuareg.2.0.10 on 4.13 had its build status changed: passing to failing
• tuareg.2.0.10 on 5.0 is now installable. Current state is: failing
• tuareg.2.0.10 on 5.1 is now installable. Current state is: failing
• tuareg.2.0.7 on 4.08 had its build status changed: passing to failing
• tuareg.2.0.7 on 4.09 had its build status changed: passing to failing
• tuareg.2.0.7 on 4.10 had its build status changed: passing to failing
• tuareg.2.0.7 on 4.11 had its build status changed: passing to failing
• tuareg.2.0.7 on 4.12 had its build status changed: passing to failing
• tuareg.2.0.7 on 4.13 had its build status changed: passing to failing
• tuareg.2.0.7 on 4.14 had its build status changed: passing to failing
• tuareg.2.0.7 on 5.0 is now installable. Current state is: failing
• tuareg.2.0.7 on 5.1 is now installable. Current state is: failing
• tuareg.2.1.0 on 4.09 had its build status changed: passing to failing
• tuareg.2.1.0 on 4.10 had its build status changed: passing to failing
• tuareg.2.1.0 on 4.12 had its build status changed: passing to failing
• tuareg.2.2.0 on 4.14 had its build status changed: passing to failing
• utop.2.10.0 on 5.0 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
• vcaml.v0.16.0 on 5.1 is now installable. Current state is: failing
• vhd-format.0.12.0 on 4.08 had its build status changed: passing to failing
• vhd-format.0.12.0 on 4.09 had its build status changed: passing to failing
• vhd-format.0.12.0 on 4.10 had its build status changed: passing to failing
• vhd-format.0.12.0 on 4.11 had its build status changed: passing to failing
• vhd-format.0.12.0 on 4.12 had its build status changed: passing to failing
• vhd-format.0.12.1 on 4.08 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
• 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
• x509.0.6.2 on 4.08 had its build status changed: passing to failing
• x509.0.6.2 on 4.09 had its build status changed: passing to failing
• x509.0.6.2 on 4.10 had its build status changed: passing to failing
• x509.0.6.2 on 4.11 had its build status changed: passing to failing
• x509.0.6.2 on 4.12 had its build status changed: passing to failing
• x509.0.6.2 on 4.13 had its build status changed: passing to failing
• yuscii.0.2.0 on 4.08 had its build status changed: passing to failing
• yuscii.0.2.0 on 4.09 had its build status changed: passing to failing
• yuscii.0.2.0 on 4.10 had its build status changed: passing to failing
• yuscii.0.2.0 on 4.11 had its build status changed: passing to failing
• z3.4.12.2 on 4.08 is now installable. Current state is: failing
• z3.4.12.2 on 4.09 is now installable. Current state is: failing
• z3.4.12.2 on 4.10 is now installable. Current state is: failing
• z3.4.12.2 on 4.11 is now installable. Current state is: failing
• z3.4.12.2 on 4.12 is now installable. Current state is: failing
• z3.4.12.2 on 4.13 is now installable. Current state is: failing
• z3.4.12.2 on 4.14 is now installable. Current state is: failing
• z3.4.12.2 on 5.0 is now installable. Current state is: failing
• z3.4.12.2 on 5.1 is now installable. Current state is: failing
• z3.4.8.14 on 5.0 is now installable. Current state is: failing
• z3.4.8.14 on 5.1 is now installable. Current state is: failing
• zelus.2.2 on 4.08 had its build status changed: passing to failing
• zelus.2.2 on 4.09 had its build status changed: passing to failing
• zelus.2.2 on 4.10 had its build status changed: passing to failing
• zelus.2.2 on 4.11 had its build status changed: passing to failing
• zelus.2.2 on 4.12 had its build status changed: passing to failing
• zelus.2.2 on 4.13 had its build status changed: passing to failing
• zelus.2.2 on 4.14 had its build status changed: passing to failing
• zelus.2.2 on 5.0 is now installable. Current state is: failing
• zelus.2.2 on 5.1 is now installable. Current state is: failing