Home|Differences with the last checks|Previous runs

Differences between 97da9a1 and 064e616 (git diff)

Packages now failing:

• acgtk.1.5.1 on 5.1 is now installable. Current state is: failing
• acpc.1.0 on 4.02 had its build status changed: passing to failing
• acpc.1.0 on 4.03 had its build status changed: passing to failing
• acpc.1.0 on 4.04 had its build status changed: passing to failing
• acpc.1.0 on 4.05 had its build status changed: passing to failing
• acpc.1.1 on 4.02 had its build status changed: passing to failing
• acpc.1.1 on 4.03 had its build status changed: passing to failing
• acpc.1.1 on 4.04 had its build status changed: passing to failing
• acpc.1.1 on 4.05 had its build status changed: passing to failing
• acpc.1.1.1 on 4.02 had its build status changed: passing to failing
• acpc.1.1.1 on 4.03 had its build status changed: passing to failing
• acpc.1.1.1 on 4.04 had its build status changed: passing to failing
• acpc.1.1.1 on 4.05 had its build status changed: passing to failing
• acpc.1.1.1 on 4.06 had its build status changed: passing to failing
• acpc.1.1.1 on 4.07 had its build status changed: passing to failing
• acpc.1.2 on 4.02 had its build status changed: passing to failing
• acpc.1.2 on 4.03 had its build status changed: passing to failing
• acpc.1.2 on 4.04 had its build status changed: passing to failing
• acpc.1.2 on 4.05 had its build status changed: passing to failing
• acpc.1.2.1 on 4.02 had its build status changed: passing to failing
• acpc.1.2.1 on 4.03 had its build status changed: passing to failing
• acpc.1.2.1 on 4.04 had its build status changed: passing to failing
• acpc.1.2.1 on 4.05 had its build status changed: passing to failing
• acpc.1.2.2 on 4.02 had its build status changed: passing to failing
• acpc.1.2.2 on 4.03 had its build status changed: passing to failing
• acpc.1.2.2 on 4.04 had its build status changed: passing to failing
• acpc.1.2.2 on 4.05 had its build status changed: passing to failing
• acpc.1.2.3 on 4.02 had its build status changed: passing to failing
• acpc.1.2.3 on 4.03 had its build status changed: passing to failing
• acpc.1.2.3 on 4.04 had its build status changed: passing to failing
• acpc.1.2.3 on 4.05 had its build status changed: passing to failing
• acpc.1.2.3 on 4.06 had its build status changed: passing to failing
• acpc.1.2.3 on 4.07 had its build status changed: passing to failing
• ahrocksdb.0.2.2 on 5.1 is now installable. Current state is: failing
• b0.0.0.2 on 5.1 is now installable. Current state is: failing
• b0.0.0.3 on 5.1 is now installable. Current state is: failing
• b0.0.0.4 on 5.1 is now installable. Current state is: failing
• bap-ghidra.2.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
• bap-objdump.1.3.0 on 4.02 had its build status changed: partially failing to failing
• batteries.3.6.0 on 5.1 is now installable. Current state is: failing
• binsec.0.3 on 4.06 had its build status changed: passing to failing
• binsec.0.3 on 4.07 had its build status changed: passing to failing
• bitmasks.1.4.0 on 5.1 is now installable. Current state is: failing
• bitwuzla-bin.0.0.0 on 5.1 is now installable. Current state is: failing
• blake3.0.1 on 5.1 is now installable. Current state is: failing
• bulletml.0.1.0 on 4.02 had its build status changed: partially failing to failing
• bulletml.0.1.0 on 4.03 had its build status changed: partially failing to failing
• bulletml.0.1.0 on 4.04 had its build status changed: partially failing to failing
• bulletml.0.2.0 on 4.02 had its build status changed: partially failing to failing
• bulletml.0.2.0 on 4.03 had its build status changed: partially failing to failing
• bulletml.0.2.0 on 4.04 had its build status changed: partially failing to failing
• camllib.1.3.3 on 5.1 is now installable. Current state is: failing
• camlmix.1.3.0 on 5.1 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
• combine.0.6 on 5.0 had its build status changed: internal failure to failing
• combine.0.6 on 5.1 is now installable. Current state is: failing
• conf-libclang.12 on 5.1 is now installable. Current state is: failing
• conf-python-3-7.1.0.0 on 4.02 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.03 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.04 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.05 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.06 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.07 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.08 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.09 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.10 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.11 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.12 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.13 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 4.14 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 5.0 had its build status changed: passing to failing
• conf-python-3-7.1.0.0 on 5.1 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.02 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.03 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.04 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.05 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.06 is now installable. Current state is: failing
• conf-trexio.0.1 on 4.07 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
• coq.8.12.1 on 4.07 had its build status changed: passing to failing
• coq.8.12.2 on 4.11 had its build status changed: passing to failing
• coq.8.13.0 on 4.06 had its build status changed: passing to failing
• coq.8.13.2 on 4.14 had its build status changed: passing to failing
• coq.8.14.1 on 4.07 had its build status changed: passing to failing
• coqide.8.4.5 on 4.02 had its build status changed: passing to failing
• coqide.8.4.6 on 4.02 had its build status changed: passing to failing
• csvfields.v0.15.0 on 5.0 had its build status changed: not available to failing
• datakit-client-9p.0.12.0 on 4.12 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.0 on 4.13 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.2 on 4.08 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.2 on 4.09 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.2 on 4.10 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.2 on 4.11 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.2 on 4.12 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.2 on 4.13 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.3 on 4.08 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.3 on 4.09 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.3 on 4.10 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.3 on 4.11 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.3 on 4.12 had its build status changed: partially failing to failing
• datakit-client-9p.0.12.3 on 4.13 had its build status changed: partially failing to failing
• datakit-client-9p.1.0.0 on 4.08 had its build status changed: partially failing to failing
• datakit-client-9p.1.0.0 on 4.09 had its build status changed: partially failing to failing
• datakit-client-9p.1.0.0 on 4.10 had its build status changed: partially failing to failing
• datakit-client-9p.1.0.0 on 4.11 had its build status changed: partially failing to failing
• datakit-client-9p.1.0.0 on 4.12 had its build status changed: partially failing to failing
• datakit-client-9p.1.0.0 on 4.13 had its build status changed: partially failing to failing
• datakit.0.12.2 on 4.04 had its build status changed: partially failing to failing
• datakit.0.12.2 on 4.05 had its build status changed: partially failing to failing
• datakit.0.12.3 on 4.04 had its build status changed: partially failing to failing
• datakit.0.12.3 on 4.05 had its build status changed: partially failing to failing
• datakit.1.0.0 on 4.04 had its build status changed: partially failing to failing
• datakit.1.0.0 on 4.05 had its build status changed: partially failing 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
• disml.0.2.5 on 4.05 had its build status changed: passing to failing
• distributed.0.6.0 on 5.1 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.1 is now installable. Current state is: failing
• docker-api.0.2.2 on 5.1 is now installable. Current state is: failing
• domainslib.0.3.0 on 5.1 is now installable. Current state is: failing
• domainslib.0.3.1 on 5.1 is now installable. Current state is: failing
• domainslib.0.4.0 on 5.1 is now installable. Current state is: failing
• domainslib.0.4.1 on 5.1 is now installable. Current state is: failing
• duff.0.2 on 5.1 is now installable. Current state is: failing
• duff.0.3 on 5.1 is now installable. Current state is: failing
• duff.0.4 on 5.1 is now installable. Current state is: failing
• duff.0.5 on 5.1 is now installable. Current state is: failing
• eigen.0.1.4 on 5.1 is now installable. Current state is: failing
• eigen.0.1.5 on 5.1 is now installable. Current state is: failing
• errpy.0.0.7 on 4.02 is now installable. Current state is: failing
• errpy.0.0.7 on 4.03 is now installable. Current state is: failing
• facile.1.1 on 5.1 is now installable. Current state is: failing
• fasmifra.1.0.0 on 4.03 had its build status changed: passing to failing
• fasmifra.1.0.0 on 4.04 had its build status changed: passing to failing
• fasmifra.1.0.0 on 4.05 had its build status changed: passing to failing
• fasmifra.1.0.0 on 4.06 had its build status changed: passing to failing
• fasmifra.1.0.0 on 4.07 had its build status changed: passing to failing
• fasmifra.1.1.0 on 4.03 had its build status changed: passing to failing
• fasmifra.1.1.0 on 4.04 had its build status changed: passing to failing
• fasmifra.1.1.0 on 4.05 had its build status changed: passing to failing
• fasmifra.1.1.0 on 4.06 had its build status changed: passing to failing
• fasmifra.1.1.0 on 4.07 had its build status changed: passing to failing
• frama-c.21.1 on 4.06 had its build status changed: passing to failing
• gammu.0.9.3 on 5.1 is now installable. Current state is: failing
• get_line.2.1.1 on 4.02 had its build status changed: passing to failing
• get_line.2.1.1 on 4.03 had its build status changed: passing to failing
• get_line.2.1.1 on 4.04 had its build status changed: passing to failing
• get_line.2.1.1 on 4.05 had its build status changed: passing to failing
• get_line.2.1.1 on 4.06 had its build status changed: passing to failing
• get_line.2.1.1 on 4.07 had its build status changed: passing to failing
• get_line.3.0.0 on 4.02 had its build status changed: passing to failing
• get_line.3.0.0 on 4.03 had its build status changed: passing to failing
• get_line.3.0.0 on 4.04 had its build status changed: passing to failing
• get_line.3.0.0 on 4.05 had its build status changed: passing to failing
• get_line.3.0.0 on 4.06 had its build status changed: passing to failing
• get_line.3.0.0 on 4.07 had its build status changed: passing to failing
• get_line.7.0.0 on 4.02 had its build status changed: passing to failing
• get_line.7.0.0 on 4.03 had its build status changed: passing to failing
• get_line.7.0.0 on 4.04 had its build status changed: passing to failing
• get_line.7.0.0 on 4.05 had its build status changed: passing to failing
• get_line.7.0.0 on 4.06 had its build status changed: passing to failing
• get_line.7.0.0 on 4.07 had its build status changed: passing to failing
• git-unix.3.2.0 on 4.08 had its build status changed: partially failing to failing
• git-unix.3.2.0 on 4.09 had its build status changed: partially failing to failing
• git-unix.3.2.0 on 4.10 had its build status changed: partially failing to failing
• git-unix.3.2.0 on 4.11 had its build status changed: partially failing to failing
• git-unix.3.2.0 on 4.12 had its build status changed: partially failing to failing
• git-unix.3.3.0 on 4.08 had its build status changed: partially failing to failing
• git-unix.3.3.0 on 4.09 had its build status changed: partially failing to failing
• git-unix.3.3.0 on 4.10 had its build status changed: partially failing to failing
• git-unix.3.3.0 on 4.11 had its build status changed: partially failing to failing
• git-unix.3.3.0 on 4.12 had its build status changed: partially failing to failing
• git-unix.3.3.1 on 4.08 had its build status changed: partially failing to failing
• git-unix.3.3.1 on 4.09 had its build status changed: partially failing to failing
• git-unix.3.3.1 on 4.10 had its build status changed: partially failing to failing
• git-unix.3.3.1 on 4.11 had its build status changed: partially failing to failing
• git-unix.3.3.1 on 4.12 had its build status changed: partially failing to failing
• git-unix.3.3.2 on 4.08 had its build status changed: partially failing to failing
• git-unix.3.3.2 on 4.09 had its build status changed: partially failing to failing
• git-unix.3.3.2 on 4.10 had its build status changed: partially failing to failing
• git-unix.3.3.2 on 4.11 had its build status changed: partially failing to failing
• git-unix.3.3.2 on 4.12 had its build status changed: partially failing to failing
• git-unix.3.3.3 on 4.08 had its build status changed: partially failing to failing
• git-unix.3.3.3 on 4.09 had its build status changed: partially failing to failing
• git-unix.3.3.3 on 4.10 had its build status changed: partially failing to failing
• git-unix.3.3.3 on 4.11 had its build status changed: partially failing to failing
• git-unix.3.3.3 on 4.12 had its build status changed: partially failing to failing
• goblint-cil.1.8.0 on 4.04 had its build status changed: passing to failing
• goblint-cil.1.8.0 on 4.05 had its build status changed: passing to failing
• goblint-cil.1.8.0 on 4.06 had its build status changed: passing to failing
• goblint-cil.1.8.0 on 4.07 had its build status changed: passing to failing
• goblint-cil.1.8.2 on 4.05 had its build status changed: passing to failing
• goblint-cil.1.8.2 on 4.06 had its build status changed: passing to failing
• goblint-cil.1.8.2 on 4.07 had its build status changed: passing to failing
• grenier.0.11 on 5.1 is now installable. Current state is: failing
• grenier.0.12 on 5.1 is now installable. Current state is: failing
• grenier.0.13 on 5.1 is now installable. Current state is: failing
• grenier.0.14 on 5.1 is now installable. Current state is: failing
• gsl.1.24.3 on 4.13 had its build status changed: passing to failing
• hevea.2.25 on 5.1 is now installable. Current state is: failing
• hevea.2.28 on 5.1 is now installable. Current state is: failing
• hevea.2.29 on 5.1 is now installable. Current state is: failing
• hevea.2.32 on 5.1 is now installable. Current state is: failing
• hevea.2.35 on 5.1 is now installable. Current state is: failing
• hts_shrink.2.0.0 on 4.03 had its build status changed: passing to failing
• hts_shrink.2.0.0 on 4.04 had its build status changed: passing to failing
• hts_shrink.2.0.0 on 4.05 had its build status changed: passing to failing
• hts_shrink.2.0.0 on 4.06 had its build status changed: passing to failing
• hts_shrink.2.0.0 on 4.07 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.03 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.04 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.05 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.06 had its build status changed: passing to failing
• hts_shrink.2.1.0 on 4.07 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.03 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.04 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.05 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.06 had its build status changed: passing to failing
• hts_shrink.2.1.1 on 4.07 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.03 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.04 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.05 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.06 had its build status changed: passing to failing
• hts_shrink.2.1.2 on 4.07 had its build status changed: passing to 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
• iocamljs-kernel.0.4.6 on 4.02 had its build status changed: partially failing to failing
• iocamljs-kernel.0.4.6 on 4.03 had its build status changed: partially failing to failing
• iocamljs-kernel.0.4.6 on 4.04 had its build status changed: partially failing to failing
• jupyter-kernel.0.4 on 4.08 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.09 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.10 had its build status changed: passing to failing
• jupyter-kernel.0.4 on 4.11 had its build status changed: passing to failing
• jupyter.2.1.0 on 4.02 had its build status changed: passing to failing
• ketrew.3.1.0 on 4.04 had its build status changed: partially failing to failing
• ketrew.3.2.0 on 4.04 had its build status changed: partially failing to failing
• kind2.1.5.0 on 5.1 is now installable. Current state is: failing
• kinetic-client.0.0.1 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.1 on 4.07 had its build status changed: not available 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.3 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.3 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.4 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.4 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.5 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.5 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.6 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.6 on 4.07 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.06 had its build status changed: not available to failing
• kinetic-client.0.0.9 on 4.07 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.1 is now installable. Current state is: failing
• labltk.8.06.12 on 4.14 had its build status changed: passing to failing
• labltk.8.06.12 on 5.1 is now installable. Current state is: failing
• libssh.0.1 on 4.14 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.02 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.03 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.04 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.05 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.06 had its build status changed: passing to failing
• linwrap.0.0.1 on 4.07 had its build status changed: passing to failing
• lua-ml.0.9 on 5.1 is now installable. Current state is: failing
• luv.0.5.0 on 5.1 is now installable. Current state is: failing
• mccs.1.1+11 on 5.0 had its build status changed: partially failing to failing
• mccs.1.1+11 on 5.1 is now installable. Current state is: failing
• memtrace.0.1 on 5.1 is now installable. Current state is: failing
• menhir.20220210 on 5.1 is now installable. Current state is: failing
• mesh-triangle.0.9.5 on 5.1 is now installable. Current state is: failing
• meta_conv.1.1.5 on 4.02 had its build status changed: passing to failing
• minios-xen.0.7 on 4.02 had its build status changed: passing to failing
• minios-xen.0.7 on 4.03 had its build status changed: passing to failing
• minios-xen.0.7 on 4.04 had its build status changed: passing to failing
• minios-xen.0.7 on 4.05 had its build status changed: passing to failing
• minios-xen.0.7 on 4.06 had its build status changed: passing to failing
• minios-xen.0.7 on 4.07 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 had its build status changed: passing to failing
• minios-xen.0.7 on 5.1 is now installable. Current state is: failing
• minisat.0.3 on 5.1 is now installable. Current state is: failing
• minisat.0.4 on 5.1 is now installable. Current state is: failing
• mirage-fs-unix.1.6.0 on 5.0 had its build status changed: partially failing to failing
• mirage-fs-unix.1.6.0 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.2 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 4.07 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 had its build status changed: passing to failing
• mirage-xen-minios.0.2 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.3 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to failing
• mirage-xen-minios.0.3 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.4 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to failing
• mirage-xen-minios.0.4 on 5.1 is now installable. Current state is: failing
• mirage-xen-minios.0.4.1 on 4.02 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.4.1 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.4.2 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.5.0 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.06 had its build status changed: passing to failing
• mirage-xen-minios.0.6.0 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.03 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.04 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.05 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 4.06 had its build status changed: passing to 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 had its build status changed: passing to failing
• mirage-xen-minios.0.7.0 on 5.1 is now installable. Current state is: failing
• molenc.0.0.1 on 4.04 had its build status changed: passing to failing
• molenc.0.0.1 on 4.05 had its build status changed: passing to failing
• molenc.0.0.1 on 4.06 had its build status changed: passing to failing
• molenc.0.0.1 on 4.07 had its build status changed: passing to failing
• molenc.1.0.0 on 4.04 had its build status changed: passing to failing
• molenc.1.0.0 on 4.05 had its build status changed: passing to failing
• molenc.1.0.0 on 4.06 had its build status changed: passing to failing
• molenc.1.0.0 on 4.07 had its build status changed: passing to failing
• molenc.1.1.0 on 4.04 had its build status changed: passing to failing
• molenc.1.1.0 on 4.05 had its build status changed: passing to failing
• molenc.1.1.0 on 4.06 had its build status changed: passing to failing
• molenc.1.1.0 on 4.07 had its build status changed: passing to failing
• molenc.11.4.0 on 4.06 had its build status changed: passing to failing
• molenc.11.4.0 on 4.07 had its build status changed: passing to failing
• molenc.2.0.0 on 4.04 had its build status changed: passing to failing
• molenc.2.0.0 on 4.05 had its build status changed: passing to failing
• molenc.2.0.0 on 4.06 had its build status changed: passing to failing
• molenc.2.0.0 on 4.07 had its build status changed: passing to failing
• molenc.4.0.2 on 4.04 had its build status changed: passing to failing
• molenc.4.0.2 on 4.05 had its build status changed: passing to failing
• molenc.4.0.2 on 4.06 had its build status changed: passing to failing
• molenc.4.0.2 on 4.07 had its build status changed: passing to failing
• molenc.5.0.0 on 4.04 had its build status changed: passing to failing
• molenc.5.0.0 on 4.05 had its build status changed: passing to failing
• molenc.5.0.0 on 4.06 had its build status changed: passing to failing
• molenc.5.0.0 on 4.07 had its build status changed: passing to failing
• molenc.5.0.1 on 4.04 had its build status changed: passing to failing
• molenc.5.0.1 on 4.05 had its build status changed: passing to failing
• molenc.5.0.1 on 4.06 had its build status changed: passing to failing
• molenc.5.0.1 on 4.07 had its build status changed: passing to failing
• molenc.7.0.1 on 4.02 had its build status changed: passing to failing
• molenc.7.0.1 on 4.03 had its build status changed: passing to failing
• molenc.7.0.1 on 4.04 had its build status changed: passing to failing
• molenc.7.0.1 on 4.05 had its build status changed: passing to failing
• molenc.7.0.1 on 4.06 had its build status changed: passing to failing
• molenc.7.0.1 on 4.07 had its build status changed: passing to failing
• molenc.8.0.2 on 4.02 had its build status changed: passing to failing
• molenc.8.0.2 on 4.03 had its build status changed: passing to failing
• molenc.8.0.2 on 4.04 had its build status changed: passing to failing
• molenc.8.0.2 on 4.05 had its build status changed: passing to failing
• molenc.8.0.2 on 4.06 had its build status changed: passing to failing
• molenc.8.0.2 on 4.07 had its build status changed: passing to failing
• mosquitto.0.1-0 on 5.1 is now installable. Current state is: failing
• mparser.1.2.1 on 5.0 had its build status changed: internal failure to failing
• mparser.1.2.1 on 5.1 is now installable. Current state is: failing
• multicont.1.0.0~rc.1 on 5.1 is now installable. Current state is: failing
• mysql8.1.0 on 5.0 had its build status changed: not available to failing
• netkat.0.1 on 4.08 had its build status changed: internal failure to failing
• netkat.0.1 on 4.09 had its build status changed: internal failure to failing
• netkat.0.1 on 4.10 had its build status changed: internal failure to failing
• netkat.0.1 on 4.11 had its build status changed: internal failure to failing
• ocaml-freestanding.0.2.1 on 4.02 had its build status changed: passing to failing
• ocaml-freestanding.0.2.1 on 4.03 had its build status changed: passing to failing
• ocaml-freestanding.0.2.1 on 4.04 had its build status changed: passing to failing
• ocaml-freestanding.0.2.2 on 4.02 had its build status changed: passing to failing
• ocaml-freestanding.0.2.2 on 4.03 had its build status changed: passing to failing
• ocaml-freestanding.0.2.2 on 4.04 had its build status changed: passing to failing
• ocaml-freestanding.0.2.2 on 4.05 had its build status changed: passing to failing
• ocaml-gist.0.0.1 on 4.04 had its build status changed: partially failing to failing
• ocaml-makefile.6.37.0 on 5.1 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.1 is now installable. Current state is: failing
• ocaml-r.0.3.1 on 5.0 had its build status changed: not available to failing
• ocaml-r.0.3.1 on 5.1 is now installable. Current state is: failing
• ocaml-r.0.4.0 on 5.0 had its build status changed: not available to failing
• ocaml-r.0.4.0 on 5.1 is now installable. Current state is: failing
• ocaml-r.0.5.0 on 5.0 had its build status changed: not available to failing
• ocaml-r.0.5.0 on 5.1 is now installable. Current state is: failing
• ocaml-twt.0.93 on 5.1 is now installable. Current state is: failing
• ocaml-twt.0.93.2 on 5.1 is now installable. Current state is: failing
• ocaml-twt.0.94.0 on 5.1 is now installable. Current state is: failing
• ocamldiff.1.1 on 5.1 is now installable. Current state is: failing
• ocp-index-top.0.4.1 on 4.08 had its build status changed: passing to failing
• ocp-index-top.0.4.1 on 4.09 had its build status changed: passing to failing
• ocp-index-top.0.4.3 on 4.08 had its build status changed: passing to failing
• ocp-index-top.0.4.3 on 4.09 had its build status changed: passing to failing
• ocp-index-top.0.5.0 on 4.08 had its build status changed: passing to failing
• ocp-index-top.0.5.0 on 4.09 had its build status changed: passing to failing
• ocp-index.1.3.3 on 5.1 is now installable. Current state is: failing
• ocp-index.1.3.4 on 5.1 is now installable. Current state is: failing
• ocp-pack-split.1.0.1 on 5.1 is now installable. Current state is: failing
• ocplib-simplex.0.3 on 5.1 is now installable. Current state is: failing
• ocplib-simplex.0.4 on 5.1 is now installable. Current state is: failing
• odepack.0.6.9 on 5.1 is now installable. Current state is: failing
• odepack.0.7 on 5.1 is now installable. Current state is: failing
• odoc.2.1.1 on 5.1 is now installable. Current state is: failing
• odoc.2.2.0 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 had its build status changed: passing to failing
• ogg.0.7.2 on 4.14 is now installable. Current state is: failing
• ojs-base.0.5.0 on 4.04 had its build status changed: partially failing to failing
• olinq.0.1 on 5.1 is now installable. Current state is: failing
• olinq.0.2 on 5.1 is now installable. Current state is: failing
• olinq.0.3 on 5.1 is now installable. Current state is: failing
• opam-depext.1.2.0 on 5.1 is now installable. Current state is: failing
• opam-file-format.2.1.2 on 5.1 is now installable. Current state is: failing
• opam-file-format.2.1.3 on 5.1 is now installable. Current state is: failing
• opam-file-format.2.1.4 on 5.1 is now installable. Current state is: failing
• opam-monorepo.0.3.4 on 5.1 is now installable. Current state is: failing
• opam-monorepo.0.3.5 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.4 on 4.08 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.09 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.10 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.11 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.12 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.13 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 4.14 is now installable. Current state is: failing
• opentelemetry-cohttp-lwt.0.4 on 5.0 is now installable. Current state is: failing
• operf-micro.1.1.1 on 5.1 is now installable. Current state is: failing
• oplsr.8.0.1 on 5.0 had its build status changed: not available to 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
• orpie.1.6.0 on 4.05 had its build status changed: passing to failing
• orpie.1.6.1 on 4.05 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 5.1 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.08 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.09 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.10 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.11 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.12 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.13 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 4.14 is now installable. Current state is: failing
• paf-cohttp.0.5.0 on 5.0 is now installable. Current state is: failing
• paf.0.0.1 on 4.08 had its build status changed: passing to failing
• paf.0.0.1 on 4.09 had its build status changed: passing to failing
• paf.0.0.1 on 4.10 had its build status changed: passing to failing
• paf.0.0.1 on 4.11 had its build status changed: passing to failing
• paf.0.0.1 on 4.12 had its build status changed: passing to failing
• paf.0.0.1 on 4.13 had its build status changed: passing to failing
• paf.0.0.1 on 4.14 had its build status changed: passing to failing
• paf.0.0.1 on 5.0 had its build status changed: not available to failing
• paf.0.0.2 on 4.08 had its build status changed: passing to failing
• paf.0.0.2 on 4.09 had its build status changed: passing to failing
• paf.0.0.2 on 4.10 had its build status changed: passing to failing
• paf.0.0.2 on 4.11 had its build status changed: passing to failing
• paf.0.0.2 on 4.12 had its build status changed: passing to failing
• paf.0.0.2 on 4.13 had its build status changed: passing to failing
• paf.0.0.2 on 4.14 had its build status changed: passing to failing
• paf.0.0.3 on 4.08 had its build status changed: passing to failing
• paf.0.0.3 on 4.09 had its build status changed: passing to failing
• paf.0.0.3 on 4.10 had its build status changed: passing to failing
• paf.0.0.3 on 4.11 had its build status changed: passing to failing
• paf.0.0.3 on 4.12 had its build status changed: passing to failing
• paf.0.0.3 on 4.13 had its build status changed: passing to failing
• paf.0.0.3 on 4.14 had its build status changed: passing to failing
• papi.0.1.1 on 5.1 is now installable. Current state is: failing
• pardi.1.0.1 on 4.05 had its build status changed: passing to failing
• pardi.1.0.1 on 4.06 had its build status changed: passing to failing
• pardi.1.0.1 on 4.07 had its build status changed: passing to failing
• pardi.2.0.2 on 4.05 had its build status changed: passing to failing
• pardi.2.0.2 on 4.06 had its build status changed: passing to failing
• pardi.2.0.2 on 4.07 had its build status changed: passing to failing
• pardi.2.0.3 on 4.05 had its build status changed: passing to failing
• pardi.2.0.3 on 4.06 had its build status changed: passing to failing
• pardi.2.0.3 on 4.07 had its build status changed: passing to failing
• pardi.2.0.4 on 4.05 had its build status changed: passing to failing
• pardi.2.0.4 on 4.06 had its build status changed: passing to failing
• pardi.2.0.4 on 4.07 had its build status changed: passing to failing
• pds-reachability.0.2 on 4.07 had its build status changed: passing to failing
• pds-reachability.0.2.1 on 4.07 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.02 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.03 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.04 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.05 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.06 had its build status changed: passing to failing
• ppx_nanocaml.0.1 on 4.07 had its build status changed: passing to 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
• protocol-9p.1.0.0 on 5.0 had its build status changed: not available to failing
• protocol-9p.1.0.1 on 5.0 had its build status changed: not available to failing
• proverif.2.00 on 5.0 had its build status changed: not available to failing
• proverif.2.00 on 5.1 is now installable. Current state is: failing
• randoml.0.1.5 on 5.0 had its build status changed: not available to failing
• resto-cohttp-server.1.1 on 4.10 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 4.11 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 4.12 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 4.13 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 4.14 is now installable. Current state is: failing
• resto-cohttp-server.1.1 on 5.0 is now installable. Current state is: failing
• rml.1.09.06 on 5.1 is now installable. Current state is: failing
• rml.1.09.07 on 5.1 is now installable. Current state is: failing
• rmlbuild.0.14.0-00 on 5.1 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.02 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.03 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.04 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.06 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.5 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.6 on 4.07 had its build status changed: passing to 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.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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.7 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.8 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.03 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.04 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.05 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.06 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.07 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.09 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.10 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.11 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.12 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.13 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 4.14 had its build status changed: passing to failing
• solo5-bindings-hvt.0.6.9 on 5.0 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.03 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.04 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.05 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.06 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.5 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.6 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.7 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.8 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.03 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.04 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.05 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.06 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.07 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.08 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.09 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.10 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.11 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.12 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.13 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 4.14 had its build status changed: passing to failing
• solo5-bindings-muen.0.6.9 on 5.0 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.03 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.04 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.05 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.06 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.5 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.6 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.7 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.8 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.03 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.04 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.05 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.06 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.07 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.08 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.09 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.10 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.11 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.12 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.13 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 4.14 had its build status changed: passing to failing
• solo5-bindings-spt.0.6.9 on 5.0 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.03 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.04 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.05 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.06 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.5 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.6 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.7 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.8 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.03 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.04 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.05 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.06 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.07 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.08 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.09 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.10 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.11 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.12 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.13 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 4.14 had its build status changed: passing to failing
• solo5-bindings-virtio.0.6.9 on 5.0 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.03 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.04 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.05 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.06 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.6 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.03 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.04 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.05 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.06 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.7 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.03 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.04 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.05 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.06 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.8 on 4.07 had its build status changed: passing to 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 had its build status changed: passing to 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.02 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.03 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.04 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.05 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.06 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.07 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.08 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.09 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.10 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.11 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.12 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.13 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 4.14 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 5.0 had its build status changed: passing to failing
• solo5-bindings-xen.0.6.9 on 5.1 is now installable. Current state is: failing
• solo5.0.7.0 on 4.02 had its build status changed: passing to failing
• solo5.0.7.0 on 4.03 had its build status changed: passing to failing
• solo5.0.7.0 on 4.04 had its build status changed: passing to failing
• solo5.0.7.0 on 4.05 had its build status changed: passing to failing
• solo5.0.7.0 on 4.06 had its build status changed: passing to failing
• solo5.0.7.0 on 4.07 had its build status changed: passing to failing
• solo5.0.7.0 on 4.08 had its build status changed: passing to failing
• solo5.0.7.0 on 4.09 had its build status changed: passing to failing
• solo5.0.7.0 on 4.10 had its build status changed: passing to failing
• solo5.0.7.0 on 4.11 had its build status changed: passing to failing
• solo5.0.7.0 on 4.12 had its build status changed: passing to failing
• solo5.0.7.0 on 4.13 had its build status changed: passing to failing
• solo5.0.7.0 on 4.14 had its build status changed: passing to failing
• solo5.0.7.0 on 5.0 had its build status changed: passing to failing
• solo5.0.7.0 on 5.1 is now installable. Current state is: failing
• solo5.0.7.1 on 4.02 had its build status changed: passing to failing
• solo5.0.7.1 on 4.03 had its build status changed: passing to failing
• solo5.0.7.1 on 4.04 had its build status changed: passing to failing
• solo5.0.7.1 on 4.05 had its build status changed: passing to failing
• solo5.0.7.1 on 4.06 had its build status changed: passing to failing
• solo5.0.7.1 on 4.07 had its build status changed: passing to failing
• solo5.0.7.1 on 4.08 had its build status changed: passing to failing
• solo5.0.7.1 on 4.09 had its build status changed: passing to failing
• solo5.0.7.1 on 4.10 had its build status changed: passing to failing
• solo5.0.7.1 on 4.11 had its build status changed: passing to failing
• solo5.0.7.1 on 4.12 had its build status changed: passing to failing
• solo5.0.7.1 on 4.13 had its build status changed: passing to failing
• solo5.0.7.1 on 4.14 had its build status changed: passing to failing
• solo5.0.7.1 on 5.0 had its build status changed: passing to failing
• solo5.0.7.1 on 5.1 is now installable. Current state is: failing
• sphinxcontrib-ocaml.0.2.0 on 4.05 had its build status changed: partially failing to failing
• srt.0.2.2 on 4.03 is now installable. Current state is: failing
• srt.0.2.2 on 4.04 is now installable. Current state is: failing
• srt.0.2.2 on 4.05 is now installable. Current state is: failing
• srt.0.2.2 on 4.06 is now installable. Current state is: failing
• srt.0.2.2 on 4.07 is now installable. Current state is: failing
• srt.0.3.0 on 4.03 is now installable. Current state is: failing
• srt.0.3.0 on 4.04 is now installable. Current state is: failing
• srt.0.3.0 on 4.05 is now installable. Current state is: failing
• srt.0.3.0 on 4.06 is now installable. Current state is: failing
• srt.0.3.0 on 4.07 is now installable. Current state is: failing
• stb_truetype.0.5 on 4.02 had its build status changed: passing to failing
• stb_truetype.0.5 on 4.03 had its build status changed: passing to failing
• stb_truetype.0.5 on 4.04 had its build status changed: passing to failing
• stb_truetype.0.6 on 4.02 had its build status changed: passing to failing
• stb_truetype.0.6 on 4.03 had its build status changed: passing to failing
• stb_truetype.0.6 on 4.04 had its build status changed: passing to failing
• stdcompat.0 on 5.1 is now installable. Current state is: failing
• stdcompat.1 on 5.1 is now installable. Current state is: failing
• stog.0.20.0 on 4.12 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.03 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.04 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.05 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.06 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.07 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.08 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.09 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.10 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.11 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.12 had its build status changed: passing to failing
• sundialsml.5.8.0p0 on 4.13 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.03 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.04 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.05 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.06 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.07 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.08 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.09 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.10 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.11 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.12 had its build status changed: passing to failing
• sundialsml.6.0.0p0 on 4.13 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.03 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.04 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.05 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.06 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.07 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.08 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.09 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.10 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.11 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.12 had its build status changed: passing to failing
• sundialsml.6.1.0p0 on 4.13 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.03 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.04 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.05 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.06 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.07 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.08 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.09 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.10 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.11 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.12 had its build status changed: passing to failing
• sundialsml.6.1.1p0 on 4.13 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.03 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.04 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.05 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.06 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.07 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.08 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.09 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.10 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.11 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.12 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.13 had its build status changed: passing to failing
• sundialsml.6.1.1p1 on 4.14 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: passing to failing
• tezos-sapling.11.1 on 4.12 had its build status changed: passing to failing
• tezos-sapling.11.1 on 4.13 had its build status changed: passing to failing
• tezos-sapling.11.1 on 4.14 had its build status changed: passing to failing
• tezos-sapling.12.0 on 4.12 had its build status changed: passing to failing
• tezos-sapling.12.0 on 4.13 had its build status changed: passing to failing
• tezos-sapling.12.0 on 4.14 had its build status changed: passing to failing
• tezos-sapling.12.3 on 4.12 had its build status changed: passing to failing
• tezos-sapling.12.3 on 4.13 had its build status changed: passing to failing
• tezos-sapling.12.3 on 4.14 had its build status changed: passing to failing
• tezos-stdlib-unix.10.2 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.10.2 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.10.2 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.10.2 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.8.0 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.8.0 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.8.0 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.8.0 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.8.1 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.8.1 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.8.1 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.8.1 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.8.2 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.8.2 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.8.2 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.8.2 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.8.3 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.8.3 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.8.3 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.8.3 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.0 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.1 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.2 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.2 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.2 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.2 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.3 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.3 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.3 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.3 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.4 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.4 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.4 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.4 on 4.11 had its build status changed: passing to failing
• tezos-stdlib-unix.9.7 on 4.08 had its build status changed: passing to failing
• tezos-stdlib-unix.9.7 on 4.09 had its build status changed: passing to failing
• tezos-stdlib-unix.9.7 on 4.10 had its build status changed: passing to failing
• tezos-stdlib-unix.9.7 on 4.11 had its build status changed: passing to failing
• toplevel_backend.v0.15.0 on 5.0 had its build status changed: not available to failing
• toplevel_expect_test.v0.15.0 on 5.0 had its build status changed: not available to failing
• tplib.1.3 on 5.1 is now installable. Current state is: failing
• utop.2.10.0 on 5.1 is now installable. Current state is: failing
• utop.2.11.0 on 5.1 is now installable. Current state is: failing
• wasm.2.0.0 on 5.1 is now installable. Current state is: failing
• websocket-async.2.16 on 4.11 is now installable. Current state is: failing
• websocket-async.2.16 on 4.12 is now installable. Current state is: failing
• websocket-async.2.16 on 4.13 is now installable. Current state is: failing
• websocket-async.2.16 on 4.14 is now installable. Current state is: failing
• websocket-async.2.16 on 5.0 is now installable. Current state is: failing
• xtmpl.0.13.0 on 4.02 had its build status changed: partially failing to failing
• xtmpl.0.14.0 on 4.03 had its build status changed: partially failing to failing
• xtmpl.0.14.0 on 4.04 had its build status changed: partially failing to failing
• xtmpl.0.15.0 on 4.03 had its build status changed: partially failing to failing
• xtmpl.0.15.0 on 4.04 had its build status changed: partially failing to failing
• z3.4.11.0 on 5.0 is now installable. Current state is: failing
• z3.4.8.13 on 4.02 had its build status changed: passing to failing
• z3.4.8.14 on 5.0 had its build status changed: passing to failing
• z3.4.8.14 on 5.1 is now installable. Current state is: failing

Packages now partially failing:

• FrontC.4.0.0 on 5.1 is now installable. Current state is: partially failing
• FrontC.4.1.0 on 5.1 is now installable. Current state is: partially failing
• acgtk.1.5.2 on 5.1 is now installable. Current state is: partially failing
• acgtk.1.5.3 on 5.1 is now installable. Current state is: partially failing
• acp4.1.0.1 on 5.1 is now installable. Current state is: partially failing
• acpc.2.0.0 on 5.1 is now installable. Current state is: partially failing
• aifad.2.2.1 on 5.1 is now installable. Current state is: partially failing
• aifad.2.2.2 on 5.1 is now installable. Current state is: partially failing
• aifad.2.3.0 on 5.1 is now installable. Current state is: partially failing
• alonzo.0.4.0 on 5.1 is now installable. Current state is: partially failing
• alt-ergo-lib.2.4.2 on 5.1 is now installable. Current state is: partially failing
• alt-ergo-parsers.2.4.2 on 5.1 is now installable. Current state is: partially failing
• alt-ergo.2.4.2 on 5.1 is now installable. Current state is: partially failing
• altgr-ergo.2.4.2 on 5.1 is now installable. Current state is: partially failing
• anders.0.12.1 on 5.1 is now installable. Current state is: partially failing
• anders.0.7.1 on 5.1 is now installable. Current state is: partially failing
• anders.0.7.2 on 5.1 is now installable. Current state is: partially failing
• anders.1.1.1 on 5.1 is now installable. Current state is: partially failing
• atd.2.10.0 on 5.1 is now installable. Current state is: partially failing
• atd.2.11.0 on 5.1 is now installable. Current state is: partially failing
• atd.2.3.3 on 5.1 is now installable. Current state is: partially failing
• atd.2.4.0 on 5.1 is now installable. Current state is: partially failing
• atd.2.4.1 on 5.1 is now installable. Current state is: partially failing
• atd.2.5.0 on 5.1 is now installable. Current state is: partially failing
• atd.2.6.0 on 5.1 is now installable. Current state is: partially failing
• atd.2.7.0 on 5.1 is now installable. Current state is: partially failing
• atd.2.8.0 on 5.1 is now installable. Current state is: partially failing
• atd.2.9.1 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.10.0 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.11.0 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.3.3 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.4.0 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.4.1 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.5.0 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.6.0 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.7.0 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.8.0 on 5.1 is now installable. Current state is: partially failing
• atdgen.2.9.1 on 5.1 is now installable. Current state is: partially failing
• atdj.2.10.0 on 5.1 is now installable. Current state is: partially failing
• atdj.2.11.0 on 5.1 is now installable. Current state is: partially failing
• atdj.2.3.3 on 5.1 is now installable. Current state is: partially failing
• atdj.2.4.0 on 5.1 is now installable. Current state is: partially failing
• atdj.2.4.1 on 5.1 is now installable. Current state is: partially failing
• atdj.2.5.0 on 5.1 is now installable. Current state is: partially failing
• atdj.2.6.0 on 5.1 is now installable. Current state is: partially failing
• atdj.2.7.0 on 5.1 is now installable. Current state is: partially failing
• atdj.2.8.0 on 5.1 is now installable. Current state is: partially failing
• atdj.2.9.1 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.10.0 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.11.0 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.3.3 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.4.0 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.4.1 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.5.0 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.6.0 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.7.0 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.8.0 on 5.1 is now installable. Current state is: partially failing
• atdpy.2.9.1 on 5.1 is now installable. Current state is: partially failing
• atds.2.10.0 on 5.1 is now installable. Current state is: partially failing
• atds.2.11.0 on 5.1 is now installable. Current state is: partially failing
• atds.2.3.3 on 5.1 is now installable. Current state is: partially failing
• atds.2.4.0 on 5.1 is now installable. Current state is: partially failing
• atds.2.4.1 on 5.1 is now installable. Current state is: partially failing
• atds.2.5.0 on 5.1 is now installable. Current state is: partially failing
• atds.2.6.0 on 5.1 is now installable. Current state is: partially failing
• atds.2.7.0 on 5.1 is now installable. Current state is: partially failing
• atds.2.8.0 on 5.1 is now installable. Current state is: partially failing
• atds.2.9.1 on 5.1 is now installable. Current state is: partially failing
• atdts.2.10.0 on 5.1 is now installable. Current state is: partially failing
• atdts.2.11.0 on 5.1 is now installable. Current state is: partially failing
• atdts.2.5.0 on 5.1 is now installable. Current state is: partially failing
• atdts.2.6.0 on 5.1 is now installable. Current state is: partially failing
• atdts.2.7.0 on 5.1 is now installable. Current state is: partially failing
• atdts.2.8.0 on 5.1 is now installable. Current state is: partially failing
• atdts.2.9.1 on 5.1 is now installable. Current state is: partially failing
• bap-abi.1.3.0 on 4.02 had its build status changed: passing to partially failing
• bap-mc.1.0.0 on 4.02 had its build status changed: passing to partially failing
• bnfgen.2.0 on 5.1 is now installable. Current state is: partially failing
• bnfgen.3.0.0 on 5.1 is now installable. Current state is: partially failing
• bst.7.0.1 on 5.1 is now installable. Current state is: partially failing
• calculon-web.0.7 on 5.1 is now installable. Current state is: partially failing
• calculon-web.0.8 on 5.1 is now installable. Current state is: partially failing
• calipso.4.0.0 on 5.1 is now installable. Current state is: partially failing
• calipso.4.1.0 on 5.1 is now installable. Current state is: partially failing
• carton-git.0.4.4 on 5.1 is now installable. Current state is: partially failing
• carton-git.0.5.0 on 5.1 is now installable. Current state is: partially failing
• carton-git.0.6.0 on 5.1 is now installable. Current state is: partially failing
• carton-lwt.0.4.4 on 5.1 is now installable. Current state is: partially failing
• carton-lwt.0.5.0 on 5.1 is now installable. Current state is: partially failing
• carton-lwt.0.6.0 on 5.1 is now installable. Current state is: partially failing
• carton.0.4.4 on 5.1 is now installable. Current state is: partially failing
• carton.0.5.0 on 5.1 is now installable. Current state is: partially failing
• carton.0.6.0 on 5.1 is now installable. Current state is: partially failing
• cfg.2.3.0 on 5.1 is now installable. Current state is: partially failing
• cfgen.1.0 on 5.1 is now installable. Current state is: partially failing
• cfml.20211215 on 5.1 is now installable. Current state is: partially failing
• cfml.20220102 on 5.1 is now installable. Current state is: partially failing
• cfml.20220112 on 5.1 is now installable. Current state is: partially failing
• cmarker.0.3.0 on 5.1 is now installable. Current state is: partially failing
• cmon.0.1 on 5.1 is now installable. Current state is: partially failing
• cmon.0.2 on 5.1 is now installable. Current state is: partially failing
• coq-serapi.8.12.0+0.12.0 on 4.10 had its build status changed: passing to partially failing
• coq-serapi.8.12.0+0.12.1 on 4.10 had its build status changed: passing to partially failing
• coq-serapi.8.13.0+0.13.1 on 4.11 had its build status changed: passing to partially failing
• coq-serapi.8.15.0+0.15.0 on 4.10 had its build status changed: passing to partially failing
• coq-serapi.8.8.0+0.5.3 on 4.08 had its build status changed: passing to partially failing
• coq.8.15.1 on 4.06 had its build status changed: passing to partially failing
• coqide.8.10.2 on 4.07 had its build status changed: passing to partially failing
• cosovo.3 on 5.1 is now installable. Current state is: partially failing
• cpm.12.1.2 on 5.1 is now installable. Current state is: partially failing
• cpm.12.2.0 on 5.1 is now installable. Current state is: partially failing
• ctoxml.4.0.0 on 5.1 is now installable. Current state is: partially failing
• ctoxml.4.1.0 on 5.1 is now installable. Current state is: partially failing
• daft.0.0.4 on 5.1 is now installable. Current state is: partially failing
• daypack-lib.0.0.6 on 5.1 is now installable. Current state is: partially failing
• dedukti.2.6.0 on 5.1 is now installable. Current state is: partially failing
• dedukti.2.7 on 5.1 is now installable. Current state is: partially failing
• distributed-lwt.0.2.0 on 5.1 is now installable. Current state is: partially failing
• docteur-solo5.0.0.2 on 4.08 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.09 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.10 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.11 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.12 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.13 had its build status changed: passing to partially failing
• docteur-solo5.0.0.2 on 4.14 had its build status changed: passing to partially failing
• docteur.0.0.1 on 4.08 had its build status changed: passing to partially failing
• docteur.0.0.1 on 4.09 had its build status changed: passing to partially failing
• docteur.0.0.1 on 4.10 had its build status changed: passing to partially failing
• docteur.0.0.1 on 4.11 had its build status changed: passing to partially failing
• docteur.0.0.1 on 4.12 had its build status changed: passing to partially failing
• docteur.0.0.1 on 4.13 had its build status changed: passing to partially failing
• docteur.0.0.1 on 4.14 had its build status changed: passing to partially failing
• dolmen.0.1 on 5.1 is now installable. Current state is: partially failing
• dolmen.0.2 on 5.1 is now installable. Current state is: partially failing
• dolmen.0.5 on 5.1 is now installable. Current state is: partially failing
• dolmen.0.6 on 5.1 is now installable. Current state is: partially failing
• dolmen.0.7 on 5.1 is now installable. Current state is: partially failing
• dolmen.0.8 on 5.1 is now installable. Current state is: partially failing
• dolmen.0.8.1 on 5.1 is now installable. Current state is: partially failing
• dolmen_bin.0.5 on 5.1 is now installable. Current state is: partially failing
• dolmen_bin.0.6 on 5.1 is now installable. Current state is: partially failing
• dolmen_bin.0.7 on 5.1 is now installable. Current state is: partially failing
• dolmen_loop.0.5 on 5.1 is now installable. Current state is: partially failing
• dolmen_loop.0.6 on 5.1 is now installable. Current state is: partially failing
• dolmen_loop.0.7 on 5.1 is now installable. Current state is: partially failing
• dolmen_loop.0.8 on 5.1 is now installable. Current state is: partially failing
• dolmen_loop.0.8.1 on 5.1 is now installable. Current state is: partially failing
• dolmen_lsp.0.5 on 5.1 is now installable. Current state is: partially failing
• dolmen_lsp.0.6 on 5.1 is now installable. Current state is: partially failing
• dolmen_lsp.0.7 on 5.1 is now installable. Current state is: partially failing
• dolmen_lsp.0.8 on 5.1 is now installable. Current state is: partially failing
• dolmen_lsp.0.8.1 on 5.1 is now installable. Current state is: partially failing
• dolmen_type.0.5 on 5.1 is now installable. Current state is: partially failing
• dolmen_type.0.6 on 5.1 is now installable. Current state is: partially failing
• dolmen_type.0.7 on 5.1 is now installable. Current state is: partially failing
• dolmen_type.0.8 on 5.1 is now installable. Current state is: partially failing
• dolmen_type.0.8.1 on 5.1 is now installable. Current state is: partially failing
• drom_toml.0.8.0 on 5.1 is now installable. Current state is: partially failing
• dune-release.1.4.0 on 5.1 is now installable. Current state is: partially failing
• dune-release.1.5.0 on 5.1 is now installable. Current state is: partially failing
• dune-release.1.5.1 on 5.1 is now installable. Current state is: partially failing
• dune-release.1.5.2 on 5.1 is now installable. Current state is: partially failing
• dune-release.1.6.0 on 5.1 is now installable. Current state is: partially failing
• dune-release.1.6.1 on 5.1 is now installable. Current state is: partially failing
• dune-release.1.6.2 on 5.1 is now installable. Current state is: partially failing
• edn.0.2.0 on 5.1 is now installable. Current state is: partially failing
• elasticsearch-cli.0.4 on 4.08 had its build status changed: passing to partially failing
• elasticsearch-cli.0.4 on 4.09 had its build status changed: passing to partially failing
• elasticsearch-cli.0.4 on 4.10 had its build status changed: passing to partially failing
• elasticsearch-cli.0.4 on 4.11 had its build status changed: passing to partially failing
• ezxenstore.0.4.3 on 4.02 is now installable. Current state is: partially failing
• ezxenstore.0.4.3 on 4.03 is now installable. Current state is: partially failing
• ezxenstore.0.4.3 on 4.04 is now installable. Current state is: partially failing
• ezxenstore.0.4.3 on 4.05 is now installable. Current state is: partially failing
• ezxenstore.0.4.3 on 4.06 is now installable. Current state is: partially failing
• ezxenstore.0.4.3 on 4.07 is now installable. Current state is: partially failing
• fasmifra.1.0.0 on 5.1 is now installable. Current state is: partially failing
• fasmifra.1.1.0 on 5.1 is now installable. Current state is: partially failing
• gadelac.0.6 on 5.1 is now installable. Current state is: partially failing
• get_line.7.0.0 on 5.1 is now installable. Current state is: partially failing
• git-kv.0.0.2 on 5.1 is now installable. Current state is: partially failing
• git-kv.0.0.3 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.10.0 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.10.1 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.11.0 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.12.0 on 5.1 is now installable. Current state is: partially failing
• git-paf.3.4.0 on 4.08 had its build status changed: passing to partially failing
• git-paf.3.4.0 on 4.09 had its build status changed: passing to partially failing
• git-paf.3.4.0 on 4.10 had its build status changed: passing to partially failing
• git-paf.3.4.0 on 4.11 had its build status changed: passing to partially failing
• git-paf.3.4.0 on 4.12 had its build status changed: passing to partially failing
• git-paf.3.4.0 on 4.13 had its build status changed: passing to partially failing
• git-paf.3.4.0 on 4.14 had its build status changed: passing to partially failing
• git-paf.3.9.1 on 5.1 is now installable. Current state is: partially failing
• git.2.1.1 on 5.1 is now installable. Current state is: partially failing
• git.2.1.2 on 5.1 is now installable. Current state is: partially failing
• git.2.1.3 on 5.1 is now installable. Current state is: partially failing
• git.3.10.0 on 5.1 is now installable. Current state is: partially failing
• git.3.10.1 on 5.1 is now installable. Current state is: partially failing
• git.3.11.0 on 5.1 is now installable. Current state is: partially failing
• git.3.12.0 on 5.1 is now installable. Current state is: partially failing
• git.3.9.1 on 5.1 is now installable. Current state is: partially failing
• github-data.4.4.0 on 5.1 is now installable. Current state is: partially failing
• github-data.4.4.1 on 5.1 is now installable. Current state is: partially failing
• gmp-freestanding.6.1.2-2 on 4.08 had its build status changed: passing to partially failing
• gmp-freestanding.6.1.2-2 on 4.09 had its build status changed: passing to partially failing
• gmp-freestanding.6.1.2-2 on 4.10 had its build status changed: passing to partially failing
• gmp-freestanding.6.1.2-2 on 4.11 had its build status changed: passing to partially failing
• gmp-freestanding.6.1.2-2 on 4.12 had its build status changed: passing to partially failing
• gmp-freestanding.6.1.2-2 on 4.13 had its build status changed: passing to partially failing
• gmp-freestanding.6.1.2-2 on 4.14 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.0 on 4.08 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.0 on 4.09 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.0 on 4.10 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.0 on 4.11 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.0 on 4.12 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.0 on 4.13 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.0 on 4.14 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.1 on 4.08 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.1 on 4.09 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.1 on 4.10 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.1 on 4.11 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.1 on 4.12 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.1 on 4.13 had its build status changed: passing to partially failing
• gmp-freestanding.6.2.1 on 4.14 had its build status changed: passing to partially failing
• graphql-lwt.0.13.0 on 5.1 is now installable. Current state is: partially failing
• graphql-lwt.0.14.0 on 5.1 is now installable. Current state is: partially failing
• graphql-lwt.0.9.0 on 5.1 is now installable. Current state is: partially failing
• graphql.0.13.0 on 5.1 is now installable. Current state is: partially failing
• graphql.0.14.0 on 5.1 is now installable. Current state is: partially failing
• graphql.0.9.0 on 5.1 is now installable. Current state is: partially failing
• graphql_parser.0.13.0 on 5.1 is now installable. Current state is: partially failing
• graphql_parser.0.14.0 on 5.1 is now installable. Current state is: partially failing
• herdtools7.7.55 on 5.1 is now installable. Current state is: partially failing
• herdtools7.7.56 on 5.1 is now installable. Current state is: partially failing
• herdtools7.7.56.1 on 5.1 is now installable. Current state is: partially failing
• herdtools7.7.56.2 on 5.1 is now installable. Current state is: partially failing
• herdtools7.7.56.3 on 5.1 is now installable. Current state is: partially failing
• hts_shrink.2.1.2 on 5.1 is now installable. Current state is: partially failing
• http-date.0.1 on 5.1 is now installable. Current state is: partially failing
• inuit.0.1 on 5.1 is now installable. Current state is: partially failing
• inuit.0.2 on 5.1 is now installable. Current state is: partially failing
• inuit.0.3 on 5.1 is now installable. Current state is: partially failing
• irmin-git.2.0.0 on 5.1 is now installable. Current state is: partially failing
• irmin-git.2.2.0 on 5.1 is now installable. Current state is: partially failing
• irmin-mirage-git.2.6.0 on 4.08 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.0 on 4.09 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.0 on 4.10 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.0 on 4.11 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.0 on 4.12 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.0 on 4.13 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.0 on 4.14 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.1 on 4.08 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.1 on 4.09 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.1 on 4.10 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.1 on 4.11 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.1 on 4.12 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.1 on 4.13 had its build status changed: passing to partially failing
• irmin-mirage-git.2.6.1 on 4.14 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.0 on 4.08 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.0 on 4.09 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.0 on 4.10 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.0 on 4.11 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.0 on 4.12 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.0 on 4.13 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.0 on 4.14 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.1 on 4.08 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.1 on 4.09 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.1 on 4.10 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.1 on 4.11 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.1 on 4.12 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.1 on 4.13 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.1 on 4.14 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.2 on 4.08 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.2 on 4.09 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.2 on 4.10 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.2 on 4.11 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.2 on 4.12 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.2 on 4.13 had its build status changed: passing to partially failing
• irmin-mirage-git.2.7.2 on 4.14 had its build status changed: passing to partially failing
• irmin-pack.2.0.0 on 4.08 had its build status changed: passing to partially failing
• irmin-pack.2.0.0 on 4.09 had its build status changed: passing to partially failing
• irmin-pack.2.0.0 on 4.10 had its build status changed: passing to partially failing
• irmin-pack.2.0.0 on 4.11 had its build status changed: passing to partially failing
• irmin-pack.2.1.0 on 4.08 had its build status changed: passing to partially failing
• irmin-pack.2.1.0 on 4.09 had its build status changed: passing to partially failing
• irmin-pack.2.1.0 on 4.10 had its build status changed: passing to partially failing
• irmin-pack.2.1.0 on 4.11 had its build status changed: passing to partially failing
• irmin-pack.2.2.0 on 4.08 had its build status changed: passing to partially failing
• irmin-pack.2.2.0 on 4.09 had its build status changed: passing to partially failing
• irmin-pack.2.2.0 on 4.10 had its build status changed: passing to partially failing
• irmin-pack.2.2.0 on 4.11 had its build status changed: passing to partially failing
• jupyter-kernel.0.7 on 5.1 is now installable. Current state is: partially failing
• jupyter-kernel.0.8 on 5.1 is now installable. Current state is: partially failing
• key-parsers.0.8.1 on 4.02 had its build status changed: passing to partially failing
• kicadsch.0.4.0 on 5.1 is now installable. Current state is: partially failing
• kicadsch.0.5.0 on 5.1 is now installable. Current state is: partially failing
• kind2.1.6.0 on 5.1 is now installable. Current state is: partially failing
• kind2.1.7.0 on 5.1 is now installable. Current state is: partially failing
• kind2.1.8.0 on 5.1 is now installable. Current state is: partially failing
• lambda.0.1.7 on 5.1 is now installable. Current state is: partially failing
• lbvs_consent.2.1.3 on 5.0 is now installable. Current state is: partially failing
• lbvs_consent.2.2.0 on 5.0 is now installable. Current state is: partially failing
• libdash.0.3 on 5.1 is now installable. Current state is: partially failing
• libsail.0.15 on 5.1 is now installable. Current state is: partially failing
• line_oriented.1.0.0 on 5.1 is now installable. Current state is: partially failing
• line_oriented.1.2.0 on 5.1 is now installable. Current state is: partially failing
• line_oriented.1.3.0 on 5.1 is now installable. Current state is: partially failing
• lp-glpk.0.1.0 on 5.1 is now installable. Current state is: partially failing
• lp-glpk.0.2.0 on 5.1 is now installable. Current state is: partially failing
• lp-glpk.0.3.0 on 5.1 is now installable. Current state is: partially failing
• lp-glpk.0.4.0 on 5.1 is now installable. Current state is: partially failing
• lp-gurobi.0.2.0 on 5.1 is now installable. Current state is: partially failing
• lp-gurobi.0.3.0 on 5.1 is now installable. Current state is: partially failing
• lp-gurobi.0.4.0 on 5.1 is now installable. Current state is: partially failing
• lp.0.0.1 on 5.1 is now installable. Current state is: partially failing
• lp.0.0.2 on 5.1 is now installable. Current state is: partially failing
• lp.0.1.0 on 5.1 is now installable. Current state is: partially failing
• lp.0.2.0 on 5.1 is now installable. Current state is: partially failing
• lp.0.3.0 on 5.1 is now installable. Current state is: partially failing
• lp.0.4.0 on 5.1 is now installable. Current state is: partially failing
• markdown.0.2.1 on 5.1 is now installable. Current state is: partially failing
• minicaml.0.1 on 5.1 is now installable. Current state is: partially failing
• minicaml.0.2 on 5.1 is now installable. Current state is: partially failing
• mirage-block-solo5.0.6.0 on 4.08 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.0 on 4.09 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.0 on 4.10 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.0 on 4.11 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.0 on 4.12 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.0 on 4.13 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.0 on 4.14 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.1 on 4.08 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.1 on 4.09 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.1 on 4.10 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.1 on 4.11 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.1 on 4.12 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.1 on 4.13 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.1 on 4.14 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.2 on 4.08 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.2 on 4.09 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.2 on 4.10 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.2 on 4.11 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.2 on 4.12 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.2 on 4.13 had its build status changed: passing to partially failing
• mirage-block-solo5.0.6.2 on 4.14 had its build status changed: passing to partially failing
• mirage-block-xen.2.0.0 on 4.08 had its build status changed: passing to partially failing
• mirage-block-xen.2.0.0 on 4.09 had its build status changed: passing to partially failing
• mirage-block-xen.2.0.0 on 4.10 had its build status changed: passing to partially failing
• mirage-block-xen.2.0.0 on 4.11 had its build status changed: passing to partially failing
• mirage-block-xen.2.0.0 on 4.12 had its build status changed: passing to partially failing
• mirage-block-xen.2.0.0 on 4.13 had its build status changed: passing to partially failing
• mirage-block-xen.2.0.0 on 4.14 had its build status changed: passing to partially failing
• mirage-console-solo5.0.6.0 on 4.08 had its build status changed: passing to partially failing
• mirage-console-solo5.0.6.0 on 4.09 had its build status changed: passing to partially failing
• mirage-console-solo5.0.6.0 on 4.10 had its build status changed: passing to partially failing
• mirage-console-solo5.0.6.0 on 4.11 had its build status changed: passing to partially failing
• mirage-console-solo5.0.6.0 on 4.12 had its build status changed: passing to partially failing
• mirage-console-solo5.0.6.0 on 4.13 had its build status changed: passing to partially failing
• mirage-console-solo5.0.6.0 on 4.14 had its build status changed: passing to partially failing
• mirage-console-xen-backend.4.0.0 on 4.08 had its build status changed: passing to partially failing
• mirage-console-xen-backend.4.0.0 on 4.09 had its build status changed: passing to partially failing
• mirage-console-xen-backend.4.0.0 on 4.10 had its build status changed: passing to partially failing
• mirage-console-xen-backend.4.0.0 on 4.11 had its build status changed: passing to partially failing
• mirage-console-xen-backend.4.0.0 on 4.12 had its build status changed: passing to partially failing
• mirage-console-xen-backend.4.0.0 on 4.13 had its build status changed: passing to partially failing
• mirage-console-xen-backend.4.0.0 on 4.14 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.08 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.09 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.10 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.11 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.12 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.13 had its build status changed: passing to partially failing
• mirage-console-xen-backend.5.0.0 on 4.14 had its build status changed: passing to partially failing
• mirage-console-xen.4.0.0 on 4.08 had its build status changed: passing to partially failing
• mirage-console-xen.4.0.0 on 4.09 had its build status changed: passing to partially failing
• mirage-console-xen.4.0.0 on 4.10 had its build status changed: passing to partially failing
• mirage-console-xen.4.0.0 on 4.11 had its build status changed: passing to partially failing
• mirage-console-xen.4.0.0 on 4.12 had its build status changed: passing to partially failing
• mirage-console-xen.4.0.0 on 4.13 had its build status changed: passing to partially failing
• mirage-console-xen.4.0.0 on 4.14 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.08 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.09 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.10 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.11 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.12 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.13 had its build status changed: passing to partially failing
• mirage-console-xen.5.0.0 on 4.14 had its build status changed: passing to partially failing
• mirage-monitoring.0.0.1 on 4.11 had its build status changed: passing to partially failing
• mirage-monitoring.0.0.1 on 4.12 had its build status changed: passing to partially failing
• mirage-monitoring.0.0.1 on 4.13 had its build status changed: passing to partially failing
• mirage-monitoring.0.0.1 on 4.14 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.0 on 4.08 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.0 on 4.09 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.0 on 4.10 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.0 on 4.11 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.0 on 4.12 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.0 on 4.13 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.0 on 4.14 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.1 on 4.08 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.1 on 4.09 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.1 on 4.10 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.1 on 4.11 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.1 on 4.12 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.1 on 4.13 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.1 on 4.14 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.2 on 4.08 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.2 on 4.09 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.2 on 4.10 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.2 on 4.11 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.2 on 4.12 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.2 on 4.13 had its build status changed: passing to partially failing
• mirage-net-solo5.0.6.2 on 4.14 had its build status changed: passing to partially failing
• mirage-net-xen.2.0.0 on 4.08 had its build status changed: passing to partially failing
• mirage-net-xen.2.0.0 on 4.09 had its build status changed: passing to partially failing
• mirage-net-xen.2.0.0 on 4.10 had its build status changed: passing to partially failing
• mirage-net-xen.2.0.0 on 4.11 had its build status changed: passing to partially failing
• mirage-net-xen.2.0.0 on 4.12 had its build status changed: passing to partially failing
• mirage-net-xen.2.0.0 on 4.13 had its build status changed: passing to partially failing
• mirage-net-xen.2.0.0 on 4.14 had its build status changed: passing to partially failing
• mirage-solo5.0.6.0 on 4.08 had its build status changed: passing to partially failing
• mirage-solo5.0.6.0 on 4.09 had its build status changed: passing to partially failing
• mirage-solo5.0.6.1 on 4.08 had its build status changed: passing to partially failing
• mirage-solo5.0.6.1 on 4.09 had its build status changed: passing to partially failing
• mirage-solo5.0.6.2 on 4.08 had its build status changed: passing to partially failing
• mirage-solo5.0.6.2 on 4.09 had its build status changed: passing to partially failing
• mirage-solo5.0.6.2 on 4.10 had its build status changed: passing to partially failing
• mirage-solo5.0.6.2 on 4.11 had its build status changed: passing to partially failing
• mirage-solo5.0.6.2 on 4.12 had its build status changed: passing to partially failing
• mirage-solo5.0.6.2 on 4.13 had its build status changed: passing to partially failing
• mirage-solo5.0.6.2 on 4.14 had its build status changed: passing to partially failing
• mirage-solo5.0.6.3 on 4.08 had its build status changed: passing to partially failing
• mirage-solo5.0.6.3 on 4.09 had its build status changed: passing to partially failing
• mirage-solo5.0.6.3 on 4.10 had its build status changed: passing to partially failing
• mirage-solo5.0.6.3 on 4.11 had its build status changed: passing to partially failing
• mirage-solo5.0.6.3 on 4.12 had its build status changed: passing to partially failing
• mirage-solo5.0.6.3 on 4.13 had its build status changed: passing to partially failing
• mirage-solo5.0.6.3 on 4.14 had its build status changed: passing to partially failing
• mirage-solo5.0.6.4 on 4.08 had its build status changed: passing to partially failing
• mirage-solo5.0.6.4 on 4.09 had its build status changed: passing to partially failing
• mirage-solo5.0.6.4 on 4.10 had its build status changed: passing to partially failing
• mirage-solo5.0.6.4 on 4.11 had its build status changed: passing to partially failing
• mirage-solo5.0.6.4 on 4.12 had its build status changed: passing to partially failing
• mirage-solo5.0.6.4 on 4.13 had its build status changed: passing to partially failing
• mirage-solo5.0.6.4 on 4.14 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.08 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.09 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.10 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.11 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.12 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.13 had its build status changed: passing to partially failing
• mirage-solo5.0.6.5 on 4.14 had its build status changed: passing to partially failing
• mirage-xen.6.0.0 on 4.08 had its build status changed: passing to partially failing
• mirage-xen.6.0.0 on 4.09 had its build status changed: passing to partially failing
• mirage-xen.6.0.0 on 4.10 had its build status changed: passing to partially failing
• mirage-xen.6.0.0 on 4.11 had its build status changed: passing to partially failing
• mirage-xen.6.0.0 on 4.12 had its build status changed: passing to partially failing
• mirage-xen.6.0.0 on 4.13 had its build status changed: passing to partially failing
• mirage-xen.6.0.0 on 4.14 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.08 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.09 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.10 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.11 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.12 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.13 had its build status changed: passing to partially failing
• mirage-xen.6.0.1 on 4.14 had its build status changed: passing to partially failing
• mirage.4.0.0~beta1 on 5.1 is now installable. Current state is: partially failing
• mirage.4.0.0~beta2 on 5.1 is now installable. Current state is: partially failing
• mirage.4.0.0~beta3 on 5.1 is now installable. Current state is: partially failing
• mirage.4.1.0 on 5.1 is now installable. Current state is: partially failing
• mirage.4.1.1 on 5.1 is now installable. Current state is: partially failing
• mirage.4.2.0 on 5.1 is now installable. Current state is: partially failing
• mirage.4.2.1 on 5.1 is now installable. Current state is: partially failing
• mirage.4.3.0 on 5.1 is now installable. Current state is: partially failing
• mirage.4.3.1 on 5.1 is now installable. Current state is: partially failing
• mirage.4.3.2 on 5.1 is now installable. Current state is: partially failing
• mirage.4.3.3 on 5.1 is now installable. Current state is: partially failing
• mirage.4.3.4 on 5.1 is now installable. Current state is: partially failing
• mirage.4.3.5 on 5.1 is now installable. Current state is: partially failing
• mustache.3.1.0 on 5.1 is now installable. Current state is: partially failing
• mutf8.0.1 on 5.1 is now installable. Current state is: partially failing
• mutf8.0.2 on 5.1 is now installable. Current state is: partially failing
• netchannel.2.0.0 on 4.08 had its build status changed: passing to partially failing
• netchannel.2.0.0 on 4.09 had its build status changed: passing to partially failing
• netchannel.2.0.0 on 4.10 had its build status changed: passing to partially failing
• netchannel.2.0.0 on 4.11 had its build status changed: passing to partially failing
• netchannel.2.0.0 on 4.12 had its build status changed: passing to partially failing
• netchannel.2.0.0 on 4.13 had its build status changed: passing to partially failing
• netchannel.2.0.0 on 4.14 had its build status changed: passing to partially failing
• obelisk.0.1.0 on 5.1 is now installable. Current state is: partially failing
• obelisk.0.1.1 on 5.1 is now installable. Current state is: partially failing
• obelisk.0.2.0 on 5.1 is now installable. Current state is: partially failing
• obelisk.0.3.0 on 5.1 is now installable. Current state is: partially failing
• obelisk.0.3.2 on 5.1 is now installable. Current state is: partially failing
• obelisk.0.4.0 on 5.1 is now installable. Current state is: partially failing
• obelisk.0.5.0 on 5.1 is now installable. Current state is: partially failing
• obelisk.0.5.2 on 5.1 is now installable. Current state is: partially failing
• obelisk.0.6.0 on 5.1 is now installable. Current state is: partially failing
• ocaml-freestanding.0.6.0 on 4.08 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.0 on 4.09 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.0 on 4.10 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.2 on 4.08 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.2 on 4.09 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.2 on 4.10 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.2 on 4.11 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.3 on 4.08 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.3 on 4.09 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.3 on 4.10 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.3 on 4.11 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.4 on 4.08 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.4 on 4.09 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.4 on 4.10 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.4 on 4.11 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.4 on 4.12 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.08 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.09 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.10 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.11 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.12 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.5 on 4.13 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.08 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.09 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.10 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.11 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.12 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.6 on 4.13 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.7 on 4.08 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.7 on 4.09 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.7 on 4.10 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.7 on 4.11 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.7 on 4.12 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.7 on 4.13 had its build status changed: passing to partially failing
• ocaml-freestanding.0.6.7 on 4.14 had its build status changed: passing to partially failing
• ocaml-in-python.0.1.0 on 4.13 had its build status changed: passing to partially failing
• ocaml-in-python.0.1.0 on 4.14 had its build status changed: passing to partially failing
• ocaml-markdown.transition on 5.1 is now installable. Current state is: partially failing
• ocaml-option-address-sanitizer.1 on 5.1 is now installable. Current state is: partially failing
• ocaml-top.1.2.0 on 5.1 is now installable. Current state is: partially failing
• ocamlbrowser.4.14.0 on 4.14 had its build status changed: passing to partially failing
• ocamlformat-lib.0.25.1 on 5.1 is now installable. Current state is: partially failing
• ocamlformat.0.23.0 on 5.1 is now installable. Current state is: partially failing
• ocamlformat.0.24.1 on 5.1 is now installable. Current state is: partially failing
• ocamlformat.0.25.1 on 5.1 is now installable. Current state is: partially failing
• octez-accuser-PtKathma.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-accuser-PtKathma.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-accuser-PtLimaPt.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-accuser-PtLimaPt.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-accuser-PtLimaPt.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-accuser-PtMumbai.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-baker-PtKathma.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-baker-PtKathma.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-baker-PtLimaPt.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-baker-PtLimaPt.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-baker-PtLimaPt.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-baker-PtMumbai.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-client.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-client.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-client.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-codec.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-codec.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-codec.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-node-config.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-node.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-node.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-proxy-server.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-proxy-server.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-proxy-server.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-signer.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-signer.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-signer.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-smart-rollup-client-PtMumbai.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-smart-rollup-node-PtMumbai.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-smart-rollup-wasm-debugger.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-client-PtKathma.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-client-PtKathma.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-client-PtLimaPt.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-client-PtLimaPt.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-client-PtLimaPt.16.0 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-node-PtKathma.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-node-PtKathma.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-node-PtLimaPt.15.0 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-node-PtLimaPt.15.1 on 4.14 is now installable. Current state is: partially failing
• octez-tx-rollup-node-PtLimaPt.16.0 on 4.14 is now installable. Current state is: partially failing
• octez.15.1 on 4.14 is now installable. Current state is: partially failing
• octez.16.0 on 4.14 is now installable. Current state is: partially failing
• odds.1.0 on 5.1 is now installable. Current state is: partially failing
• odds.1.1 on 5.1 is now installable. Current state is: partially failing
• odds.1.2 on 5.1 is now installable. Current state is: partially failing
• odig.0.0.7 on 5.1 is now installable. Current state is: partially failing
• odig.0.0.8 on 5.1 is now installable. Current state is: partially failing
• odnnr.2.0.0 on 5.1 is now installable. Current state is: partially failing
• opam-publish.2.0.1 on 4.03 had its build status changed: passing to partially failing
• opam-publish.2.0.1 on 4.04 had its build status changed: passing to partially failing
• opam-publish.2.0.1 on 4.05 had its build status changed: passing to partially failing
• opam-publish.2.0.2 on 4.03 had its build status changed: passing to partially failing
• opam-publish.2.0.2 on 4.04 had its build status changed: passing to partially failing
• opam-publish.2.0.2 on 4.05 had its build status changed: passing to partially failing
• opam-publish.2.0.3 on 4.03 had its build status changed: passing to partially failing
• opam-publish.2.0.3 on 4.04 had its build status changed: passing to partially failing
• opam-publish.2.0.3 on 4.05 had its build status changed: passing to partially failing
• opam-publish.2.1.0 on 4.03 had its build status changed: passing to partially failing
• opam-publish.2.1.0 on 4.04 had its build status changed: passing to partially failing
• opam-publish.2.1.0 on 4.05 had its build status changed: passing to partially failing
• openQASM.0.3.0 on 5.1 is now installable. Current state is: partially failing
• openQASM.0.4.0 on 5.1 is now installable. Current state is: partially failing
• oplsr.2.0.0 on 5.1 is now installable. Current state is: partially failing
• oplsr.5.0.1 on 5.1 is now installable. Current state is: partially failing
• oplsr.8.0.1 on 5.1 is now installable. Current state is: partially failing
• optal.0.3 on 5.1 is now installable. Current state is: partially failing
• oranger.2.0.1 on 5.1 is now installable. Current state is: partially failing
• oranger.2.0.2 on 5.1 is now installable. Current state is: partially failing
• oranger.2.0.4 on 5.1 is now installable. Current state is: partially failing
• orrandomForest.3.0.0 on 5.1 is now installable. Current state is: partially failing
• otoml.0.9.0 on 5.1 is now installable. Current state is: partially failing
• otoml.0.9.1 on 5.1 is now installable. Current state is: partially failing
• otoml.0.9.2 on 5.1 is now installable. Current state is: partially failing
• otoml.0.9.3 on 5.1 is now installable. Current state is: partially failing
• otoml.1.0.0 on 5.1 is now installable. Current state is: partially failing
• otoml.1.0.1 on 5.1 is now installable. Current state is: partially failing
• otoml.1.0.2 on 5.1 is now installable. Current state is: partially failing
• otoml.1.0.3 on 5.1 is now installable. Current state is: partially failing
• otoml.1.0.4 on 5.1 is now installable. Current state is: partially failing
• owl-ode-sundials.0.5.0 on 4.10 had its build status changed: passing to partially failing
• owl-ode-sundials.0.5.0 on 4.11 had its build status changed: passing to partially failing
• owl-ode-sundials.0.5.0 on 4.12 had its build status changed: passing to partially failing
• owl-ode-sundials.0.5.0 on 4.13 had its build status changed: passing to partially failing
• owl-ode-sundials.0.5.0 on 4.14 had its build status changed: passing to partially failing
• pardi.2.0.4 on 5.1 is now installable. Current state is: partially failing
• pardi.3.1.1 on 5.1 is now installable. Current state is: partially failing
• pardi.3.2.0 on 5.1 is now installable. Current state is: partially failing
• pardi.3.2.2 on 5.1 is now installable. Current state is: partially failing
• pb-plugin.1.0.0 on 5.1 is now installable. Current state is: partially failing
• piece_rope.0.9.0 on 5.1 is now installable. Current state is: partially failing
• plist-xml.0.4.0 on 5.1 is now installable. Current state is: partially failing
• plist-xml.0.5.0 on 5.1 is now installable. Current state is: partially failing
• portia.1.1 on 5.1 is now installable. Current state is: partially failing
• portia.1.3 on 5.1 is now installable. Current state is: partially failing
• portia.1.5 on 5.1 is now installable. Current state is: partially failing
• ppx_expect.113.33.00 on 4.02 had its build status changed: failing to partially failing
• prbnmcn-dagger-gsl.0.0.1 on 4.13 had its build status changed: passing to partially failing
• prbnmcn-dagger-gsl.0.0.2 on 4.13 had its build status changed: passing to partially failing
• prbnmcn-dagger-test.0.0.1 on 4.13 had its build status changed: passing to partially failing
• prbnmcn-dagger-test.0.0.2 on 4.13 had its build status changed: passing to partially failing
• primes.1.3.3 on 4.03 had its build status changed: passing to partially failing
• protocol-9p-unix.1.0.0 on 5.0 had its build status changed: not available to partially failing
• protocol-9p-unix.1.0.1 on 5.0 had its build status changed: not available to partially failing
• psmt2-frontend.0.3.0 on 5.1 is now installable. Current state is: partially failing
• psmt2-frontend.0.3.1 on 5.1 is now installable. Current state is: partially failing
• psmt2-frontend.0.4.0 on 5.1 is now installable. Current state is: partially failing
• publish.0.3.4+transition on 4.03 had its build status changed: passing to partially failing
• publish.0.3.4+transition on 4.04 had its build status changed: passing to partially failing
• publish.0.3.4+transition on 4.05 had its build status changed: passing to partially failing
• rankers.1.0.0 on 4.02 had its build status changed: passing to partially failing
• rankers.1.0.0 on 4.03 had its build status changed: passing to partially failing
• rankers.1.0.0 on 4.04 had its build status changed: passing to partially failing
• rankers.1.0.0 on 4.05 had its build status changed: passing to partially failing
• rankers.1.0.0 on 4.06 had its build status changed: passing to partially failing
• rankers.1.0.0 on 4.07 had its build status changed: passing to partially failing
• rankers.2.0.1 on 4.02 had its build status changed: passing to partially failing
• rankers.2.0.1 on 4.03 had its build status changed: passing to partially failing
• rankers.2.0.1 on 4.04 had its build status changed: passing to partially failing
• rankers.2.0.1 on 4.05 had its build status changed: passing to partially failing
• rankers.2.0.1 on 4.06 had its build status changed: passing to partially failing
• rankers.2.0.1 on 4.07 had its build status changed: passing to partially failing
• rankers.2.0.7 on 4.04 had its build status changed: passing to partially failing
• rankers.2.0.7 on 4.05 had its build status changed: passing to partially failing
• rankers.2.0.7 on 4.06 had its build status changed: passing to partially failing
• rankers.2.0.7 on 4.07 had its build status changed: passing to partially failing
• resto-cohttp-self-serving-client.1.1 on 4.10 is now installable. Current state is: partially failing
• resto-cohttp-self-serving-client.1.1 on 4.11 is now installable. Current state is: partially failing
• resto-cohttp-self-serving-client.1.1 on 4.12 is now installable. Current state is: partially failing
• resto-cohttp-self-serving-client.1.1 on 4.13 is now installable. Current state is: partially failing
• resto-cohttp-self-serving-client.1.1 on 4.14 is now installable. Current state is: partially failing
• resto-cohttp-self-serving-client.1.1 on 5.0 is now installable. Current state is: partially failing
• sail.0.15 on 5.1 is now installable. Current state is: partially failing
• sail_c_backend.0.15 on 5.1 is now installable. Current state is: partially failing
• sail_coq_backend.0.15 on 5.1 is now installable. Current state is: partially failing
• sail_latex_backend.0.15 on 5.1 is now installable. Current state is: partially failing
• sail_lem_backend.0.15 on 5.1 is now installable. Current state is: partially failing
• sail_ocaml_backend.0.15 on 5.1 is now installable. Current state is: partially failing
• sail_output.0.15 on 5.1 is now installable. Current state is: partially failing
• sail_smt_backend.0.15 on 5.1 is now installable. Current state is: partially failing
• sanddb.0.2 on 5.1 is now installable. Current state is: partially failing
• sanddb.0.3.0 on 5.1 is now installable. Current state is: partially failing
• sifun.3.0.0 on 5.1 is now installable. Current state is: partially failing
• smtlib-utils.0.4 on 5.1 is now installable. Current state is: partially failing
• socialpeek.1.0.0 on 4.04 had its build status changed: failing to partially failing
• socialpeek.1.0.0 on 4.05 had its build status changed: failing to partially failing
• solidity-parser.0.2.0 on 5.1 is now installable. Current state is: partially failing
• solo5-cross-aarch64.0.7.0 on 4.02 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.03 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.04 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.05 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.06 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.07 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.08 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.09 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.10 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.11 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.12 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.13 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 4.14 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 5.0 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.0 on 5.1 is now installable. Current state is: partially failing
• solo5-cross-aarch64.0.7.1 on 4.02 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.03 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.04 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.05 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.06 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.07 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.08 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.09 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.10 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.11 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.12 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.13 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 4.14 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 5.0 had its build status changed: passing to partially failing
• solo5-cross-aarch64.0.7.1 on 5.1 is now installable. Current state is: partially failing
• spirv.1.1.1 on 5.1 is now installable. Current state is: partially failing
• spirv.1.1.2 on 5.1 is now installable. Current state is: partially failing
• squirrel.0.1 on 5.1 is now installable. Current state is: partially failing
• stog-writing.0.19.0 on 4.12 had its build status changed: failing to partially failing
• stog_asy.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_dot.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_extern.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_markdown.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_multi_doc.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_nocaml.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_noexec.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_plugins.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_rdf.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_rel_href.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_server.0.20.0 on 4.12 had its build status changed: failing to partially failing
• stog_sitemap.0.20.0 on 4.12 had its build status changed: passing to partially failing
• stog_writing.0.20.0 on 4.12 had its build status changed: passing to partially failing
• sturgeon.0.1 on 5.1 is now installable. Current state is: partially failing
• sturgeon.0.2 on 5.1 is now installable. Current state is: partially failing
• sturgeon.0.3 on 5.1 is now installable. Current state is: partially failing
• sturgeon.0.4 on 5.1 is now installable. Current state is: partially failing
• sturgeon.0.4.2 on 5.1 is now installable. Current state is: partially failing
• swhid.0.1 on 5.1 is now installable. Current state is: partially failing
• talaria-bibtex.0.5 on 5.1 is now installable. Current state is: partially failing
• telltime.0.0.3 on 5.1 is now installable. Current state is: partially failing
• textrazor.0.1 on 4.04 had its build status changed: passing to partially failing
• textrazor.0.1 on 4.05 had its build status changed: passing to partially failing
• textrazor.0.1.1 on 4.04 had its build status changed: passing to partially failing
• textrazor.0.1.1 on 4.05 had its build status changed: passing to partially failing
• tezos-accuser-007-PsDELPH1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-accuser-007-PsDELPH1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-accuser-007-PsDELPH1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-accuser-007-PsDELPH1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-accuser-007-PsDELPH1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-accuser-007-PsDELPH1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-accuser-007-PsDELPH1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-accuser-007-PsDELPH1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-accuser-008-PtEdo2Zk.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-accuser-008-PtEdo2Zk.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-accuser-008-PtEdo2Zk.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-accuser-008-PtEdo2Zk.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-accuser-008-PtEdoTez.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-accuser-008-PtEdoTez.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-accuser-008-PtEdoTez.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-accuser-008-PtEdoTez.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-alpha-test-helpers.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-alpha-test-helpers.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-alpha-test-helpers.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-alpha-test-helpers.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-007-PsDELPH1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-baker-007-PsDELPH1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-007-PsDELPH1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-baker-007-PsDELPH1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-007-PsDELPH1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-baker-007-PsDELPH1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-007-PsDELPH1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-baker-007-PsDELPH1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-008-PtEdo2Zk.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-baker-008-PtEdo2Zk.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-008-PtEdo2Zk.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-baker-008-PtEdo2Zk.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-008-PtEdoTez.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-baker-008-PtEdoTez.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-008-PtEdoTez.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-baker-008-PtEdoTez.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-007-PsDELPH1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdoTez-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdoTez-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdoTez-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdoTez-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdoTez.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdoTez.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdoTez.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdoTez.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-014-PtKathma-commands.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-014-PtKathma-commands.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-014-PtKathma.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-014-PtKathma.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-015-PtLimaPt-commands.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-015-PtLimaPt-commands.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-015-PtLimaPt-commands.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-015-PtLimaPt.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-015-PtLimaPt.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-015-PtLimaPt.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-016-PtMumbai-commands.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-016-PtMumbai.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-alpha-commands.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-alpha-commands.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-alpha-commands.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-alpha-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-alpha-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-alpha-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-alpha-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-alpha-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-alpha-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-alpha-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-alpha-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-alpha.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-alpha.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-alpha.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-baking-alpha.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-alpha.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-alpha.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-alpha.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-alpha.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-alpha.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-alpha.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-baking-alpha.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-base.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-base.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-base.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-base.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-base.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-base.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-base.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-base.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-base.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-base.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-base.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-base.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-base.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-base.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-base.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-base.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-base.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-base.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-base.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-base.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-base.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-base.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-base.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-base.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-base.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-base.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-base.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-base.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-base.9.2 on 4.08 had its build status changed: passing to partially failing
• tezos-base.9.2 on 4.09 had its build status changed: passing to partially failing
• tezos-base.9.2 on 4.10 had its build status changed: passing to partially failing
• tezos-base.9.2 on 4.11 had its build status changed: passing to partially failing
• tezos-base.9.3 on 4.08 had its build status changed: passing to partially failing
• tezos-base.9.3 on 4.09 had its build status changed: passing to partially failing
• tezos-base.9.3 on 4.10 had its build status changed: passing to partially failing
• tezos-base.9.3 on 4.11 had its build status changed: passing to partially failing
• tezos-base.9.4 on 4.08 had its build status changed: passing to partially failing
• tezos-base.9.4 on 4.09 had its build status changed: passing to partially failing
• tezos-base.9.4 on 4.10 had its build status changed: passing to partially failing
• tezos-base.9.4 on 4.11 had its build status changed: passing to partially failing
• tezos-base.9.7 on 4.08 had its build status changed: passing to partially failing
• tezos-base.9.7 on 4.09 had its build status changed: passing to partially failing
• tezos-base.9.7 on 4.10 had its build status changed: passing to partially failing
• tezos-base.9.7 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.9.2 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.9.2 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.9.2 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.9.2 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.9.3 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.9.3 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.9.3 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.9.3 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.9.4 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.9.4 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.9.4 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.9.4 on 4.11 had its build status changed: passing to partially failing
• tezos-clic.9.7 on 4.08 had its build status changed: passing to partially failing
• tezos-clic.9.7 on 4.09 had its build status changed: passing to partially failing
• tezos-clic.9.7 on 4.10 had its build status changed: passing to partially failing
• tezos-clic.9.7 on 4.11 had its build status changed: passing to partially failing
• tezos-client-000-Ps9mPmXa.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-000-Ps9mPmXa.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-000-Ps9mPmXa.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-000-Ps9mPmXa.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-000-Ps9mPmXa.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-000-Ps9mPmXa.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-000-Ps9mPmXa.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-000-Ps9mPmXa.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands-registration.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands-registration.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands-registration.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands-registration.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands-registration.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands-registration.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands-registration.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands-registration.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands-registration.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands-registration.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands-registration.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands-registration.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez-commands-registration.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez-commands-registration.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez-commands-registration.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez-commands-registration.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-008-PtEdoTez.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-009-PsFLoren.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-009-PsFLoren.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-009-PsFLoren.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-010-PtGRANAD.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-010-PtGRANAD.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-010-PtGRANAD.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-011-PtHangz2.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-011-PtHangz2.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-011-PtHangz2.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-012-Psithaca.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-012-Psithaca.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-012-Psithaca.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-013-PtJakart.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-013-PtJakart.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-013-PtJakart.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-014-PtKathma.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-014-PtKathma.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-014-PtKathma.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-015-PtLimaPt.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-015-PtLimaPt.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-015-PtLimaPt.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-016-PtMumbai.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-alpha-commands-registration.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha-commands-registration.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha-commands-registration.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha-commands-registration.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha-commands-registration.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha-commands-registration.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha-commands-registration.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha-commands-registration.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-alpha.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-alpha.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-alpha.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-alpha.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base-unix.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-base-unix.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-base-unix.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-base-unix.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base-unix.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base.11.0 on 4.12 had its build status changed: passing to partially failing
• tezos-client-base.11.0 on 4.13 had its build status changed: passing to partially failing
• tezos-client-base.11.0 on 4.14 had its build status changed: passing to partially failing
• tezos-client-base.11.1 on 4.12 had its build status changed: passing to partially failing
• tezos-client-base.11.1 on 4.13 had its build status changed: passing to partially failing
• tezos-client-base.11.1 on 4.14 had its build status changed: passing to partially failing
• tezos-client-base.12.0 on 4.12 had its build status changed: passing to partially failing
• tezos-client-base.12.0 on 4.13 had its build status changed: passing to partially failing
• tezos-client-base.12.0 on 4.14 had its build status changed: passing to partially failing
• tezos-client-base.12.3 on 4.12 had its build status changed: passing to partially failing
• tezos-client-base.12.3 on 4.13 had its build status changed: passing to partially failing
• tezos-client-base.12.3 on 4.14 had its build status changed: passing to partially failing
• tezos-client-base.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-client-commands.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-client-commands.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-commands.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-commands.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-client-commands.11.0 on 4.12 had its build status changed: passing to partially failing
• tezos-client-commands.11.0 on 4.13 had its build status changed: passing to partially failing
• tezos-client-commands.11.0 on 4.14 had its build status changed: passing to partially failing
• tezos-client-commands.11.1 on 4.12 had its build status changed: passing to partially failing
• tezos-client-commands.11.1 on 4.13 had its build status changed: passing to partially failing
• tezos-client-commands.11.1 on 4.14 had its build status changed: passing to partially failing
• tezos-client-commands.12.0 on 4.12 had its build status changed: passing to partially failing
• tezos-client-commands.12.0 on 4.13 had its build status changed: passing to partially failing
• tezos-client-commands.12.0 on 4.14 had its build status changed: passing to partially failing
• tezos-client-commands.12.3 on 4.12 had its build status changed: passing to partially failing
• tezos-client-commands.12.3 on 4.13 had its build status changed: passing to partially failing
• tezos-client-commands.12.3 on 4.14 had its build status changed: passing to partially failing
• tezos-client-commands.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-client-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-commands.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-client-commands.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-client-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-commands.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-client-commands.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-client-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-commands.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-client-commands.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-client-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-commands.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-client-demo-counter.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-demo-counter.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-demo-counter.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-demo-counter.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-demo-counter.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-demo-counter.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-demo-counter.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-demo-counter.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis-carthagenet.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-genesis-carthagenet.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis-carthagenet.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-genesis-carthagenet.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis-carthagenet.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-genesis-carthagenet.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis-carthagenet.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-genesis-carthagenet.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-genesis.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-client-genesis.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-client-genesis.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-genesis.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-genesis.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-genesis.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-genesis.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-sapling-008-PtEdo2Zk.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client-sapling-008-PtEdo2Zk.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client-sapling-008-PtEdo2Zk.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client-sapling-008-PtEdo2Zk.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-client-sapling-008-PtEdoTez.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-sapling-008-PtEdoTez.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-sapling-008-PtEdoTez.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client-sapling-008-PtEdoTez.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-client.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-client.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-client.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-client.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-client.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-codec.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-codec.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-codec.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-codec.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-codec.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-codec.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-codec.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-codec.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-codec.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-codec.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-codec.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-codec.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-codec.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-codec.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-codec.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-codec.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.9.2 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.9.2 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.9.2 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.9.2 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.9.3 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.9.3 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.9.3 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.9.3 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.9.4 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.9.4 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.9.4 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.9.4 on 4.11 had its build status changed: passing to partially failing
• tezos-crypto.9.7 on 4.08 had its build status changed: passing to partially failing
• tezos-crypto.9.7 on 4.09 had its build status changed: passing to partially failing
• tezos-crypto.9.7 on 4.10 had its build status changed: passing to partially failing
• tezos-crypto.9.7 on 4.11 had its build status changed: passing to partially failing
• tezos-dal-node-lib.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-embedded-protocol-000-Ps9mPmXa.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-000-Ps9mPmXa.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-000-Ps9mPmXa.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-000-Ps9mPmXa.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-000-Ps9mPmXa.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-000-Ps9mPmXa.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-000-Ps9mPmXa.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-000-Ps9mPmXa.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-001-PtCJ7pwo.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-001-PtCJ7pwo.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-001-PtCJ7pwo.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-001-PtCJ7pwo.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-001-PtCJ7pwo.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-001-PtCJ7pwo.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-001-PtCJ7pwo.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-001-PtCJ7pwo.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-002-PsYLVpVv.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-002-PsYLVpVv.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-002-PsYLVpVv.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-002-PsYLVpVv.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-002-PsYLVpVv.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-002-PsYLVpVv.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-002-PsYLVpVv.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-002-PsYLVpVv.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-003-PsddFKi3.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-003-PsddFKi3.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-003-PsddFKi3.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-003-PsddFKi3.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-003-PsddFKi3.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-003-PsddFKi3.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-003-PsddFKi3.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-003-PsddFKi3.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-004-Pt24m4xi.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-004-Pt24m4xi.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-004-Pt24m4xi.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-004-Pt24m4xi.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-004-Pt24m4xi.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-004-Pt24m4xi.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-004-Pt24m4xi.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-004-Pt24m4xi.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBABY5H.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBABY5H.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBABY5H.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBABY5H.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBABY5H.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBABY5H.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBABY5H.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBABY5H.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBabyM1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBabyM1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBabyM1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBabyM1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBabyM1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBabyM1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBabyM1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBabyM1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-006-PsCARTHA.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-006-PsCARTHA.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-006-PsCARTHA.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-006-PsCARTHA.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-006-PsCARTHA.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-006-PsCARTHA.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-006-PsCARTHA.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-006-PsCARTHA.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-007-PsDELPH1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-007-PsDELPH1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-007-PsDELPH1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-007-PsDELPH1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-007-PsDELPH1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-007-PsDELPH1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-007-PsDELPH1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-007-PsDELPH1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdo2Zk.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdo2Zk.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdo2Zk.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdo2Zk.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdoTez.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdoTez.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdoTez.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdoTez.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdoTez.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdoTez.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdoTez.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdoTez.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-alpha.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-alpha.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-alpha.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-alpha.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-alpha.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-alpha.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-alpha.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-alpha.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-counter.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-counter.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-counter.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-counter.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-counter.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-counter.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-counter.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-counter.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-noops.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-noops.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-noops.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-noops.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-noops.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-noops.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-noops.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-noops.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis-carthagenet.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis-carthagenet.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis-carthagenet.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis-carthagenet.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis-carthagenet.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis-carthagenet.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis-carthagenet.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis-carthagenet.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-007-PsDELPH1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-endorser-007-PsDELPH1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-007-PsDELPH1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-endorser-007-PsDELPH1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-007-PsDELPH1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-endorser-007-PsDELPH1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-007-PsDELPH1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-endorser-007-PsDELPH1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-008-PtEdo2Zk.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-endorser-008-PtEdo2Zk.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-008-PtEdo2Zk.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-endorser-008-PtEdo2Zk.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-008-PtEdoTez.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-endorser-008-PtEdoTez.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-008-PtEdoTez.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-endorser-008-PtEdoTez.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-injector-014-PtKathma.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-injector-014-PtKathma.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-injector-015-PtLimaPt.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-injector-015-PtLimaPt.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-injector-015-PtLimaPt.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-injector-016-PtMumbai.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-layer2-utils-016-PtMumbai.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-mempool-007-PsDELPH1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-mempool-007-PsDELPH1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-mempool-007-PsDELPH1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-mempool-007-PsDELPH1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-mempool-008-PtEdoTez.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-mempool-008-PtEdoTez.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-mempool-008-PtEdoTez.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-mempool-008-PtEdoTez.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-commands.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-mockup-commands.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-mockup-commands.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-mockup-commands.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-commands.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup-proxy.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-mockup-proxy.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-mockup-proxy.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-mockup-registration.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-registration.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup.15.0 on 4.14 is now installable. Current state is: partially failing
• tezos-mockup.15.1 on 4.14 is now installable. Current state is: partially failing
• tezos-mockup.16.0 on 4.14 is now installable. Current state is: partially failing
• tezos-mockup.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-node.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-node.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-node.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-node.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-node.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-node.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-node.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-node.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.9.2 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.9.2 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.9.2 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.9.2 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.9.3 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.9.3 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.9.3 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.9.3 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.9.4 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.9.4 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.9.4 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.9.4 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p-services.9.7 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p-services.9.7 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p-services.9.7 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p-services.9.7 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.10.2 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.10.2 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.10.2 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.10.2 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.8.0 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.8.0 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.8.1 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.8.1 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.8.2 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.8.2 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.8.3 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.8.3 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.9.1 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.9.1 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.9.1 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.9.1 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.9.2 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.9.2 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.9.2 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.9.2 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.9.3 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.9.3 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.9.3 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.9.3 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.9.4 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.9.4 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.9.4 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.9.4 on 4.11 had its build status changed: passing to partially failing
• tezos-p2p.9.7 on 4.08 had its build status changed: passing to partially failing
• tezos-p2p.9.7 on 4.09 had its build status changed: passing to partially failing
• tezos-p2p.9.7 on 4.10 had its build status changed: passing to partially failing
• tezos-p2p.9.7 on 4.11 had its build status changed: passing to partially failing
• tezos-protocol-000-Ps9mPmXa.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-000-Ps9mPmXa.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-000-Ps9mPmXa.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-000-Ps9mPmXa.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-000-Ps9mPmXa.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-000-Ps9mPmXa.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-000-Ps9mPmXa.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-000-Ps9mPmXa.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-001-PtCJ7pwo.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-001-PtCJ7pwo.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-001-PtCJ7pwo.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-001-PtCJ7pwo.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-001-PtCJ7pwo.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-001-PtCJ7pwo.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-001-PtCJ7pwo.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-001-PtCJ7pwo.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-002-PsYLVpVv.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-002-PsYLVpVv.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-002-PsYLVpVv.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-002-PsYLVpVv.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-002-PsYLVpVv.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-002-PsYLVpVv.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-002-PsYLVpVv.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-002-PsYLVpVv.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-003-PsddFKi3.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-003-PsddFKi3.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-003-PsddFKi3.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-003-PsddFKi3.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-003-PsddFKi3.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-003-PsddFKi3.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-003-PsddFKi3.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-003-PsddFKi3.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-004-Pt24m4xi.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-004-Pt24m4xi.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-004-Pt24m4xi.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-004-Pt24m4xi.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-004-Pt24m4xi.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-004-Pt24m4xi.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-004-Pt24m4xi.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-004-Pt24m4xi.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBABY5H.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBABY5H.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBABY5H.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBABY5H.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBABY5H.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBABY5H.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBABY5H.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBABY5H.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBabyM1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBabyM1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBabyM1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBabyM1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBabyM1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBabyM1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBabyM1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBabyM1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA-parameters.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA-parameters.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA-parameters.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA-parameters.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA-parameters.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA-parameters.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA-parameters.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA-parameters.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1-parameters.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1-parameters.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1-parameters.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1-parameters.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1-parameters.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1-parameters.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1-parameters.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1-parameters.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1.8.1 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk-parameters.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk-parameters.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk-parameters.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk-parameters.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk.8.2 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk.8.2 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk.8.3 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk.8.3 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdoTez-parameters.8.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdoTez-parameters.8.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdoTez-parameters.8.1 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdoTez-parameters.8.1 on 4.10 had its build status changed: