Home
|
Differences with the last checks
|
Previous runs
Differences between
892f7bc
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
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
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:
passing
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
bimage-display.0.3.0
on
5.0
had its build status changed:
partially failing
to
failing
bimage-display.0.3.1
on
5.0
had its build status changed:
partially failing
to
failing
bimage-display.0.4.0
on
5.0
had its build status changed:
partially failing
to
failing
bimage-display.0.5.0
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
bitcoin.2.0
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
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
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
coq.8.13.1
on
4.07
had its build status changed:
passing
to
failing
cow.2.2.0
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
distributed.0.6.0
on
5.0
had its build status changed:
passing
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
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:
partially failing
to
failing
easy_logging_yojson.0.4
on
4.05
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.4
on
4.06
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.4
on
4.07
had its build status changed:
partially failing
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:
partially failing
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:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.06
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.07
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.08
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.09
had its build status changed:
partially failing
to
failing
easy_logging_yojson.0.5
on
4.10
had its build status changed:
partially failing
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:
partially failing
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:
partially failing
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:
partially failing
to
failing
easy_logging_yojson.0.5.2
on
4.10
had its build status changed:
partially failing
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
electrod.0.2.1
on
4.06
had its build status changed:
partially failing
to
failing
elpi.1.0.2
on
4.05
had its build status changed:
partially failing
to
failing
elpi.1.0.3
on
4.05
had its build status changed:
partially failing
to
failing
elpi.1.0.3
on
4.06
had its build status changed:
partially failing
to
failing
elpi.1.0.4
on
4.06
had its build status changed:
partially failing
to
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
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
frenetic.5.0.3
on
4.06
had its build status changed:
partially failing
to
failing
frenetic.5.0.3
on
4.07
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
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
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:
internal failure
to
failing
git.3.2.0
on
4.08
had its build status changed:
partially failing
to
failing
git.3.2.0
on
4.09
had its build status changed:
partially failing
to
failing
git.3.2.0
on
4.10
had its build status changed:
partially failing
to
failing
git.3.2.0
on
4.11
had its build status changed:
partially failing
to
failing
git.3.2.0
on
4.12
had its build status changed:
partially failing
to
failing
git.3.3.0
on
4.08
had its build status changed:
partially failing
to
failing
git.3.3.0
on
4.09
had its build status changed:
partially failing
to
failing
git.3.3.0
on
4.10
had its build status changed:
partially failing
to
failing
git.3.3.0
on
4.11
had its build status changed:
partially failing
to
failing
git.3.3.0
on
4.12
had its build status changed:
partially failing
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
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
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
hidapi.1.1
on
5.0
had its build status changed:
partially failing
to
failing
hidapi.1.1.1
on
5.0
had its build status changed:
partially failing
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
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
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
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
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.02
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
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
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
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
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:
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
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
mdx.1.7.0
on
4.10
had its build status changed:
internal failure
to
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
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-triangle.0.9.5
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
minicaml.0.2.2
on
4.02
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:
passing
to
failing
mirage-fs.0.4.0
on
5.0
had its build status changed:
passing
to
failing
mirage-fs.0.5.0
on
5.0
had its build status changed:
passing
to
failing
mm.0.8.0
on
5.0
is now installable. Current state is:
failing
morbig.0.9
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
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
netchannel.1.10.2
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.10.2
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.10.2
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.10.2
on
4.11
had its build status changed:
passing
to
failing
netchannel.1.11.0
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.11.0
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.11.0
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.11.0
on
4.11
had its build status changed:
passing
to
failing
netchannel.1.12.0
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.12.0
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.12.0
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.12.0
on
4.11
had its build status changed:
passing
to
failing
netchannel.1.13.0
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.13.0
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.13.0
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.13.0
on
4.11
had its build status changed:
passing
to
failing
netchannel.1.13.1
on
4.08
had its build status changed:
passing
to
failing
netchannel.1.13.1
on
4.09
had its build status changed:
passing
to
failing
netchannel.1.13.1
on
4.10
had its build status changed:
passing
to
failing
netchannel.1.13.1
on
4.11
had its build status changed:
passing
to
failing
netkat.0.1
on
4.07
had its build status changed:
internal failure
to
failing
noCanren.0.3.0
on
4.13
is now installable. Current state is:
failing
noCanren.0.3.0~alpha1
on
4.13
had its build status changed:
passing
to
failing
nproc.0.5.1
on
5.0
had its build status changed:
partially failing
to
failing
nuscr.1.0.0
on
4.04
had its build status changed:
partially failing
to
failing
nuscr.1.0.0
on
4.05
had its build status changed:
partially failing
to
failing
nuscr.1.0.0
on
4.07
had its build status changed:
partially failing
to
failing
nuscr.1.0.0
on
4.08
had its build status changed:
partially failing
to
failing
nuscr.1.0.0
on
4.09
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
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
oclaunch.0.3.0-pre1
on
4.02
had its build status changed:
partially failing
to
failing
oclaunch.0.3.0-pre1
on
4.03
had its build status changed:
partially failing
to
failing
oclaunch.0.3.0-pre1
on
4.04
had its build status changed:
partially failing
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
ocsigenserver.2.6
on
4.02
had its build status changed:
internal failure
to
failing
ocsigenserver.2.6
on
4.03
had its build status changed:
internal failure
to
failing
ocsigenserver.2.6
on
4.04
had its build status changed:
internal failure
to
failing
ocsigenserver.2.6
on
4.05
had its build status changed:
internal failure
to
failing
omake.0.10.5
on
5.0
is now installable. Current state is:
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
orun.0.0.1
on
4.07
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
5.0
had its build status changed:
partially failing
to
failing
ott.0.32
on
5.0
is now installable. Current state is:
failing
override.0.4.0
on
4.14
had its build status changed:
partially failing
to
failing
petr4.0.1
on
4.06
had its build status changed:
partially failing
to
failing
petr4.0.1
on
4.08
had its build status changed:
partially failing
to
failing
petr4.0.1.1
on
4.05
had its build status changed:
partially failing
to
failing
petr4.0.1.1
on
4.08
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
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
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
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
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
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
rpclib.6.0.0
on
4.08
had its build status changed:
passing
to
failing
rpclib.6.0.0
on
4.09
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
scid.1.0
on
5.0
had its build status changed:
partially failing
to
failing
session-postgresql-async.0.4.1
on
4.03
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
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
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
stdlib-diff.0.1.3
on
5.0
had its build status changed:
not available
to
failing
stog_server.0.20.0
on
4.12
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
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
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
uri.2.0.0
on
4.10
had its build status changed:
passing
to
failing
usbmux.0.3
on
4.02
had its build status changed:
partially failing
to
failing
usbmux.0.5
on
4.02
had its build status changed:
partially failing
to
failing
usbmux.0.7
on
4.02
had its build status changed:
partially failing
to
failing
usbmux.0.8
on
4.02
had its build status changed:
partially failing
to
failing
usbmux.1.0
on
4.02
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
websocket.2.3
on
4.05
had its build status changed:
partially failing
to
failing
why3.1.5.0
on
5.0
is now installable. Current state is:
failing
xe.0.6.3
on
4.05
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
zarith.1.3
on
5.0
had its build status changed:
passing
to
failing
zxcvbn.2.3+2
on
4.07
had its build status changed:
partially failing
to
failing
zxcvbn.2.3+2
on
4.09
had its build status changed:
partially failing
to
failing
zxcvbn.2.3+2
on
4.10
had its build status changed:
partially failing
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.04
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
aws-s3.0.9.0
on
4.04
had its build status changed:
internal failure
to
partially failing
aws-s3.1.1.0
on
4.03
had its build status changed:
internal failure
to
partially failing
aws-s3.1.1.0
on
4.05
had its build status changed:
internal failure
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
bitcoin.1.0
on
4.02
had its build status changed:
internal failure
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.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:
passing
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.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
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
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.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.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.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.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.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.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.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.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:
internal failure
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:
internal failure
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
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
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.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.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
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
had its build status changed:
internal failure
to
partially failing
ocsigen-start.4.6.0
on
4.09
had its build status changed:
internal failure
to
partially failing
ocsigen-start.4.6.0
on
4.10
had its build status changed:
internal failure
to
partially failing
ocsigen-start.4.6.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.4.6.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigen-start.4.6.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigen-start.4.6.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigen-start.4.7.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.4.7.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.4.7.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.4.7.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.4.7.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigen-start.4.7.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigen-start.4.7.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigen-start.5.0.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.5.0.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.5.0.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.5.0.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.5.0.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigen-start.5.0.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigen-start.5.0.0
on
4.14
had its build status changed:
passing
to
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
ocsigenserver.2.4.0
on
4.02
had its build status changed:
internal failure
to
partially failing
ocsigenserver.2.4.0
on
4.03
had its build status changed:
internal failure
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
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
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.2
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
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
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:
passing
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.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
SZXX.2.1.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
albatross.1.4.2
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:
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.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-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-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-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-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-main.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-main.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-main.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-mc.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-mc.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-mc.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-microx.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-microx.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-microx.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-mips.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-mips.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-mips.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-objdump.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-objdump.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-objdump.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-optimization.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-optimization.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-optimization.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-patterns.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-phoenix.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-phoenix.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-phoenix.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-piqi.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-piqi.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-piqi.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-plugins.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-plugins.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-plugins.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-powerpc.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-powerpc.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-powerpc.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-dictionary.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-dictionary.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-dictionary.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-exploring-scheduler.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-exploring-scheduler.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-exploring-scheduler.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-greedy-scheduler.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-greedy-scheduler.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-greedy-scheduler.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-limit.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-limit.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-limit.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-lisp.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-lisp.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-lisp.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-loader.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-loader.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-loader.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-mark-visited.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-mark-visited.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-mark-visited.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-powerpc.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-powerpc.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-powerpc.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-print.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-print.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-print.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-promiscuous.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-promiscuous.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-promiscuous.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-propagate-taint.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-propagate-taint.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-propagate-taint.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-random.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-random.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-random.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-region.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-region.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-region.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-round-robin-scheduler.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-round-robin-scheduler.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-round-robin-scheduler.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-support.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-support.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-support.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-symbolic-executor.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-symbolic-executor.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-symbolic-executor.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-systems.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-systems.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-systems.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-taint.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-taint.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-taint.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-test.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-test.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-test.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-track-visited.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-track-visited.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-track-visited.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-wandering-scheduler.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-wandering-scheduler.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus-wandering-scheduler.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-primus.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-print.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-print.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-print.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-radare2.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-radare2.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-radare2.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-raw.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-raw.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-raw.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-recipe-command.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-recipe-command.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-recipe-command.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-recipe.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-recipe.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-recipe.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-relation.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-relation.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-relation.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-report.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-report.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-report.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-riscv.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-riscv.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-run.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-run.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-run.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-specification.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-specification.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-specification.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-ssa.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-ssa.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-ssa.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-std.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-std.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-std.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-strings.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-strings.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-strings.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-stub-resolver.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-stub-resolver.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-stub-resolver.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-symbol-reader.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-symbol-reader.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-symbol-reader.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-systemz.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-systemz.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-systemz.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-taint-propagator.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-taint-propagator.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-taint-propagator.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-taint.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-taint.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-taint.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-term-mapper.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-term-mapper.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-term-mapper.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-thumb.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-thumb.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-thumb.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-toplevel.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-trace.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-trace.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-trace.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-traces.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-traces.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-traces.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-trivial-condition-form.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-trivial-condition-form.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-trivial-condition-form.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-warn-unused.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-warn-unused.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bap-warn-unused.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bare.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bare.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bare.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
base-nnp.base
on
4.14
had its build status changed:
passing
to
not available
base.v0.14.2
on
5.0
had its build status changed:
partially failing
to
not available
base.v0.14.3
on
5.0
had its build status changed:
partially failing
to
not available
base_bigstring.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
base_quickcheck.v0.14.1
on
5.0
had its build status changed:
partially failing
to
not available
bastet_async.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
bechamel-js.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
bechamel-js.0.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bechamel-notty.0.1.0
on
4.14
had its build status changed:
partially failing
to
not available
bechamel-notty.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
bechamel-notty.0.2.0
on
4.14
had its build status changed:
partially failing
to
not available
bechamel-notty.0.2.0
on
5.0
had its build status changed:
partially failing
to
not available
benchpress-server.0.1
on
5.0
had its build status changed:
partially failing
to
not available
benchpress.0.1
on
5.0
had its build status changed:
partially failing
to
not available
bignum.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
bimap.20201231
on
5.0
had its build status changed:
partially failing
to
not available
bin_prot.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
binaryen_dsl.0.7
on
5.0
had its build status changed:
partially failing
to
not available
biniou.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
bio_io.0.1.1
on
5.0
had its build status changed:
partially failing
to
not available
bio_io.0.1.2
on
5.0
had its build status changed:
partially failing
to
not available
bio_io.0.2.1
on
5.0
had its build status changed:
partially failing
to
not available
bio_io.0.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bio_io.0.4.0
on
5.0
had its build status changed:
partially failing
to
not available
biocaml.0.11.0
on
5.0
had its build status changed:
partially failing
to
not available
biocaml.0.11.1
on
5.0
had its build status changed:
partially failing
to
not available
bistro.0.6.0
on
5.0
had its build status changed:
partially failing
to
not available
bitvec-binprot.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bitvec-binprot.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bitvec-binprot.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
bitvec-order.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
bitvec-order.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bitvec-order.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
blake2.0.3
on
5.0
had its build status changed:
passing
to
not available
bos.0.1.0
on
5.0
had its build status changed:
failing
to
not available
bos.0.1.1
on
5.0
had its build status changed:
failing
to
not available
bos.0.1.2
on
5.0
had its build status changed:
failing
to
not available
bos.0.1.3
on
5.0
had its build status changed:
failing
to
not available
bos.0.1.4
on
5.0
had its build status changed:
failing
to
not available
bos.0.1.5
on
5.0
had its build status changed:
failing
to
not available
bos.0.1.6
on
5.0
had its build status changed:
failing
to
not available
bos.0.2.0
on
5.0
had its build status changed:
failing
to
not available
builder.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
builder.0.1.1
on
5.0
had its build status changed:
partially failing
to
not available
builder.0.1.2
on
5.0
had its build status changed:
partially failing
to
not available
builder.0.2.0
on
5.0
had its build status changed:
partially failing
to
not available
builder.0.3.0
on
5.0
had its build status changed:
partially failing
to
not available
bytearray.1.0.1
on
4.14
had its build status changed:
failing
to
not available
bytearray.1.0.1
on
5.0
had its build status changed:
failing
to
not available
bytearray.1.0.2
on
4.14
had its build status changed:
failing
to
not available
bytearray.1.0.2
on
5.0
had its build status changed:
failing
to
not available
bytebuffer.0.0.2
on
5.0
had its build status changed:
partially failing
to
not available
cactus.1.0.0
on
5.0
had its build status changed:
passing
to
not available
caldav.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
caldav.0.1.1
on
5.0
had its build status changed:
partially failing
to
not available
camels.0.0.3
on
4.14
had its build status changed:
partially failing
to
not available
camels.0.0.3
on
5.0
had its build status changed:
partially failing
to
not available
camels.0.0.4
on
4.14
had its build status changed:
partially failing
to
not available
camels.0.0.4
on
5.0
had its build status changed:
partially failing
to
not available
camelsnakekebab.0.4
on
5.0
had its build status changed:
partially failing
to
not available
camlimages.5.0.3
on
5.0
had its build status changed:
partially failing
to
not available
camlimages.5.0.4
on
5.0
had its build status changed:
partially failing
to
not available
camlix.0.1
on
5.0
had its build status changed:
partially failing
to
not available
camlon.3.0.0
on
5.0
had its build status changed:
failing
to
not available
camlp-streams.5.0
on
4.02
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.03
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.04
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.05
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.06
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.07
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.08
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.09
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.10
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.11
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.12
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.13
had its build status changed:
passing
to
not available
camlp-streams.5.0
on
4.14
had its build status changed:
passing
to
not available
camyll.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
canary.0.0.1
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.5.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.5.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.6.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.6.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.7.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.7.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.8.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.8.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.9.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.0.9.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.1.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.1.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.1.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.1.1
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.1.2
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.1.2
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.1.2.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-lwt.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.0.7.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.0.7.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.0.8.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.0.8.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.0.9.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.0.9.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.1.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.1.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.1.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.1.1
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.1.2
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.1.2
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.1.2.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-mirage.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-net.0.7.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-net.0.7.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-net.0.8.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-net.0.8.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-net.0.9.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-net.0.9.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-net.1.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-net.1.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-net.1.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-net.1.1
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-net.1.2
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-net.1.2
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-net.1.2.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-net.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-net.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.0.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.0.7.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.0.7.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.0.8.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.0.8.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.0.9.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.0.9.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.1.0
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.1.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.1.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.1.1
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.1.2
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.1.2
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.1.2.1
on
4.14
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc-unix.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc.0.1
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.2
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.3
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.3.1
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.3.2
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.3.2
on
5.0
had its build status changed:
partially failing
to
not available
capnp-rpc.0.3.3
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.3.3
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.0.4.0
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.4.0
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.0.5.0
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.5.0
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.0.6.0
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.6.0
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.0.7.0
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.7.0
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.0.8.0
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.8.0
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.0.9.0
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.0.9.0
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.1.0
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.1.0
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.1.1
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.1.1
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.1.2
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.1.2
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.1.2.1
on
4.14
had its build status changed:
failing
to
not available
capnp-rpc.1.2.1
on
5.0
had its build status changed:
failing
to
not available
capnp-rpc.1.2.2
on
5.0
had its build status changed:
passing
to
not available
capnp.3.3.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp.3.4.0
on
5.0
had its build status changed:
partially failing
to
not available
capnp.3.5.0
on
5.0
had its build status changed:
partially failing
to
not available
caqti-async.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
caqti-async.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
caqti-async.1.6.0
on
5.0
had its build status changed:
partially failing
to
not available
caqti-async.1.7.0
on
5.0
had its build status changed:
partially failing
to
not available
certify.0.2
on
5.0
had its build status changed:
partially failing
to
not available
certify.0.3.0
on
5.0
had its build status changed:
partially failing
to
not available
certify.0.3.1
on
5.0
had its build status changed:
partially failing
to
not available
certify.0.3.2
on
5.0
had its build status changed:
partially failing
to
not available
cfstream.1.3.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client-lwt.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client-lwt.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client-lwt.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client-mirage.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client-mirage.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client-mirage.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client.1.1.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client.1.4.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua-client.1.5.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-server.1.1.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-server.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-server.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua-server.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
charrua-server.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-server.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-server.1.4.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua-server.1.5.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-unix.1.1.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-unix.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-unix.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua-unix.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
charrua-unix.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-unix.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua-unix.1.4.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua-unix.1.5.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua.1.1.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua.1.2.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
charrua.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
charrua.1.4.1
on
5.0
had its build status changed:
partially failing
to
not available
charrua.1.5.0
on
5.0
had its build status changed:
partially failing
to
not available
cinaps.v0.10.0
on
4.14
had its build status changed:
failing
to
not available
cinaps.v0.11.0
on
4.14
had its build status changed:
failing
to
not available
cinaps.v0.12.0
on
4.14
had its build status changed:
failing
to
not available
cinaps.v0.12.0
on
5.0
had its build status changed:
failing
to
not available
cinaps.v0.12.1
on
4.14
had its build status changed:
failing
to
not available
cinaps.v0.12.1
on
5.0
had its build status changed:
failing
to
not available
cinaps.v0.13.0
on
4.14
had its build status changed:
failing
to
not available
cinaps.v0.13.0
on
5.0
had its build status changed:
failing
to
not available
clap.0.1.0
on
5.0
had its build status changed:
passing
to
not available
clz.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
cmdliner.0.9.4
on
5.0
had its build status changed:
failing
to
not available
cmdliner.1.0.3
on
5.0
had its build status changed:
failing
to
not available
cohttp-async.2.5.4
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-async.2.5.5
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-async.2.5.6
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-async.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-async.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.1.3
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.5.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.5.1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.5.2-1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.5.4
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.5.5
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.2.5.6
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt-unix.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.1.3
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.5.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.5.1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.5.2-1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.5.4
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.5.5
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.2.5.6
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-lwt.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.2.5.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.2.5.1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.2.5.2
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.2.5.2-1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.2.5.3
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.2.5.4
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.2.5.5
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.2.5.6
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-mirage.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.1.1.1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.1.3
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.5.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.5.1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.5.2-1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.5.4
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.5.5
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.2.5.6
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp-top.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.1.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.1.2
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.1.3
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.4.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.5.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.5.1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.5.2-1
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.5.4
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.5.5
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.2.5.6
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cohttp.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
colombe.0.1.0
on
5.0
had its build status changed:
partially failing
to
not available
combinat.1.0
on
5.0
had its build status changed:
partially failing
to
not available
comby-kernel.1.4.1
on
5.0
had its build status changed:
partially failing
to
not available
comby-kernel.1.7.0
on
5.0
had its build status changed:
partially failing
to
not available
comby-semantic.1.7.0
on
5.0
had its build status changed:
partially failing
to
not available
comby.1.2.2
on
5.0
had its build status changed:
partially failing
to
not available
comby.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
comby.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
comby.1.4.1
on
5.0
had its build status changed:
partially failing
to
not available
comby.1.7.0
on
5.0
had its build status changed:
partially failing
to
not available
command_rpc.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.1.5.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.2.0.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.2.0.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.2.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.4.0.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.4.0.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-async.5.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.1.5.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.2.0.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.2.0.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.2.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.2.2.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.4.0.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.4.0.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt-unix.5.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.1.5.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.2.0.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.2.0.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.2.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.4.0.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.4.0.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-lwt.5.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-mirage.2.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-mirage.2.2.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit-mirage.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-mirage.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-mirage.4.0.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit-mirage.4.0.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit-mirage.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit-mirage.5.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit.1.3.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit.1.4.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit.1.5.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit.2.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit.2.0.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit.2.0.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit.2.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit.2.3.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit.4.0.1
on
5.0
had its build status changed:
partially failing
to
not available
conduit.4.0.2
on
5.0
had its build status changed:
partially failing
to
not available
conduit.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
conduit.5.1.0
on
5.0
had its build status changed:
partially failing
to
not available
conex-nocrypto.0.10.0
on
5.0
had its build status changed:
partially failing
to
not available
conex-nocrypto.0.10.1
on
5.0
had its build status changed:
partially failing
to
not available
conex-nocrypto.0.11.0
on
5.0
had its build status changed:
partially failing
to
not available
conex.0.9.2
on
5.0
had its build status changed:
partially failing
to
not available
cookies.1.0.0
on
5.0
had its build status changed:
partially failing
to
not available
core-and-more.0.0.1
on
5.0
had its build status changed:
partially failing
to
not available
core.v0.14.1
on
5.0
had its build status changed:
partially failing
to
not available
core_bench.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
core_extended.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
core_kernel.v0.14.1
on
5.0
had its build status changed:
partially failing
to
not available
core_kernel.v0.14.2
on
5.0
had its build status changed:
partially failing
to
not available
core_profiler.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
core_unix.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
cppffigen.0.002
on
5.0
had its build status changed:
partially failing
to
not available
crc.2.1.0
on
5.0
had its build status changed:
partially failing
to
not available
cryptokit.1.11
on
5.0
had its build status changed:
failing
to
not available
cryptokit.1.12
on
5.0
had its build status changed:
failing
to
not available
cryptokit.1.13
on
5.0
had its build status changed:
failing
to
not available
cryptokit.1.14
on
5.0
had its build status changed:
failing
to
not available
css-parser.0.2.2
on
5.0
had its build status changed:
partially failing
to
not available
css-parser.0.2.3
on
5.0
had its build status changed:
partially failing
to
not available
css-parser.0.2.4
on
5.0
had its build status changed:
partially failing
to
not available
css-parser.0.2.5
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.3.3.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.3.4.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.3.5.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.3.6.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.3.7.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.5.1.1
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.5.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.6.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-async.6.0.1
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-lwt.3.3.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-sexp.4.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-sexp.5.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-sexp.5.1.1
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-sexp.5.2.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-sexp.6.0.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct-sexp.6.0.1
on
5.0
had its build status changed:
partially failing
to
not available
cstruct.3.3.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct.3.4.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct.3.5.0
on
5.0
had its build status changed:
partially failing
to
not available
cstruct.3.7.0
on
5.0
had its build status changed:
partially failing
to
not available
csvfields.v0.14.0
on
5.0
had its build status changed:
partially failing
to
not available
current_examples.0.2
on
4.14
had its build status changed:
partially failing
to
not available
current_examples.0.2
on
5.0
had its build status changed:
partially failing
to
not available
current_examples.0.3
on
4.14
had its build status changed:
partially failing
to
not available
current_examples.0.3
on
5.0
had its build status changed:
partially failing
to
not available
current_examples.0.4
on
4.14
had its build status changed:
partially failing
to
not available
current_examples.0.4
on
5.0
had its build status changed:
partially failing
to
not available
current_examples.0.5
on
5.0
had its build status changed:
partially failing
to
not available
current_github.0.2
on
5.0
had its build status changed:
partially failing
to
not available
current_github.0.3
on
5.0
had its build status changed:
partially failing
to
not available
current_github.0.4
on
5.0
had its build status changed:
partially failing
to
not available
current_github.0.5
on
5.0
had its build status changed:
partially failing
to
not available
current_ocluster.0.1
on
5.0
had its build status changed:
partially failing
to
not available
current_rpc.0.1
on
5.0
had its build status changed:
partially failing
to
not available
current_rpc.0.2
on
5.0
had its build status changed:
partially failing
to
not available
current_rpc.0.3
on
5.0
had its build status changed:
partially failing
to
not available
current_rpc.0.4
on
5.0
had its build status changed:
partially failing
to
not available
current_rpc.0.5
on
5.0
had its build status changed:
partially failing
to
not available
current_slack.0.1
on
5.0
had its build status changed:
partially failing
to
not available
current_slack.0.2
on
5.0
had its build status changed:
partially failing
to
not available
current_slack.0.3
on
5.0
had its build status changed:
partially failing
to
not available
current_slack.0.4
on
5.0
had its build status changed:
partially failing
to
not available
current_slack.0.5
on
5.0
had its build status changed:
partially failing
to
not available
current_web.0.1
on
5.0
had its build status changed:
partially failing
to
not available
current_web.0.2
on
5.0
had its build status changed:
partially failing
to
not available
current_web.0.3
on
5.0
had its build status changed:
partially failing
to
not available
current_web.0.4
on
5.0
had its build status changed:
partially failing
to
not available
current_web.0.5
on
5.0
had its build status changed:
partially failing
to
not available
dap.1.0.0
on
5.0
had its build status changed:
partially failing
to
not available
dap.1.0.1
on
5.0
had its build status changed:
partially failing
to
Home|Differences with the last checks|Previous runs Home|Differences with the last checks|Previous runs