Home|Differences with the last checks|Previous runs

Differences between 99b05ee and 8fc7af6 (git diff)

Packages now failing:

• amf.0.1.0 on 4.03 had its build status changed: internal failure to failing
• amqp-client-async.2.0.0 on 4.05 had its build status changed: internal failure to failing
• amqp-client-lwt.2.0.0 on 4.06 had its build status changed: internal failure to failing
• amqp-client.0.2.0 on 4.02 had its build status changed: internal failure to failing
• bap-frontc.1.0.0 on 4.04 had its build status changed: partially failing to failing
• bap-ida-plugin.2.0.0 on 4.07 is now installable. Current state is: failing
• bap-ida-plugin.2.1.0 on 4.08 is now installable. Current state is: failing
• bap-ida-plugin.2.1.0 on 4.09 is now installable. Current state is: failing
• bap-llvm.1.0.0 on 4.02 is now installable. Current state is: failing
• bap-llvm.1.0.0 on 4.03 is now installable. Current state is: failing
• bap-llvm.1.1.0 on 4.02 is now installable. Current state is: failing
• bap-llvm.1.1.0 on 4.03 is now installable. Current state is: failing
• bap-llvm.1.2.0 on 4.02 is now installable. Current state is: failing
• bap-llvm.1.2.0 on 4.03 is now installable. Current state is: failing
• bap-llvm.1.2.0 on 4.04 is now installable. Current state is: failing
• bap-llvm.1.3.0 on 4.02 is now installable. Current state is: failing
• bap-llvm.1.3.0 on 4.03 is now installable. Current state is: failing
• bap-llvm.1.3.0 on 4.04 is now installable. Current state is: failing
• brr.0.0.1 on 4.13 had its build status changed: not available to failing
• bytepdf.0.1 on 4.04 had its build status changed: passing to failing
• bytepdf.0.1 on 4.05 had its build status changed: passing to failing
• bytepdf.0.1 on 4.06 had its build status changed: passing to failing
• bytepdf.0.1 on 4.07 had its build status changed: passing to failing
• channel.1.0.0 on 4.03 had its build status changed: passing to failing
• channel.1.0.0 on 4.04 had its build status changed: passing to failing
• channel.1.0.0 on 4.05 had its build status changed: passing to failing
• channel.1.1.0 on 4.03 had its build status changed: passing to failing
• channel.1.1.0 on 4.04 had its build status changed: passing to failing
• channel.1.1.0 on 4.05 had its build status changed: passing to failing
• channel.1.1.1 on 4.03 had its build status changed: passing to failing
• channel.1.1.1 on 4.04 had its build status changed: passing to failing
• channel.1.1.1 on 4.05 had its build status changed: passing to failing
• coqide.8.11.1 on 4.05 had its build status changed: partially failing to failing
• cpdf.2.2.1 on 4.02 had its build status changed: passing to failing
• cpdf.2.2.1 on 4.03 had its build status changed: passing to failing
• cpdf.2.2.1 on 4.04 had its build status changed: passing to failing
• cpdf.2.2.1 on 4.05 had its build status changed: passing to failing
• cwe_checker.0.3 on 4.07 is now installable. Current state is: failing
• datakit.0.12.0 on 4.04 had its build status changed: passing to failing
• datakit.0.12.0 on 4.05 had its build status changed: passing to failing
• github.0.8.0 on 4.02 had its build status changed: passing to failing
• github.0.8.1 on 4.02 had its build status changed: passing to failing
• github.0.9.0 on 4.02 had its build status changed: passing to failing
• github.0.9.1 on 4.02 had its build status changed: passing to failing
• github.0.9.2 on 4.02 had its build status changed: passing to failing
• github.0.9.3 on 4.02 had its build status changed: passing to failing
• github.0.9.4 on 4.02 had its build status changed: passing to failing
• gopcaml-mode.0.0.2 on 4.13 had its build status changed: not available to failing
• irmin.0.10.0 on 4.04 had its build status changed: passing to failing
• irmin.0.10.1 on 4.04 had its build status changed: passing to failing
• irmin.0.11.0 on 4.04 had its build status changed: passing to failing
• irmin.0.11.0 on 4.05 had its build status changed: passing to failing
• irmin.0.11.1 on 4.04 had its build status changed: passing to failing
• irmin.0.11.1 on 4.05 had its build status changed: passing to failing
• irmin.0.12.0 on 4.04 had its build status changed: passing to failing
• irmin.0.12.0 on 4.05 had its build status changed: passing to failing
• irmin.1.1.0 on 4.03 had its build status changed: passing to failing
• irmin.1.1.0 on 4.04 had its build status changed: passing to failing
• irmin.1.1.0 on 4.05 had its build status changed: passing to failing
• jhupllib.0.2.1 on 4.04 had its build status changed: passing to failing
• lablgtk3-extras.3.0 on 4.13 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.03 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.04 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.05 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.06 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.07 is now installable. Current state is: failing
• lablqml.0.5.2 on 4.08 is now installable. Current state is: failing
• lablqml.0.6 on 4.04 is now installable. Current state is: failing
• lablqml.0.6 on 4.05 is now installable. Current state is: failing
• lablqml.0.6 on 4.06 is now installable. Current state is: failing
• lablqml.0.6 on 4.07 is now installable. Current state is: failing
• lablqml.0.6 on 4.08 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.04 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.05 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.06 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.07 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.08 is now installable. Current state is: failing
• lablqml.0.6.2 on 4.09 is now installable. Current state is: failing
• liquidsoap.1.2.0 on 4.04 had its build status changed: passing to failing
• liquidsoap.1.2.0 on 4.05 had its build status changed: passing to failing
• liquidsoap.1.2.1 on 4.04 had its build status changed: passing to failing
• liquidsoap.1.2.1 on 4.05 had its build status changed: passing to failing
• mdx.1.10.0 on 4.13 is now installable. Current state is: failing
• mdx.1.8.1 on 4.13 had its build status changed: not available to failing
• mdx.1.9.0 on 4.13 is now installable. Current state is: failing
• metaquot.0.4.0 on 4.13 had its build status changed: not available to failing
• mirage-net-solo5.0.2.0 on 4.03 had its build status changed: passing to failing
• mirage-net-solo5.0.2.0 on 4.04 had its build status changed: passing to failing
• mirage-net-solo5.0.2.0 on 4.05 had its build status changed: passing to failing
• mrt-format.0.2.0 on 4.04 had its build status changed: passing to failing
• mrt-format.0.2.0 on 4.05 had its build status changed: passing to failing
• mysql8.1.0 on 4.13 had its build status changed: not available to failing
• opam2web.1.5.0 on 4.04 had its build status changed: passing to failing
• opam2web.1.5.0 on 4.05 had its build status changed: passing to failing
• opam2web.1.5.0 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.10.0 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.10.0 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.10.0 on 4.12 had its build status changed: passing to failing
• owl-zoo.0.10.0 on 4.13 had its build status changed: passing to failing
• owl-zoo.0.3.7 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.3.7 on 4.07 had its build status changed: passing to failing
• owl-zoo.0.3.7 on 4.08 had its build status changed: passing to failing
• owl-zoo.0.3.7 on 4.09 had its build status changed: passing to failing
• owl-zoo.0.3.7 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.3.7 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.3.8 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.3.8 on 4.07 had its build status changed: passing to failing
• owl-zoo.0.3.8 on 4.08 had its build status changed: passing to failing
• owl-zoo.0.3.8 on 4.09 had its build status changed: passing to failing
• owl-zoo.0.3.8 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.3.8 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.4.0 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.4.0 on 4.07 had its build status changed: passing to failing
• owl-zoo.0.4.0 on 4.08 had its build status changed: passing to failing
• owl-zoo.0.4.0 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.4.0 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.5.0 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.5.0 on 4.07 had its build status changed: passing to failing
• owl-zoo.0.5.0 on 4.08 had its build status changed: passing to failing
• owl-zoo.0.5.0 on 4.09 had its build status changed: passing to failing
• owl-zoo.0.5.0 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.5.0 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.5.0 on 4.12 had its build status changed: passing to failing
• owl-zoo.0.5.0 on 4.13 had its build status changed: passing to failing
• owl-zoo.0.6.0 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.6.0 on 4.07 had its build status changed: passing to failing
• owl-zoo.0.7.0 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.7.0 on 4.07 had its build status changed: passing to failing
• owl-zoo.0.7.0 on 4.08 had its build status changed: passing to failing
• owl-zoo.0.7.0 on 4.09 had its build status changed: passing to failing
• owl-zoo.0.7.0 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.7.0 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.7.0 on 4.12 had its build status changed: passing to failing
• owl-zoo.0.7.0 on 4.13 had its build status changed: passing to failing
• owl-zoo.0.7.1 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.7.1 on 4.07 had its build status changed: passing to failing
• owl-zoo.0.7.1 on 4.08 had its build status changed: passing to failing
• owl-zoo.0.7.1 on 4.09 had its build status changed: passing to failing
• owl-zoo.0.7.1 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.7.1 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.7.1 on 4.12 had its build status changed: passing to failing
• owl-zoo.0.7.1 on 4.13 had its build status changed: passing to failing
• owl-zoo.0.7.2 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.7.2 on 4.07 had its build status changed: passing to failing
• owl-zoo.0.7.2 on 4.08 had its build status changed: passing to failing
• owl-zoo.0.7.2 on 4.09 had its build status changed: passing to failing
• owl-zoo.0.7.2 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.7.2 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.7.2 on 4.12 had its build status changed: passing to failing
• owl-zoo.0.7.2 on 4.13 had its build status changed: passing to failing
• owl-zoo.0.8.0 on 4.06 had its build status changed: passing to failing
• owl-zoo.0.8.0 on 4.07 had its build status changed: passing to failing
• owl-zoo.0.8.0 on 4.08 had its build status changed: passing to failing
• owl-zoo.0.8.0 on 4.09 had its build status changed: passing to failing
• owl-zoo.0.8.0 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.8.0 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.8.0 on 4.12 had its build status changed: passing to failing
• owl-zoo.0.8.0 on 4.13 had its build status changed: passing to failing
• owl-zoo.0.9.0 on 4.10 had its build status changed: passing to failing
• owl-zoo.0.9.0 on 4.11 had its build status changed: passing to failing
• owl-zoo.0.9.0 on 4.12 had its build status changed: passing to failing
• owl-zoo.0.9.0 on 4.13 had its build status changed: passing to failing
• owl-zoo.1.0.0 on 4.10 had its build status changed: passing to failing
• owl-zoo.1.0.0 on 4.11 had its build status changed: passing to failing
• owl-zoo.1.0.0 on 4.12 had its build status changed: passing to failing
• owl-zoo.1.0.0 on 4.13 had its build status changed: passing to failing
• owl-zoo.1.0.1 on 4.10 had its build status changed: passing to failing
• owl-zoo.1.0.1 on 4.11 had its build status changed: passing to failing
• owl-zoo.1.0.1 on 4.12 had its build status changed: passing to failing
• owl-zoo.1.0.1 on 4.13 had its build status changed: passing to failing
• owl.0.2.9 on 4.04 had its build status changed: passing to failing
• owl.0.2.9 on 4.05 had its build status changed: passing to failing
• rdf.0.12.0 on 4.13 is now installable. Current state is: failing
• sparrow.0.1 on 4.03 had its build status changed: passing to failing
• stog.0.17.0 on 4.06 had its build status changed: internal failure to failing
• stog.0.17.1 on 4.04 had its build status changed: internal failure to failing
• stog.0.18.0 on 4.07 had its build status changed: internal failure to failing
• stog.0.18.0-1 on 4.05 had its build status changed: internal failure to failing
• stog.0.18.0-1 on 4.06 had its build status changed: internal failure to failing
• tar-mirage.1.0.0 on 4.13 had its build status changed: not available to failing
• tar-mirage.1.0.1 on 4.13 had its build status changed: not available to failing
• tar-mirage.1.1.0 on 4.13 had its build status changed: not available to failing
• tcpip.3.2.0 on 4.03 had its build status changed: passing to failing
• tcpip.3.2.0 on 4.04 had its build status changed: passing to failing
• tcpip.3.2.0 on 4.05 had its build status changed: passing to failing
• tcpip.3.3.0 on 4.03 had its build status changed: passing to failing
• tcpip.3.3.0 on 4.04 had its build status changed: passing to failing
• tcpip.3.3.0 on 4.05 had its build status changed: passing to failing
• tcpip.3.3.1 on 4.03 had its build status changed: passing to failing
• tcpip.3.3.1 on 4.04 had its build status changed: passing to failing
• tcpip.3.3.1 on 4.05 had its build status changed: passing to failing
• tcpip.3.4.0 on 4.04 had its build status changed: passing to failing
• tcpip.3.4.0 on 4.05 had its build status changed: passing to failing
• tezos-storage.9.0 on 4.08 had its build status changed: passing to failing
• tezos-storage.9.0 on 4.09 had its build status changed: passing to failing
• tezos-storage.9.0 on 4.10 had its build status changed: passing to failing
• tezos-storage.9.0 on 4.11 had its build status changed: passing to failing
• uri.2.0.0 on 4.09 had its build status changed: passing to failing
• vorbis.0.6.2 on 4.02 had its build status changed: passing to failing
• vorbis.0.6.2 on 4.03 had its build status changed: passing to failing
• vorbis.0.6.2 on 4.04 had its build status changed: passing to failing
• vorbis.0.6.2 on 4.05 had its build status changed: passing to failing
• vorbis.0.7.0 on 4.02 had its build status changed: passing to failing
• vorbis.0.7.0 on 4.03 had its build status changed: passing to failing
• vorbis.0.7.0 on 4.04 had its build status changed: passing to failing
• vorbis.0.7.0 on 4.05 had its build status changed: passing to failing
• why3-base.0.86.3 on 4.02 had its build status changed: passing to failing
• why3-base.0.86.3 on 4.03 had its build status changed: passing to failing
• why3-base.0.86.3 on 4.04 had its build status changed: passing to failing
• why3-base.0.86.3 on 4.05 had its build status changed: passing to failing
• why3-base.0.87.0 on 4.02 had its build status changed: passing to failing
• why3-base.0.87.0 on 4.03 had its build status changed: passing to failing
• why3-base.0.87.0 on 4.04 had its build status changed: passing to failing
• why3-base.0.87.0 on 4.05 had its build status changed: passing to failing
• why3-base.0.87.1 on 4.02 had its build status changed: passing to failing
• why3-base.0.87.1 on 4.03 had its build status changed: passing to failing
• why3-base.0.87.1 on 4.04 had its build status changed: passing to failing
• why3-base.0.87.1 on 4.05 had its build status changed: passing to failing
• why3-base.0.87.2 on 4.02 had its build status changed: passing to failing
• why3-base.0.87.2 on 4.03 had its build status changed: passing to failing
• why3-base.0.87.2 on 4.04 had its build status changed: passing to failing
• why3-base.0.87.2 on 4.05 had its build status changed: passing to failing
• why3-base.0.87.3 on 4.02 had its build status changed: passing to failing
• why3-base.0.87.3 on 4.03 had its build status changed: passing to failing
• why3-base.0.87.3 on 4.04 had its build status changed: passing to failing
• why3-base.0.87.3 on 4.05 had its build status changed: passing to failing
• why3-base.0.88.0 on 4.02 had its build status changed: passing to failing
• why3-base.0.88.0 on 4.03 had its build status changed: passing to failing
• why3-base.0.88.0 on 4.04 had its build status changed: passing to failing
• why3-base.0.88.0 on 4.05 had its build status changed: passing to failing
• why3-base.0.88.1 on 4.02 had its build status changed: passing to failing
• why3-base.0.88.1 on 4.03 had its build status changed: passing to failing
• why3-base.0.88.1 on 4.04 had its build status changed: passing to failing
• why3-base.0.88.1 on 4.05 had its build status changed: passing to failing
• why3-base.0.88.2 on 4.02 had its build status changed: passing to failing
• why3-base.0.88.2 on 4.03 had its build status changed: passing to failing
• why3-base.0.88.2 on 4.04 had its build status changed: passing to failing
• why3-base.0.88.2 on 4.05 had its build status changed: passing to failing
• why3-base.0.88.3 on 4.02 had its build status changed: passing to failing
• why3-base.0.88.3 on 4.03 had its build status changed: passing to failing
• why3-base.0.88.3 on 4.04 had its build status changed: passing to failing
• why3-base.0.88.3 on 4.05 had its build status changed: passing to failing
• zipperposition.1.4 on 4.03 had its build status changed: passing to failing
• zipperposition.1.4 on 4.04 had its build status changed: passing to failing
• zipperposition.1.4 on 4.05 had its build status changed: passing to failing
• zipperposition.1.4 on 4.06 had its build status changed: passing to failing

Packages now partially failing:

• bap-arm.1.0.0 on 4.02 is now installable. Current state is: partially failing
• bap-arm.1.0.0 on 4.03 is now installable. Current state is: partially failing
• bap-arm.1.0.0 on 4.04 is now installable. Current state is: partially failing
• bap-arm.1.1.0 on 4.02 is now installable. Current state is: partially failing
• bap-arm.1.1.0 on 4.03 is now installable. Current state is: partially failing
• bap-arm.1.1.0 on 4.04 is now installable. Current state is: partially failing
• bap-arm.1.2.0 on 4.02 is now installable. Current state is: partially failing
• bap-arm.1.2.0 on 4.03 is now installable. Current state is: partially failing
• bap-arm.1.2.0 on 4.04 is now installable. Current state is: partially failing
• bap-arm.1.3.0 on 4.02 is now installable. Current state is: partially failing
• bap-arm.1.3.0 on 4.03 is now installable. Current state is: partially failing
• bap-arm.1.3.0 on 4.04 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.0.0 on 4.02 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.0.0 on 4.03 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.1.0 on 4.02 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.1.0 on 4.03 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.2.0 on 4.02 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.2.0 on 4.03 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.2.0 on 4.04 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.3.0 on 4.02 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.3.0 on 4.03 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.3.0 on 4.04 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.6.0 on 4.04 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.6.0 on 4.05 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.6.0 on 4.06 is now installable. Current state is: partially failing
• bap-fsi-benchmark.1.6.0 on 4.07 is now installable. Current state is: partially failing
• bap-fsi-benchmark.2.2.0 on 4.08 is now installable. Current state is: partially failing
• bap-fsi-benchmark.2.2.0 on 4.09 is now installable. Current state is: partially failing
• bap-fsi-benchmark.2.3.0 on 4.08 is now installable. Current state is: partially failing
• bap-fsi-benchmark.2.3.0 on 4.09 is now installable. Current state is: partially failing
• bap-fsi-benchmark.2.3.0 on 4.10 is now installable. Current state is: partially failing
• bap-fsi-benchmark.2.3.0 on 4.11 is now installable. Current state is: partially failing
• bap-fsi-benchmark.2.3.0 on 4.12 is now installable. Current state is: partially failing
• bap-ida-plugin.1.0.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida-plugin.1.0.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida-plugin.1.1.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida-plugin.1.1.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida-plugin.1.2.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida-plugin.1.2.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida-plugin.1.2.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida-plugin.1.3.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida-plugin.1.3.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida-plugin.1.3.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida-plugin.2.0.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida-plugin.2.0.0 on 4.05 is now installable. Current state is: partially failing
• bap-ida-plugin.2.0.0 on 4.06 is now installable. Current state is: partially failing
• bap-ida-python.1.0.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida-python.1.0.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida-python.1.1.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida-python.1.1.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida-python.1.2.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida-python.1.2.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida-python.1.2.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida-python.1.3.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida-python.1.3.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida-python.1.3.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida-python.1.6.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida-python.1.6.0 on 4.05 is now installable. Current state is: partially failing
• bap-ida-python.1.6.0 on 4.06 is now installable. Current state is: partially failing
• bap-ida-python.1.6.0 on 4.07 is now installable. Current state is: partially failing
• bap-ida-python.2.0.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida-python.2.0.0 on 4.05 is now installable. Current state is: partially failing
• bap-ida-python.2.0.0 on 4.06 is now installable. Current state is: partially failing
• bap-ida-python.2.0.0 on 4.07 is now installable. Current state is: partially failing
• bap-ida-python.2.1.0 on 4.07 is now installable. Current state is: partially failing
• bap-ida-python.2.1.0 on 4.08 is now installable. Current state is: partially failing
• bap-ida-python.2.1.0 on 4.09 is now installable. Current state is: partially failing
• bap-ida-python.2.2.0 on 4.08 is now installable. Current state is: partially failing
• bap-ida-python.2.2.0 on 4.09 is now installable. Current state is: partially failing
• bap-ida-python.2.3.0 on 4.08 is now installable. Current state is: partially failing
• bap-ida-python.2.3.0 on 4.09 is now installable. Current state is: partially failing
• bap-ida-python.2.3.0 on 4.10 is now installable. Current state is: partially failing
• bap-ida-python.2.3.0 on 4.11 is now installable. Current state is: partially failing
• bap-ida-python.2.3.0 on 4.12 is now installable. Current state is: partially failing
• bap-ida.1.0.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida.1.0.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida.1.1.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida.1.1.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida.1.2.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida.1.2.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida.1.2.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida.1.3.0 on 4.02 is now installable. Current state is: partially failing
• bap-ida.1.3.0 on 4.03 is now installable. Current state is: partially failing
• bap-ida.1.3.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida.1.6.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida.1.6.0 on 4.05 is now installable. Current state is: partially failing
• bap-ida.1.6.0 on 4.06 is now installable. Current state is: partially failing
• bap-ida.1.6.0 on 4.07 is now installable. Current state is: partially failing
• bap-ida.2.0.0 on 4.04 is now installable. Current state is: partially failing
• bap-ida.2.0.0 on 4.05 is now installable. Current state is: partially failing
• bap-ida.2.0.0 on 4.06 is now installable. Current state is: partially failing
• bap-ida.2.0.0 on 4.07 is now installable. Current state is: partially failing
• bap-ida.2.1.0 on 4.07 is now installable. Current state is: partially failing
• bap-ida.2.1.0 on 4.08 is now installable. Current state is: partially failing
• bap-ida.2.1.0 on 4.09 is now installable. Current state is: partially failing
• bap-ida.2.2.0 on 4.08 is now installable. Current state is: partially failing
• bap-ida.2.2.0 on 4.09 is now installable. Current state is: partially failing
• bap-ida.2.3.0 on 4.08 is now installable. Current state is: partially failing
• bap-ida.2.3.0 on 4.09 is now installable. Current state is: partially failing
• bap-ida.2.3.0 on 4.10 is now installable. Current state is: partially failing
• bap-ida.2.3.0 on 4.11 is now installable. Current state is: partially failing
• bap-ida.2.3.0 on 4.12 is now installable. Current state is: partially failing
• bap-llvm.1.0.0 on 4.04 is now installable. Current state is: partially failing
• bap-llvm.1.1.0 on 4.04 is now installable. Current state is: partially failing
• bap-primus-x86.1.3.0 on 4.02 is now installable. Current state is: partially failing
• bap-primus-x86.1.3.0 on 4.03 is now installable. Current state is: partially failing
• bap-primus-x86.1.3.0 on 4.04 is now installable. Current state is: partially failing
• bap-server.0.1.0 on 4.02 is now installable. Current state is: partially failing
• bap-server.0.1.0 on 4.03 is now installable. Current state is: partially failing
• bap-server.0.1.0 on 4.04 is now installable. Current state is: partially failing
• bap-x86.1.0.0 on 4.02 is now installable. Current state is: partially failing
• bap-x86.1.0.0 on 4.03 is now installable. Current state is: partially failing
• bap-x86.1.0.0 on 4.04 is now installable. Current state is: partially failing
• bap-x86.1.1.0 on 4.02 is now installable. Current state is: partially failing
• bap-x86.1.1.0 on 4.03 is now installable. Current state is: partially failing
• bap-x86.1.1.0 on 4.04 is now installable. Current state is: partially failing
• bap-x86.1.2.0 on 4.02 is now installable. Current state is: partially failing
• bap-x86.1.2.0 on 4.03 is now installable. Current state is: partially failing
• bap-x86.1.2.0 on 4.04 is now installable. Current state is: partially failing
• bap-x86.1.3.0 on 4.02 is now installable. Current state is: partially failing
• bap-x86.1.3.0 on 4.03 is now installable. Current state is: partially failing
• bap-x86.1.3.0 on 4.04 is now installable. Current state is: partially failing
• bap.1.0.0 on 4.02 is now installable. Current state is: partially failing
• bap.1.0.0 on 4.03 is now installable. Current state is: partially failing
• bap.1.1.0 on 4.02 is now installable. Current state is: partially failing
• bap.1.1.0 on 4.03 is now installable. Current state is: partially failing
• bap.1.2.0 on 4.02 is now installable. Current state is: partially failing
• bap.1.2.0 on 4.03 is now installable. Current state is: partially failing
• bap.1.2.0 on 4.04 is now installable. Current state is: partially failing
• bap.1.3.0 on 4.02 is now installable. Current state is: partially failing
• bap.1.3.0 on 4.03 is now installable. Current state is: partially failing
• bap.1.3.0 on 4.04 is now installable. Current state is: partially failing
• bap.2.0.0 on 4.04 is now installable. Current state is: partially failing
• bap.2.0.0 on 4.05 is now installable. Current state is: partially failing
• bap.2.0.0 on 4.06 is now installable. Current state is: partially failing
• bap.2.0.0 on 4.07 is now installable. Current state is: partially failing
• charrua-client-lwt.0.10 on 4.03 had its build status changed: passing to partially failing
• charrua-client-lwt.0.9 on 4.03 had its build status changed: passing to partially failing
• charrua-client-mirage.0.9 on 4.03 had its build status changed: passing to partially failing
• charrua-client.0.10 on 4.03 had its build status changed: passing to partially failing
• charrua-client.0.9 on 4.03 had its build status changed: passing to partially failing
• charrua-core.0.10 on 4.03 had its build status changed: passing to partially failing
• charrua-core.0.11.0 on 4.03 had its build status changed: passing to partially failing
• charrua-core.0.9 on 4.03 had its build status changed: passing to partially failing
• clangml.4.4.0 on 4.13 had its build status changed: not available to partially failing
• cohttp-async.2.1.1 on 4.05 had its build status changed: passing to partially failing
• cwe_checker.0.2 on 4.05 is now installable. Current state is: partially failing
• cwe_checker.0.2 on 4.06 is now installable. Current state is: partially failing
• cwe_checker.0.2 on 4.07 is now installable. Current state is: partially failing
• datakit-bridge-github.0.10.0 on 4.03 had its build status changed: passing to partially failing
• datakit-bridge-github.0.10.0 on 4.04 had its build status changed: passing to partially failing
• datakit-ci.0.10.0 on 4.03 had its build status changed: passing to partially failing
• datakit-ci.0.10.0 on 4.04 had its build status changed: passing to partially failing
• datakit-ci.0.10.1 on 4.03 had its build status changed: passing to partially failing
• datakit-ci.0.10.1 on 4.04 had its build status changed: passing to partially failing
• datakit-ci.0.11.0 on 4.03 had its build status changed: passing to partially failing
• datakit-ci.0.11.0 on 4.04 had its build status changed: passing to partially failing
• fkie-cad-cwe-checker.0.2 on 4.07 is now installable. Current state is: partially failing
• hardcaml-bloop.0.1.0 on 4.05 had its build status changed: passing to partially failing
• morsmall.0.1 on 4.13 had its build status changed: not available to partially failing
• opam-publish.0.2.0 on 4.02 had its build status changed: failing to partially failing
• opam-publish.0.2.1 on 4.02 had its build status changed: failing to partially failing
• opam-publish.0.3.5 on 4.05 had its build status changed: passing to partially failing
• opam-sync-github-prs.1.0.0 on 4.02 had its build status changed: failing to partially failing
• owl-jupyter.1.0 on 4.06 had its build status changed: passing to partially failing
• owl-jupyter.1.0 on 4.07 had its build status changed: passing to partially failing
• owl-jupyter.1.0 on 4.08 had its build status changed: passing to partially failing
• owl-jupyter.1.0 on 4.09 had its build status changed: passing to partially failing
• owl-jupyter.1.0 on 4.10 had its build status changed: passing to partially failing
• owl-jupyter.1.0 on 4.11 had its build status changed: passing to partially failing
• owl-jupyter.1.0 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.10.0 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.10.0 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.10.0 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.10.0 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.3.7 on 4.06 had its build status changed: passing to partially failing
• owl-top.0.3.7 on 4.07 had its build status changed: passing to partially failing
• owl-top.0.3.7 on 4.08 had its build status changed: passing to partially failing
• owl-top.0.3.7 on 4.09 had its build status changed: passing to partially failing
• owl-top.0.3.7 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.3.7 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.3.7 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.3.7 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.3.8 on 4.06 had its build status changed: passing to partially failing
• owl-top.0.3.8 on 4.07 had its build status changed: passing to partially failing
• owl-top.0.3.8 on 4.08 had its build status changed: passing to partially failing
• owl-top.0.3.8 on 4.09 had its build status changed: passing to partially failing
• owl-top.0.3.8 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.3.8 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.3.8 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.3.8 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.4.0 on 4.06 had its build status changed: passing to partially failing
• owl-top.0.4.0 on 4.07 had its build status changed: passing to partially failing
• owl-top.0.4.0 on 4.08 had its build status changed: passing to partially failing
• owl-top.0.4.0 on 4.09 had its build status changed: passing to partially failing
• owl-top.0.4.0 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.4.0 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.4.0 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.4.0 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.5.0 on 4.06 had its build status changed: passing to partially failing
• owl-top.0.5.0 on 4.07 had its build status changed: passing to partially failing
• owl-top.0.5.0 on 4.08 had its build status changed: passing to partially failing
• owl-top.0.5.0 on 4.09 had its build status changed: passing to partially failing
• owl-top.0.5.0 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.5.0 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.5.0 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.5.0 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.6.0 on 4.06 had its build status changed: passing to partially failing
• owl-top.0.6.0 on 4.07 had its build status changed: passing to partially failing
• owl-top.0.6.0 on 4.08 had its build status changed: passing to partially failing
• owl-top.0.6.0 on 4.09 had its build status changed: passing to partially failing
• owl-top.0.6.0 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.6.0 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.6.0 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.6.0 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.7.0 on 4.06 had its build status changed: passing to partially failing
• owl-top.0.7.0 on 4.07 had its build status changed: passing to partially failing
• owl-top.0.7.0 on 4.08 had its build status changed: passing to partially failing
• owl-top.0.7.0 on 4.09 had its build status changed: passing to partially failing
• owl-top.0.7.0 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.7.0 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.7.0 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.7.0 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.7.1 on 4.06 had its build status changed: passing to partially failing
• owl-top.0.7.1 on 4.07 had its build status changed: passing to partially failing
• owl-top.0.7.1 on 4.08 had its build status changed: passing to partially failing
• owl-top.0.7.1 on 4.09 had its build status changed: passing to partially failing
• owl-top.0.7.1 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.7.1 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.7.1 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.7.1 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.7.2 on 4.06 had its build status changed: passing to partially failing
• owl-top.0.7.2 on 4.07 had its build status changed: passing to partially failing
• owl-top.0.7.2 on 4.08 had its build status changed: passing to partially failing
• owl-top.0.7.2 on 4.09 had its build status changed: passing to partially failing
• owl-top.0.7.2 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.7.2 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.7.2 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.7.2 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.8.0 on 4.06 had its build status changed: passing to partially failing
• owl-top.0.8.0 on 4.07 had its build status changed: passing to partially failing
• owl-top.0.8.0 on 4.08 had its build status changed: passing to partially failing
• owl-top.0.8.0 on 4.09 had its build status changed: passing to partially failing
• owl-top.0.8.0 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.8.0 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.8.0 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.8.0 on 4.13 had its build status changed: passing to partially failing
• owl-top.0.9.0 on 4.10 had its build status changed: passing to partially failing
• owl-top.0.9.0 on 4.11 had its build status changed: passing to partially failing
• owl-top.0.9.0 on 4.12 had its build status changed: passing to partially failing
• owl-top.0.9.0 on 4.13 had its build status changed: passing to partially failing
• owl-top.1.0.0 on 4.10 had its build status changed: passing to partially failing
• owl-top.1.0.0 on 4.11 had its build status changed: passing to partially failing
• owl-top.1.0.0 on 4.12 had its build status changed: passing to partially failing
• owl-top.1.0.0 on 4.13 had its build status changed: passing to partially failing
• owl-top.1.0.1 on 4.10 had its build status changed: passing to partially failing
• owl-top.1.0.1 on 4.11 had its build status changed: passing to partially failing
• owl-top.1.0.1 on 4.12 had its build status changed: passing to partially failing
• owl-top.1.0.1 on 4.13 had its build status changed: passing to partially failing
• pattern.0.3.0 on 4.13 had its build status changed: not available to partially failing
• pds-reachability.0.2 on 4.04 had its build status changed: passing to partially failing
• pds-reachability.0.2.1 on 4.04 had its build status changed: passing to partially failing
• ppx_pbt.0.1.0 on 4.13 had its build status changed: not available to partially failing
• qocamlbrowser.0.2.10 on 4.04 is now installable. Current state is: partially failing
• qocamlbrowser.0.2.10 on 4.05 is now installable. Current state is: partially failing
• qocamlbrowser.0.2.10 on 4.06 is now installable. Current state is: partially failing
• qocamlbrowser.0.2.10 on 4.07 is now installable. Current state is: partially failing
• qocamlbrowser.0.2.11 on 4.08 is now installable. Current state is: partially failing
• qocamlbrowser.0.2.11 on 4.09 is now installable. Current state is: partially failing
• qocamlbrowser.0.2.9 on 4.04 is now installable. Current state is: partially failing
• qocamlbrowser.0.2.9 on 4.05 is now installable. Current state is: partially failing
• refl.0.4.0 on 4.13 had its build status changed: not available to partially failing
• sphinxcontrib-ocaml.0.2.0 on 4.05 had its build status changed: failing to partially failing
• stog.0.17.1 on 4.03 had its build status changed: internal failure to partially failing
• tezos-accuser-008-PtEdo2Zk.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-accuser-009-PsFLoren.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-alpha-test-helpers.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-008-PtEdo2Zk.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baker-009-PsFLoren.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-008-PtEdo2Zk.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-009-PsFLoren-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-009-PsFLoren.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-alpha-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-baking-alpha.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-000-Ps9mPmXa.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-001-PtCJ7pwo.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-002-PsYLVpVv.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-003-PsddFKi3.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-004-Pt24m4xi.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-005-PsBabyM1.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-006-PsCARTHA.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands-registration.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-007-PsDELPH1.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands-registration.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-008-PtEdo2Zk.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-009-PsFLoren-commands-registration.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-009-PsFLoren-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-009-PsFLoren.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha-commands-registration.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-alpha.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base-unix.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base-unix.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base-unix.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base-unix.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-client-base.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-client-base.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-base.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-base.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-client-commands.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-client-commands.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-client-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-commands.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-client-demo-counter.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis-carthagenet.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-genesis.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-sapling-008-PtEdo2Zk.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-sapling-009-PsFLoren.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client-sapling-alpha.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-client.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-codec.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-codec.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-codec.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-codec.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-embedded-protocol-000-Ps9mPmXa.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-001-PtCJ7pwo.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-002-PsYLVpVv.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-003-PsddFKi3.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-004-Pt24m4xi.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBABY5H.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-005-PsBabyM1.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-006-PsCARTHA.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-007-PsDELPH1.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdo2Zk.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-008-PtEdoTez.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-009-PsFLoren.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-alpha.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-counter.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-demo-noops.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis-carthagenet.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-embedded-protocol-genesis.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-008-PtEdo2Zk.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-endorser-009-PsFLoren.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-commands.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-commands.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-commands.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-commands.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup-registration.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup-registration.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup-registration.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup-registration.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-mockup.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-mockup.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-mockup.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-mockup.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-node.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-000-Ps9mPmXa.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-001-PtCJ7pwo.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-002-PsYLVpVv.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-003-PsddFKi3.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-004-Pt24m4xi.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBABY5H.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-005-PsBabyM1.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA-parameters.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-006-PsCARTHA.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-007-PsDELPH1.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk-parameters.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdo2Zk.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-008-PtEdoTez.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-009-PsFLoren-parameters.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-009-PsFLoren.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-alpha-parameters.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-alpha.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-compiler.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-demo-counter.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-demo-noops.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-environment.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-protocol-environment.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-protocol-environment.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-environment.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-protocol-genesis-carthagenet.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-genesis.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-plugin-007-PsDELPH1-registerer.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-plugin-007-PsDELPH1.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-plugin-008-PtEdo2Zk-registerer.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-plugin-008-PtEdo2Zk.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-plugin-009-PsFLoren-registerer.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-plugin-009-PsFLoren.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-plugin-alpha-registerer.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-plugin-alpha.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-protocol-updater.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-shell-context.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-shell-context.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-shell-context.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-shell-context.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-shell.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-signer-backends.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-signer-backends.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-signer-backends.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-signer-backends.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-signer-services.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-signer-services.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-signer-services.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-signer-services.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-signer.9.0 on 4.08 had its build status changed: passing to partially failing
• tezos-signer.9.0 on 4.09 had its build status changed: passing to partially failing
• tezos-signer.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-signer.9.0 on 4.11 had its build status changed: passing to partially failing
• tezos-validation.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos-validator.9.0 on 4.10 had its build status changed: passing to partially failing
• tezos.9.0 on 4.10 had its build status changed: passing to partially failing
• traverse.0.3.0 on 4.13 had its build status changed: not available to partially failing
• vpnkit.0.2.0 on 4.04 had its build status changed: passing to partially failing
• vpnkit.0.2.0 on 4.05 had its build status changed: passing to partially failing
• why.2.36 on 4.02 had its build status changed: passing to partially failing
• why.2.36 on 4.03 had its build status changed: passing to partially failing
• why.2.37 on 4.02 had its build status changed: passing to partially failing
• why.2.37 on 4.03 had its build status changed: passing to partially failing
• why.2.38 on 4.02 had its build status changed: passing to partially failing
• why.2.38 on 4.03 had its build status changed: passing to partially failing
• why.2.38 on 4.04 had its build status changed: passing to partially failing
• why.2.39 on 4.02 had its build status changed: passing to partially failing
• why.2.39 on 4.03 had its build status changed: passing to partially failing
• why.2.39 on 4.04 had its build status changed: passing to partially failing
• why.2.40 on 4.02 had its build status changed: passing to partially failing
• why.2.40 on 4.03 had its build status changed: passing to partially failing
• why.2.40 on 4.04 had its build status changed: passing to partially failing
• why.2.40 on 4.05 had its build status changed: passing to partially failing
• why.2.41 on 4.02 had its build status changed: passing to partially failing
• why.2.41 on 4.03 had its build status changed: passing to partially failing
• why.2.41 on 4.04 had its build status changed: passing to partially failing
• why.2.41 on 4.05 had its build status changed: passing to partially failing
• why3.0.85 on 4.03 had its build status changed: passing to partially failing
• why3.0.85 on 4.04 had its build status changed: passing to partially failing
• why3.0.85 on 4.05 had its build status changed: passing to partially failing
• why3.0.86 on 4.03 had its build status changed: passing to partially failing
• why3.0.86 on 4.04 had its build status changed: passing to partially failing
• why3.0.86 on 4.05 had its build status changed: passing to partially failing
• why3.0.86.2 on 4.03 had its build status changed: passing to partially failing
• why3.0.86.2 on 4.04 had its build status changed: passing to partially failing
• why3.0.86.2 on 4.05 had its build status changed: passing to partially failing
• why3.0.86.3 on 4.02 had its build status changed: passing to partially failing
• why3.0.86.3 on 4.03 had its build status changed: passing to partially failing
• why3.0.86.3 on 4.04 had its build status changed: passing to partially failing
• why3.0.86.3 on 4.05 had its build status changed: passing to partially failing
• why3.0.87.0 on 4.02 had its build status changed: passing to partially failing
• why3.0.87.0 on 4.03 had its build status changed: passing to partially failing
• why3.0.87.0 on 4.04 had its build status changed: passing to partially failing
• why3.0.87.0 on 4.05 had its build status changed: passing to partially failing
• why3.0.87.1 on 4.02 had its build status changed: passing to partially failing
• why3.0.87.1 on 4.03 had its build status changed: passing to partially failing
• why3.0.87.1 on 4.04 had its build status changed: passing to partially failing
• why3.0.87.1 on 4.05 had its build status changed: passing to partially failing
• why3.0.87.2 on 4.02 had its build status changed: passing to partially failing
• why3.0.87.2 on 4.03 had its build status changed: passing to partially failing
• why3.0.87.2 on 4.04 had its build status changed: passing to partially failing
• why3.0.87.2 on 4.05 had its build status changed: passing to partially failing
• why3.0.87.3 on 4.02 had its build status changed: passing to partially failing
• why3.0.87.3 on 4.03 had its build status changed: passing to partially failing
• why3.0.87.3 on 4.04 had its build status changed: passing to partially failing
• why3.0.87.3 on 4.05 had its build status changed: passing to partially failing
• why3.0.88.0 on 4.02 had its build status changed: passing to partially failing
• why3.0.88.0 on 4.03 had its build status changed: passing to partially failing
• why3.0.88.0 on 4.04 had its build status changed: passing to partially failing
• why3.0.88.0 on 4.05 had its build status changed: passing to partially failing
• why3.0.88.1 on 4.02 had its build status changed: passing to partially failing
• why3.0.88.1 on 4.03 had its build status changed: passing to partially failing
• why3.0.88.1 on 4.04 had its build status changed: passing to partially failing
• why3.0.88.1 on 4.05 had its build status changed: passing to partially failing
• why3.0.88.2 on 4.02 had its build status changed: passing to partially failing
• why3.0.88.2 on 4.03 had its build status changed: passing to partially failing
• why3.0.88.2 on 4.04 had its build status changed: passing to partially failing
• why3.0.88.2 on 4.05 had its build status changed: passing to partially failing
• why3.0.88.3 on 4.02 had its build status changed: passing to partially failing
• why3.0.88.3 on 4.03 had its build status changed: passing to partially failing
• why3.0.88.3 on 4.04 had its build status changed: passing to partially failing
• why3.0.88.3 on 4.05 had its build status changed: passing to partially failing

Packages now not available:

• 0install-solver.2.17 on 4.06 had its build status changed: failing to not available
• 0install.2.11 on 4.06 had its build status changed: failing to not available
• accessor_async.v0.14.1 on 4.02 had its build status changed: internal failure to not available
• camltc.0.9.6 on 4.08 had its build status changed: passing to not available
• camltc.0.9.6 on 4.09 had its build status changed: passing to not available
• camltc.0.9.6 on 4.10 had its build status changed: passing to not available
• camltc.0.9.6 on 4.11 had its build status changed: passing to not available
• camltc.0.9.6 on 4.12 had its build status changed: passing to not available
• camltc.0.9.6 on 4.13 had its build status changed: passing to not available
• conf-binutils.0.3 on 4.02 had its build status changed: passing to not available
• conf-binutils.0.3 on 4.03 had its build status changed: passing to not available
• conf-binutils.0.3 on 4.04 had its build status changed: passing to not available
• conf-binutils.0.3 on 4.05 had its build status changed: passing to not available
• conf-binutils.0.3 on 4.06 had its build status changed: passing to not available
• conf-binutils.0.3 on 4.07 had its build status changed: passing to not available
• kappa-agents.4.1.0 on 4.12 had its build status changed: internal failure to not available
• kappa-agents.4.1.0 on 4.13 had its build status changed: internal failure to not available
• kappa-binaries.4.1.0 on 4.12 had its build status changed: internal failure to not available
• kappa-binaries.4.1.0 on 4.13 had its build status changed: internal failure to not available
• kappa-library.4.1.0 on 4.12 had its build status changed: internal failure to not available
• kappa-library.4.1.0 on 4.13 had its build status changed: internal failure to not available
• kappa-server.4.1.0 on 4.12 had its build status changed: internal failure to not available
• lustre-v6.6.101.7 on 4.12 had its build status changed: internal failure to not available
• lustre-v6.6.101.7 on 4.13 had its build status changed: internal failure to not available
• ocamlformat.0.16.0 on 4.06 had its build status changed: passing to not available
• opam-depext.1.1.4 on 4.02 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.03 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.04 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.05 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.06 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.07 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.08 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.09 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.10 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.11 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.12 is not available anymore. Previous state was: passing
• opam-depext.1.1.4 on 4.13 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.02 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.03 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.04 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.05 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.06 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.07 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.08 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.09 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.10 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.11 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.12 is not available anymore. Previous state was: passing
• opam-depext.1.1.5 on 4.13 is not available anymore. Previous state was: passing
• opam-sync-github-prs.1.0.0 on 4.05 had its build status changed: internal failure to not available
• parsexp.v0.11.0 on 4.13 had its build status changed: failing to not available
• parsexp.v0.14.0 on 4.13 had its build status changed: failing to not available
• sexplib.v0.11.0 on 4.13 had its build status changed: partially failing to not available
• tezos-protocol-001-PtCJ7pwo.7.3 on 4.13 had its build status changed: failing to not available
• tezos-protocol-001-PtCJ7pwo.9.0 on 4.13 had its build status changed: failing to not available
• tezos-protocol-002-PsYLVpVv.7.4 on 4.13 had its build status changed: failing to not available
• tezos-protocol-002-PsYLVpVv.8.0 on 4.13 had its build status changed: failing to not available
• tezos-protocol-003-PsddFKi3.7.4 on 4.13 had its build status changed: failing to not available
• tezos-protocol-004-Pt24m4xi.7.2 on 4.13 had its build status changed: failing to not available
• tezos-protocol-004-Pt24m4xi.8.2 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBABY5H.7.3 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBABY5H.8.0 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBABY5H.9.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBabyM1.7.0 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBabyM1.7.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBabyM1.7.2 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBabyM1.7.4 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBabyM1.8.0 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBabyM1.8.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBabyM1.8.2 on 4.13 had its build status changed: failing to not available
• tezos-protocol-005-PsBabyM1.9.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-006-PsCARTHA-parameters.7.0 on 4.13 had its build status changed: failing to not available
• tezos-protocol-006-PsCARTHA-parameters.7.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-006-PsCARTHA-parameters.9.0 on 4.13 had its build status changed: failing to not available
• tezos-protocol-006-PsCARTHA.8.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-006-PsCARTHA.8.3 on 4.13 had its build status changed: failing to not available
• tezos-protocol-006-PsCARTHA.9.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-007-PsDELPH1-parameters.8.2 on 4.13 had its build status changed: failing to not available
• tezos-protocol-008-PtEdo2Zk.9.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-alpha.7.0 on 4.13 had its build status changed: failing to not available
• tezos-protocol-compiler.7.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-compiler.9.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-demo-counter.7.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-demo-counter.8.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-demo-noops.7.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-plugin-008-PtEdo2Zk-registerer.8.2 on 4.13 had its build status changed: failing to not available
• tezos-protocol-plugin-008-PtEdo2Zk-registerer.8.3 on 4.13 had its build status changed: failing to not available
• tezos-protocol-plugin-009-PsFLoren.9.1 on 4.13 had its build status changed: failing to not available
• tezos-protocol-updater.9.1 on 4.13 had its build status changed: failing to not available
• tezos-proxy.9.1 on 4.13 had its build status changed: failing to not available
• tezos-requester.8.1 on 4.13 had its build status changed: failing to not available
• tezos-requester.8.3 on 4.13 had its build status changed: failing to not available
• tezos-rpc-http-server.8.1 on 4.13 had its build status changed: failing to not available
• tezos-sapling.8.1 on 4.13 had its build status changed: failing to not available
• tezos-sapling.8.2 on 4.13 had its build status changed: failing to not available
• tezos-sapling.9.0 on 4.13 had its build status changed: failing to not available
• tezos-shell-context.7.3 on 4.13 had its build status changed: failing to not available
• tezos-shell-context.8.0 on 4.13 had its build status changed: failing to not available
• tezos-shell-context.8.2 on 4.13 had its build status changed: failing to not available
• tezos-shell-context.8.3 on 4.13 had its build status changed: failing to not available
• tezos-shell-services.7.0 on 4.13 had its build status changed: failing to not available
• tezos-shell-services.8.2 on 4.13 had its build status changed: failing to not available
• tezos-shell.7.0 on 4.13 had its build status changed: failing to not available
• tezos-shell.7.2 on 4.13 had its build status changed: failing to not available
• tezos-shell.9.0 on 4.13 had its build status changed: failing to not available
• tezos-signer-services.7.0 on 4.13 had its build status changed: failing to not available
• tezos-signer-services.7.2 on 4.13 had its build status changed: failing to not available
• tezos-signer-services.9.1 on 4.13 had its build status changed: failing to not available
• tezos-signer.9.0 on 4.13 had its build status changed: failing to not available
• tezos-stdlib-unix.8.0 on 4.13 had its build status changed: failing to not available
• tezos-stdlib-unix.8.1 on 4.13 had its build status changed: failing to not available
• tezos-stdlib-unix.8.3 on 4.13 had its build status changed: failing to not available
• tezos-storage.7.3 on 4.13 had its build status changed: failing to not available
• tezos-storage.7.4 on 4.13 had its build status changed: failing to not available
• tezos-storage.8.1 on 4.13 had its build status changed: failing to not available
• tezos-storage.8.2 on 4.13 had its build status changed: failing to not available
• tezos-test-services.8.3 on 4.13 had its build status changed: failing to not available
• tezos-test-services.9.0 on 4.13 had its build status changed: failing to not available
• tezos-tooling.7.0 on 4.13 had its build status changed: failing to not available
• tezos-tooling.7.3 on 4.13 had its build status changed: failing to not available
• tezos-validation.7.2 on 4.13 had its build status changed: failing to not available
• tezos-validation.8.1 on 4.13 had its build status changed: failing to not available
• tezos-validator.8.2 on 4.13 had its build status changed: failing to not available
• tezos-validator.9.1 on 4.13 had its build status changed: failing to not available
• tezos-version.8.1 on 4.13 had its build status changed: failing to not available
• tezos-workers.9.0 on 4.13 had its build status changed: failing to not available
• tezos-workers.9.1 on 4.13 had its build status changed: failing to not available
• tezos.7.1 on 4.13 had its build status changed: failing to not available
• tezos.7.4 on 4.13 had its build status changed: failing to not available
• tezos.8.0 on 4.13 had its build status changed: failing to not available
• tezos.8.1 on 4.13 had its build status changed: failing to not available
• tezos.9.0 on 4.13 had its build status changed: failing to not available
• tgls.0.8.1 on 4.13 had its build status changed: failing to not available
• tgls.0.8.3 on 4.13 had its build status changed: failing to not available
• thrift.0.9.0 on 4.13 had its build status changed: failing to not available
• tidy.5-0.2 on 4.13 had its build status changed: failing to not available
• tldr.0.1 on 4.13 had its build status changed: failing to not available
• tls-mirage.0.12.0 on 4.13 had its build status changed: failing to not available
• tls-mirage.0.12.4 on 4.13 had its build status changed: failing to not available
• tls.0.10.3 on 4.13 had its build status changed: failing to not available
• tls.0.11.0 on 4.13 had its build status changed: failing to not available
• tls.0.12.0 on 4.13 had its build status changed: failing to not available
• tls.0.12.3 on 4.13 had its build status changed: failing to not available
• tls.0.12.4 on 4.13 had its build status changed: failing to not available
• tls.0.7.0 on 4.13 had its build status changed: failing to not available
• tlstunnel.0.1.1 on 4.13 had its build status changed: failing to not available
• toml.2.1.0 on 4.13 had its build status changed: failing to not available
• topkg-care.0.9.0 on 4.13 had its build status changed: failing to not available
• topkg-care.0.9.1 on 4.13 had its build status changed: failing to not available
• topkg-care.1.0.0 on 4.13 had its build status changed: failing to not available
• topkg-care.1.0.1 on 4.13 had its build status changed: failing to not available
• topkg.0.7.5 on 4.13 had its build status changed: failing to not available
• topkg.0.8.0 on 4.13 had its build status changed: failing to not available
• topkg.0.9.0 on 4.13 had its build status changed: failing to not available
• topkg.1.0.0 on 4.13 had its build status changed: failing to not available
• topkg.1.0.2 on 4.13 had its build status changed: failing to not available
• toplevel_expect_test.113.33.01 on 4.13 had its build status changed: failing to not available
• toplevel_expect_test.113.33.02 on 4.13 had its build status changed: failing to not available
• toplevel_expect_test.v0.10.0 on 4.13 had its build status changed: failing to not available
• toplevel_expect_test.v0.12.0 on 4.13 had its build status changed: failing to not available
• toplevel_expect_test.v0.12.1 on 4.13 had its build status changed: failing to not available
• toplevel_expect_test.v0.13.0 on 4.13 had its build status changed: failing to not available
• toplevel_expect_test.v0.9.2 on 4.13 had its build status changed: failing to not available
• topological_sort.v0.9.0 on 4.13 had its build status changed: failing to not available
• topology.0.2.0 on 4.13 had its build status changed: failing to not available
• topology.0.4.0 on 4.13 had its build status changed: failing to not available
• touist.3.4.0 on 4.13 had its build status changed: failing to not available
• tptp.0.3.0 on 4.13 had its build status changed: failing to not available
• tptp.0.3.1 on 4.13 had its build status changed: failing to not available
• trakeva.0.1.0 on 4.13 had its build status changed: failing to not available
• transmission-rpc.1.0 on 4.13 had its build status changed: failing to not available
• travesty.0.2.0 on 4.13 had its build status changed: failing to not available
• travesty.0.6.0 on 4.13 had its build status changed: failing to not available
• travis-senv.1.0.0 on 4.13 had its build status changed: failing to not available
• treeprint.1.0.2 on 4.13 had its build status changed: failing to not available
• treeprint.2.0.0 on 4.13 had its build status changed: failing to not available
• treeprint.2.1.0 on 4.13 had its build status changed: failing to not available
• treeprint.2.1.1 on 4.13 had its build status changed: failing to not available
• tsdl.0.8.0 on 4.13 had its build status changed: failing to not available
• tsdl.0.8.1 on 4.13 had its build status changed: failing to not available
• tsdl.0.8.2 on 4.13 had its build status changed: failing to not available
• tube.4.1.1 on 4.13 had its build status changed: failing to not available
• tuntap.0.6 on 4.13 had its build status changed: failing to not available
• tuntap.0.7.0 on 4.13 had its build status changed: failing to not available
• tuntap.1.0.0 on 4.13 had its build status changed: failing to not available
• type-beat.0.1 on 4.13 had its build status changed: failing to not available
• type_conv.108.07.01 on 4.13 had its build status changed: failing to not available
• type_conv.108.08.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.08.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.09.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.10.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.12.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.13.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.15.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.20.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.41.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.47.00 on 4.13 had its build status changed: failing to not available
• type_conv.109.60.00 on 4.13 had its build status changed: failing to not available
• type_conv.112.01.00 on 4.13 had its build status changed: failing to not available
• type_conv.112.01.01 on 4.13 had its build status changed: failing to not available
• type_conv.112.01.02 on 4.13 had its build status changed: failing to not available
• type_conv.113.00.00 on 4.13 had its build status changed: failing to not available
• type_conv.113.00.02 on 4.13 had its build status changed: failing to not available
• typehashlib.108.00.02 on 4.13 had its build status changed: failing to not available
• typehashlib.108.07.00 on 4.13 had its build status changed: failing to not available
• typehashlib.108.08.00 on 4.13 had its build status changed: failing to not available
• typehashlib.109.07.00 on 4.13 had its build status changed: failing to not available
• typehashlib.109.09.00 on 4.13 had its build status changed: failing to not available
• typehashlib.109.11.00 on 4.13 had its build status changed: failing to not available
• typehashlib.109.12.00 on 4.13 had its build status changed: failing to not available
• typehashlib.109.15.00 on 4.13 had its build status changed: failing to not available
• typehashlib.109.15.01 on 4.13 had its build status changed: failing to not available
• typehashlib.109.15.02 on 4.13 had its build status changed: failing to not available
• typerep.109.55.00 on 4.13 had its build status changed: failing to not available
• typerep.109.55.02 on 4.13 had its build status changed: failing to not available
• typerep.111.06.00 on 4.13 had its build status changed: failing to not available
• typerep.112.24.00 on 4.13 had its build status changed: failing to not available
• typerep.112.35.00 on 4.13 had its build status changed: failing to not available
• typerep.113.33.03 on 4.13 had its build status changed: failing to not available
• typerep.v0.10.0 on 4.13 had its build status changed: failing to not available
• typerep.v0.11.0 on 4.13 had its build status changed: failing to not available
• typerep.v0.13.0 on 4.13 had its build status changed: failing to not available
• typerep.v0.9.0 on 4.13 had its build status changed: failing to not available
• typerep_extended.112.17.00 on 4.13 had its build status changed: failing to not available
• typerep_extended.113.00.00 on 4.13 had its build status changed: failing to not available
• typerep_extended.113.33.00 on 4.13 had its build status changed: failing to not available
• typerep_extended.113.33.03 on 4.13 had its build status changed: failing to not available
• typerep_extended.v0.9.0 on 4.13 had its build status changed: failing to not available
• typerex-build.1.99.17-beta on 4.13 had its build status changed: failing to not available
• typpx.1.0.2 on 4.13 had its build status changed: failing to not available
• typpx.1.1.2 on 4.13 had its build status changed: failing to not available
• typpx.1.2.0 on 4.13 had its build status changed: failing to not available
• typpx.1.2.1 on 4.13 had its build status changed: failing to not available
• typpx.1.2.2 on 4.13 had its build status changed: failing to not available
• typpx.1.4.1 on 4.13 had its build status changed: failing to not available
• typpx.1.4.2 on 4.13 had its build status changed: failing to not available
• typpx.1.4.3 on 4.13 had its build status changed: failing to not available
• tyxml-lwd.0.1 on 4.13 had its build status changed: failing to not available
• tyxml-ppx.4.0.0 on 4.13 had its build status changed: failing to not available
• tyxml-ppx.4.0.1 on 4.13 had its build status changed: failing to not available
• tyxml-ppx.4.1.0 on 4.13 had its build status changed: failing to not available
• tyxml-ppx.4.3.0 on 4.13 had its build status changed: failing to not available
• tyxml-ppx.4.4.0 on 4.13 had its build status changed: failing to not available
• tyxml.2.2.0 on 4.13 had its build status changed: failing to not available
• tyxml.3.1.1 on 4.13 had its build status changed: failing to not available
• tyxml.3.2.1 on 4.13 had its build status changed: failing to not available
• tyxml.3.5.0 on 4.13 had its build status changed: failing to not available
• tyxml.3.6.0 on 4.13 had its build status changed: failing to not available
• tyxml.4.1.0 on 4.13 had its build status changed: failing to not available
• ucorelib.0.1.0 on 4.13 had its build status changed: failing to not available
• ucorelib.0.2.0 on 4.13 had its build status changed: failing to not available
• udunits.0.1.1 on 4.13 had its build status changed: failing to not available
• uecc.0.1 on 4.13 had its build status changed: failing to not available
• uint.1.0.2 on 4.13 had its build status changed: failing to not available
• uint.1.0.3 on 4.13 had its build status changed: failing to not available
• uint.1.1.0 on 4.13 had its build status changed: failing to not available
• uint.1.1.4 on 4.13 had its build status changed: failing to not available
• uint.1.1.5 on 4.13 had its build status changed: failing to not available
• uint.1.2.0 on 4.13 had its build status changed: failing to not available
• ulex.1.1 on 4.13 had its build status changed: failing to not available
• ulex.1.2 on 4.13 had its build status changed: failing to not available
• unison.2.40.63 on 4.13 had its build status changed: failing to not available
• unison.2.48.3 on 4.13 had its build status changed: failing to not available
• unix-errno.0.2.0 on 4.13 had its build status changed: failing to not available
• unix-fcntl.0.2.0 on 4.13 had its build status changed: failing to not available
• unix-fcntl.0.3.1 on 4.13 had its build status changed: failing to not available
• unix-fcntl.0.3.2 on 4.13 had its build status changed: failing to not available
• unix-fcntl.0.3.3 on 4.13 had its build status changed: failing to not available
• unix-fcntl.0.3.4 on 4.13 had its build status changed: failing to not available
• unix-fcntl.0.3.5 on 4.13 had its build status changed: failing to not available
• unix-sys-resource.0.1.1 on 4.13 had its build status changed: failing to not available
• unix-sys-stat.0.3.1 on 4.13 had its build status changed: failing to not available
• unmagic.0.9.0 on 4.13 had its build status changed: failing to not available
• unmagic.1.0.0 on 4.13 had its build status changed: failing to not available
• unmagic.1.0.2 on 4.13 had its build status changed: failing to not available
• uri.1.3.0 on 4.13 had its build status changed: failing to not available
• uri.1.3.11 on 4.13 had its build status changed: failing to not available
• uri.1.3.13 on 4.13 had its build status changed: failing to not available
• uri.1.3.2 on 4.13 had its build status changed: failing to not available
• uri.1.3.5 on 4.13 had its build status changed: failing to not available
• uri.1.3.6 on 4.13 had its build status changed: failing to not available
• uri.1.3.9 on 4.13 had its build status changed: failing to not available
• uri.1.4.0 on 4.13 had its build status changed: failing to not available
• uri.1.5.0 on 4.13 had its build status changed: failing to not available
• uri.1.8.0 on 4.13 had its build status changed: failing to not available
• uri.1.9.1 on 4.13 had its build status changed: failing to not available
• uri.1.9.2 on 4.13 had its build status changed: failing to not available
• uri.1.9.5 on 4.13 had its build status changed: failing to not available
• uri.2.0.0 on 4.13 had its build status changed: failing to not available
• uri.2.1.0 on 4.13 had its build status changed: failing to not available
• usbmux.0.3 on 4.13 had its build status changed: failing to not available
• usbmux.0.5 on 4.13 had its build status changed: failing to not available
• usbmux.0.6 on 4.13 had its build status changed: failing to not available
• usbmux.0.7 on 4.13 had its build status changed: failing to not available
• usbmux.0.8 on 4.13 had its build status changed: failing to not available
• usbmux.0.9 on 4.13 had its build status changed: failing to not available
• usbmux.1.2.0 on 4.13 had its build status changed: failing to not available
• usbmux.1.3.1 on 4.13 had its build status changed: failing to not available
• usbmux.1.3.2 on 4.13 had its build status changed: failing to not available
• user-setup.0.1 on 4.02 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.03 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.04 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.05 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.06 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.07 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.08 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.09 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.10 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.11 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.12 is not available anymore. Previous state was: failing
• user-setup.0.1 on 4.13 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.02 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.03 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.04 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.05 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.06 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.07 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.08 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.09 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.10 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.11 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.12 is not available anymore. Previous state was: failing
• user-setup.0.2 on 4.13 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.02 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.03 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.04 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.05 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.06 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.07 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.08 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.09 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.10 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.11 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.12 is not available anymore. Previous state was: failing
• user-setup.0.3 on 4.13 is not available anymore. Previous state was: failing
• utop.1.17 on 4.13 had its build status changed: failing to not available
• utop.1.18 on 4.13 had its build status changed: failing to not available
• utop.1.18.1 on 4.13 had its build status changed: failing to not available
• utop.1.18.2 on 4.13 had its build status changed: failing to not available
• utop.1.19 on 4.13 had its build status changed: failing to not available
• utop.1.19.3 on 4.13 had its build status changed: failing to not available
• utop.2.0.0 on 4.13 had its build status changed: failing to not available
• utop.2.0.2 on 4.13 had its build status changed: failing to not available
• utop.2.1.0 on 4.13 had its build status changed: failing to not available
• utop.2.2.0 on 4.13 had its build status changed: failing to not available
• utop.2.4.2 on 4.13 had its build status changed: failing to not available
• utop.2.4.3 on 4.13 had its build status changed: failing to not available
• utop.2.5.0 on 4.13 had its build status changed: failing to not available
• utop.2.6.0 on 4.13 had its build status changed: failing to not available
• utp.0.9.0 on 4.13 had its build status changed: failing to not available
• uucd.2.0.0 on 4.13 had its build status changed: failing to not available
• uucd.3.0.0 on 4.13 had its build status changed: failing to not available
• uucp.0.9.0 on 4.13 had its build status changed: failing to not available
• uucp.1.0.0 on 4.13 had its build status changed: failing to not available
• uuidm.0.9.5 on 4.13 had its build status changed: failing to not available
• uunf.0.9.0 on 4.13 had its build status changed: failing to not available
• uunf.1.0.0 on 4.13 had its build status changed: failing to not available
• uunf.2.0.0 on 4.13 had its build status changed: failing to not available
• uuseg.1.0.0 on 4.13 had its build status changed: failing to not available
• uutf.0.9.1 on 4.13 had its build status changed: failing to not available
• uutf.1.0.0 on 4.13 had its build status changed: failing to not available
• uwt.0.0.1 on 4.13 had its build status changed: failing to not available
• uwt.0.0.3 on 4.13 had its build status changed: failing to not available
• uwt.0.1.0 on 4.13 had its build status changed: failing to not available
• uwt.0.2.0 on 4.13 had its build status changed: failing to not available
• uwt.0.2.1 on 4.13 had its build status changed: failing to not available
• uwt.0.2.2 on 4.13 had its build status changed: failing to not available
• uwt.0.2.3 on 4.13 had its build status changed: failing to not available
• uwt.0.2.4 on 4.13 had its build status changed: failing to not available
• uwt.0.3.0 on 4.13 had its build status changed: failing to not available
• uwt.0.3.3 on 4.13 had its build status changed: failing to not available
• variantslib.108.00.02 on 4.13 had its build status changed: failing to not available
• variantslib.108.08.00 on 4.13 had its build status changed: failing to not available
• variantslib.109.07.00 on 4.13 had its build status changed: failing to not available
• variantslib.109.09.00 on 4.13 had its build status changed: failing to not available
• variantslib.109.10.00 on 4.13 had its build status changed: failing to not available
• variantslib.109.11.00 on 4.13 had its build status changed: failing to not available
• variantslib.109.15.00 on 4.13 had its build status changed: failing to not available
• variantslib.109.15.02 on 4.13 had its build status changed: failing to not available
• variantslib.v0.10.0 on 4.13 had its build status changed: failing to not available
• variantslib.v0.13.0 on 4.13 had its build status changed: failing to not available
• variantslib.v0.9.0 on 4.13 had its build status changed: failing to not available
• vcaml.v0.13.0 on 4.13 had its build status changed: failing to not available
• vchan-xen.4.0.2 on 4.13 had its build status changed: failing to not available
• vchan-xen.4.0.3 on 4.13 had its build status changed: failing to not available
• vector3.0.2 on 4.13 had its build status changed: failing to not available
• vg.0.8.0 on 4.13 had its build status changed: failing to not available
• vg.0.8.2 on 4.13 had its build status changed: failing to not available
• vg.0.9.2 on 4.13 had its build status changed: failing to not available
• vhd-format-lwt.0.9.1 on 4.13 had its build status changed: failing to not available
• vhd-format.0.0.2 on 4.13 had its build status changed: failing to not available
• vhd-format.0.12.1 on 4.13 had its build status changed: failing to not available
• vhd-format.0.8.0 on 4.13 had its build status changed: failing to not available
• vhd-format.0.9.1 on 4.13 had its build status changed: failing to not available
• vhd-format.0.9.2 on 4.13 had its build status changed: failing to not available
• vhd-tool.0.6.5 on 4.13 had its build status changed: failing to not available
• vimebac.0.0.0 on 4.13 had its build status changed: failing to not available
• virtual_dom.v0.10.0 on 4.13 had its build status changed: failing to not available
• virtual_dom.v0.11.0 on 4.13 had its build status changed: failing to not available
• virtual_dom.v0.12.0 on 4.13 had its build status changed: failing to not available
• virtual_dom.v0.9.1 on 4.13 had its build status changed: failing to not available
• visitors.20170308 on 4.13 had its build status changed: failing to not available
• visitors.20170404 on 4.13 had its build status changed: failing to not available
• visitors.20170420 on 4.13 had its build status changed: failing to not available
• visitors.20170828 on 4.13 had its build status changed: failing to not available
• visitors.20180306 on 4.13 had its build status changed: failing to not available
• visitors.20190711 on 4.13 had its build status changed: failing to not available
• visitors.20200210 on 4.13 had its build status changed: failing to not available
• visitors.20210127 on 4.13 had its build status changed: failing to not available
• vorbis.0.6.2 on 4.13 had its build status changed: failing to not available
• vorbis.0.7.0 on 4.13 had its build status changed: failing to not available
• vpnkit.0.0.0 on 4.13 had its build status changed: failing to not available
• vpnkit.0.1.1 on 4.13 had its build status changed: failing to not available
• vrt.0.1.0 on 4.13 had its build status changed: failing to not available
• wall.0.2 on 4.13 had its build status changed: failing to not available
• wall.0.3 on 4.13 had its build status changed: failing to not available
• wasm.0.13 on 4.13 had its build status changed: failing to not available
• wasm.1.0 on 4.13 had its build status changed: failing to not available
• wasm.1.0.1 on 4.13 had its build status changed: failing to not available
• wasm.1.1.1 on 4.13 had its build status changed: failing to not available
• wcs-api.2017-05-26.01 on 4.13 had its build status changed: failing to not available
• wcs-lib.2017-05-26.00 on 4.13 had its build status changed: failing to not available
• wcs-lib.2017-05-26.02 on 4.13 had its build status changed: failing to not available
• wcs-lib.2017-05-26.03 on 4.13 had its build status changed: failing to not available
• wcs.2017-05-26.01 on 4.13 had its build status changed: failing to not available
• wcs.2017-05-26.02 on 4.13 had its build status changed: failing to not available
• wcs.2017-05-26.03 on 4.13 had its build status changed: failing to not available
• webdav.1.1.5 on 4.13 had its build status changed: failing to not available
• weberizer.0.7.3 on 4.13 had its build status changed: failing to not available
• weberizer.0.7.7 on 4.13 had its build status changed: failing to not available
• webidl.0.1 on 4.13 had its build status changed: failing to not available
• webmachine.0.1.1 on 4.13 had its build status changed: failing to not available
• webmachine.0.1.2 on 4.13 had its build status changed: failing to not available
• webmachine.0.2.2 on 4.13 had its build status changed: failing to not available
• webmachine.0.2.4 on 4.13 had its build status changed: failing to not available
• webmachine.0.3.1 on 4.13 had its build status changed: failing to not available
• webmachine.0.3.2 on 4.13 had its build status changed: failing to not available
• websocket-async.2.12 on 4.13 had its build status changed: failing to not available
• websocket-lwt.2.11 on 4.13 had its build status changed: failing to not available
• websocket.0.6 on 4.13 had its build status changed: failing to not available
• websocket.0.7 on 4.13 had its build status changed: failing to not available
• websocket.0.8 on 4.13 had its build status changed: failing to not available
• websocket.0.8.1 on 4.13 had its build status changed: failing to not available
• websocket.2.0.0 on 4.13 had its build status changed: failing to not available
• websocket.2.1 on 4.13 had its build status changed: failing to not available
• websocket.2.3 on 4.13 had its build status changed: failing to not available
• websocket.2.5 on 4.13 had its build status changed: failing to not available
• websocket.2.7 on 4.13 had its build status changed: failing to not available
• websocket.2.8 on 4.13 had its build status changed: failing to not available
• websocket.2.9 on 4.13 had its build status changed: failing to not available
• webtest.1.0.2 on 4.13 had its build status changed: failing to not available
• webtest.1.1.0 on 4.13 had its build status changed: failing to not available
• webtest.1.2.0 on 4.13 had its build status changed: failing to not available
• why.2.35 on 4.13 had its build status changed: failing to not available
• why.2.36 on 4.13 had its build status changed: failing to not available
• why.2.37 on 4.13 had its build status changed: failing to not available
• why.2.39 on 4.13 had its build status changed: failing to not available
• why.2.41 on 4.13 had its build status changed: failing to not available
• why3-base.0.86.2 on 4.13 had its build status changed: failing to not available
• why3-base.0.87.1 on 4.13 had its build status changed: failing to not available
• why3-base.0.87.2 on 4.13 had its build status changed: failing to not available
• why3-base.0.88.1 on 4.13 had its build status changed: failing to not available
• why3-base.0.88.3 on 4.13 had its build status changed: failing to not available
• why3-coq.1.1.0 on 4.13 had its build status changed: failing to not available
• why3-coq.1.1.1 on 4.13 had its build status changed: failing to not available
• why3-coq.1.2.0 on 4.13 had its build status changed: failing to not available
• why3-coq.1.2.1 on 4.13 had its build status changed: failing to not available
• why3-coq.1.3.1 on 4.13 had its build status changed: failing to not available
• why3-coq.1.3.2 on 4.13 had its build status changed: failing to not available
• why3-coq.1.3.3 on 4.13 had its build status changed: failing to not available
• why3-coq.1.4.0 on 4.13 had its build status changed: failing to not available
• why3-ide.1.0.0 on 4.13 had its build status changed: failing to not available
• why3-ide.1.1.0 on 4.13 had its build status changed: failing to not available
• why3-ide.1.1.1 on 4.13 had its build status changed: failing to not available
• why3-ide.1.2.0 on 4.13 had its build status changed: failing to not available
• why3.0.83 on 4.13 had its build status changed: failing to not available
• why3.0.84 on 4.13 had its build status changed: failing to not available
• why3.0.86.2 on 4.13 had its build status changed: failing to not available
• why3.0.86.3 on 4.13 had its build status changed: failing to not available
• why3.0.87.2 on 4.13 had its build status changed: failing to not available
• why3.0.88.2 on 4.13 had its build status changed: failing to not available
• why3.1.1.0 on 4.13 had its build status changed: failing to not available
• why3.1.1.1 on 4.13 had its build status changed: failing to not available
• x509.0.2.0 on 4.13 had its build status changed: failing to not available
• x509.0.2.1 on 4.13 had its build status changed: failing to not available
• x509.0.3.0 on 4.13 had its build status changed: failing to not available
• x509.0.3.1 on 4.13 had its build status changed: failing to not available
• x509.0.4.0 on 4.13 had its build status changed: failing to not available
• x509.0.5.0 on 4.13 had its build status changed: failing to not available
• x509.0.5.1 on 4.13 had its build status changed: failing to not available
• x509.0.5.2 on 4.13 had its build status changed: failing to not available
• x509.0.5.3 on 4.13 had its build status changed: failing to not available
• x509.0.6.0 on 4.13 had its build status changed: failing to not available
• x509.0.6.1 on 4.13 had its build status changed: failing to not available
• xapi-backtrace.0.4 on 4.13 had its build status changed: failing to not available
• xapi-backtrace.0.5 on 4.13 had its build status changed: failing to not available
• xapi-forkexecd.1.4.0 on 4.13 had its build status changed: failing to not available
• xapi-rrd.0.12.0 on 4.13 had its build status changed: failing to not available
• xapi-rrd.1.0.0 on 4.13 had its build status changed: failing to not available
• xapi-rrd.1.0.1 on 4.13 had its build status changed: failing to not available
• xapi-rrd.1.0.2 on 4.13 had its build status changed: failing to not available
• xapi-rrdd.1.2.1 on 4.13 had its build status changed: failing to not available
• xapi-stdext.2.1.0 on 4.13 had its build status changed: failing to not available
• xe-unikernel-upload.0.4 on 4.13 had its build status changed: failing to not available
• xe-unikernel-upload.0.5 on 4.13 had its build status changed: failing to not available
• xe.0.6.0 on 4.13 had its build status changed: failing to not available
• xe.0.6.2 on 4.13 had its build status changed: failing to not available
• xe.0.6.3 on 4.13 had its build status changed: failing to not available
• xen-api-client.0.9.10 on 4.13 had its build status changed: failing to not available
• xen-api-client.0.9.3 on 4.13 had its build status changed: failing to not available
• xen-api-client.0.9.7 on 4.13 had its build status changed: failing to not available
• xen-api-client.0.9.8 on 4.13 had its build status changed: failing to not available
• xen-evtchn.1.0.1 on 4.13 had its build status changed: failing to not available
• xen-evtchn.1.0.3 on 4.13 had its build status changed: failing to not available
• xen-evtchn.1.0.4 on 4.13 had its build status changed: failing to not available
• xen-evtchn.1.0.5 on 4.13 had its build status changed: failing to not available
• xen-evtchn.1.0.6 on 4.13 had its build status changed: failing to not available
• xen-evtchn.1.0.7 on 4.13 had its build status changed: failing to not available
• xen-gnt.0.9.9 on 4.13 had its build status changed: failing to not available
• xen-gnt.1.0.0 on 4.13 had its build status changed: failing to not available
• xen-gnt.1.0.2 on 4.13 had its build status changed: failing to not available
• xen-gnt.1.0.3 on 4.13 had its build status changed: failing to not available
• xen-gnt.2.2.0 on 4.13 had its build status changed: failing to not available
• xen-gnt.2.2.3 on 4.13 had its build status changed: failing to not available
• xenctrl.0.10.0 on 4.13 had its build status changed: failing to not available
• xenctrl.0.9.29 on 4.13 had its build status changed: failing to not available
• xenctrl.0.9.30 on 4.13 had its build status changed: failing to not available
• xenctrl.0.9.31 on 4.13 had its build status changed: failing to not available
• xenctrl.0.9.32 on 4.13 had its build status changed: failing to not available
• xenstore.1.0.0 on 4.13 had its build status changed: failing to not available
• xenstore.1.1.0 on 4.13 had its build status changed: failing to not available
• xenstore.1.3.0 on 4.13 had its build status changed: failing to not available
• xenstore.1.4.0 on 4.13 had its build status changed: failing to not available
• xenstore_transport.0.9.0 on 4.13 had its build status changed: failing to not available
• xenstore_transport.0.9.1 on 4.13 had its build status changed: failing to not available
• xenstore_transport.0.9.4 on 4.13 had its build status changed: failing to not available
• xenstore_transport.0.9.6 on 4.13 had its build status changed: failing to not available
• xentropyd.0.9.1 on 4.13 had its build status changed: failing to not available
• xentropyd.0.9.3 on 4.13 had its build status changed: failing to not available
• xmldiff.0.1 on 4.13 had its build status changed: failing to not available
• xmldiff.0.2 on 4.13 had its build status changed: failing to not available
• xmldiff.0.3.0 on 4.13 had its build status changed: failing to not available
• xmldiff.0.5.0 on 4.13 had its build status changed: failing to not available
• xmlm.1.2.0 on 4.13 had its build status changed: failing to not available
• xstr.0.2.1 on 4.13 had its build status changed: failing to not available
• xtmpl.0.12 on 4.13 had its build status changed: failing to not available
• xtmpl.0.13.0 on 4.13 had its build status changed: failing to not available
• xtmpl.0.16.0 on 4.13 had its build status changed: failing to not available
• yajl-extra.0.7.3 on 4.13 had its build status changed: failing to not available
• yaml.0.2.1 on 4.13 had its build status changed: failing to not available
• yara.0.2 on 4.13 had its build status changed: failing to not available
• yojson.1.0.3 on 4.13 had its build status changed: failing to not available
• yojson.1.1.6 on 4.13 had its build status changed: failing to not available
• yojson.1.1.8 on 4.13 had its build status changed: failing to not available
• yojson.1.2.1 on 4.13 had its build status changed: failing to not available
• yojson.1.2.3 on 4.13 had its build status changed: failing to not available
• yojson.1.3.1 on 4.13 had its build status changed: failing to not available
• yojson.1.3.2 on 4.13 had its build status changed: failing to not available
• yurt.0.1 on 4.13 had its build status changed: failing to not available
• yurt.0.3 on 4.13 had its build status changed: failing to not available
• yuscii.0.2.0 on 4.13 had its build status changed: failing to not available
• zarith-freestanding.1.11 on 4.13 had its build status changed: failing to not available
• zarith-freestanding.1.12 on 4.13 had its build status changed: failing to not available
• zarith-freestanding.1.4.1 on 4.13 had its build status changed: failing to not available
• zarith-freestanding.1.6 on 4.13 had its build status changed: failing to not available
• zarith-freestanding.1.7 on 4.13 had its build status changed: failing to not available
• zarith-freestanding.1.7-1 on 4.13 had its build status changed: failing to not available
• zarith-freestanding.1.9.1 on 4.13 had its build status changed: failing to not available
• zarith-ppx.0.1 on 4.13 had its build status changed: failing to not available
• zarith.1.1 on 4.13 had its build status changed: failing to not available
• zed.1.2 on 4.13 had its build status changed: failing to not available
• zed.1.4 on 4.13 had its build status changed: failing to not available
• zed.1.5 on 4.13 had its build status changed: failing to not available
• zenon.0.7.1 on 4.13 had its build status changed: failing to not available
• zipperposition.1.1 on 4.13 had its build status changed: failing to not available
• zipperposition.1.2 on 4.13 had its build status changed: failing to not available
• zipperposition.1.4 on 4.13 had its build status changed: failing to not available
• zlib.0.5 on 4.13 had its build status changed: failing to not available
• zmq-async.5.0.0 on 4.13 had its build status changed: failing to not available
• zmq-lwt.5.0.0 on 4.13 had its build status changed: failing to not available
• zmq.4.0-1 on 4.13 had its build status changed: failing to not available
• zmq.4.0-2 on 4.13 had its build status changed: failing to not available
• zmq.4.0-4 on 4.13 had its build status changed: failing to not available
• zmq.4.0-6 on 4.13 had its build status changed: failing to not available
• zmq.4.0-7 on 4.13 had its build status changed: failing to not available
• zmq.5.0.0 on 4.13 had its build status changed: failing to not available
• zstandard.v0.12.0 on 4.13 had its build status changed: failing to not available
• zstandard.v0.12.1 on 4.13 had its build status changed: failing to not available
• zstd.0.1 on 4.13 had its build status changed: failing to not available
• zxcvbn.2.0+1 on 4.13 had its build status changed: failing to not available
• zxcvbn.2.3+1 on 4.13 had its build status changed: failing to not available