Home
|
Differences with the last checks
|
Previous runs
Differences between
1741c76
and
97da9a1
(
git diff
)
Packages now
failing
:
0install.2.12.3
on
4.02
had its build status changed:
passing
to
failing
0install.2.12.3
on
4.03
had its build status changed:
passing
to
failing
0install.2.12.3
on
4.04
had its build status changed:
passing
to
failing
0install.2.12.3
on
4.05
had its build status changed:
passing
to
failing
0install.2.12.3
on
4.06
had its build status changed:
passing
to
failing
0install.2.14
on
4.03
had its build status changed:
passing
to
failing
0install.2.14
on
4.04
had its build status changed:
passing
to
failing
0install.2.14
on
4.05
had its build status changed:
passing
to
failing
0install.2.14
on
4.06
had its build status changed:
passing
to
failing
0install.2.14
on
4.07
had its build status changed:
passing
to
failing
0install.2.14.1
on
4.03
had its build status changed:
passing
to
failing
0install.2.14.1
on
4.04
had its build status changed:
passing
to
failing
0install.2.14.1
on
4.05
had its build status changed:
passing
to
failing
0install.2.14.1
on
4.06
had its build status changed:
passing
to
failing
0install.2.14.1
on
4.07
had its build status changed:
passing
to
failing
0install.2.14.1
on
4.08
had its build status changed:
passing
to
failing
0install.2.14.1
on
4.09
had its build status changed:
passing
to
failing
0install.2.14.1
on
4.10
had its build status changed:
passing
to
failing
0install.2.14.1
on
4.11
had its build status changed:
passing
to
failing
ANSITerminal.0.7
on
5.0
had its build status changed:
partially failing
to
failing
BetterErrors.0.0.1
on
5.0
had its build status changed:
partially failing
to
failing
DAGaml.0.01
on
4.13
had its build status changed:
passing
to
failing
DrawGrammar.0.1.0
on
4.02
had its build status changed:
partially failing
to
failing
DrawGrammar.0.1.0
on
4.04
had its build status changed:
partially failing
to
failing
DrawGrammar.0.2.0
on
4.02
had its build status changed:
partially failing
to
failing
DrawGrammar.0.2.0
on
4.03
had its build status changed:
partially failing
to
failing
DrawGrammar.0.2.0
on
4.04
had its build status changed:
partially failing
to
failing
DrawGrammar.0.2.0
on
4.05
had its build status changed:
partially failing
to
failing
GuaCaml.0.02
on
5.0
had its build status changed:
partially failing
to
failing
GuaCaml.0.03.01
on
5.0
had its build status changed:
partially failing
to
failing
TCSLib.0.1
on
5.0
had its build status changed:
partially failing
to
failing
acgtk.1.5.0
on
5.0
had its build status changed:
partially failing
to
failing
acgtk.1.5.1
on
5.0
had its build status changed:
partially failing
to
failing
acgtk.1.5.2
on
5.0
had its build status changed:
partially failing
to
failing
acgtk.1.5.3
on
5.0
had its build status changed:
partially failing
to
failing
ahrocksdb.0.2.2
on
4.06
had its build status changed:
passing
to
failing
ahrocksdb.0.2.2
on
4.07
had its build status changed:
passing
to
failing
ahrocksdb.0.2.2
on
4.08
had its build status changed:
passing
to
failing
ahrocksdb.0.2.2
on
4.09
had its build status changed:
passing
to
failing
ahrocksdb.0.2.2
on
4.10
had its build status changed:
passing
to
failing
ahrocksdb.0.2.2
on
4.11
had its build status changed:
passing
to
failing
ahrocksdb.0.2.2
on
4.12
had its build status changed:
passing
to
failing
ahrocksdb.0.2.2
on
4.13
had its build status changed:
passing
to
failing
ahrocksdb.0.2.2
on
4.14
had its build status changed:
passing
to
failing
ahrocksdb.0.2.2
on
5.0
had its build status changed:
partially failing
to
failing
alba.0.4.0
on
5.0
had its build status changed:
partially failing
to
failing
asl.0.10
on
5.0
had its build status changed:
partially failing
to
failing
asl.0.9
on
5.0
had its build status changed:
partially failing
to
failing
assertions.0.1
on
5.0
had its build status changed:
partially failing
to
failing
atd.1.1.2
on
5.0
had its build status changed:
partially failing
to
failing
atd.1.2.0
on
5.0
had its build status changed:
partially failing
to
failing
atd.2.2.1
on
5.0
had its build status changed:
partially failing
to
failing
atdgen.1.4.0
on
4.02
had its build status changed:
passing
to
failing
atdgen.1.4.1
on
4.02
had its build status changed:
passing
to
failing
atdgen.1.5.0
on
4.02
had its build status changed:
passing
to
failing
atdgen.1.6.0
on
4.02
had its build status changed:
passing
to
failing
atdgen.1.6.1
on
4.02
had its build status changed:
passing
to
failing
atdgen.1.7.1
on
4.02
had its build status changed:
passing
to
failing
atdgen.1.7.2
on
4.02
had its build status changed:
passing
to
failing
atdgen.1.8.0
on
4.02
had its build status changed:
passing
to
failing
base64.1.1.0
on
5.0
had its build status changed:
partially failing
to
failing
base64.2.0.0
on
5.0
had its build status changed:
partially failing
to
failing
bear.0.0.1
on
5.0
had its build status changed:
partially failing
to
failing
bechamel.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
bechamel.0.2.0
on
5.0
had its build status changed:
partially failing
to
failing
benchmark.1.4
on
5.0
had its build status changed:
partially failing
to
failing
binsec.0.5.0
on
5.0
is now installable. Current state is:
failing
bisect_ppx.2.8.0
on
5.0
is now installable. Current state is:
failing
bitcoin.2.0
on
5.0
had its build status changed:
partially failing
to
failing
bracetax.0.4
on
5.0
had its build status changed:
partially failing
to
failing
cairo2.0.5
on
5.0
had its build status changed:
partially failing
to
failing
calculon.0.1
on
4.02
had its build status changed:
passing
to
failing
calculon.0.1
on
4.03
had its build status changed:
passing
to
failing
calculon.0.1
on
4.04
had its build status changed:
passing
to
failing
calculon.0.1
on
4.05
had its build status changed:
passing
to
failing
calculon.0.1
on
4.06
had its build status changed:
passing
to
failing
calculon.0.1
on
4.07
had its build status changed:
passing
to
failing
calculon.0.2
on
4.02
had its build status changed:
passing
to
failing
calculon.0.2
on
4.03
had its build status changed:
passing
to
failing
calculon.0.2
on
4.04
had its build status changed:
passing
to
failing
calculon.0.2
on
4.05
had its build status changed:
passing
to
failing
calculon.0.2
on
4.06
had its build status changed:
passing
to
failing
calculon.0.2
on
4.07
had its build status changed:
passing
to
failing
calculon.0.3
on
4.02
had its build status changed:
passing
to
failing
calculon.0.3
on
4.03
had its build status changed:
partially failing
to
failing
calculon.0.3
on
4.04
had its build status changed:
passing
to
failing
calculon.0.3
on
4.05
had its build status changed:
passing
to
failing
calculon.0.3
on
4.06
had its build status changed:
passing
to
failing
calculon.0.3
on
4.07
had its build status changed:
passing
to
failing
calculon.0.3
on
4.08
had its build status changed:
passing
to
failing
calculon.0.3
on
4.09
had its build status changed:
passing
to
failing
calculon.0.3
on
4.10
had its build status changed:
passing
to
failing
calculon.0.3
on
4.11
had its build status changed:
passing
to
failing
calculon.0.4
on
4.03
had its build status changed:
partially failing
to
failing
calculon.0.4
on
4.04
had its build status changed:
passing
to
failing
calculon.0.4
on
4.05
had its build status changed:
passing
to
failing
calculon.0.4
on
4.06
had its build status changed:
passing
to
failing
calculon.0.4
on
4.07
had its build status changed:
passing
to
failing
calculon.0.4
on
4.08
had its build status changed:
passing
to
failing
calculon.0.4
on
4.09
had its build status changed:
passing
to
failing
calculon.0.4
on
4.10
had its build status changed:
passing
to
failing
calculon.0.4
on
4.11
had its build status changed:
passing
to
failing
camlimages.4.1.2
on
4.03
had its build status changed:
passing
to
failing
camlimages.4.1.2
on
4.04
had its build status changed:
passing
to
failing
camlimages.4.1.2
on
4.05
had its build status changed:
passing
to
failing
camlimages.4.2.0
on
4.03
had its build status changed:
passing
to
failing
camlimages.4.2.0
on
4.04
had its build status changed:
passing
to
failing
camlimages.4.2.0
on
4.05
had its build status changed:
passing
to
failing
camlimages.4.2.2
on
4.03
had its build status changed:
passing
to
failing
camlimages.4.2.2
on
4.04
had its build status changed:
passing
to
failing
camlimages.4.2.2
on
4.05
had its build status changed:
passing
to
failing
camlimages.4.2.3
on
4.03
had its build status changed:
passing
to
failing
camlimages.4.2.3
on
4.04
had its build status changed:
passing
to
failing
camlimages.4.2.3
on
4.05
had its build status changed:
passing
to
failing
camlimages.4.2.4
on
4.03
had its build status changed:
passing
to
failing
camlimages.4.2.4
on
4.04
had its build status changed:
passing
to
failing
camlimages.4.2.4
on
4.05
had its build status changed:
passing
to
failing
camllib.1.3.3
on
5.0
had its build status changed:
partially failing
to
failing
camltc.0.9.3
on
4.02
had its build status changed:
passing
to
failing
camltc.0.9.3
on
4.03
had its build status changed:
passing
to
failing
camltc.0.9.3
on
4.04
had its build status changed:
passing
to
failing
camltc.0.9.3
on
4.05
had its build status changed:
passing
to
failing
camltc.0.9.4
on
4.02
had its build status changed:
passing
to
failing
camltc.0.9.4
on
4.03
had its build status changed:
passing
to
failing
camltc.0.9.4
on
4.04
had its build status changed:
passing
to
failing
camltc.0.9.4
on
4.05
had its build status changed:
passing
to
failing
camltc.0.9.5
on
4.02
had its build status changed:
passing
to
failing
camltc.0.9.5
on
4.03
had its build status changed:
passing
to
failing
camltc.0.9.5
on
4.04
had its build status changed:
passing
to
failing
camltc.0.9.5
on
4.05
had its build status changed:
passing
to
failing
camltc.0.9.6
on
4.02
had its build status changed:
passing
to
failing
camltc.0.9.6
on
4.03
had its build status changed:
passing
to
failing
camltc.0.9.6
on
4.04
had its build status changed:
passing
to
failing
camltc.0.9.6
on
4.05
had its build status changed:
passing
to
failing
camltc.0.9.6
on
4.06
had its build status changed:
passing
to
failing
camltc.0.9.6
on
4.07
had its build status changed:
passing
to
failing
camltc.0.9.7.0
on
5.0
had its build status changed:
partially failing
to
failing
capnp-rpc-net.1.1
on
4.08
had its build status changed:
passing
to
failing
capnp-rpc-net.1.1
on
4.09
had its build status changed:
passing
to
failing
capnp-rpc-net.1.1
on
4.10
had its build status changed:
passing
to
failing
capnp-rpc-net.1.1
on
4.11
had its build status changed:
passing
to
failing
capnp-rpc-net.1.1
on
4.12
had its build status changed:
passing
to
failing
capnp-rpc-net.1.1
on
4.13
had its build status changed:
passing
to
failing
capnp-rpc-net.1.2
on
4.08
had its build status changed:
passing
to
failing
capnp-rpc-net.1.2
on
4.09
had its build status changed:
passing
to
failing
capnp-rpc-net.1.2
on
4.10
had its build status changed:
passing
to
failing
capnp-rpc-net.1.2
on
4.11
had its build status changed:
passing
to
failing
capnp-rpc-net.1.2
on
4.12
had its build status changed:
passing
to
failing
capnp-rpc-net.1.2
on
4.13
had its build status changed:
passing
to
failing
captureio.0.1.1
on
5.0
had its build status changed:
partially failing
to
failing
captureio.0.1.2
on
5.0
had its build status changed:
partially failing
to
failing
caqti.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
caqti.1.1.0
on
5.0
had its build status changed:
partially failing
to
failing
carton.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
carton.0.4.3
on
5.0
had its build status changed:
partially failing
to
failing
cconv.0.2
on
5.0
had its build status changed:
partially failing
to
failing
cconv.0.3
on
5.0
had its build status changed:
partially failing
to
failing
cconv.0.3.1
on
5.0
had its build status changed:
partially failing
to
failing
cconv.0.4
on
5.0
had its build status changed:
partially failing
to
failing
cfstream.1.2.1
on
4.03
had its build status changed:
passing
to
failing
cfstream.1.2.1
on
4.04
had its build status changed:
passing
to
failing
cfstream.1.2.1
on
4.05
had its build status changed:
passing
to
failing
cfstream.1.2.2
on
4.03
had its build status changed:
passing
to
failing
cfstream.1.2.2
on
4.04
had its build status changed:
passing
to
failing
cfstream.1.2.2
on
4.05
had its build status changed:
passing
to
failing
cmark.0.2.0
on
5.0
had its build status changed:
partially failing
to
failing
cmdtui.0.3.0
on
5.0
had its build status changed:
partially failing
to
failing
coclobas.0.0.0
on
4.03
had its build status changed:
passing
to
failing
coclobas.0.0.0
on
4.04
had its build status changed:
passing
to
failing
coclobas.0.0.1
on
4.03
had its build status changed:
passing
to
failing
coclobas.0.0.1
on
4.04
had its build status changed:
passing
to
failing
coclobas.0.0.2
on
4.03
had its build status changed:
passing
to
failing
coclobas.0.0.2
on
4.04
had its build status changed:
passing
to
failing
conf-npm.1
on
4.02
had its build status changed:
passing
to
failing
conf-npm.1
on
4.03
had its build status changed:
passing
to
failing
conf-npm.1
on
4.04
had its build status changed:
passing
to
failing
conf-npm.1
on
4.05
had its build status changed:
passing
to
failing
conf-npm.1
on
4.06
had its build status changed:
passing
to
failing
conf-npm.1
on
4.07
had its build status changed:
passing
to
failing
conf-npm.1
on
4.08
had its build status changed:
passing
to
failing
conf-npm.1
on
4.09
had its build status changed:
passing
to
failing
conf-npm.1
on
4.10
had its build status changed:
passing
to
failing
conf-npm.1
on
4.11
had its build status changed:
passing
to
failing
conf-npm.1
on
4.12
had its build status changed:
passing
to
failing
conf-npm.1
on
4.13
had its build status changed:
passing
to
failing
conf-npm.1
on
4.14
had its build status changed:
passing
to
failing
conf-npm.1
on
5.0
had its build status changed:
passing
to
failing
conjury.2.1
on
4.08
had its build status changed:
passing
to
failing
conjury.2.1
on
4.09
had its build status changed:
passing
to
failing
conjury.2.1
on
4.10
had its build status changed:
passing
to
failing
conjury.2.1
on
4.11
had its build status changed:
passing
to
failing
conjury.2.1
on
4.12
had its build status changed:
passing
to
failing
conjury.2.1
on
4.13
had its build status changed:
passing
to
failing
conjury.2.1
on
4.14
had its build status changed:
passing
to
failing
coq.8.10.0
on
4.09
had its build status changed:
passing
to
failing
coq.8.11.2
on
4.08
had its build status changed:
passing
to
failing
coq.8.12.0
on
4.06
had its build status changed:
passing
to
failing
coq.8.13.0
on
4.12
had its build status changed:
passing
to
failing
cow.2.2.0
on
5.0
had its build status changed:
partially failing
to
failing
crdt-ml.0.10.0
on
5.0
had its build status changed:
partially failing
to
failing
crunch.1.4.0
on
5.0
had its build status changed:
partially failing
to
failing
crunch.1.4.1
on
5.0
had its build status changed:
partially failing
to
failing
csv.1.4
on
5.0
had its build status changed:
partially failing
to
failing
csv.1.4.1
on
5.0
had its build status changed:
partially failing
to
failing
csv.1.4.2
on
5.0
had its build status changed:
partially failing
to
failing
csv.1.5
on
5.0
had its build status changed:
partially failing
to
failing
csv.1.6
on
5.0
had its build status changed:
partially failing
to
failing
datakit-client.0.12.0
on
4.08
had its build status changed:
passing
to
failing
datakit-client.0.12.0
on
4.09
had its build status changed:
passing
to
failing
datakit-client.0.12.0
on
4.10
had its build status changed:
passing
to
failing
datakit-client.0.12.0
on
4.11
had its build status changed:
passing
to
failing
datakit-client.0.12.0
on
4.12
had its build status changed:
passing
to
failing
datakit-client.0.12.0
on
4.13
had its build status changed:
passing
to
failing
datakit-client.0.12.2
on
4.08
had its build status changed:
passing
to
failing
datakit-client.0.12.2
on
4.09
had its build status changed:
passing
to
failing
datakit-client.0.12.2
on
4.10
had its build status changed:
passing
to
failing
datakit-client.0.12.2
on
4.11
had its build status changed:
passing
to
failing
datakit-client.0.12.2
on
4.12
had its build status changed:
passing
to
failing
datakit-client.0.12.2
on
4.13
had its build status changed:
passing
to
failing
datakit-client.0.12.3
on
4.08
had its build status changed:
passing
to
failing
datakit-client.0.12.3
on
4.09
had its build status changed:
passing
to
failing
datakit-client.0.12.3
on
4.10
had its build status changed:
passing
to
failing
datakit-client.0.12.3
on
4.11
had its build status changed:
passing
to
failing
datakit-client.0.12.3
on
4.12
had its build status changed:
passing
to
failing
datakit-client.0.12.3
on
4.13
had its build status changed:
passing
to
failing
datakit-client.1.0.0
on
4.08
had its build status changed:
passing
to
failing
datakit-client.1.0.0
on
4.09
had its build status changed:
passing
to
failing
datakit-client.1.0.0
on
4.10
had its build status changed:
passing
to
failing
datakit-client.1.0.0
on
4.11
had its build status changed:
passing
to
failing
datakit-client.1.0.0
on
4.12
had its build status changed:
passing
to
failing
datakit-client.1.0.0
on
4.13
had its build status changed:
passing
to
failing
depyt.0.2.0
on
4.12
had its build status changed:
passing
to
failing
depyt.0.2.0
on
4.13
had its build status changed:
passing
to
failing
deriving-yojson.0.2
on
4.02
had its build status changed:
passing
to
failing
deriving-yojson.0.2
on
4.03
had its build status changed:
passing
to
failing
deriving-yojson.0.2
on
4.04
had its build status changed:
passing
to
failing
deriving-yojson.0.2
on
4.05
had its build status changed:
passing
to
failing
deriving-yojson.0.2
on
4.06
had its build status changed:
passing
to
failing
deriving-yojson.0.2
on
4.07
had its build status changed:
passing
to
failing
deriving-yojson.0.3
on
4.02
had its build status changed:
passing
to
failing
deriving-yojson.0.3
on
4.03
had its build status changed:
passing
to
failing
deriving-yojson.0.3
on
4.04
had its build status changed:
passing
to
failing
deriving-yojson.0.3
on
4.05
had its build status changed:
passing
to
failing
deriving-yojson.0.3
on
4.06
had its build status changed:
passing
to
failing
deriving-yojson.0.3
on
4.07
had its build status changed:
passing
to
failing
deriving-yojson.0.3.1
on
4.02
had its build status changed:
passing
to
failing
deriving-yojson.0.3.1
on
4.03
had its build status changed:
passing
to
failing
deriving-yojson.0.3.1
on
4.04
had its build status changed:
passing
to
failing
deriving-yojson.0.3.1
on
4.05
had its build status changed:
passing
to
failing
deriving-yojson.0.3.1
on
4.06
had its build status changed:
passing
to
failing
deriving-yojson.0.3.1
on
4.07
had its build status changed:
passing
to
failing
deriving-yojson.0.4
on
4.02
had its build status changed:
passing
to
failing
deriving-yojson.0.4
on
4.03
had its build status changed:
passing
to
failing
deriving-yojson.0.4
on
4.04
had its build status changed:
passing
to
failing
deriving-yojson.0.4
on
4.05
had its build status changed:
passing
to
failing
devkit.0.4
on
4.03
had its build status changed:
passing
to
failing
devkit.0.4
on
4.04
had its build status changed:
passing
to
failing
devkit.0.4
on
4.05
had its build status changed:
passing
to
failing
devkit.0.5
on
4.04
had its build status changed:
passing
to
failing
devkit.0.5
on
4.05
had its build status changed:
passing
to
failing
devkit.0.5
on
4.06
had its build status changed:
passing
to
failing
devkit.0.5
on
4.07
had its build status changed:
passing
to
failing
devkit.0.6
on
4.04
had its build status changed:
passing
to
failing
devkit.0.6
on
4.05
had its build status changed:
passing
to
failing
devkit.0.6
on
4.06
had its build status changed:
passing
to
failing
devkit.0.6
on
4.07
had its build status changed:
passing
to
failing
devkit.0.6
on
4.08
had its build status changed:
passing
to
failing
devkit.0.6
on
4.09
had its build status changed:
passing
to
failing
devkit.0.6
on
4.10
had its build status changed:
passing
to
failing
devkit.0.6
on
4.11
had its build status changed:
passing
to
failing
devkit.0.7
on
4.05
had its build status changed:
passing
to
failing
devkit.0.7
on
4.06
had its build status changed:
passing
to
failing
devkit.0.7
on
4.07
had its build status changed:
passing
to
failing
devkit.0.7
on
4.08
had its build status changed:
passing
to
failing
devkit.0.7
on
4.09
had its build status changed:
passing
to
failing
devkit.0.7
on
4.10
had its build status changed:
passing
to
failing
devkit.0.7
on
4.11
had its build status changed:
passing
to
failing
devkit.1.0
on
4.05
had its build status changed:
passing
to
failing
devkit.1.0
on
4.06
had its build status changed:
passing
to
failing
devkit.1.0
on
4.07
had its build status changed:
passing
to
failing
devkit.1.0
on
4.08
had its build status changed:
passing
to
failing
devkit.1.0
on
4.09
had its build status changed:
passing
to
failing
devkit.1.0
on
4.10
had its build status changed:
passing
to
failing
devkit.1.0
on
4.11
had its build status changed:
passing
to
failing
digestif.0.1
on
5.0
had its build status changed:
partially failing
to
failing
digestif.0.2
on
5.0
had its build status changed:
partially failing
to
failing
digestif.0.3
on
5.0
had its build status changed:
partially failing
to
failing
digestif.0.4
on
5.0
had its build status changed:
partially failing
to
failing
digestif.0.5
on
5.0
had its build status changed:
partially failing
to
failing
dispatch.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
dispatch.0.2.0
on
5.0
had its build status changed:
partially failing
to
failing
dispatch.0.3.0
on
5.0
had its build status changed:
partially failing
to
failing
distributed.0.6.0
on
5.0
had its build status changed:
passing
to
failing
diy.5.01
on
5.0
had its build status changed:
partially failing
to
failing
docker-api.0.1
on
5.0
had its build status changed:
partially failing
to
failing
docker-api.0.2
on
5.0
had its build status changed:
partially failing
to
failing
docker-api.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
docker-api.0.2.2
on
5.0
is now installable. Current state is:
failing
dockerfile.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
dockerfile.1.1.0
on
5.0
had its build status changed:
partially failing
to
failing
dockerfile.1.1.1
on
5.0
had its build status changed:
partially failing
to
failing
dolmen.0.1
on
5.0
had its build status changed:
partially failing
to
failing
dolmen.0.2
on
5.0
had its build status changed:
partially failing
to
failing
dolog.1.1
on
5.0
had its build status changed:
partially failing
to
failing
dolog.2.0
on
5.0
had its build status changed:
partially failing
to
failing
dolog.3.0
on
5.0
had its build status changed:
partially failing
to
failing
domainslib.0.4.1
on
5.0
is now installable. Current state is:
failing
dose.3.2.2
on
4.04
had its build status changed:
internal failure
to
failing
dum.1.0.1
on
5.0
had its build status changed:
partially failing
to
failing
dum.1.0.3
on
5.0
is now installable. Current state is:
failing
earlybird.0.1.0
on
4.06
had its build status changed:
passing
to
failing
earlybird.0.1.1
on
4.06
had its build status changed:
passing
to
failing
earlybird.0.1.1
on
4.07
had its build status changed:
passing
to
failing
earlybird.0.1.2
on
4.05
had its build status changed:
passing
to
failing
earlybird.0.1.2
on
4.06
had its build status changed:
passing
to
failing
earlybird.0.1.2
on
4.07
had its build status changed:
passing
to
failing
earlybird.0.1.3
on
4.05
had its build status changed:
passing
to
failing
earlybird.0.1.3
on
4.06
had its build status changed:
passing
to
failing
earlybird.0.1.3
on
4.07
had its build status changed:
passing
to
failing
earlybird.0.1.4
on
4.05
had its build status changed:
passing
to
failing
earlybird.0.1.4
on
4.06
had its build status changed:
passing
to
failing
earlybird.0.1.4
on
4.07
had its build status changed:
passing
to
failing
easy_logging_yojson.0.4
on
4.04
had its build status changed:
passing
to
failing
easy_logging_yojson.0.4
on
4.05
had its build status changed:
passing
to
failing
easy_logging_yojson.0.4
on
4.06
had its build status changed:
passing
to
failing
easy_logging_yojson.0.4
on
4.07
had its build status changed:
passing
to
failing
easy_logging_yojson.0.4
on
4.08
had its build status changed:
passing
to
failing
easy_logging_yojson.0.4
on
4.09
had its build status changed:
passing
to
failing
easy_logging_yojson.0.4
on
4.10
had its build status changed:
passing
to
failing
easy_logging_yojson.0.4
on
4.11
had its build status changed:
passing
to
failing
easy_logging_yojson.0.4
on
4.12
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5
on
4.04
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5
on
4.05
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5
on
4.06
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5
on
4.07
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5
on
4.08
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5
on
4.09
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5
on
4.10
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5
on
4.11
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5
on
4.12
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5.2
on
4.04
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5.2
on
4.05
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5.2
on
4.06
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5.2
on
4.07
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5.2
on
4.08
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5.2
on
4.09
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5.2
on
4.10
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5.2
on
4.11
had its build status changed:
passing
to
failing
easy_logging_yojson.0.5.2
on
4.12
had its build status changed:
passing
to
failing
eio.0.1
on
5.0
is now installable. Current state is:
failing
elpi.1.15.0
on
5.0
is now installable. Current state is:
failing
elpi.1.15.2
on
5.0
is now installable. Current state is:
failing
elpi.1.16.1
on
5.0
is now installable. Current state is:
failing
exenum.0.7
on
5.0
had its build status changed:
partially failing
to
failing
faraday.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
faraday.0.2.0
on
5.0
had its build status changed:
partially failing
to
failing
fieldslib.113.24.00
on
5.0
had its build status changed:
partially failing
to
failing
fileutils.0.5.3
on
5.0
had its build status changed:
partially failing
to
failing
fileutils.0.6.0
on
5.0
had its build status changed:
partially failing
to
failing
fsml.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
fsml.0.3.0
on
5.0
had its build status changed:
partially failing
to
failing
fstreams.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
functoria-runtime.2.0.0
on
4.08
had its build status changed:
passing
to
failing
functoria-runtime.2.0.0
on
4.09
had its build status changed:
passing
to
failing
functoria-runtime.2.0.0
on
4.10
had its build status changed:
passing
to
failing
functoria-runtime.2.0.0
on
4.11
had its build status changed:
passing
to
failing
functoria-runtime.2.1.0
on
4.08
had its build status changed:
passing
to
failing
functoria-runtime.2.1.0
on
4.09
had its build status changed:
passing
to
failing
functoria-runtime.2.1.0
on
4.10
had its build status changed:
passing
to
failing
functoria-runtime.2.1.0
on
4.11
had its build status changed:
passing
to
failing
functoria-runtime.2.2.0
on
4.08
had its build status changed:
passing
to
failing
functoria-runtime.2.2.0
on
4.09
had its build status changed:
passing
to
failing
functoria-runtime.2.2.0
on
4.10
had its build status changed:
passing
to
failing
functoria-runtime.2.2.0
on
4.11
had its build status changed:
passing
to
failing
functoria-runtime.2.2.1
on
4.08
had its build status changed:
passing
to
failing
functoria-runtime.2.2.1
on
4.09
had its build status changed:
passing
to
failing
functoria-runtime.2.2.1
on
4.10
had its build status changed:
passing
to
failing
functoria-runtime.2.2.1
on
4.11
had its build status changed:
passing
to
failing
gadelac.0.6
on
5.0
had its build status changed:
partially failing
to
failing
gadelac.0.6.1
on
5.0
had its build status changed:
partially failing
to
failing
gammu.0.9.3
on
5.0
had its build status changed:
partially failing
to
failing
gapi-ocaml.0.2
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.1
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.1
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.1
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.1
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.10
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.10
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.10
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.10
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.13
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.13
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.13
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.13
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.14
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.14
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.14
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.14
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.3
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.3
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.3
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.3
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.4
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.4
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.4
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.4
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.5
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.5
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.5
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.5
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.6
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.6
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.6
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.6
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.7
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.7
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.7
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.7
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.8
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.8
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.8
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.8
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.9
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.9
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.9
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.2.9
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.1
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.1
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.1
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.1
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.2
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.2
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.2
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.2
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.3
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.3
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.3
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.3
on
4.05
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.4
on
4.02
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.4
on
4.03
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.4
on
4.04
had its build status changed:
passing
to
failing
gapi-ocaml.0.3.4
on
4.05
had its build status changed:
passing
to
failing
gdbprofiler.0.1
on
4.04
had its build status changed:
passing
to
failing
gdbprofiler.0.1
on
4.05
had its build status changed:
passing
to
failing
gdbprofiler.0.3
on
4.03
had its build status changed:
passing
to
failing
gdbprofiler.0.3
on
4.04
had its build status changed:
passing
to
failing
gdbprofiler.0.3
on
4.05
had its build status changed:
passing
to
failing
gdbprofiler.0.3
on
4.06
had its build status changed:
passing
to
failing
gdbprofiler.0.3
on
4.07
had its build status changed:
passing
to
failing
gdbprofiler.0.3
on
4.08
had its build status changed:
passing
to
failing
gdbprofiler.0.3
on
4.09
had its build status changed:
passing
to
failing
gdbprofiler.0.3
on
4.10
had its build status changed:
passing
to
failing
gdbprofiler.0.3
on
4.11
had its build status changed:
passing
to
failing
gemini.0.1
on
4.08
had its build status changed:
passing
to
failing
gemini.0.1
on
4.09
had its build status changed:
passing
to
failing
gemini.0.2.0
on
4.08
had its build status changed:
passing
to
failing
gemini.0.2.0
on
4.09
had its build status changed:
passing
to
failing
gen.0.2.2
on
5.0
had its build status changed:
partially failing
to
failing
gen.0.5
on
5.0
had its build status changed:
partially failing
to
failing
genspio.0.0.0
on
4.03
had its build status changed:
passing
to
failing
genspio.0.0.0
on
4.04
had its build status changed:
passing
to
failing
genspio.0.0.0
on
4.05
had its build status changed:
passing
to
failing
geoip.0.0.3
on
5.0
had its build status changed:
partially failing
to
failing
getopt.20120615
on
5.0
had its build status changed:
partially failing
to
failing
gg.0.9.2
on
5.0
had its build status changed:
partially failing
to
failing
gg.0.9.3
on
5.0
had its build status changed:
partially failing
to
failing
git-mirage.1.11.2
on
4.04
had its build status changed:
partially failing
to
failing
git-mirage.1.11.2
on
4.05
had its build status changed:
partially failing
to
failing
git-mirage.1.11.4
on
4.04
had its build status changed:
partially failing
to
failing
git.3.2.0
on
4.08
had its build status changed:
passing
to
failing
git.3.2.0
on
4.09
had its build status changed:
passing
to
failing
git.3.2.0
on
4.10
had its build status changed:
passing
to
failing
git.3.2.0
on
4.11
had its build status changed:
passing
to
failing
git.3.2.0
on
4.12
had its build status changed:
passing
to
failing
git.3.3.0
on
4.08
had its build status changed:
passing
to
failing
git.3.3.0
on
4.09
had its build status changed:
passing
to
failing
git.3.3.0
on
4.10
had its build status changed:
passing
to
failing
git.3.3.0
on
4.11
had its build status changed:
passing
to
failing
git.3.3.0
on
4.12
had its build status changed:
passing
to
failing
git.3.3.1
on
4.08
had its build status changed:
passing
to
failing
git.3.3.1
on
4.09
had its build status changed:
passing
to
failing
git.3.3.1
on
4.10
had its build status changed:
passing
to
failing
git.3.3.1
on
4.11
had its build status changed:
passing
to
failing
git.3.3.1
on
4.12
had its build status changed:
passing
to
failing
git.3.3.2
on
4.08
had its build status changed:
passing
to
failing
git.3.3.2
on
4.09
had its build status changed:
passing
to
failing
git.3.3.2
on
4.10
had its build status changed:
passing
to
failing
git.3.3.2
on
4.11
had its build status changed:
passing
to
failing
git.3.3.2
on
4.12
had its build status changed:
passing
to
failing
git.3.3.3
on
4.08
had its build status changed:
passing
to
failing
git.3.3.3
on
4.09
had its build status changed:
passing
to
failing
git.3.3.3
on
4.10
had its build status changed:
passing
to
failing
git.3.3.3
on
4.11
had its build status changed:
passing
to
failing
git.3.3.3
on
4.12
had its build status changed:
passing
to
failing
glicko2.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
goblint-cil.1.7.3
on
5.0
had its build status changed:
partially failing
to
failing
goblint-cil.1.7.4
on
5.0
had its build status changed:
partially failing
to
failing
graphql.0.1.0
on
4.03
had its build status changed:
passing
to
failing
graphql.0.1.0
on
4.04
had its build status changed:
passing
to
failing
graphql.0.1.0
on
4.05
had its build status changed:
passing
to
failing
graphql.0.1.0
on
4.06
had its build status changed:
passing
to
failing
graphql.0.1.0
on
4.07
had its build status changed:
passing
to
failing
graphql.0.1.0
on
4.08
had its build status changed:
passing
to
failing
graphql.0.1.0
on
4.09
had its build status changed:
passing
to
failing
graphql.0.1.0
on
4.10
had its build status changed:
passing
to
failing
graphql.0.1.0
on
4.11
had its build status changed:
passing
to
failing
graphql.0.1.0
on
4.12
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.03
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.04
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.05
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.06
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.07
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.08
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.09
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.10
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.11
had its build status changed:
passing
to
failing
graphql.0.2.0
on
4.12
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.03
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.04
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.05
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.06
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.07
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.08
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.09
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.10
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.11
had its build status changed:
passing
to
failing
graphql.0.4.0
on
4.12
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.03
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.04
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.05
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.06
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.07
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.08
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.09
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.10
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.11
had its build status changed:
passing
to
failing
graphql.0.5.0
on
4.12
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.03
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.04
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.05
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.06
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.07
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.08
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.09
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.10
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.11
had its build status changed:
passing
to
failing
graphql.0.6.0
on
4.12
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.03
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.04
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.05
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.06
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.07
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.08
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.09
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.10
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.11
had its build status changed:
passing
to
failing
graphql.0.7.0
on
4.12
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.03
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.04
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.05
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.06
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.07
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.08
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.09
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.10
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.11
had its build status changed:
passing
to
failing
graphql.0.8.0
on
4.12
had its build status changed:
passing
to
failing
graphql_ppx.1.2.2
on
5.0
had its build status changed:
not available
to
failing
gsl.1.19.1
on
5.0
had its build status changed:
partially failing
to
failing
gsl.1.19.3
on
5.0
had its build status changed:
partially failing
to
failing
h2.0.1.0
on
5.0
had its build status changed:
passing
to
failing
h2.0.2.0
on
5.0
had its build status changed:
passing
to
failing
h2.0.3.0
on
5.0
had its build status changed:
passing
to
failing
h2.0.4.0
on
5.0
had its build status changed:
passing
to
failing
h2.0.5.0
on
5.0
had its build status changed:
passing
to
failing
h2.0.6.0
on
5.0
had its build status changed:
passing
to
failing
h2.0.6.1
on
5.0
had its build status changed:
passing
to
failing
h2.0.7.0
on
5.0
had its build status changed:
passing
to
failing
h2.0.8.0
on
5.0
had its build status changed:
passing
to
failing
hack_parallel.0.1.1
on
4.07
had its build status changed:
passing
to
failing
hack_parallel.0.1.1
on
4.08
had its build status changed:
passing
to
failing
hack_parallel.0.1.1
on
4.09
had its build status changed:
passing
to
failing
hamt.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.42
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.42-beta.3
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.43
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.44
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.45
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.46
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.47
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.48
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.49
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.50
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.51
on
5.0
had its build status changed:
partially failing
to
failing
herdtools7.7.52
on
5.0
had its build status changed:
partially failing
to
failing
hevea.2.25
on
5.0
had its build status changed:
partially failing
to
failing
hevea.2.28
on
5.0
had its build status changed:
partially failing
to
failing
hevea.2.29
on
5.0
had its build status changed:
partially failing
to
failing
hevea.2.32
on
5.0
had its build status changed:
partially failing
to
failing
hevea.2.35
on
5.0
had its build status changed:
partially failing
to
failing
hlarp.0.0.1
on
4.08
had its build status changed:
passing
to
failing
hlarp.0.0.1
on
4.09
had its build status changed:
passing
to
failing
hlarp.0.0.1
on
4.10
had its build status changed:
passing
to
failing
hlarp.0.0.1
on
4.11
had its build status changed:
passing
to
failing
hlarp.0.0.1
on
4.12
had its build status changed:
passing
to
failing
hlarp.0.0.2
on
4.08
had its build status changed:
passing
to
failing
hlarp.0.0.2
on
4.09
had its build status changed:
passing
to
failing
hlarp.0.0.2
on
4.10
had its build status changed:
passing
to
failing
hlarp.0.0.2
on
4.11
had its build status changed:
passing
to
failing
hlarp.0.0.2
on
4.12
had its build status changed:
passing
to
failing
horned_worm.0.1.1
on
4.04
had its build status changed:
passing
to
failing
horned_worm.0.1.1
on
4.05
had its build status changed:
passing
to
failing
horned_worm.0.3.3
on
4.04
had its build status changed:
passing
to
failing
horned_worm.0.3.3
on
4.05
had its build status changed:
passing
to
failing
horned_worm.0.3.3
on
4.06
had its build status changed:
passing
to
failing
horned_worm.0.3.3
on
4.07
had its build status changed:
passing
to
failing
horned_worm.0.3.4
on
4.04
had its build status changed:
passing
to
failing
horned_worm.0.3.4
on
4.05
had its build status changed:
passing
to
failing
horned_worm.0.3.4
on
4.06
had its build status changed:
passing
to
failing
horned_worm.0.3.4
on
4.07
had its build status changed:
passing
to
failing
hxd.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
icalendar.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
icalendar.0.1.1
on
5.0
had its build status changed:
partially failing
to
failing
icalendar.0.1.2
on
5.0
had its build status changed:
partially failing
to
failing
inotify.2.1
on
5.0
had its build status changed:
partially failing
to
failing
inotify.2.2
on
5.0
had its build status changed:
partially failing
to
failing
inotify.2.3
on
5.0
had its build status changed:
partially failing
to
failing
inuit.0.4
on
5.0
had its build status changed:
partially failing
to
failing
ipaddr.3.0.0
on
5.0
had its build status changed:
partially failing
to
failing
ipaddr.3.1.0
on
5.0
had its build status changed:
partially failing
to
failing
ipaddr.4.0.0
on
5.0
had its build status changed:
partially failing
to
failing
irmin.1.3.2
on
4.12
had its build status changed:
passing
to
failing
irmin.1.3.2
on
4.13
had its build status changed:
passing
to
failing
irmin.1.4.0
on
4.12
had its build status changed:
passing
to
failing
irmin.1.4.0
on
4.13
had its build status changed:
passing
to
failing
iter.1.4
on
5.0
is now installable. Current state is:
failing
itv-tree.2.1
on
5.0
had its build status changed:
partially failing
to
failing
jhupllib.0.1
on
4.02
had its build status changed:
passing
to
failing
jhupllib.0.1
on
4.03
had its build status changed:
passing
to
failing
jhupllib.0.1
on
4.04
had its build status changed:
passing
to
failing
jhupllib.0.1
on
4.05
had its build status changed:
passing
to
failing
jhupllib.0.1
on
4.06
had its build status changed:
passing
to
failing
jhupllib.0.1
on
4.07
had its build status changed:
passing
to
failing
jhupllib.0.1
on
4.08
had its build status changed:
passing
to
failing
jhupllib.0.1
on
4.09
had its build status changed:
passing
to
failing
jhupllib.0.1.1
on
4.05
had its build status changed:
passing
to
failing
jhupllib.0.1.1
on
4.06
had its build status changed:
passing
to
failing
jhupllib.0.1.1
on
4.07
had its build status changed:
passing
to
failing
jhupllib.0.1.1
on
4.08
had its build status changed:
passing
to
failing
jhupllib.0.1.1
on
4.09
had its build status changed:
passing
to
failing
jhupllib.0.2.1
on
4.05
had its build status changed:
passing
to
failing
jhupllib.0.2.1
on
4.06
had its build status changed:
passing
to
failing
jhupllib.0.2.1
on
4.07
had its build status changed:
passing
to
failing
jhupllib.0.2.1
on
4.08
had its build status changed:
passing
to
failing
jhupllib.0.2.1
on
4.09
had its build status changed:
passing
to
failing
jingoo.1.2.16
on
5.0
had its build status changed:
partially failing
to
failing
jingoo.1.2.17
on
5.0
had its build status changed:
partially failing
to
failing
jingoo.1.2.18
on
5.0
had its build status changed:
partially failing
to
failing
js_of_ocaml.2.8.4
on
4.02
had its build status changed:
passing
to
failing
js_of_ocaml.2.8.4
on
4.03
had its build status changed:
passing
to
failing
js_of_ocaml.2.8.4
on
4.04
had its build status changed:
passing
to
failing
json-pointer.0.1.1-0
on
4.02
had its build status changed:
passing
to
failing
json-pointer.0.1.1-0
on
4.03
had its build status changed:
passing
to
failing
json-pointer.0.1.1-0
on
4.04
had its build status changed:
passing
to
failing
json-pointer.0.1.1-0
on
4.05
had its build status changed:
passing
to
failing
json-rpc.0.5.0-0
on
5.0
had its build status changed:
partially failing
to
failing
junit.0.1
on
5.0
had its build status changed:
partially failing
to
failing
jupyter.0.0.0
on
4.04
had its build status changed:
passing
to
failing
jupyter.0.0.0
on
4.05
had its build status changed:
passing
to
failing
jupyter.0.0.0
on
4.06
had its build status changed:
passing
to
failing
jupyter.0.0.0
on
4.07
had its build status changed:
passing
to
failing
jupyter.0.1.0
on
4.04
had its build status changed:
passing
to
failing
jupyter.0.1.0
on
4.05
had its build status changed:
passing
to
failing
jupyter.0.1.0
on
4.06
had its build status changed:
passing
to
failing
jupyter.0.1.0
on
4.07
had its build status changed:
passing
to
failing
jupyter.1.0.0
on
4.04
had its build status changed:
passing
to
failing
jupyter.1.0.0
on
4.05
had its build status changed:
passing
to
failing
jupyter.1.0.0
on
4.06
had its build status changed:
passing
to
failing
jupyter.1.0.0
on
4.07
had its build status changed:
passing
to
failing
jupyter.1.0.1
on
4.04
had its build status changed:
passing
to
failing
jupyter.1.0.1
on
4.05
had its build status changed:
passing
to
failing
jupyter.1.0.1
on
4.06
had its build status changed:
passing
to
failing
jupyter.1.0.1
on
4.07
had its build status changed:
passing
to
failing
jupyter.1.0.2
on
4.04
had its build status changed:
passing
to
failing
jupyter.1.0.2
on
4.05
had its build status changed:
passing
to
failing
jupyter.1.0.2
on
4.06
had its build status changed:
passing
to
failing
jupyter.1.0.2
on
4.07
had its build status changed:
passing
to
failing
jupyter.1.1.0
on
4.04
had its build status changed:
passing
to
failing
jupyter.1.1.0
on
4.05
had its build status changed:
passing
to
failing
jupyter.1.1.0
on
4.06
had its build status changed:
passing
to
failing
jupyter.1.1.0
on
4.07
had its build status changed:
passing
to
failing
jupyter.2.0.0
on
4.06
had its build status changed:
passing
to
failing
jupyter.2.0.0
on
4.07
had its build status changed:
passing
to
failing
jupyter.2.1.0
on
4.06
had its build status changed:
passing
to
failing
jupyter.2.1.0
on
4.07
had its build status changed:
passing
to
failing
jupyter.2.2.0
on
4.02
had its build status changed:
passing
to
failing
jupyter.2.2.0
on
4.06
had its build status changed:
passing
to
failing
jupyter.2.2.0
on
4.07
had its build status changed:
passing
to
failing
jupyter.2.2.1
on
4.06
had its build status changed:
passing
to
failing
jupyter.2.2.1
on
4.07
had its build status changed:
passing
to
failing
jupyter.2.2.2
on
4.04
had its build status changed:
passing
to
failing
jupyter.2.3.2
on
4.05
had its build status changed:
passing
to
failing
jupyter.2.3.2
on
4.06
had its build status changed:
passing
to
failing
jupyter.2.3.2
on
4.07
had its build status changed:
passing
to
failing
jupyter.2.3.3
on
4.05
had its build status changed:
passing
to
failing
jupyter.2.3.3
on
4.06
had its build status changed:
passing
to
failing
jupyter.2.3.3
on
4.07
had its build status changed:
passing
to
failing
jupyter.2.3.4
on
4.05
had its build status changed:
passing
to
failing
jupyter.2.3.4
on
4.06
had its build status changed:
passing
to
failing
jupyter.2.3.4
on
4.07
had its build status changed:
passing
to
failing
jupyter.2.3.5
on
4.05
had its build status changed:
passing
to
failing
jupyter.2.3.5
on
4.06
had its build status changed:
passing
to
failing
jupyter.2.3.5
on
4.07
had its build status changed:
passing
to
failing
jupyter.2.4.0
on
4.05
had its build status changed:
passing
to
failing
jupyter.2.4.0
on
4.06
had its build status changed:
passing
to
failing
jupyter.2.4.0
on
4.07
had its build status changed:
passing
to
failing
kafka_lwt.0.5
on
5.0
had its build status changed:
partially failing
to
failing
kappa-library.4.1.0
on
4.05
had its build status changed:
passing
to
failing
kappa-library.4.1.0
on
4.06
had its build status changed:
passing
to
failing
kappa-library.4.1.0
on
4.07
had its build status changed:
passing
to
failing
kappa-library.4.1.0
on
4.08
had its build status changed:
passing
to
failing
kappa-library.4.1.0
on
4.09
had its build status changed:
passing
to
failing
kappa-library.4.1.0
on
4.10
had its build status changed:
passing
to
failing
kappa-library.4.1.0
on
4.11
had its build status changed:
passing
to
failing
kaputt.1.2
on
5.0
had its build status changed:
partially failing
to
failing
ketrew.3.2.1
on
4.03
had its build status changed:
passing
to
failing
ketrew.3.2.1
on
4.04
had its build status changed:
passing
to
failing
ketrew.3.2.1
on
4.05
had its build status changed:
passing
to
failing
key-parsers.0.9.1
on
4.04
had its build status changed:
passing
to
failing
key-parsers.0.9.1
on
4.05
had its build status changed:
passing
to
failing
key-parsers.0.9.2
on
4.04
had its build status changed:
passing
to
failing
key-parsers.0.9.2
on
4.05
had its build status changed:
passing
to
failing
key-parsers.0.9.2
on
4.06
had its build status changed:
passing
to
failing
key-parsers.0.9.2
on
4.07
had its build status changed:
passing
to
failing
key-parsers.0.9.2
on
4.08
had its build status changed:
passing
to
failing
key-parsers.0.9.2
on
4.09
had its build status changed:
passing
to
failing
key-parsers.0.9.2
on
4.10
had its build status changed:
passing
to
failing
key-parsers.0.9.2
on
4.11
had its build status changed:
passing
to
failing
key-parsers.0.9.2
on
4.12
had its build status changed:
passing
to
failing
key-parsers.1.4.0
on
5.0
had its build status changed:
partially failing
to
failing
labltk.8.06.11
on
5.0
had its build status changed:
passing
to
failing
labltk.8.06.12
on
5.0
is now installable. Current state is:
failing
lacaml.7.2.1
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.7.2.2
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.7.2.6
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.8.0.4
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.8.0.5
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.8.0.6
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.8.0.7
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.8.1.1
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.9.0.0
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.9.1.0
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.9.1.1
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.9.2.2
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.9.2.3
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.9.3.1
on
5.0
had its build status changed:
partially failing
to
failing
lacaml.9.3.2
on
5.0
had its build status changed:
partially failing
to
failing
lambdasoup.0.5
on
5.0
had its build status changed:
partially failing
to
failing
lambdasoup.0.5.1
on
5.0
had its build status changed:
partially failing
to
failing
lambdasoup.0.6
on
5.0
had its build status changed:
partially failing
to
failing
lambdasoup.0.6.1
on
5.0
had its build status changed:
partially failing
to
failing
lambdasoup.0.6.4
on
5.0
had its build status changed:
partially failing
to
failing
lambdasoup.0.7.0
on
5.0
had its build status changed:
partially failing
to
failing
lambdasoup.0.7.1
on
5.0
had its build status changed:
partially failing
to
failing
lambdasoup.0.7.2
on
5.0
had its build status changed:
partially failing
to
failing
lambdasoup.0.7.3
on
5.0
had its build status changed:
partially failing
to
failing
lem.2020-06-03
on
5.0
had its build status changed:
partially failing
to
failing
lens.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
lens.1.0.2
on
5.0
had its build status changed:
partially failing
to
failing
lens.1.1.0
on
5.0
had its build status changed:
partially failing
to
failing
linkage.0.1
on
5.0
had its build status changed:
partially failing
to
failing
lua-ml.0.9
on
5.0
had its build status changed:
partially failing
to
failing
lutils.1.49.5
on
5.0
had its build status changed:
partially failing
to
failing
luv.0.5.0
on
4.02
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.03
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.04
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.05
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.06
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.07
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.08
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.09
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.10
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.11
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.12
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.13
had its build status changed:
passing
to
failing
luv.0.5.0
on
4.14
had its build status changed:
passing
to
failing
luv.0.5.0
on
5.0
had its build status changed:
partially failing
to
failing
lwt-zmq.2.0.1
on
4.04
had its build status changed:
passing
to
failing
lwt-zmq.2.0.1
on
4.05
had its build status changed:
passing
to
failing
lwt-zmq.2.1.0
on
4.04
had its build status changed:
passing
to
failing
lwt-zmq.2.1.0
on
4.05
had its build status changed:
passing
to
failing
lwt_glib.1.0.1
on
5.0
had its build status changed:
partially failing
to
failing
lwt_log.1.1.1
on
5.0
had its build status changed:
partially failing
to
failing
lwt_react.1.0.1
on
5.0
had its build status changed:
partially failing
to
failing
lymp.0.2.4
on
5.0
had its build status changed:
partially failing
to
failing
lymp.0.2.5
on
5.0
had its build status changed:
partially failing
to
failing
lz4.1.1.1
on
5.0
had its build status changed:
partially failing
to
failing
lzo.0.0.2
on
5.0
had its build status changed:
partially failing
to
failing
magic-mime.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
mariadb.0.10.0
on
4.07
had its build status changed:
passing
to
failing
mariadb.0.9.0
on
4.07
had its build status changed:
passing
to
failing
mariadb.1.0.0
on
4.07
had its build status changed:
passing
to
failing
mariadb.1.0.1
on
4.07
had its build status changed:
passing
to
failing
mariadb.1.1.0
on
4.07
had its build status changed:
passing
to
failing
mariadb.1.1.1
on
4.07
had its build status changed:
passing
to
failing
mariadb.1.1.2
on
4.07
had its build status changed:
passing
to
failing
mariadb.1.1.5
on
5.0
is now installable. Current state is:
failing
mariadb.1.1.6
on
5.0
is now installable. Current state is:
failing
memtrace-mirage.0.2.1.2.1
on
5.0
is now installable. Current state is:
failing
memtrace-mirage.0.2.1.2.2
on
5.0
is now installable. Current state is:
failing
memtrace.0.1
on
5.0
had its build status changed:
passing
to
failing
memtrace_viewer.v0.14.1
on
4.11
had its build status changed:
passing
to
failing
merlin-acme.0.1
on
4.02
had its build status changed:
passing
to
failing
merlin-acme.0.1
on
4.03
had its build status changed:
passing
to
failing
merlin-acme.0.1
on
4.04
had its build status changed:
passing
to
failing
merlin-acme.0.1
on
4.05
had its build status changed:
passing
to
failing
merlin.3.0.3
on
4.02
had its build status changed:
passing
to
failing
merlin.3.0.3
on
4.03
had its build status changed:
passing
to
failing
merlin.3.0.3
on
4.04
had its build status changed:
passing
to
failing
merlin.3.0.3
on
4.05
had its build status changed:
passing
to
failing
mesh.0.8.7
on
5.0
had its build status changed:
partially failing
to
failing
mesh.0.8.8
on
5.0
had its build status changed:
partially failing
to
failing
metrics.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
mimic.0.0.1
on
5.0
had its build status changed:
partially failing
to
failing
mimic.0.0.2
on
5.0
had its build status changed:
partially failing
to
failing
mimic.0.0.3
on
5.0
had its build status changed:
partially failing
to
failing
mimic.0.0.4
on
5.0
had its build status changed:
partially failing
to
failing
mindstorm.0.6
on
5.0
had its build status changed:
partially failing
to
failing
mindstorm.0.6.1
on
5.0
had its build status changed:
partially failing
to
failing
minisat.0.1
on
5.0
had its build status changed:
partially failing
to
failing
mirage-block-xen.1.7.0
on
4.08
had its build status changed:
passing
to
failing
mirage-block-xen.1.7.0
on
4.09
had its build status changed:
passing
to
failing
mirage-block-xen.1.7.0
on
4.10
had its build status changed:
passing
to
failing
mirage-block-xen.1.7.0
on
4.11
had its build status changed:
passing
to
failing
mirage-btrees.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-console-xen-backend.2.4.0
on
4.08
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.0
on
4.09
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.0
on
4.10
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.0
on
4.11
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.1
on
4.08
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.1
on
4.09
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.1
on
4.10
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.1
on
4.11
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.2
on
4.08
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.2
on
4.09
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.2
on
4.10
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.2
on
4.11
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.3
on
4.08
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.3
on
4.09
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.3
on
4.10
had its build status changed:
passing
to
failing
mirage-console-xen-backend.2.4.3
on
4.11
had its build status changed:
passing
to
failing
mirage-console-xen-backend.3.0.2
on
4.08
had its build status changed:
passing
to
failing
mirage-console-xen-backend.3.0.2
on
4.09
had its build status changed:
passing
to
failing
mirage-console-xen-backend.3.0.2
on
4.10
had its build status changed:
passing
to
failing
mirage-console-xen-backend.3.0.2
on
4.11
had its build status changed:
passing
to
failing
mirage-console-xen.2.4.2
on
4.08
had its build status changed:
passing
to
failing
mirage-console-xen.2.4.2
on
4.09
had its build status changed:
passing
to
failing
mirage-console-xen.2.4.2
on
4.10
had its build status changed:
passing
to
failing
mirage-console-xen.2.4.2
on
4.11
had its build status changed:
passing
to
failing
mirage-console-xen.2.4.3
on
4.08
had its build status changed:
passing
to
failing
mirage-console-xen.2.4.3
on
4.09
had its build status changed:
passing
to
failing
mirage-console-xen.2.4.3
on
4.10
had its build status changed:
passing
to
failing
mirage-console-xen.2.4.3
on
4.11
had its build status changed:
passing
to
failing
mirage-console-xen.3.0.2
on
4.08
had its build status changed:
passing
to
failing
mirage-console-xen.3.0.2
on
4.09
had its build status changed:
passing
to
failing
mirage-console-xen.3.0.2
on
4.10
had its build status changed:
passing
to
failing
mirage-console-xen.3.0.2
on
4.11
had its build status changed:
passing
to
failing
mirage-fs-lwt.1.2.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-fs.0.3.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-fs.0.4.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-fs.0.5.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-types.1.1.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-types.1.1.1
on
5.0
had its build status changed:
partially failing
to
failing
mirage-types.1.1.2
on
5.0
had its build status changed:
partially failing
to
failing
mirage-types.1.1.3
on
5.0
had its build status changed:
partially failing
to
failing
mirage-types.1.2.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-types.2.3.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-types.2.5.1
on
5.0
had its build status changed:
partially failing
to
failing
mirage-types.2.6.0
on
5.0
had its build status changed:
partially failing
to
failing
mirage-types.2.8.0
on
5.0
had its build status changed:
partially failing
to
failing
mm.0.8.0
on
5.0
is now installable. Current state is:
failing
monomorphic.1.2
on
5.0
had its build status changed:
partially failing
to
failing
morbig.0.9
on
5.0
had its build status changed:
partially failing
to
failing
mosquitto.0.1-0
on
5.0
had its build status changed:
partially failing
to
failing
mosquitto.0.2.1-0
on
5.0
had its build status changed:
partially failing
to
failing
mparser.1.2
on
5.0
had its build status changed:
partially failing
to
failing
mrmime.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.1
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.2
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.3
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.4
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.4.1
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.5
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.5.1
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.6
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.6.1
on
5.0
had its build status changed:
partially failing
to
failing
msat.0.7
on
5.0
had its build status changed:
partially failing
to
failing
msgpack.1.3.0
on
5.0
had its build status changed:
partially failing
to
failing
multicont.1.0.0~rc.1
on
5.0
is now installable. Current state is:
failing
mustache.2.2.0
on
5.0
had its build status changed:
partially failing
to
failing
mustache.2.3.0
on
5.0
had its build status changed:
partially failing
to
failing
naboris.0.0.3
on
5.0
had its build status changed:
not available
to
failing
naboris.0.0.4
on
5.0
had its build status changed:
not available
to
failing
naboris.0.1.0
on
5.0
had its build status changed:
not available
to
failing
naboris.0.1.1
on
5.0
had its build status changed:
not available
to
failing
naboris.0.1.2
on
5.0
had its build status changed:
not available
to
failing
naboris.0.1.3
on
5.0
had its build status changed:
not available
to
failing
named-pipe.0.4.0
on
4.08
had its build status changed:
passing
to
failing
named-pipe.0.4.0
on
4.09
had its build status changed:
passing
to
failing
named-pipe.0.4.0
on
4.10
had its build status changed:
passing
to
failing
named-pipe.0.4.0
on
4.11
had its build status changed:
passing
to
failing
netchannel.1.10.2
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.10.2
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.10.2
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.10.2
on
4.11
had its build status changed:
passing
to
failing
netchannel.1.11.0
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.11.0
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.11.0
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.11.0
on
4.11
had its build status changed:
passing
to
failing
netchannel.1.12.0
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.12.0
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.12.0
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.12.0
on
4.11
had its build status changed:
passing
to
failing
netchannel.1.13.0
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.13.0
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.13.0
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.13.0
on
4.11
had its build status changed:
passing
to
failing
netchannel.1.13.1
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.13.1
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.13.1
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.13.1
on
4.11
had its build status changed:
passing
to
failing
netlink.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
noCanren.0.3.0
on
4.13
is now installable. Current state is:
failing
noCanren.0.3.0~alpha1
on
4.13
is now installable. Current state is:
failing
not-ocamlfind.0.07.02
on
5.0
had its build status changed:
partially failing
to
failing
not-ocamlfind.0.08
on
5.0
had its build status changed:
partially failing
to
failing
nproc.0.5.1
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.0.1.1
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.0.1.2
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.0.1.3
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.0.1.3.2
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.1.0.1
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.1.0.3
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.1.0.4
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.1.2.0
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.1.2.6
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-protoc.2.1
on
5.0
is now installable. Current state is:
failing
ocaml-protoc.2.2
on
5.0
is now installable. Current state is:
failing
ocaml-r.0.1.0
on
4.03
had its build status changed:
passing
to
failing
ocaml-r.0.1.0
on
4.04
had its build status changed:
passing
to
failing
ocaml-r.0.1.0
on
4.05
had its build status changed:
passing
to
failing
ocaml-r.0.1.0
on
4.06
had its build status changed:
passing
to
failing
ocaml-r.0.1.0
on
4.07
had its build status changed:
passing
to
failing
ocaml-r.0.1.0
on
4.08
had its build status changed:
passing
to
failing
ocaml-r.0.1.0
on
4.09
had its build status changed:
passing
to
failing
ocaml-r.0.1.0
on
4.10
had its build status changed:
passing
to
failing
ocaml-r.0.1.0
on
4.11
had its build status changed:
passing
to
failing
ocaml-r.0.1.1
on
4.03
had its build status changed:
passing
to
failing
ocaml-r.0.1.1
on
4.04
had its build status changed:
passing
to
failing
ocaml-r.0.1.1
on
4.05
had its build status changed:
passing
to
failing
ocaml-r.0.1.1
on
4.06
had its build status changed:
passing
to
failing
ocaml-r.0.1.1
on
4.07
had its build status changed:
passing
to
failing
ocaml-r.0.1.1
on
4.08
had its build status changed:
passing
to
failing
ocaml-r.0.1.1
on
4.09
had its build status changed:
passing
to
failing
ocaml-r.0.1.1
on
4.10
had its build status changed:
passing
to
failing
ocaml-r.0.1.1
on
4.11
had its build status changed:
passing
to
failing
ocaml-r.0.2.0
on
4.03
had its build status changed:
passing
to
failing
ocaml-r.0.2.0
on
4.04
had its build status changed:
passing
to
failing
ocaml-r.0.2.0
on
4.05
had its build status changed:
passing
to
failing
ocaml-r.0.2.0
on
4.06
had its build status changed:
passing
to
failing
ocaml-r.0.2.0
on
4.07
had its build status changed:
passing
to
failing
ocaml-r.0.2.0
on
4.08
had its build status changed:
passing
to
failing
ocaml-r.0.2.0
on
4.09
had its build status changed:
passing
to
failing
ocaml-r.0.2.0
on
4.10
had its build status changed:
passing
to
failing
ocaml-r.0.2.0
on
4.11
had its build status changed:
passing
to
failing
ocaml-r.0.3.0
on
4.03
had its build status changed:
passing
to
failing
ocaml-r.0.3.0
on
4.04
had its build status changed:
passing
to
failing
ocaml-r.0.3.0
on
4.05
had its build status changed:
passing
to
failing
ocaml-r.0.3.0
on
4.06
had its build status changed:
passing
to
failing
ocaml-r.0.3.0
on
4.07
had its build status changed:
passing
to
failing
ocaml-r.0.3.0
on
4.08
had its build status changed:
passing
to
failing
ocaml-r.0.3.0
on
4.09
had its build status changed:
passing
to
failing
ocaml-r.0.3.0
on
4.10
had its build status changed:
passing
to
failing
ocaml-r.0.3.0
on
4.11
had its build status changed:
passing
to
failing
ocaml-r.0.3.1
on
4.07
had its build status changed:
passing
to
failing
ocaml-r.0.3.1
on
4.08
had its build status changed:
passing
to
failing
ocaml-r.0.3.1
on
4.09
had its build status changed:
passing
to
failing
ocaml-r.0.3.1
on
4.10
had its build status changed:
passing
to
failing
ocaml-r.0.3.1
on
4.11
had its build status changed:
passing
to
failing
ocaml-r.0.3.1
on
4.12
had its build status changed:
passing
to
failing
ocaml-r.0.3.1
on
4.13
had its build status changed:
passing
to
failing
ocaml-r.0.3.1
on
4.14
had its build status changed:
passing
to
failing
ocaml-r.0.4.0
on
4.08
had its build status changed:
passing
to
failing
ocaml-r.0.4.0
on
4.09
had its build status changed:
passing
to
failing
ocaml-r.0.4.0
on
4.10
had its build status changed:
passing
to
failing
ocaml-r.0.4.0
on
4.11
had its build status changed:
passing
to
failing
ocaml-r.0.4.0
on
4.12
had its build status changed:
passing
to
failing
ocaml-r.0.4.0
on
4.13
had its build status changed:
passing
to
failing
ocaml-r.0.4.0
on
4.14
had its build status changed:
passing
to
failing
ocaml-r.0.5.0
on
4.08
had its build status changed:
passing
to
failing
ocaml-r.0.5.0
on
4.09
had its build status changed:
passing
to
failing
ocaml-r.0.5.0
on
4.10
had its build status changed:
passing
to
failing
ocaml-r.0.5.0
on
4.11
had its build status changed:
passing
to
failing
ocaml-r.0.5.0
on
4.12
had its build status changed:
passing
to
failing
ocaml-r.0.5.0
on
4.13
had its build status changed:
passing
to
failing
ocaml-r.0.5.0
on
4.14
had its build status changed:
passing
to
failing
ocaml-sat-solvers.0.3
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-sat-solvers.0.4
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-systemd.1.1
on
5.0
had its build status changed:
partially failing
to
failing
ocaml-systemd.1.2
on
5.0
had its build status changed:
partially failing
to
failing
ocamlbuild-pkg.0.1
on
5.0
had its build status changed:
partially failing
to
failing
ocamlbuild-pkg.0.2
on
5.0
had its build status changed:
partially failing
to
failing
ocamlbuild-pkg.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
ocamlformat-rpc.0.18.0
on
4.08
had its build status changed:
passing
to
failing
ocamlformat-rpc.0.18.0
on
4.09
had its build status changed:
passing
to
failing
ocamlformat-rpc.0.18.0
on
4.10
had its build status changed:
passing
to
failing
ocamlformat-rpc.0.18.0
on
4.11
had its build status changed:
passing
to
failing
ocamlformat-rpc.0.18.0
on
4.12
had its build status changed:
passing
to
failing
ocamlify.0.0.1
on
5.0
had its build status changed:
partially failing
to
failing
ocamlmod.0.0.8
on
5.0
had its build status changed:
partially failing
to
failing
ocamlmod.0.0.9
on
5.0
had its build status changed:
partially failing
to
failing
ocamlrss.2.0
on
5.0
had its build status changed:
partially failing
to
failing
ocf.0.5.0
on
4.03
had its build status changed:
passing
to
failing
ocf.0.5.0
on
4.04
had its build status changed:
passing
to
failing
ocf.0.5.0
on
4.05
had its build status changed:
passing
to
failing
ocf.0.5.0
on
4.06
had its build status changed:
passing
to
failing
ocf.0.5.0
on
4.07
had its build status changed:
passing
to
failing
ocsigen-start.1.1.0
on
4.03
had its build status changed:
passing
to
failing
ocsigen-start.1.1.0
on
4.04
had its build status changed:
passing
to
failing
ocsigen-start.1.1.0
on
4.05
had its build status changed:
passing
to
failing
ocsigen-start.1.1.0
on
4.06
had its build status changed:
passing
to
failing
odepack.0.6.7
on
5.0
had its build status changed:
partially failing
to
failing
odepack.0.6.8
on
5.0
had its build status changed:
partially failing
to
failing
olinq.0.1
on
5.0
had its build status changed:
partially failing
to
failing
olinq.0.2
on
5.0
had its build status changed:
partially failing
to
failing
olmi.1.0
on
5.0
had its build status changed:
partially failing
to
failing
olmi.1.1
on
5.0
had its build status changed:
partially failing
to
failing
omake.0.10.5
on
5.0
is now installable. Current state is:
failing
omd.1.3.1
on
5.0
had its build status changed:
partially failing
to
failing
oolc.0.2
on
5.0
had its build status changed:
partially failing
to
failing
oolc.0.3
on
5.0
had its build status changed:
partially failing
to
failing
opal.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
opam-file-format.2.1.2
on
5.0
had its build status changed:
passing
to
failing
opam-file-format.2.1.3
on
5.0
had its build status changed:
passing
to
failing
opam-file-format.2.1.4
on
5.0
is now installable. Current state is:
failing
opam-monorepo.0.3.0
on
5.0
is now installable. Current state is:
failing
opam-monorepo.0.3.1
on
5.0
is now installable. Current state is:
failing
opam-monorepo.0.3.2
on
5.0
is now installable. Current state is:
failing
opam-monorepo.0.3.3
on
5.0
is now installable. Current state is:
failing
opam-sync-github-prs.1.1.0
on
4.02
had its build status changed:
partially failing
to
failing
opam-sync-github-prs.1.1.0
on
4.03
had its build status changed:
partially failing
to
failing
opium.0.15.1
on
4.03
had its build status changed:
passing
to
failing
opium.0.15.1
on
4.04
had its build status changed:
passing
to
failing
opium.0.15.1
on
4.05
had its build status changed:
passing
to
failing
opium.0.15.1
on
4.06
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.02
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.03
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.04
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.05
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.06
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.07
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.08
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.09
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.10
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.11
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.12
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.13
had its build status changed:
passing
to
failing
oplsr.5.0.1
on
4.14
had its build status changed:
passing
to
failing
orun.0.0.1
on
4.07
had its build status changed:
passing
to
failing
orun.0.0.1
on
4.08
had its build status changed:
passing
to
failing
orun.0.0.1
on
4.09
had its build status changed:
passing
to
failing
orun.0.0.1
on
4.10
had its build status changed:
passing
to
failing
orun.0.0.1
on
4.11
had its build status changed:
passing
to
failing
orun.0.0.1
on
4.13
had its build status changed:
passing
to
failing
orun.0.0.1
on
4.14
had its build status changed:
passing
to
failing
orun.0.0.1
on
5.0
had its build status changed:
partially failing
to
failing
osdp.0.6.0
on
5.0
had its build status changed:
partially failing
to
failing
osdp.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
osdp.1.1.0
on
5.0
is now installable. Current state is:
failing
ott.0.32
on
5.0
is now installable. Current state is:
failing
override.0.2.2
on
4.05
had its build status changed:
internal failure
to
failing
override.0.2.2
on
4.06
had its build status changed:
internal failure
to
failing
override.0.2.2
on
4.07
had its build status changed:
internal failure
to
failing
override.0.2.2
on
4.08
had its build status changed:
internal failure
to
failing
override.0.2.2
on
4.09
had its build status changed:
internal failure
to
failing
override.0.4.0
on
4.14
had its build status changed:
partially failing
to
failing
owl-zoo.1.0.2
on
4.10
is now installable. Current state is:
failing
owl-zoo.1.0.2
on
4.11
is now installable. Current state is:
failing
owl-zoo.1.0.2
on
4.12
is now installable. Current state is:
failing
owl-zoo.1.0.2
on
4.13
is now installable. Current state is:
failing
papi.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
parmap.1.0-rc11
on
5.0
had its build status changed:
partially failing
to
failing
pci.1.0.1
on
5.0
had its build status changed:
partially failing
to
failing
pcre.7.1.3
on
5.0
had its build status changed:
partially failing
to
failing
pcre.7.1.5
on
5.0
had its build status changed:
partially failing
to
failing
pcre.7.1.6
on
5.0
had its build status changed:
partially failing
to
failing
pcre.7.2.2
on
5.0
had its build status changed:
partially failing
to
failing
pcre.7.2.3
on
5.0
had its build status changed:
partially failing
to
failing
plplot.5.11.0
on
5.0
had its build status changed:
partially failing
to
failing
podge.0.4
on
4.02
had its build status changed:
passing
to
failing
podge.0.4
on
4.03
had its build status changed:
passing
to
failing
podge.0.4
on
4.04
had its build status changed:
passing
to
failing
podge.0.4
on
4.05
had its build status changed:
passing
to
failing
podge.0.5
on
4.02
had its build status changed:
passing
to
failing
podge.0.5
on
4.03
had its build status changed:
passing
to
failing
podge.0.5
on
4.04
had its build status changed:
passing
to
failing
podge.0.5
on
4.05
had its build status changed:
passing
to
failing
podge.0.7.0
on
4.02
had its build status changed:
passing
to
failing
podge.0.7.0
on
4.03
had its build status changed:
passing
to
failing
podge.0.7.0
on
4.04
had its build status changed:
passing
to
failing
podge.0.7.0
on
4.05
had its build status changed:
passing
to
failing
podge.0.8.0
on
4.04
had its build status changed:
passing
to
failing
podge.0.8.0
on
4.05
had its build status changed:
passing
to
failing
posix-math.0.3.0-0
on
5.0
had its build status changed:
partially failing
to
failing
posix-math.0.3.1-0
on
5.0
had its build status changed:
partially failing
to
failing
posix-time.0.3.0-0
on
5.0
had its build status changed:
partially failing
to
failing
posix-time.0.5.1-0
on
5.0
had its build status changed:
partially failing
to
failing
posix-time.0.5.2-0
on
5.0
had its build status changed:
partially failing
to
failing
posix-time.0.5.3-0
on
5.0
had its build status changed:
partially failing
to
failing
posix-time.1.0.0-0
on
5.0
had its build status changed:
partially failing
to
failing
posix-time.1.0.1-0
on
5.0
had its build status changed:
partially failing
to
failing
postgresql.3.2.1
on
5.0
had its build status changed:
partially failing
to
failing
postgresql.4.0.0
on
5.0
had its build status changed:
partially failing
to
failing
postgresql.4.0.1
on
5.0
had its build status changed:
partially failing
to
failing
ppx_deriving_protocol.0.8
on
4.03
had its build status changed:
passing
to
failing
ppx_deriving_protocol.0.8
on
4.04
had its build status changed:
passing
to
failing
ppx_deriving_protocol.0.8
on
4.05
had its build status changed:
passing
to
failing
ppx_deriving_protocol.0.8
on
4.06
had its build status changed:
passing
to
failing
ppx_deriving_protocol.0.8
on
4.07
had its build status changed:
passing
to
failing
prof_spacetime.0.1.0
on
4.04
had its build status changed:
passing
to
failing
prof_spacetime.0.1.0
on
4.05
had its build status changed:
passing
to
failing
promise.1.1.0
on
5.0
had its build status changed:
not available
to
failing
promise.1.1.2
on
5.0
had its build status changed:
not available
to
failing
qcheck.0.3
on
5.0
had its build status changed:
partially failing
to
failing
qcheck.0.4
on
5.0
had its build status changed:
partially failing
to
failing
qcheck.0.5.2
on
5.0
had its build status changed:
partially failing
to
failing
qcheck.0.5.3
on
5.0
had its build status changed:
partially failing
to
failing
qcheck.0.5.3.1
on
5.0
had its build status changed:
partially failing
to
failing
qcheck.0.6
on
5.0
had its build status changed:
partially failing
to
failing
qcheck.0.7
on
5.0
had its build status changed:
partially failing
to
failing
qtest.2.10.1
on
5.0
had its build status changed:
partially failing
to
failing
qtest.2.7
on
5.0
had its build status changed:
partially failing
to
failing
qtest.2.8
on
5.0
had its build status changed:
partially failing
to
failing
quest.0.1
on
5.0
had its build status changed:
partially failing
to
failing
radare2.0.0.1
on
4.03
had its build status changed:
passing
to
failing
radare2.0.0.1
on
4.04
had its build status changed:
passing
to
failing
radare2.0.0.1
on
4.05
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.03
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.04
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.05
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.06
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.07
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.08
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.09
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.10
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.11
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.12
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.13
had its build status changed:
passing
to
failing
radare2.0.0.2
on
4.14
had its build status changed:
passing
to
failing
rdf.0.11.0
on
4.03
had its build status changed:
passing
to
failing
rdf.0.11.0
on
4.04
had its build status changed:
passing
to
failing
rdf.0.11.0
on
4.05
had its build status changed:
passing
to
failing
rdf.0.11.0
on
4.06
had its build status changed:
passing
to
failing
rdf.0.11.0
on
4.07
had its build status changed:
passing
to
failing
rdr.1.0
on
5.0
had its build status changed:
partially failing
to
failing
rdr.1.1
on
5.0
had its build status changed:
partially failing
to
failing
re.1.3.0
on
5.0
had its build status changed:
partially failing
to
failing
re.1.3.1
on
5.0
had its build status changed:
partially failing
to
failing
re.1.3.2
on
5.0
had its build status changed:
partially failing
to
failing
re.1.4.0
on
5.0
had its build status changed:
partially failing
to
failing
re.1.4.1
on
5.0
had its build status changed:
partially failing
to
failing
re.1.5.0
on
5.0
had its build status changed:
partially failing
to
failing
re.1.6.0
on
5.0
had its build status changed:
partially failing
to
failing
re.1.6.1
on
5.0
had its build status changed:
partially failing
to
failing
re.1.7.0
on
5.0
had its build status changed:
partially failing
to
failing
re.1.7.1
on
5.0
had its build status changed:
partially failing
to
failing
reactiveData.0.2.2
on
5.0
had its build status changed:
partially failing
to
failing
records.0.6.0
on
4.02
had its build status changed:
passing
to
failing
records.0.6.0
on
4.03
had its build status changed:
passing
to
failing
records.0.6.0
on
4.04
had its build status changed:
passing
to
failing
records.0.6.0
on
4.05
had its build status changed:
passing
to
failing
records.0.6.0
on
4.06
had its build status changed:
passing
to
failing
records.0.6.0
on
4.07
had its build status changed:
passing
to
failing
records.0.6.0
on
4.08
had its build status changed:
passing
to
failing
redis.0.4
on
5.0
had its build status changed:
partially failing
to
failing
redis.0.5
on
5.0
had its build status changed:
partially failing
to
failing
res.4.0.7
on
5.0
had its build status changed:
partially failing
to
failing
rhythm.0.0.1
on
5.0
had its build status changed:
not available
to
failing
ringo.0.8
on
5.0
is now installable. Current state is:
failing
ringo.0.9
on
5.0
is now installable. Current state is:
failing
rml.1.09.05
on
5.0
had its build status changed:
partially failing
to
failing
root1d.0.4
on
5.0
had its build status changed:
partially failing
to
failing
rosetta.0.1.0
on
4.08
had its build status changed:
passing
to
failing
rosetta.0.1.0
on
4.09
had its build status changed:
passing
to
failing
rosetta.0.1.0
on
4.10
had its build status changed:
passing
to
failing
rosetta.0.1.0
on
4.11
had its build status changed:
passing
to
failing
rpc.2.2.0
on
4.02
had its build status changed:
passing
to
failing
rpc.2.2.0
on
4.03
had its build status changed:
passing
to
failing
rpc.2.2.0
on
4.04
had its build status changed:
passing
to
failing
rpc.2.2.0
on
4.05
had its build status changed:
passing
to
failing
rpclib.6.0.0
on
4.04
had its build status changed:
passing
to
failing
rpclib.6.0.0
on
4.05
had its build status changed:
passing
to
failing
rpclib.6.0.0
on
4.06
had its build status changed:
passing
to
failing
rpclib.6.0.0
on
4.07
had its build status changed:
passing
to
failing
rtop.3.6.2
on
4.03
had its build status changed:
passing
to
failing
rtop.3.6.2
on
4.04
had its build status changed:
passing
to
failing
rtop.3.6.2
on
4.05
had its build status changed:
passing
to
failing
rtop.3.6.2
on
4.06
had its build status changed:
passing
to
failing
rtop.3.6.2
on
4.07
had its build status changed:
passing
to
failing
rtop.3.6.2
on
4.08
had its build status changed:
passing
to
failing
rtop.3.6.2
on
4.09
had its build status changed:
passing
to
failing
rtop.3.6.2
on
4.10
had its build status changed:
passing
to
failing
rtop.3.6.2
on
4.11
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.03
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.04
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.05
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.06
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.07
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.08
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.09
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.10
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.11
had its build status changed:
passing
to
failing
rtop.3.7.0
on
4.12
had its build status changed:
passing
to
failing
safepass.2.0
on
5.0
had its build status changed:
partially failing
to
failing
scid.1.0
on
5.0
had its build status changed:
partially failing
to
failing
semver.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
sequence.0.2
on
5.0
had its build status changed:
partially failing
to
failing
sessions.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
setr.0.1
on
5.0
had its build status changed:
partially failing
to
failing
setr.0.1.1
on
5.0
had its build status changed:
partially failing
to
failing
slacko.0.10.0
on
4.02
had its build status changed:
passing
to
failing
slacko.0.10.0
on
4.03
had its build status changed:
passing
to
failing
slacko.0.10.0
on
4.04
had its build status changed:
passing
to
failing
slacko.0.10.0
on
4.05
had its build status changed:
passing
to
failing
slacko.0.11.0
on
4.02
had its build status changed:
passing
to
failing
slacko.0.11.0
on
4.03
had its build status changed:
passing
to
failing
slacko.0.11.0
on
4.04
had its build status changed:
passing
to
failing
slacko.0.11.0
on
4.05
had its build status changed:
passing
to
failing
slacko.0.11.0
on
4.06
had its build status changed:
passing
to
failing
slacko.0.12.0
on
4.02
had its build status changed:
passing
to
failing
slacko.0.12.0
on
4.03
had its build status changed:
passing
to
failing
slacko.0.12.0
on
4.04
had its build status changed:
passing
to
failing
slacko.0.12.0
on
4.05
had its build status changed:
passing
to
failing
slacko.0.12.0
on
4.06
had its build status changed:
passing
to
failing
slacko.0.13.0
on
4.04
had its build status changed:
passing
to
failing
slacko.0.13.0
on
4.05
had its build status changed:
passing
to
failing
slacko.0.13.0
on
4.06
had its build status changed:
passing
to
failing
slacko.0.9.0
on
4.02
had its build status changed:
passing
to
failing
slacko.0.9.0
on
4.03
had its build status changed:
passing
to
failing
slacko.0.9.0
on
4.04
had its build status changed:
passing
to
failing
slacko.0.9.0
on
4.05
had its build status changed:
passing
to
failing
slacko.0.9.1
on
4.02
had its build status changed:
passing
to
failing
slacko.0.9.1
on
4.03
had its build status changed:
passing
to
failing
slacko.0.9.1
on
4.04
had its build status changed:
passing
to
failing
slacko.0.9.1
on
4.05
had its build status changed:
passing
to
failing
sodium.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
sosa.0.2.0
on
5.0
had its build status changed:
partially failing
to
failing
sosa.0.3.0
on
5.0
had its build status changed:
partially failing
to
failing
spacetime_lib.0.1.0
on
4.06
had its build status changed:
passing
to
failing
spacetime_lib.0.1.0
on
4.07
had its build status changed:
passing
to
failing
spacetime_lib.0.3.0
on
4.06
had its build status changed:
passing
to
failing
spacetime_lib.0.3.0
on
4.07
had its build status changed:
passing
to
failing
spacetime_lib.0.3.0
on
4.08
had its build status changed:
passing
to
failing
spacetime_lib.0.3.0
on
4.09
had its build status changed:
passing
to
failing
spacetime_lib.0.3.0
on
4.10
had its build status changed:
passing
to
failing
spacetime_lib.0.3.0
on
4.11
had its build status changed:
passing
to
failing
sparrow.0.1
on
4.03
had its build status changed:
passing
to
failing
spelll.0.2
on
5.0
had its build status changed:
partially failing
to
failing
spreadsheet.0.1
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.3.0.0
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.4.0.0
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.4.0.1
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.4.0.2
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.4.0.3
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.4.0.4
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.4.0.6
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.4.1.0
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.4.1.2
on
5.0
had its build status changed:
partially failing
to
failing
sqlite3.4.1.3
on
5.0
had its build status changed:
partially failing
to
failing
statverif.1.97pl1.1
on
5.0
had its build status changed:
partially failing
to
failing
statverif.1.97pl1.2
on
5.0
had its build status changed:
partially failing
to
failing
stdcompat.18
on
5.0
is now installable. Current state is:
failing
stdlib-diff.0.1.3
on
5.0
had its build status changed:
not available
to
failing
stemming.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
stog_server.0.20.0
on
4.12
had its build status changed:
passing
to
failing
syndic.1.5.1
on
5.0
had its build status changed:
partially failing
to
failing
syndic.1.5.2
on
5.0
had its build status changed:
partially failing
to
failing
syndic.1.5.3
on
5.0
had its build status changed:
partially failing
to
failing
taglib.0.3.7
on
5.0
had its build status changed:
passing
to
failing
taglib.0.3.8
on
5.0
had its build status changed:
passing
to
failing
tcpip.4.0.0
on
4.08
had its build status changed:
passing
to
failing
tcpip.4.0.0
on
4.09
had its build status changed:
passing
to
failing
tcpip.4.0.0
on
4.10
had its build status changed:
passing
to
failing
tcpip.4.0.0
on
4.11
had its build status changed:
passing
to
failing
tdk.0.1.1
on
5.0
had its build status changed:
partially failing
to
failing
tdk.0.2.0
on
5.0
had its build status changed:
partially failing
to
failing
telegraml.1.0
on
4.02
had its build status changed:
passing
to
failing
telegraml.1.0
on
4.03
had its build status changed:
passing
to
failing
telegraml.1.0
on
4.04
had its build status changed:
passing
to
failing
telegraml.1.0
on
4.05
had its build status changed:
passing
to
failing
telegraml.1.0
on
4.06
had its build status changed:
passing
to
failing
telegraml.1.1
on
4.02
had its build status changed:
passing
to
failing
telegraml.1.1
on
4.03
had its build status changed:
passing
to
failing
telegraml.1.1
on
4.04
had its build status changed:
passing
to
failing
telegraml.1.1
on
4.05
had its build status changed:
passing
to
failing
telegraml.1.1
on
4.06
had its build status changed:
passing
to
failing
telegraml.1.2
on
4.02
had its build status changed:
passing
to
failing
telegraml.1.2
on
4.03
had its build status changed:
passing
to
failing
telegraml.1.2
on
4.04
had its build status changed:
passing
to
failing
telegraml.1.2
on
4.05
had its build status changed:
passing
to
failing
telegraml.1.2
on
4.06
had its build status changed:
passing
to
failing
telegraml.2.0.0
on
4.02
had its build status changed:
passing
to
failing
telegraml.2.0.0
on
4.03
had its build status changed:
passing
to
failing
telegraml.2.0.0
on
4.04
had its build status changed:
passing
to
failing
telegraml.2.0.0
on
4.05
had its build status changed:
passing
to
failing
telegraml.2.0.0
on
4.06
had its build status changed:
passing
to
failing
telegraml.2.1.0
on
4.02
had its build status changed:
passing
to
failing
telegraml.2.1.0
on
4.03
had its build status changed:
passing
to
failing
telegraml.2.1.0
on
4.04
had its build status changed:
passing
to
failing
telegraml.2.1.0
on
4.05
had its build status changed:
passing
to
failing
telegraml.2.1.0
on
4.06
had its build status changed:
passing
to
failing
telegraml.2.1.1
on
4.02
had its build status changed:
passing
to
failing
telegraml.2.1.1
on
4.03
had its build status changed:
passing
to
failing
telegraml.2.1.1
on
4.04
had its build status changed:
passing
to
failing
telegraml.2.1.1
on
4.05
had its build status changed:
passing
to
failing
telegraml.2.1.1
on
4.06
had its build status changed:
passing
to
failing
telegraml.2.1.2
on
4.02
had its build status changed:
passing
to
failing
telegraml.2.1.2
on
4.03
had its build status changed:
passing
to
failing
telegraml.2.1.2
on
4.04
had its build status changed:
passing
to
failing
telegraml.2.1.2
on
4.05
had its build status changed:
passing
to
failing
telegraml.2.1.2
on
4.06
had its build status changed:
passing
to
failing
telegraml.2.1.3
on
4.02
had its build status changed:
passing
to
failing
telegraml.2.1.3
on
4.03
had its build status changed:
passing
to
failing
telegraml.2.1.3
on
4.04
had its build status changed:
passing
to
failing
telegraml.2.1.3
on
4.05
had its build status changed:
passing
to
failing
telegraml.2.1.3
on
4.06
had its build status changed:
passing
to
failing
telegraml.2.1.4
on
4.02
had its build status changed:
passing
to
failing
telegraml.2.1.4
on
4.03
had its build status changed:
passing
to
failing
telegraml.2.1.4
on
4.04
had its build status changed:
passing
to
failing
telegraml.2.1.4
on
4.05
had its build status changed:
passing
to
failing
telegraml.2.1.4
on
4.06
had its build status changed:
passing
to
failing
testrunner.0.1.0
on
4.03
had its build status changed:
passing
to
failing
testrunner.0.1.0
on
4.04
had its build status changed:
passing
to
failing
testrunner.0.1.0
on
4.05
had its build status changed:
passing
to
failing
testrunner.0.1.0
on
4.06
had its build status changed:
passing
to
failing
testrunner.0.1.0
on
4.07
had its build status changed:
passing
to
failing
text.0.8.1
on
5.0
had its build status changed:
partially failing
to
failing
textwrap.0.2
on
5.0
had its build status changed:
partially failing
to
failing
tezos-stdlib.7.0
on
5.0
had its build status changed:
partially failing
to
failing
tezos-stdlib.7.1
on
5.0
had its build status changed:
partially failing
to
failing
tezos-stdlib.7.2
on
5.0
had its build status changed:
partially failing
to
failing
tezos-stdlib.7.3
on
5.0
had its build status changed:
partially failing
to
failing
tezos-stdlib.7.4
on
5.0
had its build status changed:
partially failing
to
failing
tplib.1.3
on
5.0
had its build status changed:
partially failing
to
failing
tptp.0.3.2
on
5.0
had its build status changed:
partially failing
to
failing
travis-opam.1.0.0
on
5.0
had its build status changed:
partially failing
to
failing
travis-opam.1.0.2
on
5.0
had its build status changed:
partially failing
to
failing
travis-opam.1.0.3
on
5.0
had its build status changed:
partially failing
to
failing
travis-opam.1.1.0
on
5.0
had its build status changed:
partially failing
to
failing
travis-opam.1.5.0
on
5.0
had its build status changed:
partially failing
to
failing
tree_layout.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
typerep.113.24.00
on
5.0
had its build status changed:
partially failing
to
failing
tyxml-syntax.4.5.0
on
5.0
had its build status changed:
partially failing
to
failing
tyxml.4.2.0
on
5.0
had its build status changed:
partially failing
to
failing
tyxml.4.3.0
on
5.0
had its build status changed:
partially failing
to
failing
ubpf.0.1
on
4.08
had its build status changed:
passing
to
failing
ubpf.0.1
on
4.09
had its build status changed:
passing
to
failing
ubpf.0.1
on
4.10
had its build status changed:
passing
to
failing
ubpf.0.1
on
4.12
had its build status changed:
passing
to
failing
ubpf.0.1
on
4.13
had its build status changed:
passing
to
failing
ubpf.0.1
on
4.14
had its build status changed:
passing
to
failing
ubpf.0.1
on
5.0
had its build status changed:
passing
to
failing
uint.1.2.1
on
5.0
had its build status changed:
partially failing
to
failing
unix-errno.0.3.0
on
5.0
had its build status changed:
partially failing
to
failing
unix-errno.0.4.0
on
5.0
had its build status changed:
partially failing
to
failing
unix-errno.0.4.1
on
5.0
had its build status changed:
partially failing
to
failing
unix-errno.0.4.2
on
5.0
had its build status changed:
partially failing
to
failing
unix-type-representations.0.1.0
on
5.0
had its build status changed:
partially failing
to
failing
uri.2.0.0
on
4.10
had its build status changed:
passing
to
failing
variantslib.113.24.00
on
5.0
had its build status changed:
partially failing
to
failing
vector3.0.2.1
on
5.0
had its build status changed:
partially failing
to
failing
vhd-format.0.12.0
on
4.08
had its build status changed:
passing
to
failing
vhd-format.0.12.0
on
4.09
had its build status changed:
passing
to
failing
vhd-format.0.12.0
on
4.10
had its build status changed:
passing
to
failing
vhd-format.0.12.0
on
4.11
had its build status changed:
passing
to
failing
vhd-format.0.12.0
on
4.12
had its build status changed:
passing
to
failing
vhd-format.0.12.1
on
4.08
had its build status changed:
passing
to
failing
vhd-format.0.12.1
on
4.09
had its build status changed:
passing
to
failing
vhd-format.0.12.1
on
4.10
had its build status changed:
passing
to
failing
vhd-format.0.12.1
on
4.11
had its build status changed:
passing
to
failing
vhd-format.0.12.1
on
4.12
had its build status changed:
passing
to
failing
wamp.0.1
on
4.05
had its build status changed:
passing
to
failing
wamp.0.1
on
4.06
had its build status changed:
passing
to
failing
wamp.0.1
on
4.07
had its build status changed:
passing
to
failing
wamp.0.1
on
4.08
had its build status changed:
passing
to
failing
wamp.0.1
on
4.09
had its build status changed:
passing
to
failing
wamp.0.1
on
4.10
had its build status changed:
passing
to
failing
wamp.0.1
on
4.11
had its build status changed:
passing
to
failing
wamp.0.1
on
4.12
had its build status changed:
passing
to
failing
wasm.2.0.0
on
5.0
is now installable. Current state is:
failing
wcs-lib.2017-05-26.05
on
4.08
had its build status changed:
passing
to
failing
wcs-lib.2017-05-26.05
on
4.09
had its build status changed:
passing
to
failing
wcs-lib.2017-05-26.05
on
4.10
had its build status changed:
passing
to
failing
wcs-lib.2017-05-26.05
on
4.11
had its build status changed:
passing
to
failing
wcs-lib.2017-05-26.05
on
4.12
had its build status changed:
passing
to
failing
why3.1.4.1
on
5.0
is now installable. Current state is:
failing
why3.1.5.0
on
5.0
is now installable. Current state is:
failing
win-error.0.2
on
5.0
had its build status changed:
partially failing
to
failing
win-eventlog.0.1
on
5.0
had its build status changed:
partially failing
to
failing
xen-api-client.0.9.10
on
4.02
had its build status changed:
partially failing
to
failing
xen-api-client.0.9.8
on
4.02
had its build status changed:
partially failing
to
failing
xmlplaylist.0.1.3
on
5.0
had its build status changed:
partially failing
to
failing
yajl.0.7.0
on
5.0
had its build status changed:
partially failing
to
failing
yajl.0.7.1
on
5.0
had its build status changed:
partially failing
to
failing
yajl.0.7.2
on
5.0
had its build status changed:
partially failing
to
failing
yajl.0.7.3
on
5.0
had its build status changed:
partially failing
to
failing
yuscii.0.2.0
on
4.08
had its build status changed:
passing
to
failing
yuscii.0.2.0
on
4.09
had its build status changed:
passing
to
failing
yuscii.0.2.0
on
4.10
had its build status changed:
passing
to
failing
yuscii.0.2.0
on
4.11
had its build status changed:
passing
to
failing
zarith.1.3
on
5.0
had its build status changed:
passing
to
failing
zbar.0.9
on
4.04
had its build status changed:
passing
to
failing
zbar.0.9
on
4.05
had its build status changed:
passing
to
failing
Packages now
partially failing
:
JsOfOCairo.0.1.0
on
4.02
had its build status changed:
passing
to
partially failing
JsOfOCairo.0.1.0
on
4.03
had its build status changed:
passing
to
partially failing
JsOfOCairo.0.1.0
on
4.04
had its build status changed:
passing
to
partially failing
acgtk.1.3.2
on
4.03
had its build status changed:
internal failure
to
partially failing
acgtk.1.3.2
on
4.05
had its build status changed:
internal failure
to
partially failing
acgtk.1.3.3
on
4.03
had its build status changed:
internal failure
to
partially failing
acgtk.1.3.3
on
4.04
had its build status changed:
internal failure
to
partially failing
acgtk.1.3.3
on
4.05
had its build status changed:
internal failure
to
partially failing
acgtk.1.4.0
on
4.03
had its build status changed:
internal failure
to
partially failing
acgtk.1.4.0
on
4.04
had its build status changed:
internal failure
to
partially failing
acgtk.1.4.0
on
4.05
had its build status changed:
internal failure
to
partially failing
acgtk.1.5.0
on
4.03
had its build status changed:
passing
to
partially failing
acgtk.1.5.0
on
4.04
had its build status changed:
passing
to
partially failing
acgtk.1.5.0
on
4.05
had its build status changed:
passing
to
partially failing
acgtk.1.5.0
on
4.06
had its build status changed:
passing
to
partially failing
acgtk.1.5.0
on
4.07
had its build status changed:
passing
to
partially failing
arakoon.1.8.6
on
4.02
had its build status changed:
failing
to
partially failing
arakoon.1.8.7
on
4.02
had its build status changed:
failing
to
partially failing
async_js.v0.9.0
on
4.03
had its build status changed:
passing
to
partially failing
async_js.v0.9.0
on
4.04
had its build status changed:
passing
to
partially failing
aws-s3-async.4.1.0
on
4.05
had its build status changed:
passing
to
partially failing
aws-s3-async.4.1.0
on
4.06
had its build status changed:
passing
to
partially failing
aws-s3-async.4.2.0
on
4.05
had its build status changed:
passing
to
partially failing
aws-s3-async.4.2.0
on
4.06
had its build status changed:
passing
to
partially failing
aws-s3-async.4.3.0
on
4.05
had its build status changed:
passing
to
partially failing
aws-s3-async.4.3.0
on
4.06
had its build status changed:
passing
to
partially failing
bap-cache.1.0.0
on
4.02
had its build status changed:
passing
to
partially failing
bap-objdump.1.3.0
on
4.02
had its build status changed:
failing
to
partially failing
biocaml.0.5.0
on
4.03
had its build status changed:
passing
to
partially failing
biocaml.0.6.0
on
4.03
had its build status changed:
passing
to
partially failing
biocaml.0.6.0
on
4.04
had its build status changed:
passing
to
partially failing
biocaml.0.7.0
on
4.03
had its build status changed:
passing
to
partially failing
biocaml.0.7.0
on
4.04
had its build status changed:
passing
to
partially failing
bulletml.0.1.0
on
4.02
had its build status changed:
failing
to
partially failing
bulletml.0.1.0
on
4.03
had its build status changed:
failing
to
partially failing
bulletml.0.1.0
on
4.04
had its build status changed:
failing
to
partially failing
bulletml.0.2.0
on
4.02
had its build status changed:
failing
to
partially failing
bulletml.0.2.0
on
4.03
had its build status changed:
failing
to
partially failing
bulletml.0.2.0
on
4.04
had its build status changed:
failing
to
partially failing
c3.0.2.1
on
4.02
had its build status changed:
passing
to
partially failing
c3.0.2.1
on
4.03
had its build status changed:
passing
to
partially failing
c3.0.2.1
on
4.04
had its build status changed:
passing
to
partially failing
c3.0.3.0
on
4.02
had its build status changed:
passing
to
partially failing
c3.0.3.0
on
4.03
had its build status changed:
passing
to
partially failing
c3.0.3.0
on
4.04
had its build status changed:
passing
to
partially failing
camldm.0.1.0
on
4.02
had its build status changed:
passing
to
partially failing
camldm.0.1.0
on
4.03
had its build status changed:
passing
to
partially failing
camldm.0.1.0
on
4.04
had its build status changed:
passing
to
partially failing
camldm.0.1.0
on
4.05
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.1
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.1
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.1
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.1
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.1
on
4.12
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.1
on
4.13
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.2
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.2
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.2
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.2
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.2
on
4.12
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.1.2
on
4.13
had its build status changed:
passing
to
partially failing
caqti-driver-mariadb.0.10.0
on
4.07
had its build status changed:
passing
to
partially failing
caqti-driver-mariadb.0.10.1
on
4.07
had its build status changed:
passing
to
partially failing
caqti-driver-mariadb.0.10.2
on
4.07
had its build status changed:
passing
to
partially failing
caqti-driver-mariadb.0.11.0
on
4.07
had its build status changed:
passing
to
partially failing
caqti-driver-mariadb.0.9.0
on
4.07
had its build status changed:
passing
to
partially failing
caqti-driver-mariadb.1.7.0
on
5.0
is now installable. Current state is:
partially failing
caqti-driver-mariadb.1.8.0
on
5.0
is now installable. Current state is:
partially failing
cca.0.1
on
4.11
had its build status changed:
passing
to
partially failing
cca.0.1
on
4.12
had its build status changed:
passing
to
partially failing
clangml-transforms.0.26
on
5.0
had its build status changed:
not available
to
partially failing
clangml.4.5.0
on
5.0
had its build status changed:
not available
to
partially failing
clangml.4.6.0
on
5.0
is now installable. Current state is:
partially failing
commonjs_of_ocaml.0.1.0
on
4.02
had its build status changed:
passing
to
partially failing
commonjs_of_ocaml.0.1.0
on
4.03
had its build status changed:
passing
to
partially failing
commonjs_of_ocaml.0.1.0
on
4.04
had its build status changed:
passing
to
partially failing
cookie-js.1.0.0
on
4.02
had its build status changed:
passing
to
partially failing
cookie-js.1.0.0
on
4.03
had its build status changed:
passing
to
partially failing
cookie-js.1.0.0
on
4.04
had its build status changed:
passing
to
partially failing
coq-serapi.8.11.0+0.11.1
on
4.09
had its build status changed:
internal failure
to
partially failing
coq-serapi.8.13.0+0.13.1
on
4.10
is now installable. Current state is:
partially failing
coq-serapi.8.14.0+0.14.0
on
4.14
had its build status changed:
passing
to
partially failing
coq-serapi.8.15.0+0.15.1
on
4.09
is now installable. Current state is:
partially failing
coq-serapi.8.15.0+0.15.1
on
4.14
is now installable. Current state is:
partially failing
coq-serapi.8.15.0+0.15.2
on
4.12
is now installable. Current state is:
partially failing
coq-serapi.8.8.0+0.5.4
on
4.07
had its build status changed:
passing
to
partially failing
coq-serapi.8.8.0+0.5.6
on
4.07
had its build status changed:
passing
to
partially failing
coq.8.14.0
on
4.10
had its build status changed:
passing
to
partially failing
coq.8.15.2
on
4.07
is now installable. Current state is:
partially failing
d3.0.1.0
on
4.02
had its build status changed:
passing
to
partially failing
d3.0.1.0
on
4.03
had its build status changed:
passing
to
partially failing
d3.0.1.0
on
4.04
had its build status changed:
passing
to
partially failing
d3.0.2.0
on
4.02
had its build status changed:
passing
to
partially failing
d3.0.2.0
on
4.03
had its build status changed:
passing
to
partially failing
d3.0.2.0
on
4.04
had its build status changed:
passing
to
partially failing
d3.0.2.1
on
4.02
had its build status changed:
passing
to
partially failing
d3.0.2.1
on
4.03
had its build status changed:
passing
to
partially failing
d3.0.2.1
on
4.04
had its build status changed:
passing
to
partially failing
d3.0.2.2
on
4.02
had its build status changed:
passing
to
partially failing
d3.0.2.2
on
4.03
had its build status changed:
passing
to
partially failing
d3.0.2.2
on
4.04
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.0
on
4.08
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.0
on
4.09
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.0
on
4.10
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.0
on
4.11
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.0
on
4.12
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.0
on
4.13
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.2
on
4.08
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.2
on
4.09
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.2
on
4.10
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.2
on
4.11
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.2
on
4.12
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.2
on
4.13
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.3
on
4.08
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.3
on
4.09
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.3
on
4.10
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.3
on
4.11
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.3
on
4.12
had its build status changed:
passing
to
partially failing
datakit-client-9p.0.12.3
on
4.13
had its build status changed:
passing
to
partially failing
datakit-client-9p.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
datakit-client-9p.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
datakit-client-9p.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
datakit-client-9p.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
datakit-client-9p.1.0.0
on
4.12
had its build status changed:
passing
to
partially failing
datakit-client-9p.1.0.0
on
4.13
had its build status changed:
passing
to
partially failing
datakit.0.12.2
on
4.04
had its build status changed:
failing
to
partially failing
datakit.0.12.2
on
4.05
had its build status changed:
failing
to
partially failing
datakit.0.12.3
on
4.04
had its build status changed:
failing
to
partially failing
datakit.0.12.3
on
4.05
had its build status changed:
failing
to
partially failing
datakit.1.0.0
on
4.04
had its build status changed:
failing
to
partially failing
datakit.1.0.0
on
4.05
had its build status changed:
failing
to
partially failing
eio_linux.0.1
on
5.0
is now installable. Current state is:
partially failing
eio_luv.0.1
on
5.0
is now installable. Current state is:
partially failing
eio_main.0.1
on
5.0
is now installable. Current state is:
partially failing
eliom.6.0.0
on
4.02
had its build status changed:
passing
to
partially failing
eliom.6.0.0
on
4.03
had its build status changed:
passing
to
partially failing
eliom.6.0.0
on
4.04
had its build status changed:
passing
to
partially failing
eliom.6.1.0
on
4.02
had its build status changed:
passing
to
partially failing
eliom.6.1.0
on
4.03
had its build status changed:
passing
to
partially failing
eliom.6.1.0
on
4.04
had its build status changed:
passing
to
partially failing
eliom.6.2.0
on
4.02
had its build status changed:
passing
to
partially failing
eliom.6.2.0
on
4.03
had its build status changed:
passing
to
partially failing
eliom.6.2.0
on
4.04
had its build status changed:
passing
to
partially failing
freetennis.0.4.8
on
4.03
had its build status changed:
passing
to
partially failing
freetennis.0.4.8
on
4.04
had its build status changed:
passing
to
partially failing
freetennis.0.4.8
on
4.05
had its build status changed:
passing
to
partially failing
future.0.2.0
on
4.03
had its build status changed:
passing
to
partially failing
future.0.2.0
on
4.04
had its build status changed:
passing
to
partially failing
gamepad.0.1.0
on
4.02
had its build status changed:
passing
to
partially failing
gamepad.0.1.0
on
4.03
had its build status changed:
passing
to
partially failing
gamepad.0.1.0
on
4.04
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.2.0
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.2.0
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.2.0
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.2.0
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.2.0
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.0
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.0
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.0
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.0
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.0
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.1
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.1
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.1
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.1
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.1
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.2
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.2
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.2
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.2
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.2
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.3
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.3
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.3
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.3
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-mirage.3.3.3
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.2.0
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.2.0
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.2.0
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.2.0
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.2.0
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.0
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.0
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.0
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.0
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.0
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.1
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.1
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.1
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.1
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.1
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.2
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.2
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.2
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.2
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.2
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.3
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.3
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.3
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.3
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp-unix.3.3.3
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp.3.2.0
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp.3.2.0
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp.3.2.0
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp.3.2.0
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp.3.2.0
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.0
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.0
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.0
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.0
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.0
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.1
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.1
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.1
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.1
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.1
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.2
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.2
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.2
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.2
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.2
on
4.12
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.3
on
4.08
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.3
on
4.09
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.3
on
4.10
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.3
on
4.11
had its build status changed:
passing
to
partially failing
git-cohttp.3.3.3
on
4.12
had its build status changed:
passing
to
partially failing
git-mirage.3.2.0
on
4.08
had its build status changed:
passing
to
partially failing
git-mirage.3.2.0
on
4.09
had its build status changed:
passing
to
partially failing
git-mirage.3.2.0
on
4.10
had its build status changed:
passing
to
partially failing
git-mirage.3.2.0
on
4.11
had its build status changed:
passing
to
partially failing
git-mirage.3.2.0
on
4.12
had its build status changed:
passing
to
partially failing
git-mirage.3.3.0
on
4.08
had its build status changed:
passing
to
partially failing
git-mirage.3.3.0
on
4.09
had its build status changed:
passing
to
partially failing
git-mirage.3.3.0
on
4.10
had its build status changed:
passing
to
partially failing
git-mirage.3.3.0
on
4.11
had its build status changed:
passing
to
partially failing
git-mirage.3.3.0
on
4.12
had its build status changed:
passing
to
partially failing
git-mirage.3.3.1
on
4.08
had its build status changed:
passing
to
partially failing
git-mirage.3.3.1
on
4.09
had its build status changed:
passing
to
partially failing
git-mirage.3.3.1
on
4.10
had its build status changed:
passing
to
partially failing
git-mirage.3.3.1
on
4.11
had its build status changed:
passing
to
partially failing
git-mirage.3.3.1
on
4.12
had its build status changed:
passing
to
partially failing
git-mirage.3.3.2
on
4.08
had its build status changed:
passing
to
partially failing
git-mirage.3.3.2
on
4.09
had its build status changed:
passing
to
partially failing
git-mirage.3.3.2
on
4.10
had its build status changed:
passing
to
partially failing
git-mirage.3.3.2
on
4.11
had its build status changed:
passing
to
partially failing
git-mirage.3.3.2
on
4.12
had its build status changed:
passing
to
partially failing
git-mirage.3.3.3
on
4.08
had its build status changed:
passing
to
partially failing
git-mirage.3.3.3
on
4.09
had its build status changed:
passing
to
partially failing
git-mirage.3.3.3
on
4.10
had its build status changed:
passing
to
partially failing
git-mirage.3.3.3
on
4.11
had its build status changed:
passing
to
partially failing
git-mirage.3.3.3
on
4.12
had its build status changed:
passing
to
partially failing
git-unix.3.2.0
on
4.08
had its build status changed:
passing
to
partially failing
git-unix.3.2.0
on
4.09
had its build status changed:
passing
to
partially failing
git-unix.3.2.0
on
4.10
had its build status changed:
passing
to
partially failing
git-unix.3.2.0
on
4.11
had its build status changed:
passing
to
partially failing
git-unix.3.2.0
on
4.12
had its build status changed:
passing
to
partially failing
git-unix.3.3.0
on
4.08
had its build status changed:
passing
to
partially failing
git-unix.3.3.0
on
4.09
had its build status changed:
passing
to
partially failing
git-unix.3.3.0
on
4.10
had its build status changed:
passing
to
partially failing
git-unix.3.3.0
on
4.11
had its build status changed:
passing
to
partially failing
git-unix.3.3.0
on
4.12
had its build status changed:
passing
to
partially failing
git-unix.3.3.1
on
4.08
had its build status changed:
passing
to
partially failing
git-unix.3.3.1
on
4.09
had its build status changed:
passing
to
partially failing
git-unix.3.3.1
on
4.10
had its build status changed:
passing
to
partially failing
git-unix.3.3.1
on
4.11
had its build status changed:
passing
to
partially failing
git-unix.3.3.1
on
4.12
had its build status changed:
passing
to
partially failing
git-unix.3.3.2
on
4.08
had its build status changed:
passing
to
partially failing
git-unix.3.3.2
on
4.09
had its build status changed:
passing
to
partially failing
git-unix.3.3.2
on
4.10
had its build status changed:
passing
to
partially failing
git-unix.3.3.2
on
4.11
had its build status changed:
passing
to
partially failing
git-unix.3.3.2
on
4.12
had its build status changed:
passing
to
partially failing
git-unix.3.3.3
on
4.08
had its build status changed:
passing
to
partially failing
git-unix.3.3.3
on
4.09
had its build status changed:
passing
to
partially failing
git-unix.3.3.3
on
4.10
had its build status changed:
passing
to
partially failing
git-unix.3.3.3
on
4.11
had its build status changed:
passing
to
partially failing
git-unix.3.3.3
on
4.12
had its build status changed:
passing
to
partially failing
git.3.8.0
on
5.0
is now installable. Current state is:
partially failing
git.3.9.0
on
5.0
is now installable. Current state is:
partially failing
glsurf.3.3
on
4.03
had its build status changed:
passing
to
partially failing
glsurf.3.3
on
4.04
had its build status changed:
passing
to
partially failing
glsurf.3.3
on
4.05
had its build status changed:
passing
to
partially failing
glsurf.3.3.1
on
4.03
had its build status changed:
passing
to
partially failing
glsurf.3.3.1
on
4.04
had its build status changed:
passing
to
partially failing
glsurf.3.3.1
on
4.05
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.21
on
4.02
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.21
on
4.03
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.21
on
4.04
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.21
on
4.05
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.03
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.04
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.05
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.06
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.07
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.08
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.09
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.10
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
graphql-async.0.1.0
on
4.12
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.03
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.04
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.05
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.06
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.07
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.08
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.09
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.10
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.11
had its build status changed:
passing
to
partially failing
graphql-async.0.8.0
on
4.12
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.03
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.04
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.05
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.06
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.07
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.08
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.09
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.10
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
graphql-lwt.0.1.0
on
4.12
had its build status changed:
passing
to
partially failing
graphql-lwt.0.3.0
on
4.03
had its build status changed:
passing
to
partially failing
graphql-lwt.0.3.0
on
4.04
had its build status changed:
passing
to
partially failing
graphql-lwt.0.3.0
on
4.05
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.03
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.04
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.05
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.06
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.07
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.08
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.09
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.10
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.11
had its build status changed:
passing
to
partially failing
graphql-lwt.0.6.0
on
4.12
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.03
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.04
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.05
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.06
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.07
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.08
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.09
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.10
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.11
had its build status changed:
passing
to
partially failing
graphql-lwt.0.7.0
on
4.12
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.03
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.04
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.05
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.06
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.07
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.08
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.09
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.10
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.11
had its build status changed:
passing
to
partially failing
graphql-lwt.0.8.0
on
4.12
had its build status changed:
passing
to
partially failing
hardcaml.1.0.0
on
4.02
had its build status changed:
passing
to
partially failing
hardcaml.1.0.0
on
4.03
had its build status changed:
passing
to
partially failing
hardcaml.1.0.0
on
4.04
had its build status changed:
passing
to
partially failing
hardcaml.1.1.0
on
4.02
had its build status changed:
passing
to
partially failing
hardcaml.1.1.0
on
4.03
had its build status changed:
passing
to
partially failing
hardcaml.1.1.0
on
4.04
had its build status changed:
passing
to
partially failing
higlo.0.1
on
4.02
had its build status changed:
passing
to
partially failing
higlo.0.2
on
4.02
had its build status changed:
passing
to
partially failing
higlo.0.3
on
4.02
had its build status changed:
passing
to
partially failing
higlo.0.4
on
4.02
had its build status changed:
passing
to
partially failing
incr_dom.v0.9.0
on
4.03
had its build status changed:
passing
to
partially failing
incr_dom.v0.9.0
on
4.04
had its build status changed:
passing
to
partially failing
incr_select.v0.9.0
on
4.03
had its build status changed:
passing
to
partially failing
incr_select.v0.9.0
on
4.04
had its build status changed:
passing
to
partially failing
iocaml-kernel.0.4.6
on
4.02
had its build status changed:
passing
to
partially failing
iocaml-kernel.0.4.8
on
4.02
had its build status changed:
passing
to
partially failing
iocaml.0.4.8
on
4.02
had its build status changed:
passing
to
partially failing
iocaml.0.4.9
on
4.02
had its build status changed:
passing
to
partially failing
iocamljs-kernel.0.4.0
on
4.02
had its build status changed:
passing
to
partially failing
iocamljs-kernel.0.4.0
on
4.03
had its build status changed:
passing
to
partially failing
iocamljs-kernel.0.4.0
on
4.04
had its build status changed:
passing
to
partially failing
iocamljs-kernel.0.4.6
on
4.02
had its build status changed:
failing
to
partially failing
iocamljs-kernel.0.4.6
on
4.03
had its build status changed:
failing
to
partially failing
iocamljs-kernel.0.4.6
on
4.04
had its build status changed:
failing
to
partially failing
irmin-chunk.1.3.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-chunk.1.3.0
on
4.13
had its build status changed:
passing
to
partially failing
irmin-containers.2.3.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-containers.2.3.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-containers.2.3.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-containers.2.3.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-containers.2.3.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-containers.2.4.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-containers.2.4.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-containers.2.4.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-containers.2.4.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-containers.2.4.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.1
on
4.08
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.1
on
4.09
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.1
on
4.10
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.1
on
4.11
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.1
on
4.12
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.2
on
4.08
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.2
on
4.09
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.2
on
4.10
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.2
on
4.11
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.2
on
4.12
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.3
on
4.08
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.3
on
4.09
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.3
on
4.10
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.3
on
4.11
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.3
on
4.12
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.4
on
4.08
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.4
on
4.09
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.4
on
4.10
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.4
on
4.11
had its build status changed:
passing
to
partially failing
irmin-containers.2.5.4
on
4.12
had its build status changed:
passing
to
partially failing
irmin-fs.1.3.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-fs.1.3.0
on
4.13
had its build status changed:
passing
to
partially failing
irmin-git.2.3.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-git.2.3.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-git.2.3.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-git.2.3.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-git.2.3.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-git.2.4.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-git.2.4.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-git.2.4.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-git.2.4.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-git.2.4.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-git.2.5.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-git.2.5.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-git.2.5.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-git.2.5.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-git.2.5.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-git.2.5.1
on
4.08
had its build status changed:
passing
to
partially failing
irmin-git.2.5.1
on
4.09
had its build status changed:
passing
to
partially failing
irmin-git.2.5.1
on
4.10
had its build status changed:
passing
to
partially failing
irmin-git.2.5.1
on
4.11
had its build status changed:
passing
to
partially failing
irmin-git.2.5.1
on
4.12
had its build status changed:
passing
to
partially failing
irmin-git.2.5.2
on
4.08
had its build status changed:
passing
to
partially failing
irmin-git.2.5.2
on
4.09
had its build status changed:
passing
to
partially failing
irmin-git.2.5.2
on
4.10
had its build status changed:
passing
to
partially failing
irmin-git.2.5.2
on
4.11
had its build status changed:
passing
to
partially failing
irmin-git.2.5.2
on
4.12
had its build status changed:
passing
to
partially failing
irmin-git.2.5.3
on
4.08
had its build status changed:
passing
to
partially failing
irmin-git.2.5.3
on
4.09
had its build status changed:
passing
to
partially failing
irmin-git.2.5.3
on
4.10
had its build status changed:
passing
to
partially failing
irmin-git.2.5.3
on
4.11
had its build status changed:
passing
to
partially failing
irmin-git.2.5.3
on
4.12
had its build status changed:
passing
to
partially failing
irmin-git.2.5.4
on
4.08
had its build status changed:
passing
to
partially failing
irmin-git.2.5.4
on
4.09
had its build status changed:
passing
to
partially failing
irmin-git.2.5.4
on
4.10
had its build status changed:
passing
to
partially failing
irmin-git.2.5.4
on
4.11
had its build status changed:
passing
to
partially failing
irmin-git.2.5.4
on
4.12
had its build status changed:
passing
to
partially failing
irmin-http.1.3.3
on
4.12
had its build status changed:
passing
to
partially failing
irmin-http.1.3.3
on
4.13
had its build status changed:
passing
to
partially failing
irmin-indexeddb.0.1
on
4.02
had its build status changed:
passing
to
partially failing
irmin-indexeddb.0.2
on
4.02
had its build status changed:
passing
to
partially failing
irmin-indexeddb.0.3
on
4.02
had its build status changed:
passing
to
partially failing
irmin-indexeddb.0.3
on
4.03
had its build status changed:
passing
to
partially failing
irmin-indexeddb.0.3
on
4.04
had its build status changed:
passing
to
partially failing
irmin-mem.1.3.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mem.1.3.0
on
4.13
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.3.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.4.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.4.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.4.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.4.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.4.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.1
on
4.08
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.1
on
4.09
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.1
on
4.10
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.1
on
4.11
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.1
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.2
on
4.08
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.2
on
4.09
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.2
on
4.10
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.2
on
4.11
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.2
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.3
on
4.08
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.3
on
4.09
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.3
on
4.10
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.3
on
4.11
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.3
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.4
on
4.08
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.4
on
4.09
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.4
on
4.10
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.4
on
4.11
had its build status changed:
passing
to
partially failing
irmin-mirage-git.2.5.4
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.3.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.3.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.3.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.3.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.3.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.4.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.4.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.4.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.4.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.4.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.5.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.5.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.5.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.5.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-mirage-graphql.2.5.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-unix.2.3.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-unix.2.3.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-unix.2.3.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-unix.2.3.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-unix.2.3.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-unix.2.4.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-unix.2.4.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-unix.2.4.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-unix.2.4.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-unix.2.4.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.0
on
4.08
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.0
on
4.09
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.0
on
4.10
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.0
on
4.11
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.0
on
4.12
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.1
on
4.08
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.1
on
4.09
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.1
on
4.10
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.1
on
4.11
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.1
on
4.12
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.2
on
4.08
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.2
on
4.09
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.2
on
4.10
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.2
on
4.11
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.2
on
4.12
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.3
on
4.08
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.3
on
4.09
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.3
on
4.10
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.3
on
4.11
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.3
on
4.12
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.4
on
4.08
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.4
on
4.09
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.4
on
4.10
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.4
on
4.11
had its build status changed:
passing
to
partially failing
irmin-unix.2.5.4
on
4.12
had its build status changed:
passing
to
partially failing
json-predicate.0.1.0-0
on
4.02
had its build status changed:
passing
to
partially failing
json-predicate.0.1.0-0
on
4.03
had its build status changed:
passing
to
partially failing
json-predicate.0.1.0-0
on
4.04
had its build status changed:
passing
to
partially failing
json-predicate.0.1.0-0
on
4.05
had its build status changed:
passing
to
partially failing
json-predicate.0.2.0-0
on
4.02
had its build status changed:
passing
to
partially failing
json-predicate.0.2.0-0
on
4.03
had its build status changed:
passing
to
partially failing
json-predicate.0.2.0-0
on
4.04
had its build status changed:
passing
to
partially failing
json-predicate.0.2.0-0
on
4.05
had its build status changed:
passing
to
partially failing
jsoo_broadcastchannel.1.1
on
4.02
had its build status changed:
passing
to
partially failing
jsoo_broadcastchannel.1.1
on
4.03
had its build status changed:
passing
to
partially failing
jsoo_broadcastchannel.1.1
on
4.04
had its build status changed:
passing
to
partially failing
jsoo_router.1.0
on
4.03
had its build status changed:
passing
to
partially failing
jsoo_router.1.0
on
4.04
had its build status changed:
passing
to
partially failing
jsoo_storage.1.0
on
4.02
had its build status changed:
passing
to
partially failing
jsoo_storage.1.0
on
4.03
had its build status changed:
passing
to
partially failing
jupyter-archimedes.2.0.0
on
4.04
had its build status changed:
passing
to
partially failing
jupyter-archimedes.2.3.2
on
4.04
had its build status changed:
passing
to
partially failing
jupyter-kernel.0.4
on
4.04
had its build status changed:
passing
to
partially failing
jupyter-kernel.0.4
on
4.05
had its build status changed:
passing
to
partially failing
jupyter-kernel.0.5
on
4.04
had its build status changed:
passing
to
partially failing
jupyter-kernel.0.5
on
4.05
had its build status changed:
passing
to
partially failing
jupyter-kernel.0.6
on
4.04
had its build status changed:
passing
to
partially failing
jupyter-kernel.0.6
on
4.05
had its build status changed:
passing
to
partially failing
kappa-agents.4.1.0
on
4.08
had its build status changed:
passing
to
partially failing
kappa-agents.4.1.0
on
4.09
had its build status changed:
passing
to
partially failing
kappa-agents.4.1.0
on
4.10
had its build status changed:
passing
to
partially failing
kappa-agents.4.1.0
on
4.11
had its build status changed:
passing
to
partially failing
kappa-binaries.4.1.0
on
4.05
had its build status changed:
passing
to
partially failing
kappa-binaries.4.1.0
on
4.06
had its build status changed:
passing
to
partially failing
kappa-binaries.4.1.0
on
4.07
had its build status changed:
passing
to
partially failing
kappa-binaries.4.1.0
on
4.08
had its build status changed:
passing
to
partially failing
kappa-binaries.4.1.0
on
4.09
had its build status changed:
passing
to
partially failing
kappa-binaries.4.1.0
on
4.10
had its build status changed:
passing
to
partially failing
kappa-binaries.4.1.0
on
4.11
had its build status changed:
passing
to
partially failing
kappa-server.4.1.0
on
4.08
had its build status changed:
passing
to
partially failing
kappa-server.4.1.0
on
4.09
had its build status changed:
passing
to
partially failing
kappa-server.4.1.0
on
4.10
had its build status changed:
passing
to
partially failing
kappa-server.4.1.0
on
4.11
had its build status changed:
passing
to
partially failing
ketrew.3.1.0
on
4.04
had its build status changed:
failing
to
partially failing
ketrew.3.2.0
on
4.04
had its build status changed:
failing
to
partially failing
lambda-term.3.2.0
on
5.0
is now installable. Current state is:
partially failing
lambdapi.2.2.0
on
5.0
is now installable. Current state is:
partially failing
ledgerwallet-tezos.0.2.0
on
5.0
is now installable. Current state is:
partially failing
ledgerwallet-tezos.0.2.1
on
5.0
is now installable. Current state is:
partially failing
ledgerwallet.0.2.0
on
5.0
is now installable. Current state is:
partially failing
ledgerwallet.0.2.1
on
5.0
is now installable. Current state is:
partially failing
liquidsoap.2.0.3
on
5.0
is now installable. Current state is:
partially failing
liquidsoap.2.0.3-1
on
5.0
is now installable. Current state is:
partially failing
liquidsoap.2.0.4
on
5.0
is now installable. Current state is:
partially failing
liquidsoap.2.0.4-1
on
5.0
is now installable. Current state is:
partially failing
liquidsoap.2.0.4-2
on
5.0
is now installable. Current state is:
partially failing
liquidsoap.2.0.5
on
5.0
is now installable. Current state is:
partially failing
m_tree.0.1
on
5.0
is now installable. Current state is:
partially failing
mccs.1.1+14
on
5.0
is now installable. Current state is:
partially failing
memcad.1.1.0
on
5.0
had its build status changed:
not available
to
partially failing
metapp.0.4.3
on
5.0
is now installable. Current state is:
partially failing
metaquot.0.5.1
on
5.0
is now installable. Current state is:
partially failing
mirage-net-xen.1.10.2
on
4.08
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.10.2
on
4.09
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.10.2
on
4.10
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.10.2
on
4.11
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.11.0
on
4.08
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.11.0
on
4.09
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.11.0
on
4.10
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.11.0
on
4.11
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.12.0
on
4.08
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.12.0
on
4.09
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.12.0
on
4.10
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.12.0
on
4.11
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.13.0
on
4.08
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.13.0
on
4.09
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.13.0
on
4.10
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.13.0
on
4.11
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.13.1
on
4.08
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.13.1
on
4.09
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.13.1
on
4.10
had its build status changed:
passing
to
partially failing
mirage-net-xen.1.13.1
on
4.11
had its build status changed:
passing
to
partially failing
mirage.4.0.0
on
5.0
is now installable. Current state is:
partially failing
mirage.4.0.0~beta3
on
5.0
is now installable. Current state is:
partially failing
mirage.4.1.0
on
5.0
is now installable. Current state is:
partially failing
mirage.4.1.1
on
5.0
is now installable. Current state is:
partially failing
mtime.0.8.0
on
4.02
had its build status changed:
passing
to
partially failing
mtime.0.8.0
on
4.03
had its build status changed:
passing
to
partially failing
mtime.0.8.0
on
4.04
had its build status changed:
passing
to
partially failing
mtime.0.8.1
on
4.02
had its build status changed:
passing
to
partially failing
mtime.0.8.1
on
4.03
had its build status changed:
passing
to
partially failing
mtime.0.8.1
on
4.04
had its build status changed:
passing
to
partially failing
mtime.0.8.2
on
4.02
had its build status changed:
passing
to
partially failing
mtime.0.8.2
on
4.03
had its build status changed:
passing
to
partially failing
mtime.0.8.2
on
4.04
had its build status changed:
passing
to
partially failing
nbd.1.0.3
on
4.02
had its build status changed:
passing
to
partially failing
nbd.1.0.3
on
4.03
had its build status changed:
passing
to
partially failing
nbd.1.0.3
on
4.04
had its build status changed:
passing
to
partially failing
nottui-lwt.0.2
on
4.03
is now installable. Current state is:
partially failing
nottui-lwt.0.2
on
4.04
is now installable. Current state is:
partially failing
ocaml-gist.0.0.1
on
4.04
had its build status changed:
failing
to
partially failing
ocaml-in-python.0.1.0
on
5.0
is now installable. Current state is:
partially failing
ocsigen-start.1.0.0
on
4.03
had its build status changed:
passing
to
partially failing
ocsigen-start.1.0.0
on
4.04
had its build status changed:
passing
to
partially failing
ocsigen-start.2.11.0
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.12.0
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.13.0
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.15.0
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.15.1
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.15.1
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.2.15.1
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.2.15.1
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.2.15.2
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.16.0
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.16.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.2.16.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.2.16.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.2.16.1
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.16.1
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.2.16.1
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.2.16.1
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.2.18.0
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.18.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.2.18.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.2.18.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.2.18.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.2
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.2
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.2
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.2
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.2
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.3
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.3
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.3
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.3
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.2.19.3
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.2.21.1
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.2.21.1
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.2.21.1
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.2.21.1
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.2.3.0
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.4.0
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.7.0
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.9.1
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.2.9.2
on
4.07
had its build status changed:
passing
to
partially failing
ocsigen-start.4.0.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.4.0.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.4.0.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.4.0.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.4.0.1
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.4.0.1
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.4.0.1
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.4.0.1
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.4.1.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.4.1.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.4.1.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.4.1.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.4.1.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigen-start.4.1.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigen-start.4.1.0
on
4.14
had its build status changed:
not available
to
partially failing
ocsigen-start.4.3.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.4.3.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.4.3.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.4.3.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.4.3.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigen-start.4.3.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigen-start.4.3.0
on
4.14
had its build status changed:
not available
to
partially failing
ocsigen-start.4.4.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.4.4.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.4.4.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.4.4.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.4.4.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigen-start.4.4.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigen-start.4.4.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigen-start.4.5.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.4.5.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.4.5.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.4.5.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.4.5.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigen-start.4.5.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigen-start.4.5.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigen-start.4.6.0
on
4.08
is now installable. Current state is:
partially failing
ocsigen-start.4.6.0
on
4.09
is now installable. Current state is:
partially failing
ocsigen-start.4.6.0
on
4.10
is now installable. Current state is:
partially failing
ocsigen-start.4.6.0
on
4.11
is now installable. Current state is:
partially failing
ocsigen-start.4.6.0
on
4.12
is now installable. Current state is:
partially failing
ocsigen-start.4.6.0
on
4.13
is now installable. Current state is:
partially failing
ocsigen-start.4.6.0
on
4.14
is now installable. Current state is:
partially failing
ocsigen-start.4.7.0
on
4.08
is now installable. Current state is:
partially failing
ocsigen-start.4.7.0
on
4.09
is now installable. Current state is:
partially failing
ocsigen-start.4.7.0
on
4.10
is now installable. Current state is:
partially failing
ocsigen-start.4.7.0
on
4.11
is now installable. Current state is:
partially failing
ocsigen-start.4.7.0
on
4.12
is now installable. Current state is:
partially failing
ocsigen-start.4.7.0
on
4.13
is now installable. Current state is:
partially failing
ocsigen-start.4.7.0
on
4.14
is now installable. Current state is:
partially failing
ocsigen-start.5.0.0
on
4.08
is now installable. Current state is:
partially failing
ocsigen-start.5.0.0
on
4.09
is now installable. Current state is:
partially failing
ocsigen-start.5.0.0
on
4.10
is now installable. Current state is:
partially failing
ocsigen-start.5.0.0
on
4.11
is now installable. Current state is:
partially failing
ocsigen-start.5.0.0
on
4.12
is now installable. Current state is:
partially failing
ocsigen-start.5.0.0
on
4.13
is now installable. Current state is:
partially failing
ocsigen-start.5.0.0
on
4.14
is now installable. Current state is:
partially failing
ocsigen-start.6.0.1
on
4.08
is now installable. Current state is:
partially failing
ocsigen-start.6.0.1
on
4.09
is now installable. Current state is:
partially failing
ocsigen-start.6.0.1
on
4.10
is now installable. Current state is:
partially failing
ocsigen-start.6.0.1
on
4.11
is now installable. Current state is:
partially failing
ocsigen-start.6.0.1
on
4.12
is now installable. Current state is:
partially failing
ocsigen-start.6.0.1
on
4.13
is now installable. Current state is:
partially failing
ocsigen-start.6.0.1
on
4.14
is now installable. Current state is:
partially failing
ocsigen-start.6.1.0
on
4.08
is now installable. Current state is:
partially failing
ocsigen-start.6.1.0
on
4.09
is now installable. Current state is:
partially failing
ocsigen-start.6.1.0
on
4.10
is now installable. Current state is:
partially failing
ocsigen-start.6.1.0
on
4.11
is now installable. Current state is:
partially failing
ocsigen-start.6.1.0
on
4.12
is now installable. Current state is:
partially failing
ocsigen-start.6.1.0
on
4.13
is now installable. Current state is:
partially failing
ocsigen-start.6.1.0
on
4.14
is now installable. Current state is:
partially failing
ocsigen-toolkit.0.99
on
4.02
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.0.99
on
4.03
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.0.99
on
4.04
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.1.0.0
on
4.02
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.1.0.0
on
4.03
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.1.0.0
on
4.04
had its build status changed:
passing
to
partially failing
ojs-base.0.5.0
on
4.04
had its build status changed:
failing
to
partially failing
opam-0install-cudf.0.4.3
on
5.0
is now installable. Current state is:
partially failing
opentelemetry-client-ocurl.0.2
on
5.0
is now installable. Current state is:
partially failing
opentelemetry-lwt.0.2
on
5.0
is now installable. Current state is:
partially failing
opentelemetry.0.2
on
5.0
is now installable. Current state is:
partially failing
orsetto.1.0
on
4.08
had its build status changed:
passing
to
partially failing
orsetto.1.0.1
on
4.08
had its build status changed:
passing
to
partially failing
orsetto.1.0.2
on
4.08
had its build status changed:
passing
to
partially failing
orsetto.1.0.2
on
4.09
had its build status changed:
passing
to
partially failing
orsetto.1.0.2
on
4.10
had its build status changed:
passing
to
partially failing
orsetto.1.0.2
on
4.11
had its build status changed:
passing
to
partially failing
orsetto.1.0.2
on
4.12
had its build status changed:
passing
to
partially failing
orsetto.1.0.2
on
4.13
had its build status changed:
passing
to
partially failing
orsetto.1.0.2
on
4.14
had its build status changed:
passing
to
partially failing
orsetto.1.0.3
on
4.08
had its build status changed:
passing
to
partially failing
orsetto.1.0.3
on
4.09
had its build status changed:
passing
to
partially failing
orsetto.1.0.3
on
4.10
had its build status changed:
passing
to
partially failing
orsetto.1.0.3
on
4.11
had its build status changed:
passing
to
partially failing
orsetto.1.0.3
on
4.12
had its build status changed:
passing
to
partially failing
orsetto.1.0.3
on
4.13
had its build status changed:
passing
to
partially failing
orsetto.1.0.3
on
4.14
had its build status changed:
passing
to
partially failing
orsetto.1.1
on
4.08
had its build status changed:
passing
to
partially failing
orsetto.1.1
on
4.09
had its build status changed:
passing
to
partially failing
orsetto.1.1
on
4.10
had its build status changed:
passing
to
partially failing
orsetto.1.1
on
4.11
had its build status changed:
passing
to
partially failing
orsetto.1.1
on
4.12
had its build status changed:
passing
to
partially failing
orsetto.1.1
on
4.13
had its build status changed:
passing
to
partially failing
orsetto.1.1
on
4.14
had its build status changed:
passing
to
partially failing
orsetto.1.1.1
on
4.08
had its build status changed:
passing
to
partially failing
orsetto.1.1.1
on
4.09
had its build status changed:
passing
to
partially failing
orsetto.1.1.1
on
4.10
had its build status changed:
passing
to
partially failing
orsetto.1.1.1
on
4.11
had its build status changed:
passing
to
partially failing
orsetto.1.1.1
on
4.12
had its build status changed:
passing
to
partially failing
orsetto.1.1.1
on
4.13
had its build status changed:
passing
to
partially failing
orsetto.1.1.1
on
4.14
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-jupyter.1.0
on
4.13
had its build status changed:
passing
to
partially failing
owl-top.1.0.2
on
4.10
is now installable. Current state is:
partially failing
owl-top.1.0.2
on
4.11
is now installable. Current state is:
partially failing
owl-top.1.0.2
on
4.12
is now installable. Current state is:
partially failing
owl-top.1.0.2
on
4.13
is now installable. Current state is:
partially failing
patoline.0.1
on
4.03
had its build status changed:
failing
to
partially failing
patoline.0.1
on
4.04
had its build status changed:
failing
to
partially failing
patoline.0.1
on
4.05
had its build status changed:
failing
to
partially failing
pattern.0.3.0
on
5.0
had its build status changed:
not available
to
partially failing
pattern.0.3.1
on
5.0
had its build status changed:
not available
to
partially failing
pkcs11.0.1.0
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.1.0
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.2.0
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.2.0
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.3.0
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.3.0
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.4.0
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.4.0
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.5.0
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.5.0
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.6.0
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.6.0
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.7.0
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.7.0
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.7.1
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.7.1
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.7.2
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.7.2
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.7.3
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.7.3
on
4.05
had its build status changed:
passing
to
partially failing
pkcs11.0.8.0
on
4.04
had its build status changed:
passing
to
partially failing
pkcs11.0.8.0
on
4.05
had its build status changed:
passing
to
partially failing
plato.1.1.2
on
5.0
is now installable. Current state is:
partially failing
ppx_deriving_rpc.6.0.0
on
4.04
had its build status changed:
passing
to
partially failing
ppx_deriving_rpc.6.0.0
on
4.05
had its build status changed:
passing
to
partially failing
ppx_deriving_rpc.6.0.0
on
4.06
had its build status changed:
passing
to
partially failing
ppx_deriving_rpc.6.0.0
on
4.07
had its build status changed:
passing
to
partially failing
ppx_deriving_rpc.6.0.0
on
4.08
had its build status changed:
passing
to
partially failing
ppx_deriving_rpc.6.0.0
on
4.09
had its build status changed:
passing
to
partially failing
prbnmcn-dagger-gsl.0.0.1
on
5.0
is now installable. Current state is:
partially failing
prbnmcn-dagger-gsl.0.0.2
on
5.0
is now installable. Current state is:
partially failing
prbnmcn-dagger-test.0.0.1
on
5.0
is now installable. Current state is:
partially failing
prbnmcn-dagger-test.0.0.2
on
5.0
is now installable. Current state is:
partially failing
prof_spacetime.0.1.0
on
4.06
had its build status changed:
passing
to
partially failing
prof_spacetime.0.3.0
on
4.06
had its build status changed:
passing
to
partially failing
prof_spacetime.0.3.0
on
4.07
had its build status changed:
passing
to
partially failing
prof_spacetime.0.3.0
on
4.08
had its build status changed:
passing
to
partially failing
prof_spacetime.0.3.0
on
4.09
had its build status changed:
passing
to
partially failing
prof_spacetime.0.3.0
on
4.10
had its build status changed:
passing
to
partially failing
prof_spacetime.0.3.0
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.0
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.0
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.0
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.0
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.1
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.1
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.1
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.1
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.2
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.2
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.2
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.2
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.3
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.3
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.3
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p-tool.0.11.3
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.0
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.0
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.0
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.0
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.1
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.1
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.1
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.1
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.2
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.2
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.2
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.2
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.3
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.3
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.3
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.11.3
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.12.0
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.12.0
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.12.0
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p-unix.0.12.0
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.0
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.0
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.0
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.0
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.1
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.1
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.1
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.1
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.2
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.2
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.2
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.2
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.3
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.3
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.3
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p.0.11.3
on
4.11
had its build status changed:
passing
to
partially failing
protocol-9p.0.12.0
on
4.08
had its build status changed:
passing
to
partially failing
protocol-9p.0.12.0
on
4.09
had its build status changed:
passing
to
partially failing
protocol-9p.0.12.0
on
4.10
had its build status changed:
passing
to
partially failing
protocol-9p.0.12.0
on
4.11
had its build status changed:
passing
to
partially failing
pyml.20220322
on
5.0
is now installable. Current state is:
partially failing
pyml.20220325
on
5.0
is now installable. Current state is:
partially failing
pyml.20220615
on
5.0
is now installable. Current state is:
partially failing
reedsolomon.0.2
on
4.02
had its build status changed:
passing
to
partially failing
reedsolomon.0.2
on
4.03
had its build status changed:
passing
to
partially failing
reedsolomon.0.2
on
4.04
had its build status changed:
passing
to
partially failing
ringo-lwt.0.8
on
5.0
is now installable. Current state is:
partially failing
ringo-lwt.0.9
on
5.0
is now installable. Current state is:
partially failing
rpc.1.3.0
on
4.02
had its build status changed:
passing
to
partially failing
rpc.1.3.1
on
4.02
had its build status changed:
passing
to
partially failing
rpc.1.4.1
on
4.02
had its build status changed:
passing
to
partially failing
rpc.1.5.0
on
4.02
had its build status changed:
passing
to
partially failing
rpc.6.0.0
on
4.04
had its build status changed:
passing
to
partially failing
rpc.6.0.0
on
4.05
had its build status changed:
passing
to
partially failing
rpc.6.0.0
on
4.06
had its build status changed:
passing
to
partially failing
rpc.6.0.0
on
4.07
had its build status changed:
passing
to
partially failing
rpclib-async.6.0.0
on
4.04
had its build status changed:
passing
to
partially failing
rpclib-async.6.0.0
on
4.05
had its build status changed:
passing
to
partially failing
rpclib-async.6.0.0
on
4.06
had its build status changed:
passing
to
partially failing
rpclib-async.6.0.0
on
4.07
had its build status changed:
passing
to
partially failing
rpclib-async.6.0.0
on
4.08
had its build status changed:
passing
to
partially failing
rpclib-async.6.0.0
on
4.09
had its build status changed:
passing
to
partially failing
rpclib-lwt.6.0.0
on
4.04
had its build status changed:
passing
to
partially failing
rpclib-lwt.6.0.0
on
4.05
had its build status changed:
passing
to
partially failing
rpclib-lwt.6.0.0
on
4.06
had its build status changed:
passing
to
partially failing
rpclib-lwt.6.0.0
on
4.07
had its build status changed:
passing
to
partially failing
rpclib-lwt.6.0.0
on
4.08
had its build status changed:
passing
to
partially failing
rpclib-lwt.6.0.0
on
4.09
had its build status changed:
passing
to
partially failing
rtop.3.8.1
on
5.0
is now installable. Current state is:
partially failing
slack-backup.0.1
on
4.02
had its build status changed:
passing
to
partially failing
slack-backup.0.1
on
4.03
had its build status changed:
passing
to
partially failing
slack-backup.0.1
on
4.04
had its build status changed:
passing
to
partially failing
slack-backup.0.1
on
4.05
had its build status changed:
passing
to
partially failing
slack-backup.0.1
on
4.06
had its build status changed:
passing
to
partially failing
soupault.4.0.1
on
5.0
is now installable. Current state is:
partially failing
sphinxcontrib-ocaml.0.2.0
on
4.05
had its build status changed:
failing
to
partially failing
stog-writing.0.11.0
on
4.02
had its build status changed:
passing
to
partially failing
stog.0.11.1
on
4.02
had its build status changed:
passing
to
partially failing
stog.0.14.0
on
4.02
had its build status changed:
passing
to
partially failing
stog.0.16.0
on
4.04
had its build status changed:
failing
to
partially failing
stog.0.16.0
on
4.05
had its build status changed:
failing
to
partially failing
stog.0.16.0
on
4.06
had its build status changed:
failing
to
partially failing
stog.0.16.0
on
4.07
had its build status changed:
failing
to
partially failing
stog.0.17.0
on
4.04
had its build status changed:
failing
to
partially failing
stog.0.17.0
on
4.05
had its build status changed:
failing
to
partially failing
stog.0.17.0
on
4.06
had its build status changed:
failing
to
partially failing
stog.0.17.0
on
4.07
had its build status changed:
failing
to
partially failing
stog.0.17.1
on
4.04
had its build status changed:
failing
to
partially failing
stog.0.17.1
on
4.05
had its build status changed:
failing
to
partially failing
stog.0.17.1
on
4.06
had its build status changed:
failing
to
partially failing
stog.0.17.1
on
4.07
had its build status changed:
failing
to
partially failing
stog.0.18.0
on
4.04
had its build status changed:
failing
to
partially failing
stog.0.18.0
on
4.05
had its build status changed:
failing
to
partially failing
stog.0.18.0
on
4.06
had its build status changed:
failing
to
partially failing
stog.0.18.0
on
4.07
had its build status changed:
failing
to
partially failing
stog.0.18.0-1
on
4.04
had its build status changed:
failing
to
partially failing
stog.0.18.0-1
on
4.05
had its build status changed:
failing
to
partially failing
stog.0.18.0-1
on
4.06
had its build status changed:
failing
to
partially failing
stog.0.18.0-1
on
4.07
had its build status changed:
failing
to
partially failing
stog_all.0.20.0
on
4.12
had its build status changed:
passing
to
partially failing
stog_server_multi.0.20.0
on
4.12
had its build status changed:
passing
to
partially failing
tezos.10.2
on
4.10
had its build status changed:
passing
to
partially failing
tezos.7.0
on
4.09
had its build status changed:
passing
to
partially failing
tezos.7.1
on
4.09
had its build status changed:
passing
to
partially failing
tezos.7.2
on
4.09
had its build status changed:
passing
to
partially failing
tezos.7.3
on
4.09
had its build status changed:
passing
to
partially failing
tezos.7.4
on
4.09
had its build status changed:
passing
to
partially failing
tezos.8.0
on
4.09
had its build status changed:
passing
to
partially failing
tezos.8.0
on
4.10
had its build status changed:
passing
to
partially failing
tezos.8.1
on
4.09
had its build status changed:
passing
to
partially failing
tezos.8.1
on
4.10
had its build status changed:
passing
to
partially failing
tezos.8.2
on
4.09
had its build status changed:
passing
to
partially failing
tezos.8.2
on
4.10
had its build status changed:
passing
to
partially failing
tezos.8.3
on
4.09
had its build status changed:
passing
to
partially failing
tezos.8.3
on
4.10
had its build status changed:
passing
to
partially failing
tezos.9.1
on
4.10
had its build status changed:
passing
to
partially failing
tezos.9.2
on
4.10
had its build status changed:
passing
to
partially failing
tezos.9.3
on
4.10
had its build status changed:
passing
to
partially failing
tezos.9.4
on
4.10
had its build status changed:
passing
to
partially failing
tezos.9.7
on
4.10
had its build status changed:
passing
to
partially failing
themoviedb.0.8
on
4.02
had its build status changed:
passing
to
partially failing
themoviedb.0.8
on
4.03
had its build status changed:
passing
to
partially failing
themoviedb.0.8
on
4.04
had its build status changed:
passing
to
partially failing
themoviedb.0.8
on
4.05
had its build status changed:
passing
to
partially failing
themoviedb.0.8.1
on
4.02
had its build status changed:
passing
to
partially failing
themoviedb.0.8.1
on
4.03
had its build status changed:
passing
to
partially failing
themoviedb.0.8.1
on
4.04
had its build status changed:
passing
to
partially failing
themoviedb.0.8.1
on
4.05
had its build status changed:
passing
to
partially failing
timedesc.0.6.0
on
5.0
is now installable. Current state is:
partially failing
timere-parse.0.0.6
on
5.0
is now installable. Current state is:
partially failing
timere.0.7.0
on
5.0
is now installable. Current state is:
partially failing
utop.2.9.1
on
5.0
is now installable. Current state is:
partially failing
utop.2.9.2
on
5.0
is now installable. Current state is:
partially failing
vhd-format-lwt.0.12.1
on
4.08
had its build status changed:
passing
to
partially failing
vhd-format-lwt.0.12.1
on
4.09
had its build status changed:
passing
to
partially failing
vhd-format-lwt.0.12.1
on
4.10
had its build status changed:
passing
to
partially failing
vhd-format-lwt.0.12.1
on
4.11
had its build status changed:
passing
to
partially failing
vhd-format-lwt.0.12.1
on
4.12
had its build status changed:
passing
to
partially failing
vhd-format-lwt.0.12.2
on
4.08
had its build status changed:
passing
to
partially failing
vhd-format-lwt.0.12.2
on
4.09
had its build status changed:
passing
to
partially failing
vhd-format-lwt.0.12.2
on
4.10
had its build status changed:
passing
to
partially failing
vhd-format-lwt.0.12.2
on
4.11
had its build status changed:
passing
to
partially failing
vhd-format-lwt.0.12.2
on
4.12
had its build status changed:
passing
to
partially failing
virtual_dom.v0.9.0
on
4.03
had its build status changed:
passing
to
partially failing
virtual_dom.v0.9.0
on
4.04
had its build status changed:
passing
to
partially failing
wcs.2017-05-26.05
on
4.08
had its build status changed:
passing
to
partially failing
wcs.2017-05-26.05
on
4.09
had its build status changed:
passing
to
partially failing
wcs.2017-05-26.05
on
4.10
had its build status changed:
passing
to
partially failing
wcs.2017-05-26.05
on
4.11
had its build status changed:
passing
to
partially failing
wcs.2017-05-26.05
on
4.12
had its build status changed:
passing
to
partially failing
webtest.1.0.0
on
4.02
had its build status changed:
passing
to
partially failing
webtest.1.0.0
on
4.03
had its build status changed:
passing
to
partially failing
webtest.1.0.0
on
4.04
had its build status changed:
internal failure
to
partially failing
webtest.1.0.2
on
4.02
had its build status changed:
passing
to
partially failing
webtest.1.0.2
on
4.03
had its build status changed:
passing
to
partially failing
webtest.1.0.2
on
4.04
had its build status changed:
passing
to
partially failing
webtest.1.1.0
on
4.02
had its build status changed:
passing
to
partially failing
webtest.1.1.0
on
4.03
had its build status changed:
passing
to
partially failing
webtest.1.1.0
on
4.04
had its build status changed:
passing
to
partially failing
xapi-backtrace.0.4
on
4.02
had its build status changed:
passing
to
partially failing
xapi-backtrace.0.4
on
4.03
had its build status changed:
passing
to
partially failing
xapi-backtrace.0.4
on
4.04
had its build status changed:
failing
to
partially failing
xapi-backtrace.0.4
on
4.05
had its build status changed:
passing
to
partially failing
xapi-backtrace.0.5
on
4.02
had its build status changed:
passing
to
partially failing
xapi-backtrace.0.5
on
4.03
had its build status changed:
passing
to
partially failing
xapi-backtrace.0.5
on
4.04
had its build status changed:
failing
to
partially failing
xapi-backtrace.0.5
on
4.05
had its build status changed:
passing
to
partially failing
xapi-inventory.1.0.2
on
4.02
had its build status changed:
passing
to
partially failing
xapi-inventory.1.0.2
on
4.03
had its build status changed:
passing
to
partially failing
xapi-inventory.1.0.2
on
4.05
had its build status changed:
passing
to
partially failing
xapi-rrd.0.10.1
on
4.02
had its build status changed:
passing
to
partially failing
xapi-rrd.0.10.1
on
4.03
had its build status changed:
passing
to
partially failing
xapi-rrd.0.10.1
on
4.04
had its build status changed:
passing
to
partially failing
xapi-rrd.0.10.1
on
4.05
had its build status changed:
passing
to
partially failing
xapi-rrd.0.12.0
on
4.02
had its build status changed:
passing
to
partially failing
xapi-rrd.0.12.0
on
4.03
had its build status changed:
passing
to
partially failing
xapi-rrd.0.12.0
on
4.04
had its build status changed:
passing
to
partially failing
xapi-rrd.0.12.0
on
4.05
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.0
on
4.02
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.0
on
4.03
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.0
on
4.04
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.0
on
4.05
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.1
on
4.02
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.1
on
4.03
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.1
on
4.04
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.1
on
4.05
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.2
on
4.02
had its build status changed:
passing
to
partially failing
xapi-rrd.1.0.2
on
4.03
had its build status changed:
passing
to
partially failing
xapi-stdext-pervasives.4.14.0
on
4.02
had its build status changed:
passing
to
partially failing
xapi-stdext-pervasives.4.14.0
on
4.03
had its build status changed:
passing
to
partially failing
xapi-stdext-threads.4.14.0
on
4.02
had its build status changed:
passing
to
partially failing
xapi-stdext-threads.4.14.0
on
4.03
had its build status changed:
passing
to
partially failing
xapi-stdext.2.1.0
on
4.02
had its build status changed:
passing
to
partially failing
xapi-stdext.2.1.0
on
4.03
had its build status changed:
passing
to
partially failing
xapi-stdext.2.1.0
on
4.05
had its build status changed:
passing
to
partially failing
xtmpl.0.11
on
4.02
had its build status changed:
passing
to
partially failing
xtmpl.0.12
on
4.02
had its build status changed:
passing
to
partially failing
xtmpl.0.13.0
on
4.02
had its build status changed:
failing
to
partially failing
xtmpl.0.14.0
on
4.03
had its build status changed:
failing
to
partially failing
xtmpl.0.14.0
on
4.04
had its build status changed:
failing
to
partially failing
xtmpl.0.15.0
on
4.03
had its build status changed:
failing
to
partially failing
xtmpl.0.15.0
on
4.04
had its build status changed:
failing
to
partially failing
xtmpl.0.16.0
on
4.03
had its build status changed:
passing
to
partially failing
xtmpl.0.16.0
on
4.04
had its build status changed:
passing
to
partially failing
z3_tptp.4.8.13
on
5.0
is now installable. Current state is:
partially failing
zarith-xen.1.3
on
5.0
had its build status changed:
passing
to
partially failing
Packages now
not available
:
KaSim.4.0.0
on
4.08
had its build status changed:
passing
to
not available
KaSim.4.0.0
on
4.09
had its build status changed:
passing
to
not available
KaSim.4.0.0
on
4.10
had its build status changed:
passing
to
not available
KaSim.4.0.0
on
4.11
had its build status changed:
passing
to
not available
KaSim.4.0.0
on
4.12
had its build status changed:
passing
to
not available
KaSim.4.0.0
on
4.13
had its build status changed:
passing
to
not available
KaSim.4.0.0
on
4.14
had its build status changed:
passing
to
not available
KaSim.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
OCanren-ppx.0.2.0
on
5.0
had its build status changed:
partially failing
to
not available
SZXX.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
SZXX.1.0.0
on
5.0
had its build status changed:
partially failing
to
not available
SZXX.1.1.0
on
5.0
had its build status changed:
partially failing
to
not available
SZXX.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
accessor.v0.14.1
on
5.0
had its build status changed:
partially failing
to
not available
accessor_base.v0.14.1
on
5.0
had its build status changed:
partially failing
to
not available
advi.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
ahrocksdb.0.2.0
on
5.0
had its build status changed:
partially failing
to
not available
albatross.1.0.1
on
5.0
had its build status changed:
partially failing
to
not available
albatross.1.1.0
on
5.0
had its build status changed:
partially failing
to
not available
albatross.1.1.1
on
5.0
had its build status changed:
partially failing
to
not available
albatross.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
albatross.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
albatross.1.3.1
on
5.0
had its build status changed:
partially failing
to
not available
albatross.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
albatross.1.4.1
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.0.8.5
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.0.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.0.1
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.1.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.2.3
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-async.1.5.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-lwt.1.1.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-lwt.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-lwt.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-lwt.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-lwt.1.2.3
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-mirage.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-mirage.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-mirage.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
alcotest-mirage.1.2.3
on
5.0
had its build status changed:
partially failing
to
not available
alcotest.1.1.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
alcotest.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
alcotest.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
alcotest.1.2.3
on
5.0
had its build status changed:
partially failing
to
not available
alt-ergo-lib.2.3.0
on
5.0
had its build status changed:
failing
to
not available
alt-ergo-lib.2.3.1
on
5.0
had its build status changed:
failing
to
not available
alt-ergo-lib.2.3.2
on
5.0
had its build status changed:
passing
to
not available
alt-ergo-lib.2.3.3
on
5.0
had its build status changed:
passing
to
not available
alt-ergo-lib.2.4.0
on
5.0
had its build status changed:
passing
to
not available
alt-ergo-lib.2.4.1
on
5.0
had its build status changed:
passing
to
not available
alt-ergo-parsers.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
alt-ergo-parsers.2.3.1
on
5.0
had its build status changed:
partially failing
to
not available
alt-ergo-parsers.2.3.2
on
5.0
had its build status changed:
passing
to
not available
alt-ergo-parsers.2.3.3
on
5.0
had its build status changed:
passing
to
not available
alt-ergo-parsers.2.4.0
on
5.0
had its build status changed:
passing
to
not available
alt-ergo-parsers.2.4.1
on
5.0
had its build status changed:
passing
to
not available
alt-ergo.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
alt-ergo.2.3.1
on
5.0
had its build status changed:
partially failing
to
not available
alt-ergo.2.3.2
on
5.0
had its build status changed:
passing
to
not available
alt-ergo.2.3.3
on
5.0
had its build status changed:
passing
to
not available
alt-ergo.2.4.0
on
5.0
had its build status changed:
passing
to
not available
alt-ergo.2.4.1
on
5.0
had its build status changed:
passing
to
not available
amqp-client-async.2.0.3
on
5.0
had its build status changed:
partially failing
to
not available
amqp-client-async.2.1.0
on
5.0
had its build status changed:
partially failing
to
not available
amqp-client-async.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
amqp-client-async.2.2.1
on
5.0
had its build status changed:
partially failing
to
not available
amqp-client-async.2.2.2
on
5.0
had its build status changed:
partially failing
to
not available
angstrom-async.0.11.1
on
5.0
had its build status changed:
partially failing
to
not available
angstrom-async.0.11.2
on
5.0
had its build status changed:
partially failing
to
not available
angstrom-async.0.12.1
on
5.0
had its build status changed:
partially failing
to
not available
angstrom-async.0.13.0
on
5.0
had its build status changed:
partially failing
to
not available
angstrom-async.0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
angstrom-async.0.14.1
on
5.0
had its build status changed:
partially failing
to
not available
angstrom-async.0.15.0
on
5.0
had its build status changed:
partially failing
to
not available
archetype.0.1.3
on
5.0
had its build status changed:
partially failing
to
not available
archi-async.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
archimedes.0.4.19
on
4.06
had its build status changed:
passing
to
not available
archimedes.0.4.19
on
4.07
had its build status changed:
passing
to
not available
archimedes.0.4.19
on
4.08
had its build status changed:
passing
to
not available
archimedes.0.4.19
on
4.09
had its build status changed:
passing
to
not available
archimedes.0.4.19
on
4.10
had its build status changed:
passing
to
not available
archimedes.0.4.19
on
4.11
had its build status changed:
passing
to
not available
archimedes.0.4.19
on
4.12
had its build status changed:
passing
to
not available
archimedes.0.4.19
on
4.13
had its build status changed:
passing
to
not available
archimedes.0.4.19
on
4.14
had its build status changed:
passing
to
not available
arp-mirage.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
arp-mirage.2.1.0
on
5.0
had its build status changed:
partially failing
to
not available
arp-mirage.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
arp-mirage.2.2.1
on
5.0
had its build status changed:
partially failing
to
not available
arp.0.2.1
on
5.0
had its build status changed:
partially failing
to
not available
arp.0.2.2
on
5.0
had its build status changed:
partially failing
to
not available
arp.2.3.1
on
5.0
had its build status changed:
partially failing
to
not available
arp.2.3.2
on
5.0
had its build status changed:
partially failing
to
not available
arp.3.0.0
on
5.0
had its build status changed:
partially failing
to
not available
asn1-combinators.0.2.4
on
5.0
had its build status changed:
partially failing
to
not available
asn1-combinators.0.2.5
on
5.0
had its build status changed:
partially failing
to
not available
async.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_durable.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_extra.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_find.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_graphics.0.7.0
on
5.0
had its build status changed:
partially failing
to
not available
async_inotify.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_interactive.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_kernel.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_rpc_kernel.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_sendfile.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_shell.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_udp.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_unix.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
async_websocket.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
awa-lwt.0.0.1
on
5.0
had its build status changed:
partially failing
to
not available
awa-lwt.0.0.2
on
5.0
had its build status changed:
partially failing
to
not available
awa-lwt.0.0.3
on
5.0
had its build status changed:
partially failing
to
not available
awa-lwt.0.0.4
on
5.0
had its build status changed:
partially failing
to
not available
awa-lwt.0.0.5
on
5.0
had its build status changed:
partially failing
to
not available
awa-lwt.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
awa-mirage.0.0.1
on
5.0
had its build status changed:
partially failing
to
not available
awa-mirage.0.0.2
on
5.0
had its build status changed:
partially failing
to
not available
awa-mirage.0.0.3
on
5.0
had its build status changed:
partially failing
to
not available
awa-mirage.0.0.4
on
5.0
had its build status changed:
partially failing
to
not available
awa-mirage.0.0.5
on
5.0
had its build status changed:
partially failing
to
not available
awa-mirage.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
awa.0.0.1
on
5.0
had its build status changed:
partially failing
to
not available
awa.0.0.2
on
5.0
had its build status changed:
partially failing
to
not available
awa.0.0.3
on
5.0
had its build status changed:
partially failing
to
not available
awa.0.0.4
on
5.0
had its build status changed:
partially failing
to
not available
awa.0.0.5
on
5.0
had its build status changed:
partially failing
to
not available
awa.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-async.1.2
on
5.0
had its build status changed:
partially failing
to
not available
aws-autoscaling.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-cloudformation.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-cloudtrail.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-ec2.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-elasticloadbalancing.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-lwt.1.2
on
5.0
had its build status changed:
partially failing
to
not available
aws-s3-async.4.4.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-s3-async.4.4.1
on
5.0
had its build status changed:
partially failing
to
not available
aws-s3-async.4.5.1
on
5.0
had its build status changed:
partially failing
to
not available
aws-s3-lwt.4.4.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-s3-lwt.4.4.1
on
5.0
had its build status changed:
partially failing
to
not available
aws-s3-lwt.4.5.1
on
5.0
had its build status changed:
partially failing
to
not available
aws-s3.4.4.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-s3.4.4.1
on
5.0
had its build status changed:
partially failing
to
not available
aws-s3.4.5.1
on
5.0
had its build status changed:
partially failing
to
not available
aws-sdb.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-ssm.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
aws-sts.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
aws.1.0.0
on
5.0
had its build status changed:
partially failing
to
not available
aws.1.0.1
on
5.0
had its build status changed:
partially failing
to
not available
aws.1.0.2
on
5.0
had its build status changed:
partially failing
to
not available
azblob-async.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
azblob.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
b0.0.0.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-abi.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-abi.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-abi.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-analyze.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-analyze.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-analyze.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-api.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-api.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-api.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-arm.1.0.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-arm.1.0.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-arm.1.0.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-arm.1.1.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-arm.1.1.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-arm.1.1.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-arm.1.2.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-arm.1.2.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-arm.1.2.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-arm.1.3.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-arm.1.3.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-arm.1.3.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-arm.1.6.0
on
4.04
is not available anymore. Previous state was:
passing
bap-arm.1.6.0
on
4.05
is not available anymore. Previous state was:
passing
bap-arm.1.6.0
on
4.06
is not available anymore. Previous state was:
passing
bap-arm.1.6.0
on
4.07
is not available anymore. Previous state was:
passing
bap-arm.2.0.0
on
4.04
is not available anymore. Previous state was:
passing
bap-arm.2.0.0
on
4.05
is not available anymore. Previous state was:
passing
bap-arm.2.0.0
on
4.06
is not available anymore. Previous state was:
passing
bap-arm.2.0.0
on
4.07
is not available anymore. Previous state was:
passing
bap-arm.2.1.0
on
4.07
is not available anymore. Previous state was:
passing
bap-arm.2.1.0
on
4.08
is not available anymore. Previous state was:
passing
bap-arm.2.1.0
on
4.09
is not available anymore. Previous state was:
passing
bap-arm.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-arm.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-arm.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-beagle-strings.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-beagle-strings.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-beagle-strings.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-beagle.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-beagle.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-beagle.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-bil.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-bil.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-bil.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-build.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-build.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-build.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-bundle.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-bundle.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-bundle.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-byteweight-frontend.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-byteweight-frontend.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-byteweight-frontend.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-byteweight.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-byteweight.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-byteweight.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-c.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-c.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-c.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-cache.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-cache.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-cache.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-callgraph-collator.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-callgraph-collator.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-callgraph-collator.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-callsites.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-callsites.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-callsites.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-constant-tracker.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-constant-tracker.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-constant-tracker.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-core-theory.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-core-theory.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-core-theory.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-core.2.4.0
on
4.08
is not available anymore. Previous state was:
passing
bap-core.2.4.0
on
4.09
is not available anymore. Previous state was:
passing
bap-core.2.4.0
on
4.10
is not available anymore. Previous state was:
passing
bap-core.2.4.0
on
4.11
is not available anymore. Previous state was:
passing
bap-core.2.4.0
on
4.12
is not available anymore. Previous state was:
passing
bap-core.2.4.0
on
4.13
is not available anymore. Previous state was:
passing
bap-core.2.4.0
on
4.14
is not available anymore. Previous state was:
passing
bap-core.2.4.0
on
5.00
is not available anymore. Previous state was:
partially failing
bap-cxxfilt.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-cxxfilt.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-cxxfilt.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-demangle.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-demangle.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-demangle.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-dependencies.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-dependencies.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-disassemble.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-disassemble.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-disassemble.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-dump-symbols.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-dump-symbols.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-dump-symbols.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-dwarf.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-dwarf.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-dwarf.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-elementary.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-elementary.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-elementary.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-extra.2.4.0
on
4.08
is not available anymore. Previous state was:
partially failing
bap-extra.2.4.0
on
4.09
is not available anymore. Previous state was:
partially failing
bap-extra.2.4.0
on
4.10
is not available anymore. Previous state was:
partially failing
bap-extra.2.4.0
on
4.11
is not available anymore. Previous state was:
partially failing
bap-extra.2.4.0
on
4.12
is not available anymore. Previous state was:
partially failing
bap-flatten.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-frontc.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-frontc.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-frontc.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-frontend.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-frontend.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-frontend.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-fsi-benchmark.1.0.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.0.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.1.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.1.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.2.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.2.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.2.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.3.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.3.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.3.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.6.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.6.0
on
4.05
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.6.0
on
4.06
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.1.6.0
on
4.07
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.2.2.0
on
4.08
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.2.2.0
on
4.09
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.2.3.0
on
4.08
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.2.3.0
on
4.09
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.2.3.0
on
4.10
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.2.3.0
on
4.11
is not available anymore. Previous state was:
partially failing
bap-fsi-benchmark.2.3.0
on
4.12
is not available anymore. Previous state was:
partially failing
bap-future.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-future.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-future.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-ghidra.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-glibc-runtime.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-glibc-runtime.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-glibc-runtime.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-ida-plugin.1.0.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.0.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.1.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.1.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.2.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.2.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.2.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.3.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.3.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.3.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida-plugin.1.6.0
on
4.04
is not available anymore. Previous state was:
passing
bap-ida-plugin.1.6.0
on
4.05
is not available anymore. Previous state was:
passing
bap-ida-plugin.1.6.0
on
4.06
is not available anymore. Previous state was:
passing
bap-ida-plugin.1.6.0
on
4.07
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.0.0
on
4.04
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.0.0
on
4.05
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.0.0
on
4.06
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.0.0
on
4.07
is not available anymore. Previous state was:
failing
bap-ida-plugin.2.1.0
on
4.07
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.1.0
on
4.08
is not available anymore. Previous state was:
failing
bap-ida-plugin.2.1.0
on
4.09
is not available anymore. Previous state was:
failing
bap-ida-plugin.2.2.0
on
4.08
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.2.0
on
4.09
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.2.0
on
4.10
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.2.0
on
4.11
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.2.0
on
4.12
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.3.0
on
4.08
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.3.0
on
4.09
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.3.0
on
4.10
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.3.0
on
4.11
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.3.0
on
4.12
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.4.0
on
4.08
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.4.0
on
4.09
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.4.0
on
4.10
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.4.0
on
4.11
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.4.0
on
4.12
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.4.0
on
4.13
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.4.0
on
4.14
is not available anymore. Previous state was:
passing
bap-ida-plugin.2.4.0
on
5.00
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.0.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.0.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.1.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.1.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.2.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.2.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.2.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.3.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.3.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.3.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.6.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.6.0
on
4.05
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.6.0
on
4.06
is not available anymore. Previous state was:
partially failing
bap-ida-python.1.6.0
on
4.07
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.0.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.0.0
on
4.05
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.0.0
on
4.06
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.0.0
on
4.07
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.1.0
on
4.07
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.1.0
on
4.08
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.1.0
on
4.09
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.2.0
on
4.08
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.2.0
on
4.09
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.3.0
on
4.08
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.3.0
on
4.09
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.3.0
on
4.10
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.3.0
on
4.11
is not available anymore. Previous state was:
partially failing
bap-ida-python.2.3.0
on
4.12
is not available anymore. Previous state was:
partially failing
bap-ida.1.0.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida.1.0.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida.1.1.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida.1.1.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida.1.2.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida.1.2.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida.1.2.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida.1.3.0
on
4.02
is not available anymore. Previous state was:
partially failing
bap-ida.1.3.0
on
4.03
is not available anymore. Previous state was:
partially failing
bap-ida.1.3.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida.1.6.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida.1.6.0
on
4.05
is not available anymore. Previous state was:
partially failing
bap-ida.1.6.0
on
4.06
is not available anymore. Previous state was:
partially failing
bap-ida.1.6.0
on
4.07
is not available anymore. Previous state was:
partially failing
bap-ida.2.0.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-ida.2.0.0
on
4.05
is not available anymore. Previous state was:
partially failing
bap-ida.2.0.0
on
4.06
is not available anymore. Previous state was:
partially failing
bap-ida.2.0.0
on
4.07
is not available anymore. Previous state was:
partially failing
bap-ida.2.1.0
on
4.07
is not available anymore. Previous state was:
partially failing
bap-ida.2.1.0
on
4.08
is not available anymore. Previous state was:
partially failing
bap-ida.2.1.0
on
4.09
is not available anymore. Previous state was:
partially failing
bap-ida.2.2.0
on
4.08
is not available anymore. Previous state was:
partially failing
bap-ida.2.2.0
on
4.09
is not available anymore. Previous state was:
partially failing
bap-ida.2.3.0
on
4.08
is not available anymore. Previous state was:
partially failing
bap-ida.2.3.0
on
4.09
is not available anymore. Previous state was:
partially failing
bap-ida.2.3.0
on
4.10
is not available anymore. Previous state was:
partially failing
bap-ida.2.3.0
on
4.11
is not available anymore. Previous state was:
partially failing
bap-ida.2.3.0
on
4.12
is not available anymore. Previous state was:
partially failing
bap-knowledge.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-knowledge.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-knowledge.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-llvm.1.0.0
on
4.02
is not available anymore. Previous state was:
failing
bap-llvm.1.0.0
on
4.03
is not available anymore. Previous state was:
failing
bap-llvm.1.0.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-llvm.1.1.0
on
4.02
is not available anymore. Previous state was:
failing
bap-llvm.1.1.0
on
4.03
is not available anymore. Previous state was:
failing
bap-llvm.1.1.0
on
4.04
is not available anymore. Previous state was:
partially failing
bap-llvm.1.2.0
on
4.02
is not available anymore. Previous state was:
failing
bap-llvm.1.2.0
on
4.03
is not available anymore. Previous state was:
failing
bap-llvm.1.2.0
on
4.04
is not available anymore. Previous state was:
failing
bap-llvm.1.3.0
on
4.02
is not available anymore. Previous state was:
failing
bap-llvm.1.3.0
on
4.03
is not available anymore. Previous state was:
failing
bap-llvm.1.3.0
on
4.04
is not available anymore. Previous state was:
failing
bap-llvm.1.6.0
on
4.04
is not available anymore. Previous state was:
passing
bap-llvm.1.6.0
on
4.05
is not available anymore. Previous state was:
passing
bap-llvm.1.6.0
on
4.06
is not available anymore. Previous state was:
passing
bap-llvm.1.6.0
on
4.07
is not available anymore. Previous state was:
passing
bap-llvm.2.0.0
on
4.04
is not available anymore. Previous state was:
passing
bap-llvm.2.0.0
on
4.05
is not available anymore. Previous state was:
passing
bap-llvm.2.0.0
on
4.06
is not available anymore. Previous state was:
passing
bap-llvm.2.0.0
on
4.07
is not available anymore. Previous state was:
passing
bap-llvm.2.1.0
on
4.07
is not available anymore. Previous state was:
passing
bap-llvm.2.1.0
on
4.08
is not available anymore. Previous state was:
passing
bap-llvm.2.1.0
on
4.09
is not available anymore. Previous state was:
passing
bap-llvm.2.2.0
on
4.08
is not available anymore. Previous state was:
passing
bap-llvm.2.2.0
on
4.09
is not available anymore. Previous state was:
passing
bap-llvm.2.2.0
on
4.10
is not available anymore. Previous state was:
passing
bap-llvm.2.2.0
on
4.11
is not available anymore. Previous state was:
passing
bap-llvm.2.2.0
on
4.12
is not available anymore. Previous state was:
Home|Differences with the last checks|Previous runs Home|Differences with the last checks|Previous runs