Home
|
Differences with the last checks
|
Previous runs
Differences between
1d9d333
and
2dcd868
(
git diff
)
Packages now
failing
:
alt-ergo-free.2.0.0
on
4.08
had its build status changed:
passing
to
failing
alt-ergo-free.2.0.0
on
4.09
had its build status changed:
passing
to
failing
alt-ergo-free.2.0.0
on
4.12
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.0
on
4.08
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.0
on
4.09
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.0
on
4.10
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.0
on
4.11
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.0
on
4.12
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.0
on
4.13
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.0
on
4.14
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.1
on
4.08
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.1
on
4.09
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.1
on
4.10
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.1
on
4.11
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.1
on
4.12
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.1
on
4.13
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.1
on
4.14
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.2
on
4.08
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.2
on
4.09
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.2
on
4.10
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.2
on
4.11
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.2
on
4.12
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.2
on
4.13
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.2
on
4.14
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.3
on
4.08
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.3
on
4.09
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.3
on
4.10
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.3
on
4.11
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.3
on
4.12
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.3
on
4.13
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.3.3
on
4.14
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.0
on
4.08
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.0
on
4.09
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.0
on
4.10
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.0
on
4.11
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.0
on
4.12
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.0
on
4.13
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.0
on
4.14
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.1
on
4.08
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.1
on
4.09
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.1
on
4.10
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.1
on
4.11
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.1
on
4.12
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.1
on
4.13
had its build status changed:
passing
to
failing
alt-ergo-parsers.2.4.1
on
4.14
had its build status changed:
passing
to
failing
alt-ergo.2.0.0
on
4.09
had its build status changed:
passing
to
failing
alt-ergo.2.0.0
on
4.12
had its build status changed:
passing
to
failing
balancer.1.0
on
4.08
had its build status changed:
passing
to
failing
balancer.1.0
on
4.09
had its build status changed:
passing
to
failing
balancer.1.0
on
4.10
had its build status changed:
passing
to
failing
balancer.1.0
on
4.11
had its build status changed:
passing
to
failing
balancer.1.0
on
4.12
had its build status changed:
passing
to
failing
balancer.1.0
on
4.13
had its build status changed:
passing
to
failing
balancer.1.0
on
4.14
had its build status changed:
passing
to
failing
bap-frames.2.1.0
on
4.08
had its build status changed:
internal failure
to
failing
bap-ghidra.2.5.0
on
4.13
had its build status changed:
internal failure
to
failing
bap-ghidra.2.5.0
on
4.14
had its build status changed:
internal failure
to
failing
beluga.1.0
on
4.08
had its build status changed:
passing
to
failing
beluga.1.0
on
4.09
had its build status changed:
passing
to
failing
beluga.1.0
on
4.10
had its build status changed:
passing
to
failing
beluga.1.0
on
4.11
had its build status changed:
passing
to
failing
beluga.1.0
on
4.12
had its build status changed:
passing
to
failing
beluga.1.0
on
4.13
had its build status changed:
passing
to
failing
beluga.1.0
on
4.14
had its build status changed:
passing
to
failing
beluga.1.1
on
4.14
had its build status changed:
passing
to
failing
beluga.1.1
on
5.0
had its build status changed:
passing
to
failing
beluga.1.1
on
5.1
had its build status changed:
passing
to
failing
beluga.1.1.1
on
4.14
is now installable. Current state is:
failing
beluga.1.1.1
on
5.0
is now installable. Current state is:
failing
beluga.1.1.1
on
5.1
is now installable. Current state is:
failing
bitwuzla.1.0.0
on
4.08
had its build status changed:
passing
to
failing
bitwuzla.1.0.0
on
4.09
had its build status changed:
passing
to
failing
bitwuzla.1.0.0
on
4.10
had its build status changed:
passing
to
failing
bitwuzla.1.0.0
on
4.11
had its build status changed:
passing
to
failing
bitwuzla.1.0.0
on
4.12
had its build status changed:
passing
to
failing
bitwuzla.1.0.0
on
4.13
had its build status changed:
passing
to
failing
bitwuzla.1.0.0
on
4.14
had its build status changed:
passing
to
failing
bitwuzla.1.0.0
on
5.0
had its build status changed:
passing
to
failing
bitwuzla.1.0.0
on
5.1
had its build status changed:
passing
to
failing
bitwuzla.1.0.1
on
4.08
had its build status changed:
passing
to
failing
bitwuzla.1.0.1
on
4.09
had its build status changed:
passing
to
failing
bitwuzla.1.0.1
on
4.10
had its build status changed:
passing
to
failing
bitwuzla.1.0.1
on
4.11
had its build status changed:
passing
to
failing
bitwuzla.1.0.1
on
4.12
had its build status changed:
passing
to
failing
bitwuzla.1.0.1
on
4.13
had its build status changed:
passing
to
failing
bitwuzla.1.0.1
on
4.14
had its build status changed:
passing
to
failing
bitwuzla.1.0.1
on
5.0
had its build status changed:
passing
to
failing
bitwuzla.1.0.1
on
5.1
had its build status changed:
passing
to
failing
boltzgen.0.9
on
5.0
had its build status changed:
passing
to
failing
boltzgen.0.9
on
5.1
had its build status changed:
passing
to
failing
boltzgen.0.9.2
on
5.0
had its build status changed:
passing
to
failing
boltzgen.0.9.2
on
5.1
had its build status changed:
passing
to
failing
boltzgen.0.9.3
on
5.0
had its build status changed:
passing
to
failing
boltzgen.0.9.3
on
5.1
had its build status changed:
passing
to
failing
camlp4.4.08+1
on
4.08
had its build status changed:
passing
to
failing
camlp4.4.09+1
on
4.09
had its build status changed:
passing
to
failing
camlp4.4.10+1
on
4.10
had its build status changed:
passing
to
failing
camlp4.4.11+1
on
4.11
had its build status changed:
passing
to
failing
camlp4.4.12+1
on
4.12
had its build status changed:
passing
to
failing
camlp4.4.13+1
on
4.13
had its build status changed:
passing
to
failing
camlp4.4.14+1
on
4.14
had its build status changed:
passing
to
failing
camlp4.5.0
on
5.0
is now installable. Current state is:
failing
conex-mirage-crypto.0.11.1
on
4.08
had its build status changed:
passing
to
failing
conex-mirage-crypto.0.11.1
on
4.09
had its build status changed:
passing
to
failing
conex-mirage-crypto.0.11.1
on
4.10
had its build status changed:
passing
to
failing
conex-mirage-crypto.0.11.1
on
4.11
had its build status changed:
passing
to
failing
conex-mirage-crypto.0.11.1
on
4.12
had its build status changed:
passing
to
failing
conex-mirage-crypto.0.11.1
on
4.13
had its build status changed:
passing
to
failing
conex-mirage-crypto.0.11.1
on
4.14
had its build status changed:
passing
to
failing
conex-mirage-crypto.0.11.1
on
5.0
had its build status changed:
passing
to
failing
conex-mirage-crypto.0.11.1
on
5.1
had its build status changed:
passing
to
failing
conf-libclang.15
on
4.08
had its build status changed:
passing
to
failing
conf-libclang.15
on
4.09
had its build status changed:
passing
to
failing
conf-libclang.15
on
4.10
had its build status changed:
passing
to
failing
conf-libclang.15
on
4.11
had its build status changed:
passing
to
failing
conf-libclang.15
on
4.12
had its build status changed:
passing
to
failing
conf-libclang.15
on
4.13
had its build status changed:
passing
to
failing
conf-libclang.15
on
4.14
had its build status changed:
passing
to
failing
conf-libclang.15
on
5.0
had its build status changed:
passing
to
failing
conf-libclang.15
on
5.1
had its build status changed:
passing
to
failing
cppffigen.0.002
on
4.12
had its build status changed:
passing
to
failing
cppffigen.0.002
on
4.13
had its build status changed:
passing
to
failing
cppffigen.0.002
on
4.14
had its build status changed:
passing
to
failing
cppffigen.0.002
on
5.0
had its build status changed:
passing
to
failing
cppffigen.0.002
on
5.1
had its build status changed:
passing
to
failing
dedukti.2.6.0
on
4.08
had its build status changed:
passing
to
failing
dedukti.2.6.0
on
4.09
had its build status changed:
passing
to
failing
dedukti.2.6.0
on
4.10
had its build status changed:
passing
to
failing
dedukti.2.6.0
on
4.11
had its build status changed:
passing
to
failing
dedukti.2.6.0
on
4.12
had its build status changed:
passing
to
failing
dedukti.2.6.0
on
4.13
had its build status changed:
passing
to
failing
dedukti.2.6.0
on
4.14
had its build status changed:
passing
to
failing
dedukti.2.6.0
on
5.0
had its build status changed:
passing
to
failing
dedukti.2.6.0
on
5.1
had its build status changed:
passing
to
failing
eliom.8.4.8
on
4.08
had its build status changed:
passing
to
failing
eliom.8.4.8
on
4.09
had its build status changed:
passing
to
failing
eliom.8.4.8
on
4.10
had its build status changed:
passing
to
failing
eliom.8.4.8
on
4.11
had its build status changed:
passing
to
failing
eliom.8.4.8
on
4.12
had its build status changed:
passing
to
failing
eliom.8.6.0
on
4.08
had its build status changed:
passing
to
failing
eliom.8.6.0
on
4.09
had its build status changed:
passing
to
failing
eliom.8.6.0
on
4.10
had its build status changed:
passing
to
failing
eliom.8.6.0
on
4.11
had its build status changed:
passing
to
failing
eliom.8.6.0
on
4.12
had its build status changed:
passing
to
failing
eliom.8.8.0
on
4.08
had its build status changed:
passing
to
failing
eliom.8.8.0
on
4.09
had its build status changed:
passing
to
failing
eliom.8.8.0
on
4.10
had its build status changed:
passing
to
failing
eliom.8.8.0
on
4.11
had its build status changed:
passing
to
failing
eliom.8.8.0
on
4.12
had its build status changed:
passing
to
failing
eliom.8.8.1
on
4.08
had its build status changed:
passing
to
failing
eliom.8.8.1
on
4.09
had its build status changed:
passing
to
failing
eliom.8.8.1
on
4.10
had its build status changed:
passing
to
failing
eliom.8.8.1
on
4.11
had its build status changed:
passing
to
failing
eliom.8.8.1
on
4.12
had its build status changed:
passing
to
failing
frenetic.5.0.5
on
4.11
had its build status changed:
passing
to
failing
frenetic.5.0.5
on
4.12
had its build status changed:
passing
to
failing
frenetic.5.0.5
on
4.13
had its build status changed:
passing
to
failing
frenetic.5.0.5
on
4.14
had its build status changed:
passing
to
failing
gpx.1.0
on
4.08
had its build status changed:
passing
to
failing
gpx.1.0
on
4.09
had its build status changed:
passing
to
failing
gpx.1.0
on
4.10
had its build status changed:
passing
to
failing
gpx.1.0
on
4.11
had its build status changed:
passing
to
failing
gpx.1.0
on
4.12
had its build status changed:
passing
to
failing
gpx.1.0
on
4.13
had its build status changed:
passing
to
failing
gpx.1.0
on
4.14
had its build status changed:
passing
to
failing
gpx.1.0
on
5.0
had its build status changed:
passing
to
failing
gpx.1.0
on
5.1
had its build status changed:
passing
to
failing
gpx.1.0.1
on
4.08
had its build status changed:
passing
to
failing
gpx.1.0.1
on
4.09
had its build status changed:
passing
to
failing
gpx.1.0.1
on
4.10
had its build status changed:
passing
to
failing
gpx.1.0.1
on
4.11
had its build status changed:
passing
to
failing
gpx.1.0.1
on
4.12
had its build status changed:
passing
to
failing
gpx.1.0.1
on
4.13
had its build status changed:
passing
to
failing
gpx.1.0.1
on
4.14
had its build status changed:
passing
to
failing
gpx.1.0.1
on
5.0
had its build status changed:
passing
to
failing
gpx.1.0.1
on
5.1
had its build status changed:
passing
to
failing
gpx.1.0.2
on
4.08
had its build status changed:
passing
to
failing
gpx.1.0.2
on
4.09
had its build status changed:
passing
to
failing
gpx.1.0.2
on
4.10
had its build status changed:
passing
to
failing
gpx.1.0.2
on
4.11
had its build status changed:
passing
to
failing
gpx.1.0.2
on
4.12
had its build status changed:
passing
to
failing
gpx.1.0.2
on
4.13
had its build status changed:
passing
to
failing
gpx.1.0.2
on
4.14
had its build status changed:
passing
to
failing
gpx.1.0.2
on
5.0
had its build status changed:
passing
to
failing
gpx.1.0.2
on
5.1
had its build status changed:
passing
to
failing
gpx.1.1.0
on
4.08
had its build status changed:
passing
to
failing
gpx.1.1.0
on
4.09
had its build status changed:
passing
to
failing
gpx.1.1.0
on
4.10
had its build status changed:
passing
to
failing
gpx.1.1.0
on
4.11
had its build status changed:
passing
to
failing
gpx.1.1.0
on
4.12
had its build status changed:
passing
to
failing
gpx.1.1.0
on
4.13
had its build status changed:
passing
to
failing
gpx.1.1.0
on
4.14
had its build status changed:
passing
to
failing
gpx.1.1.0
on
5.0
had its build status changed:
passing
to
failing
gpx.1.1.0
on
5.1
had its build status changed:
passing
to
failing
gpx.1.1.1
on
4.08
had its build status changed:
passing
to
failing
gpx.1.1.1
on
4.09
had its build status changed:
passing
to
failing
gpx.1.1.1
on
4.10
had its build status changed:
passing
to
failing
gpx.1.1.1
on
4.11
had its build status changed:
passing
to
failing
gpx.1.1.1
on
4.12
had its build status changed:
passing
to
failing
gpx.1.1.1
on
4.13
had its build status changed:
passing
to
failing
gpx.1.1.1
on
4.14
had its build status changed:
passing
to
failing
gpx.1.1.1
on
5.0
had its build status changed:
passing
to
failing
gpx.1.1.1
on
5.1
had its build status changed:
passing
to
failing
hacl-star-raw.0.1
on
4.14
had its build status changed:
passing
to
failing
hacl-star-raw.0.1.1
on
4.08
had its build status changed:
passing
to
failing
hacl-star-raw.0.2.1
on
4.09
had its build status changed:
passing
to
failing
lambda.0.1.7
on
4.08
had its build status changed:
passing
to
failing
lambda.0.1.7
on
4.09
had its build status changed:
passing
to
failing
lambda.0.1.7
on
4.10
had its build status changed:
passing
to
failing
lambda.0.1.7
on
4.11
had its build status changed:
passing
to
failing
lambda.0.1.7
on
4.12
had its build status changed:
passing
to
failing
lambda.0.1.7
on
4.13
had its build status changed:
passing
to
failing
lambda.0.1.7
on
4.14
had its build status changed:
passing
to
failing
lambda.0.1.7
on
5.0
had its build status changed:
passing
to
failing
lambda.0.1.7
on
5.1
had its build status changed:
passing
to
failing
lbvs_consent.2.1.3
on
5.0
had its build status changed:
partially failing
to
failing
lbvs_consent.2.1.3
on
5.1
had its build status changed:
not available
to
failing
lbvs_consent.2.2.0
on
5.0
had its build status changed:
partially failing
to
failing
lbvs_consent.2.2.0
on
5.1
had its build status changed:
not available
to
failing
learn-ocaml.0.13.0
on
4.12
had its build status changed:
passing
to
failing
learn-ocaml.0.13.1
on
4.12
had its build status changed:
passing
to
failing
learn-ocaml.0.14.0
on
4.12
had its build status changed:
passing
to
failing
learn-ocaml.0.14.1
on
4.12
had its build status changed:
passing
to
failing
learn-ocaml.0.15.0
on
4.12
had its build status changed:
passing
to
failing
lem.2020-06-03
on
4.08
had its build status changed:
passing
to
failing
lem.2020-06-03
on
4.09
had its build status changed:
passing
to
failing
lem.2020-06-03
on
4.10
had its build status changed:
passing
to
failing
lem.2020-06-03
on
4.11
had its build status changed:
passing
to
failing
lem.2020-06-03
on
4.12
had its build status changed:
passing
to
failing
lem.2020-06-03
on
4.13
had its build status changed:
passing
to
failing
lem.2020-06-03
on
4.14
had its build status changed:
passing
to
failing
lem.2022-12-10
on
4.08
had its build status changed:
passing
to
failing
lem.2022-12-10
on
4.09
had its build status changed:
passing
to
failing
lem.2022-12-10
on
4.10
had its build status changed:
passing
to
failing
lem.2022-12-10
on
4.11
had its build status changed:
passing
to
failing
lem.2022-12-10
on
4.12
had its build status changed:
passing
to
failing
lem.2022-12-10
on
4.13
had its build status changed:
passing
to
failing
lem.2022-12-10
on
4.14
had its build status changed:
passing
to
failing
lem.2022-12-10
on
5.0
had its build status changed:
passing
to
failing
lem.2022-12-10
on
5.1
had its build status changed:
passing
to
failing
lustre-v6.6.101.7
on
4.08
had its build status changed:
passing
to
failing
lustre-v6.6.101.7
on
4.09
had its build status changed:
passing
to
failing
lustre-v6.6.101.7
on
4.10
had its build status changed:
passing
to
failing
lustre-v6.6.101.7
on
4.11
had its build status changed:
passing
to
failing
md2mld.0.5.1
on
4.08
had its build status changed:
passing
to
failing
md2mld.0.5.1
on
4.09
had its build status changed:
passing
to
failing
md2mld.0.5.1
on
4.10
had its build status changed:
passing
to
failing
md2mld.0.5.1
on
4.11
had its build status changed:
passing
to
failing
md2mld.0.5.1
on
4.12
had its build status changed:
passing
to
failing
md2mld.0.5.1
on
4.13
had its build status changed:
passing
to
failing
md2mld.0.5.1
on
4.14
had its build status changed:
passing
to
failing
md2mld.0.5.1
on
5.0
had its build status changed:
passing
to
failing
md2mld.0.5.1
on
5.1
had its build status changed:
passing
to
failing
md2mld.0.6
on
4.08
had its build status changed:
passing
to
failing
md2mld.0.6
on
4.09
had its build status changed:
passing
to
failing
md2mld.0.6
on
4.10
had its build status changed:
passing
to
failing
md2mld.0.6
on
4.11
had its build status changed:
passing
to
failing
md2mld.0.6
on
4.12
had its build status changed:
passing
to
failing
md2mld.0.6
on
4.13
had its build status changed:
passing
to
failing
md2mld.0.6
on
4.14
had its build status changed:
passing
to
failing
md2mld.0.6
on
5.0
had its build status changed:
passing
to
failing
md2mld.0.6
on
5.1
had its build status changed:
passing
to
failing
melange.1.0.0
on
5.0
had its build status changed:
passing
to
failing
melange.1.0.0
on
5.1
had its build status changed:
passing
to
failing
mirage-qubes.0.6
on
4.08
had its build status changed:
passing
to
failing
mirage-qubes.0.6
on
4.09
had its build status changed:
passing
to
failing
mirage-qubes.0.6
on
4.10
had its build status changed:
passing
to
failing
mirage-qubes.0.6
on
4.11
had its build status changed:
passing
to
failing
morsmall.0.2.0
on
4.08
had its build status changed:
passing
to
failing
morsmall.0.2.0
on
4.09
had its build status changed:
passing
to
failing
morsmall.0.2.0
on
4.10
had its build status changed:
passing
to
failing
morsmall.0.2.0
on
4.11
had its build status changed:
passing
to
failing
morsmall.0.2.0
on
4.12
had its build status changed:
passing
to
failing
morsmall.0.2.0
on
4.13
had its build status changed:
passing
to
failing
morsmall.0.2.0
on
4.14
had its build status changed:
passing
to
failing
morsmall.0.2.0
on
5.0
had its build status changed:
passing
to
failing
morsmall.0.2.0
on
5.1
had its build status changed:
passing
to
failing
mrmime.0.3.0
on
4.08
had its build status changed:
passing
to
failing
mrmime.0.3.0
on
4.09
had its build status changed:
passing
to
failing
mrmime.0.3.0
on
4.10
had its build status changed:
passing
to
failing
mrmime.0.3.0
on
4.11
had its build status changed:
passing
to
failing
mrmime.0.3.0
on
4.12
had its build status changed:
passing
to
failing
mrmime.0.3.0
on
4.13
had its build status changed:
passing
to
failing
mrmime.0.3.0
on
4.14
had its build status changed:
passing
to
failing
mrmime.0.3.0
on
5.0
had its build status changed:
passing
to
failing
mrmime.0.3.0
on
5.1
had its build status changed:
passing
to
failing
msat.0.5
on
4.08
had its build status changed:
passing
to
failing
msat.0.5
on
4.09
had its build status changed:
passing
to
failing
msat.0.5
on
4.10
had its build status changed:
passing
to
failing
msat.0.5
on
4.11
had its build status changed:
passing
to
failing
msat.0.5
on
4.12
had its build status changed:
passing
to
failing
msat.0.5
on
4.13
had its build status changed:
passing
to
failing
msat.0.5
on
4.14
had its build status changed:
passing
to
failing
msat.0.5.1
on
4.08
had its build status changed:
passing
to
failing
msat.0.5.1
on
4.09
had its build status changed:
passing
to
failing
msat.0.5.1
on
4.10
had its build status changed:
passing
to
failing
msat.0.5.1
on
4.11
had its build status changed:
passing
to
failing
msat.0.5.1
on
4.12
had its build status changed:
passing
to
failing
msat.0.5.1
on
4.13
had its build status changed:
passing
to
failing
msat.0.5.1
on
4.14
had its build status changed:
passing
to
failing
msat.0.6
on
4.08
had its build status changed:
passing
to
failing
msat.0.6
on
4.09
had its build status changed:
passing
to
failing
msat.0.6
on
4.10
had its build status changed:
passing
to
failing
msat.0.6
on
4.11
had its build status changed:
passing
to
failing
msat.0.6
on
4.12
had its build status changed:
passing
to
failing
msat.0.6
on
4.13
had its build status changed:
passing
to
failing
msat.0.6
on
4.14
had its build status changed:
passing
to
failing
mysql_protocol.3.0.1
on
4.09
had its build status changed:
passing
to
failing
mysql_protocol.3.0.1
on
4.10
had its build status changed:
passing
to
failing
mysql_protocol.3.0.1
on
4.11
had its build status changed:
passing
to
failing
mysql_protocol.3.0.1
on
4.12
had its build status changed:
passing
to
failing
mysql_protocol.3.0.1
on
4.13
had its build status changed:
passing
to
failing
mysql_protocol.3.0.1
on
4.14
had its build status changed:
passing
to
failing
mysql_protocol.3.0.1
on
5.0
had its build status changed:
passing
to
failing
mysql_protocol.3.0.1
on
5.1
had its build status changed:
passing
to
failing
mysql_protocol.3.0.2
on
4.09
had its build status changed:
passing
to
failing
mysql_protocol.3.0.2
on
4.10
had its build status changed:
passing
to
failing
mysql_protocol.3.0.2
on
4.11
had its build status changed:
passing
to
failing
mysql_protocol.3.0.2
on
4.12
had its build status changed:
passing
to
failing
mysql_protocol.3.0.2
on
4.13
had its build status changed:
passing
to
failing
mysql_protocol.3.0.2
on
4.14
had its build status changed:
passing
to
failing
mysql_protocol.3.0.2
on
5.0
had its build status changed:
passing
to
failing
mysql_protocol.3.0.2
on
5.1
had its build status changed:
passing
to
failing
mysql_protocol.3.0.3
on
4.09
had its build status changed:
passing
to
failing
mysql_protocol.3.0.3
on
4.10
had its build status changed:
passing
to
failing
mysql_protocol.3.0.3
on
4.11
had its build status changed:
passing
to
failing
mysql_protocol.3.0.3
on
4.12
had its build status changed:
passing
to
failing
mysql_protocol.3.0.3
on
4.13
had its build status changed:
passing
to
failing
mysql_protocol.3.0.3
on
4.14
had its build status changed:
passing
to
failing
mysql_protocol.3.0.3
on
5.0
had its build status changed:
passing
to
failing
mysql_protocol.3.0.3
on
5.1
had its build status changed:
passing
to
failing
nbd.3.0.0
on
4.08
had its build status changed:
passing
to
failing
nbd.3.0.0
on
4.09
had its build status changed:
passing
to
failing
nbd.3.0.0
on
4.10
had its build status changed:
passing
to
failing
nbd.3.0.0
on
4.11
had its build status changed:
passing
to
failing
obuild.0.1.10
on
4.08
had its build status changed:
passing
to
failing
obuild.0.1.10
on
4.09
had its build status changed:
passing
to
failing
obuild.0.1.10
on
4.10
had its build status changed:
passing
to
failing
obuild.0.1.10
on
4.11
had its build status changed:
passing
to
failing
obuild.0.1.10
on
4.12
had its build status changed:
passing
to
failing
obuild.0.1.10
on
4.13
had its build status changed:
passing
to
failing
obuild.0.1.10
on
4.14
had its build status changed:
passing
to
failing
obuild.0.1.11
on
4.08
is now installable. Current state is:
failing
obuild.0.1.11
on
4.09
is now installable. Current state is:
failing
obuild.0.1.11
on
4.10
is now installable. Current state is:
failing
obuild.0.1.11
on
4.11
is now installable. Current state is:
failing
obuild.0.1.11
on
4.12
is now installable. Current state is:
failing
obuild.0.1.11
on
4.13
is now installable. Current state is:
failing
obuild.0.1.11
on
4.14
is now installable. Current state is:
failing
obuild.0.1.11
on
5.0
is now installable. Current state is:
failing
obuild.0.1.11
on
5.1
is now installable. Current state is:
failing
obuild.0.1.9
on
4.08
had its build status changed:
passing
to
failing
obuild.0.1.9
on
4.09
had its build status changed:
passing
to
failing
obuild.0.1.9
on
4.10
had its build status changed:
passing
to
failing
obuild.0.1.9
on
4.11
had its build status changed:
passing
to
failing
obuild.0.1.9
on
4.12
had its build status changed:
passing
to
failing
obuild.0.1.9
on
4.13
had its build status changed:
passing
to
failing
obuild.0.1.9
on
4.14
had its build status changed:
passing
to
failing
ocaml-protoc.1.2.6
on
4.08
had its build status changed:
passing
to
failing
ocaml-protoc.1.2.6
on
4.09
had its build status changed:
passing
to
failing
ocaml-protoc.1.2.6
on
4.10
had its build status changed:
passing
to
failing
ocaml-protoc.1.2.6
on
4.11
had its build status changed:
passing
to
failing
ocaml-protoc.1.2.6
on
4.12
had its build status changed:
passing
to
failing
ocaml-protoc.1.2.6
on
4.13
had its build status changed:
passing
to
failing
ocaml-protoc.1.2.6
on
4.14
had its build status changed:
passing
to
failing
ocamlnet.4.1.6
on
4.08
had its build status changed:
passing
to
failing
ocamlnet.4.1.6
on
4.09
had its build status changed:
passing
to
failing
ocamlnet.4.1.7
on
4.08
had its build status changed:
passing
to
failing
ocamlnet.4.1.7
on
4.09
had its build status changed:
passing
to
failing
ocamlnet.4.1.7
on
4.10
had its build status changed:
passing
to
failing
ocamlnet.4.1.8
on
4.08
had its build status changed:
passing
to
failing
ocamlnet.4.1.8
on
4.09
had its build status changed:
passing
to
failing
ocamlnet.4.1.8
on
4.10
had its build status changed:
passing
to
failing
ocamlnet.4.1.8
on
4.11
had its build status changed:
passing
to
failing
ocamlnet.4.1.8
on
4.12
had its build status changed:
passing
to
failing
ocamlnet.4.1.8
on
4.13
had its build status changed:
passing
to
failing
ocamlnet.4.1.8
on
4.14
had its build status changed:
passing
to
failing
ocamlnet.4.1.9
on
4.08
had its build status changed:
passing
to
failing
ocamlnet.4.1.9
on
4.09
had its build status changed:
passing
to
failing
ocamlnet.4.1.9
on
4.10
had its build status changed:
passing
to
failing
ocamlnet.4.1.9
on
4.11
had its build status changed:
passing
to
failing
ocamlnet.4.1.9
on
4.12
had its build status changed:
passing
to
failing
ocamlnet.4.1.9
on
4.13
had its build status changed:
passing
to
failing
ocamlnet.4.1.9
on
4.14
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-1
on
4.08
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-1
on
4.09
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-1
on
4.10
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-1
on
4.11
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-1
on
4.12
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-1
on
4.13
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-1
on
4.14
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-2
on
4.08
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-2
on
4.09
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-2
on
4.10
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-2
on
4.11
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-2
on
4.12
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-2
on
4.13
had its build status changed:
passing
to
failing
ocamlnet.4.1.9-2
on
4.14
had its build status changed:
passing
to
failing
ocamlrss.2.0
on
4.08
had its build status changed:
passing
to
failing
ocamlrss.2.0
on
4.09
had its build status changed:
passing
to
failing
ocamlrss.2.0
on
4.10
had its build status changed:
passing
to
failing
ocamlrss.2.0
on
4.11
had its build status changed:
passing
to
failing
ocamlrss.2.0
on
4.12
had its build status changed:
passing
to
failing
ocamlrss.2.0
on
4.13
had its build status changed:
passing
to
failing
ocamlrss.2.0
on
4.14
had its build status changed:
passing
to
failing
ollvm-tapir.0.99.1
on
4.09
had its build status changed:
passing
to
failing
ollvm-tapir.0.99.1
on
4.10
had its build status changed:
passing
to
failing
ollvm-tapir.0.99.1
on
4.11
had its build status changed:
passing
to
failing
ollvm-tapir.0.99.1
on
4.13
had its build status changed:
passing
to
failing
ollvm-tapir.0.99.1
on
5.0
had its build status changed:
passing
to
failing
ollvm-tapir.0.99.1
on
5.1
had its build status changed:
passing
to
failing
ollvm.0.99
on
4.10
had its build status changed:
passing
to
failing
ollvm.0.99
on
4.11
had its build status changed:
passing
to
failing
ollvm.0.99
on
4.12
had its build status changed:
passing
to
failing
ollvm.0.99
on
4.14
had its build status changed:
passing
to
failing
ollvm.0.99
on
5.0
had its build status changed:
passing
to
failing
opentelemetry-cohttp-lwt.0.6
on
4.08
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.6
on
4.09
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.6
on
4.10
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.6
on
4.11
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.6
on
4.12
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.6
on
4.13
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.6
on
4.14
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.6
on
5.0
is now installable. Current state is:
failing
opentelemetry-cohttp-lwt.0.6
on
5.1
is now installable. Current state is:
failing
oplsr.8.0.1
on
5.1
had its build status changed:
not available
to
failing
orun.0.0.1
on
4.11
had its build status changed:
passing
to
failing
ostap.0.5
on
4.10
had its build status changed:
passing
to
failing
ostap.0.5
on
4.11
had its build status changed:
passing
to
failing
ostap.0.5
on
4.12
had its build status changed:
passing
to
failing
ostap.0.5
on
4.13
had its build status changed:
passing
to
failing
ostap.0.5
on
4.14
had its build status changed:
passing
to
failing
ott.0.27
on
4.08
had its build status changed:
passing
to
failing
ott.0.27
on
4.09
had its build status changed:
passing
to
failing
ott.0.27
on
4.10
had its build status changed:
passing
to
failing
ott.0.27
on
4.11
had its build status changed:
passing
to
failing
ott.0.27
on
4.12
had its build status changed:
passing
to
failing
ott.0.27
on
4.13
had its build status changed:
passing
to
failing
ott.0.27
on
4.14
had its build status changed:
passing
to
failing
ott.0.31
on
4.08
had its build status changed:
passing
to
failing
ott.0.31
on
4.09
had its build status changed:
passing
to
failing
ott.0.31
on
4.10
had its build status changed:
passing
to
failing
ott.0.31
on
4.11
had its build status changed:
passing
to
failing
ott.0.31
on
4.12
had its build status changed:
passing
to
failing
ott.0.31
on
4.13
had its build status changed:
passing
to
failing
ott.0.31
on
4.14
had its build status changed:
passing
to
failing
ott.0.32
on
4.08
had its build status changed:
passing
to
failing
ott.0.32
on
4.09
had its build status changed:
passing
to
failing
ott.0.32
on
4.10
had its build status changed:
passing
to
failing
ott.0.32
on
4.11
had its build status changed:
passing
to
failing
ott.0.32
on
4.12
had its build status changed:
passing
to
failing
ott.0.32
on
4.13
had its build status changed:
passing
to
failing
ott.0.32
on
4.14
had its build status changed:
passing
to
failing
ott.0.33
on
4.08
had its build status changed:
passing
to
failing
ott.0.33
on
4.09
had its build status changed:
passing
to
failing
ott.0.33
on
4.10
had its build status changed:
passing
to
failing
ott.0.33
on
4.11
had its build status changed:
passing
to
failing
ott.0.33
on
4.12
had its build status changed:
passing
to
failing
ott.0.33
on
4.13
had its build status changed:
passing
to
failing
ott.0.33
on
4.14
had its build status changed:
passing
to
failing
ott.0.33
on
5.0
had its build status changed:
passing
to
failing
ott.0.33
on
5.1
had its build status changed:
passing
to
failing
pa_ppx.0.03
on
4.11
had its build status changed:
passing
to
failing
pa_ppx.0.07.02
on
4.10
had its build status changed:
passing
to
failing
pa_ppx.0.08
on
4.10
had its build status changed:
passing
to
failing
pa_ppx.0.08
on
4.11
had its build status changed:
passing
to
failing
pa_ppx.0.08
on
4.12
had its build status changed:
passing
to
failing
pa_ppx.0.08
on
4.13
had its build status changed:
passing
to
failing
pa_ppx.0.09
on
4.10
had its build status changed:
passing
to
failing
pa_ppx.0.09
on
4.11
had its build status changed:
passing
to
failing
pa_ppx.0.09
on
4.12
had its build status changed:
passing
to
failing
pa_ppx.0.09
on
4.13
had its build status changed:
passing
to
failing
pa_ppx.0.09
on
4.14
had its build status changed:
passing
to
failing
pa_ppx.0.10
on
4.10
had its build status changed:
passing
to
failing
pa_ppx.0.10
on
4.11
had its build status changed:
passing
to
failing
pa_ppx.0.10
on
4.12
had its build status changed:
passing
to
failing
pa_ppx.0.10
on
4.13
had its build status changed:
passing
to
failing
pa_ppx.0.10
on
4.14
had its build status changed:
passing
to
failing
pa_ppx.0.10
on
5.0
had its build status changed:
passing
to
failing
pa_ppx.0.11
on
4.10
had its build status changed:
passing
to
failing
pa_ppx.0.11
on
4.11
had its build status changed:
passing
to
failing
pa_ppx.0.11
on
4.12
had its build status changed:
passing
to
failing
pa_ppx.0.11
on
4.13
had its build status changed:
passing
to
failing
pa_ppx.0.11
on
4.14
had its build status changed:
passing
to
failing
pa_ppx.0.11
on
5.0
had its build status changed:
passing
to
failing
pa_ppx.0.12
on
4.10
had its build status changed:
passing
to
failing
pa_ppx.0.12
on
4.11
had its build status changed:
passing
to
failing
pa_ppx.0.12
on
4.12
had its build status changed:
passing
to
failing
pa_ppx.0.12
on
4.13
had its build status changed:
passing
to
failing
pa_ppx.0.12
on
4.14
had its build status changed:
passing
to
failing
pa_ppx.0.12
on
5.0
had its build status changed:
passing
to
failing
pa_ppx.0.13
on
4.10
had its build status changed:
passing
to
failing
pa_ppx.0.13
on
4.11
had its build status changed:
passing
to
failing
pa_ppx.0.13
on
4.12
had its build status changed:
passing
to
failing
pa_ppx.0.13
on
4.13
had its build status changed:
passing
to
failing
pa_ppx.0.13
on
4.14
had its build status changed:
passing
to
failing
pa_ppx.0.13
on
5.0
had its build status changed:
passing
to
failing
pa_ppx.0.13
on
5.1
had its build status changed:
passing
to
failing
pa_ppx.0.14
on
4.12
is now installable. Current state is:
failing
pa_ppx.0.14
on
4.13
is now installable. Current state is:
failing
pa_ppx.0.14
on
4.14
is now installable. Current state is:
failing
pa_ppx.0.14
on
5.0
is now installable. Current state is:
failing
pa_ppx.0.14
on
5.1
is now installable. Current state is:
failing
piaf.0.1.0
on
4.08
had its build status changed:
passing
to
failing
piaf.0.1.0
on
4.09
had its build status changed:
passing
to
failing
piaf.0.1.0
on
4.10
had its build status changed:
passing
to
failing
piaf.0.1.0
on
4.11
had its build status changed:
passing
to
failing
piaf.0.1.0
on
4.12
had its build status changed:
passing
to
failing
piaf.0.1.0
on
4.13
had its build status changed:
passing
to
failing
piaf.0.1.0
on
4.14
had its build status changed:
passing
to
failing
pkcs11-driver.1.0.1
on
5.1
had its build status changed:
passing
to
failing
portia.1.1
on
5.1
had its build status changed:
not available
to
failing
portia.1.3
on
5.0
had its build status changed:
passing
to
failing
portia.1.3
on
5.1
had its build status changed:
not available
to
failing
portia.1.5
on
4.12
had its build status changed:
passing
to
failing
portia.1.5
on
5.0
had its build status changed:
passing
to
failing
portia.1.5
on
5.1
had its build status changed:
not available
to
failing
posix-semaphore.0.3.0-0
on
4.08
had its build status changed:
passing
to
failing
posix-semaphore.0.3.0-0
on
4.09
had its build status changed:
passing
to
failing
posix-semaphore.0.3.0-0
on
4.10
had its build status changed:
passing
to
failing
posix-semaphore.0.3.0-0
on
4.11
had its build status changed:
passing
to
failing
posix-semaphore.0.3.0-0
on
4.12
had its build status changed:
passing
to
failing
posix-semaphore.0.3.0-0
on
4.13
had its build status changed:
passing
to
failing
posix-semaphore.0.3.0-0
on
4.14
had its build status changed:
passing
to
failing
posix-semaphore.0.4.0-0
on
4.08
had its build status changed:
passing
to
failing
posix-semaphore.0.4.0-0
on
4.09
had its build status changed:
passing
to
failing
posix-semaphore.0.4.0-0
on
4.10
had its build status changed:
passing
to
failing
posix-semaphore.0.4.0-0
on
4.11
had its build status changed:
passing
to
failing
posix-semaphore.0.4.0-0
on
4.12
had its build status changed:
passing
to
failing
posix-semaphore.0.4.0-0
on
4.13
had its build status changed:
passing
to
failing
posix-semaphore.0.4.0-0
on
4.14
had its build status changed:
passing
to
failing
posix-semaphore.0.5.0-0
on
4.08
had its build status changed:
passing
to
failing
posix-semaphore.0.5.0-0
on
4.09
had its build status changed:
passing
to
failing
posix-semaphore.0.5.0-0
on
4.10
had its build status changed:
passing
to
failing
posix-semaphore.0.5.0-0
on
4.11
had its build status changed:
passing
to
failing
posix-semaphore.0.5.0-0
on
4.12
had its build status changed:
passing
to
failing
posix-semaphore.0.5.0-0
on
4.13
had its build status changed:
passing
to
failing
posix-semaphore.0.5.0-0
on
4.14
had its build status changed:
passing
to
failing
ppx_cstubs.0.7.0
on
5.1
had its build status changed:
passing
to
failing
ppx_gen_rec.2.0.0
on
4.08
had its build status changed:
passing
to
failing
ppx_gen_rec.2.0.0
on
4.09
had its build status changed:
passing
to
failing
ppx_gen_rec.2.0.0
on
4.10
had its build status changed:
passing
to
failing
ppx_gen_rec.2.0.0
on
4.11
had its build status changed:
passing
to
failing
ppx_gen_rec.2.0.0
on
4.12
had its build status changed:
passing
to
failing
ppx_gen_rec.2.0.0
on
4.13
had its build status changed:
passing
to
failing
ppx_gen_rec.2.0.0
on
4.14
had its build status changed:
passing
to
failing
ppx_gen_rec.2.0.0
on
5.0
had its build status changed:
passing
to
failing
ppx_gen_rec.2.0.0
on
5.1
had its build status changed:
passing
to
failing
ppxx.2.5.0
on
5.1
had its build status changed:
passing
to
failing
proverif.1.98
on
4.08
had its build status changed:
internal failure
to
failing
proverif.1.98
on
4.09
had its build status changed:
internal failure
to
failing
proverif.1.98
on
4.10
had its build status changed:
internal failure
to
failing
proverif.1.98
on
4.11
had its build status changed:
internal failure
to
failing
proverif.1.98
on
4.12
had its build status changed:
internal failure
to
failing
proverif.1.98
on
4.13
had its build status changed:
internal failure
to
failing
proverif.1.98
on
4.14
had its build status changed:
internal failure
to
failing
proverif.1.98
on
5.0
had its build status changed:
internal failure
to
failing
proverif.1.98
on
5.1
had its build status changed:
internal failure
to
failing
proverif.1.98pl1
on
4.08
had its build status changed:
internal failure
to
failing
proverif.1.98pl1
on
4.09
had its build status changed:
internal failure
to
failing
proverif.1.98pl1
on
4.10
had its build status changed:
internal failure
to
failing
proverif.1.98pl1
on
4.11
had its build status changed:
internal failure
to
failing
proverif.1.98pl1
on
4.12
had its build status changed:
internal failure
to
failing
proverif.1.98pl1
on
4.13
had its build status changed:
internal failure
to
failing
proverif.1.98pl1
on
4.14
had its build status changed:
internal failure
to
failing
proverif.1.98pl1
on
5.0
had its build status changed:
internal failure
to
failing
proverif.1.98pl1
on
5.1
had its build status changed:
internal failure
to
failing
proverif.2.00
on
4.08
had its build status changed:
passing
to
failing
proverif.2.00
on
4.09
had its build status changed:
passing
to
failing
proverif.2.00
on
4.10
had its build status changed:
passing
to
failing
proverif.2.00
on
4.11
had its build status changed:
passing
to
failing
proverif.2.00
on
4.12
had its build status changed:
passing
to
failing
proverif.2.00
on
4.13
had its build status changed:
passing
to
failing
proverif.2.00
on
4.14
had its build status changed:
passing
to
failing
solo5-cross-aarch64.0.7.0
on
4.14
had its build status changed:
partially failing
to
failing
statverif.1.97pl1.1
on
4.08
had its build status changed:
passing
to
failing
statverif.1.97pl1.1
on
4.09
had its build status changed:
passing
to
failing
statverif.1.97pl1.1
on
4.10
had its build status changed:
passing
to
failing
statverif.1.97pl1.1
on
4.11
had its build status changed:
passing
to
failing
statverif.1.97pl1.1
on
4.12
had its build status changed:
passing
to
failing
statverif.1.97pl1.1
on
4.13
had its build status changed:
passing
to
failing
statverif.1.97pl1.1
on
4.14
had its build status changed:
passing
to
failing
statverif.1.97pl1.2
on
4.08
had its build status changed:
passing
to
failing
statverif.1.97pl1.2
on
4.09
had its build status changed:
passing
to
failing
statverif.1.97pl1.2
on
4.10
had its build status changed:
passing
to
failing
statverif.1.97pl1.2
on
4.11
had its build status changed:
passing
to
failing
statverif.1.97pl1.2
on
4.12
had its build status changed:
passing
to
failing
statverif.1.97pl1.2
on
4.13
had its build status changed:
passing
to
failing
statverif.1.97pl1.2
on
4.14
had its build status changed:
passing
to
failing
sundialsml.2.5.0p0
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p0
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p0
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p0
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p0
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p0
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p1
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p1
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p1
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p1
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p1
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p1
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p2
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p2
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p2
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p2
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p2
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.2.5.0p2
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p0
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p0
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p0
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p0
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p0
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p0
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p1
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p1
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p1
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p1
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p1
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.2.6.2p1
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.2.7.0p0
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.2.7.0p0
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.2.7.0p0
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.2.7.0p0
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.2.7.0p0
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.2.7.0p0
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0-1
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0-1
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0-1
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0-1
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0-1
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p0-1
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p1
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p1
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p1
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p1
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p1
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.3.1.1p1
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.5.8.0p0
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.5.8.0p0
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.5.8.0p0
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.5.8.0p0
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.5.8.0p0
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.5.8.0p0
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.6.0.0p0
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.6.0.0p0
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.6.0.0p0
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.6.0.0p0
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.6.0.0p0
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.6.0.0p0
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.6.1.0p0
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.6.1.0p0
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.6.1.0p0
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.6.1.0p0
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.6.1.0p0
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.6.1.0p0
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p0
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p0
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p0
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p0
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p0
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p0
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p1
on
4.08
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p1
on
4.09
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p1
on
4.10
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p1
on
4.11
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p1
on
4.12
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p1
on
4.13
had its build status changed:
internal failure
to
failing
sundialsml.6.1.1p1
on
4.14
had its build status changed:
internal failure
to
failing
tls.0.10.2
on
4.08
had its build status changed:
passing
to
failing
tls.0.10.2
on
4.09
had its build status changed:
internal failure
to
failing
tls.0.10.2
on
4.10
had its build status changed:
passing
to
failing
tls.0.10.2
on
4.11
had its build status changed:
passing
to
failing
tls.0.10.3
on
4.08
had its build status changed:
passing
to
failing
tls.0.10.3
on
4.09
had its build status changed:
passing
to
failing
tls.0.10.3
on
4.10
had its build status changed:
passing
to
failing
tls.0.10.3
on
4.11
had its build status changed:
passing
to
failing
tls.0.10.4
on
4.08
had its build status changed:
passing
to
failing
tls.0.10.4
on
4.09
had its build status changed:
passing
to
failing
tls.0.10.4
on
4.10
had its build status changed:
passing
to
failing
tls.0.10.4
on
4.11
had its build status changed:
passing
to
failing
tls.0.10.5
on
4.08
had its build status changed:
passing
to
failing
tls.0.10.5
on
4.09
had its build status changed:
passing
to
failing
tls.0.10.5
on
4.10
had its build status changed:
passing
to
failing
tls.0.10.5
on
4.11
had its build status changed:
passing
to
failing
tls.0.10.6
on
4.08
had its build status changed:
passing
to
failing
tls.0.10.6
on
4.09
had its build status changed:
passing
to
failing
tls.0.10.6
on
4.10
had its build status changed:
passing
to
failing
tls.0.10.6
on
4.11
had its build status changed:
passing
to
failing
toc.0.1.0
on
4.08
had its build status changed:
passing
to
failing
toc.0.1.0
on
4.09
had its build status changed:
passing
to
failing
toc.0.1.0
on
4.10
had its build status changed:
passing
to
failing
toc.0.1.0
on
4.11
had its build status changed:
passing
to
failing
toc.0.1.0
on
4.12
had its build status changed:
passing
to
failing
toc.0.1.0
on
4.13
had its build status changed:
passing
to
failing
toc.0.1.0
on
4.14
had its build status changed:
passing
to
failing
toc.0.1.0
on
5.0
had its build status changed:
passing
to
failing
toc.0.1.0
on
5.1
had its build status changed:
passing
to
failing
torch.0.13
on
4.09
had its build status changed:
internal failure
to
failing
tsdl-image.0.1.2
on
4.08
had its build status changed:
passing
to
failing
tsdl-image.0.1.2
on
4.09
had its build status changed:
passing
to
failing
tsdl-image.0.1.2
on
4.10
had its build status changed:
passing
to
failing
tsdl-image.0.1.2
on
4.11
had its build status changed:
passing
to
failing
tsdl-image.0.1.2
on
4.12
had its build status changed:
passing
to
failing
tsdl-image.0.1.2
on
4.13
had its build status changed:
passing
to
failing
tsdl-image.0.1.2
on
4.14
had its build status changed:
passing
to
failing
tsdl-image.0.2.0
on
4.08
had its build status changed:
passing
to
failing
tsdl-image.0.2.0
on
4.09
had its build status changed:
passing
to
failing
tsdl-image.0.2.0
on
4.10
had its build status changed:
passing
to
failing
tsdl-image.0.2.0
on
4.11
had its build status changed:
passing
to
failing
tsdl-image.0.2.0
on
4.12
had its build status changed:
passing
to
failing
tsdl-image.0.2.0
on
4.13
had its build status changed:
passing
to
failing
tsdl.0.9.1
on
4.09
had its build status changed:
internal failure
to
failing
tsdl.0.9.3
on
4.09
had its build status changed:
internal failure
to
failing
tsdl.0.9.5
on
4.09
had its build status changed:
internal failure
to
failing
tuareg.2.1.0
on
4.11
had its build status changed:
passing
to
failing
tuareg.2.1.0
on
5.1
had its build status changed:
passing
to
failing
tuareg.2.2.0
on
4.11
had its build status changed:
passing
to
failing
utop.2.10.0
on
5.0
had its build status changed:
passing
to
failing
vcaml.v0.16.0
on
5.1
had its build status changed:
passing
to
failing
x509.0.6.2
on
4.08
had its build status changed:
passing
to
failing
x509.0.6.2
on
4.09
had its build status changed:
passing
to
failing
x509.0.6.2
on
4.10
had its build status changed:
passing
to
failing
x509.0.6.2
on
4.11
had its build status changed:
passing
to
failing
x509.0.6.2
on
4.12
had its build status changed:
passing
to
failing
x509.0.6.2
on
4.13
had its build status changed:
passing
to
failing
yaml.0.2.1
on
4.09
had its build status changed:
internal failure
to
failing
zelus.2.2
on
4.08
had its build status changed:
passing
to
failing
zelus.2.2
on
4.09
had its build status changed:
passing
to
failing
zelus.2.2
on
4.10
had its build status changed:
passing
to
failing
zelus.2.2
on
4.11
had its build status changed:
passing
to
failing
zelus.2.2
on
4.12
had its build status changed:
passing
to
failing
zelus.2.2
on
4.13
had its build status changed:
passing
to
failing
zelus.2.2
on
4.14
had its build status changed:
passing
to
failing
zelus.2.2
on
5.0
had its build status changed:
passing
to
failing
zelus.2.2
on
5.1
had its build status changed:
passing
to
failing
Packages now
partially failing
:
acpc.1.1.1
on
4.08
had its build status changed:
passing
to
partially failing
acpc.1.1.1
on
4.09
had its build status changed:
passing
to
partially failing
acpc.1.1.1
on
4.10
had its build status changed:
passing
to
partially failing
acpc.1.1.1
on
4.11
had its build status changed:
passing
to
partially failing
acpc.1.1.1
on
4.12
had its build status changed:
passing
to
partially failing
acpc.1.1.1
on
4.13
had its build status changed:
passing
to
partially failing
acpc.1.1.1
on
4.14
had its build status changed:
passing
to
partially failing
acpc.1.2.3
on
4.08
had its build status changed:
passing
to
partially failing
acpc.1.2.3
on
4.09
had its build status changed:
passing
to
partially failing
acpc.1.2.3
on
4.10
had its build status changed:
passing
to
partially failing
acpc.1.2.3
on
4.11
had its build status changed:
passing
to
partially failing
acpc.1.2.3
on
4.12
had its build status changed:
passing
to
partially failing
acpc.1.2.3
on
4.13
had its build status changed:
passing
to
partially failing
acpc.1.2.3
on
4.14
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.0
on
4.08
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.0
on
4.09
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.0
on
4.10
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.0
on
4.11
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.0
on
4.12
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.0
on
4.13
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.0
on
4.14
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.1
on
4.08
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.1
on
4.09
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.1
on
4.10
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.1
on
4.11
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.1
on
4.12
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.1
on
4.13
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.1
on
4.14
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.2
on
4.08
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.2
on
4.09
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.2
on
4.10
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.2
on
4.11
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.2
on
4.12
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.2
on
4.13
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.2
on
4.14
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.3
on
4.08
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.3
on
4.09
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.3
on
4.10
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.3
on
4.11
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.3
on
4.12
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.3
on
4.13
had its build status changed:
passing
to
partially failing
alt-ergo.2.3.3
on
4.14
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.0
on
4.08
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.0
on
4.09
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.0
on
4.10
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.0
on
4.11
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.0
on
4.12
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.0
on
4.13
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.0
on
4.14
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.1
on
4.08
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.1
on
4.09
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.1
on
4.10
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.1
on
4.11
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.1
on
4.12
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.1
on
4.13
had its build status changed:
passing
to
partially failing
alt-ergo.2.4.1
on
4.14
had its build status changed:
passing
to
partially failing
archimedes.0.4.18
on
4.08
had its build status changed:
passing
to
partially failing
archimedes.0.4.18
on
4.09
had its build status changed:
passing
to
partially failing
archimedes.0.4.18
on
4.10
had its build status changed:
passing
to
partially failing
archimedes.0.4.18
on
4.11
had its build status changed:
passing
to
partially failing
archimedes.0.4.18
on
4.12
had its build status changed:
passing
to
partially failing
archimedes.0.4.18
on
4.13
had its build status changed:
passing
to
partially failing
archimedes.0.4.18
on
4.14
had its build status changed:
passing
to
partially failing
archimedes.0.4.18
on
5.0
had its build status changed:
not available
to
partially failing
azure-cosmos-db.0.1.2
on
4.08
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.2
on
4.09
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.2
on
4.10
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.2
on
4.11
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.2
on
4.12
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.2
on
4.13
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.2
on
4.14
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.3
on
4.08
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.3
on
4.09
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.3
on
4.10
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.3
on
4.11
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.3
on
4.12
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.3
on
4.13
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.3
on
4.14
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.4
on
4.08
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.4
on
4.09
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.4
on
4.10
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.4
on
4.11
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.4
on
4.12
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.4
on
4.13
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.4
on
4.14
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.5
on
4.08
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.5
on
4.09
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.5
on
4.10
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.5
on
4.11
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.5
on
4.12
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.5
on
4.13
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.5
on
4.14
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.6
on
4.08
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.6
on
4.09
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.6
on
4.10
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.6
on
4.11
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.6
on
4.12
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.6
on
4.13
had its build status changed:
passing
to
partially failing
azure-cosmos-db.0.1.6
on
4.14
had its build status changed:
passing
to
partially failing
bdd.0.3
on
4.08
had its build status changed:
passing
to
partially failing
bdd.0.3
on
4.09
had its build status changed:
passing
to
partially failing
bdd.0.3
on
4.10
had its build status changed:
passing
to
partially failing
bdd.0.3
on
4.11
had its build status changed:
passing
to
partially failing
bdd.0.3
on
4.12
had its build status changed:
passing
to
partially failing
bdd.0.3
on
4.13
had its build status changed:
passing
to
partially failing
bdd.0.3
on
4.14
had its build status changed:
passing
to
partially failing
beluga.0.8.1
on
4.08
had its build status changed:
passing
to
partially failing
beluga.0.8.1
on
4.09
had its build status changed:
passing
to
partially failing
beluga.0.8.1
on
4.10
had its build status changed:
passing
to
partially failing
beluga.0.8.1
on
4.11
had its build status changed:
passing
to
partially failing
beluga.0.8.1
on
4.12
had its build status changed:
passing
to
partially failing
beluga.0.8.1
on
4.13
had its build status changed:
passing
to
partially failing
beluga.0.8.1
on
4.14
had its build status changed:
passing
to
partially failing
beluga.0.8.1
on
5.0
had its build status changed:
not available
to
partially failing
beluga.0.8.2
on
4.08
had its build status changed:
passing
to
partially failing
beluga.0.8.2
on
4.09
had its build status changed:
passing
to
partially failing
beluga.0.8.2
on
4.10
had its build status changed:
passing
to
partially failing
beluga.0.8.2
on
4.11
had its build status changed:
passing
to
partially failing
beluga.0.8.2
on
4.12
had its build status changed:
passing
to
partially failing
beluga.0.8.2
on
4.13
had its build status changed:
passing
to
partially failing
beluga.0.8.2
on
4.14
had its build status changed:
passing
to
partially failing
beluga.0.8.2
on
5.0
had its build status changed:
not available
to
partially failing
bheap.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
bheap.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
bheap.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
bheap.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
bheap.1.0.0
on
4.12
had its build status changed:
passing
to
partially failing
bheap.1.0.0
on
4.13
had its build status changed:
passing
to
partially failing
bheap.1.0.0
on
4.14
had its build status changed:
passing
to
partially failing
biotk.0.0.0
on
4.11
had its build status changed:
passing
to
partially failing
biotk.0.0.0
on
4.12
had its build status changed:
passing
to
partially failing
biotk.0.0.0
on
4.13
had its build status changed:
passing
to
partially failing
biotk.0.0.0
on
4.14
had its build status changed:
passing
to
partially failing
biotk.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
biotk.0.1.0
on
4.12
had its build status changed:
passing
to
partially failing
biotk.0.1.0
on
4.13
had its build status changed:
passing
to
partially failing
biotk.0.1.0
on
4.14
had its build status changed:
passing
to
partially failing
bisect.1.3.1
on
4.08
had its build status changed:
passing
to
partially failing
bisect.1.3.1
on
4.09
had its build status changed:
passing
to
partially failing
bisect.1.3.1
on
4.10
had its build status changed:
passing
to
partially failing
bisect.1.3.1
on
4.11
had its build status changed:
passing
to
partially failing
bisect.1.3.1
on
4.12
had its build status changed:
passing
to
partially failing
bisect.1.3.1
on
4.13
had its build status changed:
passing
to
partially failing
bisect.1.3.1
on
4.14
had its build status changed:
passing
to
partially failing
bisect.1.3.1
on
5.0
had its build status changed:
not available
to
partially failing
bistro-bio.0.6.0
on
4.11
had its build status changed:
passing
to
partially failing
bistro-bio.0.6.0
on
4.12
had its build status changed:
passing
to
partially failing
bistro-bio.0.6.0
on
4.13
had its build status changed:
passing
to
partially failing
bistro-bio.0.6.0
on
4.14
had its build status changed:
passing
to
partially failing
bogue.20190717
on
4.08
had its build status changed:
passing
to
partially failing
bogue.20190717
on
4.09
had its build status changed:
passing
to
partially failing
bogue.20190717
on
4.10
had its build status changed:
passing
to
partially failing
bogue.20190717
on
4.11
had its build status changed:
passing
to
partially failing
bogue.20190717
on
4.12
had its build status changed:
passing
to
partially failing
bogue.20190717
on
4.13
had its build status changed:
passing
to
partially failing
bogue.20190920
on
4.08
had its build status changed:
passing
to
partially failing
bogue.20190920
on
4.09
had its build status changed:
passing
to
partially failing
bogue.20190920
on
4.10
had its build status changed:
passing
to
partially failing
bogue.20190920
on
4.11
had its build status changed:
passing
to
partially failing
bogue.20190920
on
4.12
had its build status changed:
passing
to
partially failing
bogue.20190920
on
4.13
had its build status changed:
passing
to
partially failing
bogue.20200630
on
4.08
had its build status changed:
passing
to
partially failing
bogue.20200630
on
4.09
had its build status changed:
passing
to
partially failing
bogue.20200630
on
4.10
had its build status changed:
passing
to
partially failing
bogue.20200630
on
4.11
had its build status changed:
passing
to
partially failing
bogue.20200630
on
4.12
had its build status changed:
passing
to
partially failing
bogue.20200630
on
4.13
had its build status changed:
passing
to
partially failing
bogue.20210514
on
4.08
had its build status changed:
passing
to
partially failing
bogue.20210514
on
4.09
had its build status changed:
passing
to
partially failing
bogue.20210514
on
4.10
had its build status changed:
passing
to
partially failing
bogue.20210514
on
4.11
had its build status changed:
passing
to
partially failing
bogue.20210514
on
4.12
had its build status changed:
passing
to
partially failing
bogue.20210514
on
4.13
had its build status changed:
passing
to
partially failing
bogue.20210514
on
4.14
had its build status changed:
passing
to
partially failing
bookaml.2.1
on
4.08
had its build status changed:
passing
to
partially failing
bookaml.2.1
on
4.09
had its build status changed:
passing
to
partially failing
bookaml.2.1
on
4.10
had its build status changed:
passing
to
partially failing
bookaml.2.1
on
4.11
had its build status changed:
passing
to
partially failing
bookaml.2.1
on
4.12
had its build status changed:
passing
to
partially failing
bookaml.2.1
on
4.13
had its build status changed:
passing
to
partially failing
bookaml.2.1
on
4.14
had its build status changed:
passing
to
partially failing
bookaml.4.0
on
4.08
had its build status changed:
passing
to
partially failing
bookaml.4.0
on
4.09
had its build status changed:
passing
to
partially failing
bookaml.4.0
on
4.10
had its build status changed:
passing
to
partially failing
bookaml.4.0
on
4.11
had its build status changed:
passing
to
partially failing
bookaml.4.0
on
4.12
had its build status changed:
passing
to
partially failing
bookaml.4.0
on
4.13
had its build status changed:
passing
to
partially failing
bookaml.4.0
on
4.14
had its build status changed:
passing
to
partially failing
caisar.0.2
on
5.0
had its build status changed:
not available
to
partially failing
caisar.0.2.1
on
5.0
is now installable. Current state is:
partially failing
calculon.0.3
on
4.08
had its build status changed:
failing
to
partially failing
calculon.0.3
on
4.09
had its build status changed:
failing
to
partially failing
calculon.0.3
on
4.10
had its build status changed:
failing
to
partially failing
calculon.0.3
on
4.11
had its build status changed:
failing
to
partially failing
calculon.0.4
on
4.08
had its build status changed:
failing
to
partially failing
calculon.0.4
on
4.09
had its build status changed:
failing
to
partially failing
calculon.0.4
on
4.10
had its build status changed:
failing
to
partially failing
calculon.0.4
on
4.11
had its build status changed:
failing
to
partially failing
capnp-rpc-lwt.0.3.1
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.1
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.1
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.1
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.2
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.2
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.2
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.2
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.3
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.3
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.3
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.3.3
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.4.0
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.4.0
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.4.0
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-lwt.0.4.0
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.1
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.1
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.1
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.1
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.2
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.2
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.2
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.2
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.3
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.3
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.3
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.3.3
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.4.0
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.4.0
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.4.0
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.4.0
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.5.0
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.5.0
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.5.0
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-mirage.0.5.0
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-net.0.5.0
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-net.0.5.0
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-net.0.5.0
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-net.0.5.0
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.1
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.1
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.1
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.1
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.2
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.2
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.2
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.2
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.3
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.3
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.3
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.3.3
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.4.0
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.4.0
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.4.0
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.4.0
on
4.11
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.5.0
on
4.08
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.5.0
on
4.09
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.5.0
on
4.10
had its build status changed:
passing
to
partially failing
capnp-rpc-unix.0.5.0
on
4.11
had its build status changed:
passing
to
partially failing
cca.0.1
on
4.11
had its build status changed:
failing
to
partially failing
cca.0.1
on
4.12
had its build status changed:
failing
to
partially failing
cca.0.2
on
4.11
had its build status changed:
failing
to
partially failing
cca.0.2
on
4.12
had its build status changed:
failing
to
partially failing
cca.0.2
on
4.13
had its build status changed:
failing
to
partially failing
cca.0.2
on
4.14
had its build status changed:
failing
to
partially failing
cca.0.4
on
4.11
had its build status changed:
failing
to
partially failing
cca.0.4
on
4.12
had its build status changed:
failing
to
partially failing
cca.0.4
on
4.13
had its build status changed:
failing
to
partially failing
cca.0.4
on
4.14
had its build status changed:
failing
to
partially failing
cca.0.5
on
4.11
had its build status changed:
failing
to
partially failing
cca.0.5
on
4.12
had its build status changed:
failing
to
partially failing
cca.0.5
on
4.13
had its build status changed:
failing
to
partially failing
cca.0.5
on
4.14
had its build status changed:
failing
to
partially failing
cca.0.6.2
on
4.14
had its build status changed:
failing
to
partially failing
cca.0.7
on
4.14
had its build status changed:
passing
to
partially failing
cdrom.0.9.1
on
4.08
had its build status changed:
passing
to
partially failing
cdrom.0.9.1
on
4.09
had its build status changed:
passing
to
partially failing
cdrom.0.9.1
on
4.10
had its build status changed:
passing
to
partially failing
cdrom.0.9.1
on
4.11
had its build status changed:
passing
to
partially failing
cdrom.0.9.1
on
4.12
had its build status changed:
passing
to
partially failing
cdrom.0.9.1
on
4.13
had its build status changed:
passing
to
partially failing
cdrom.0.9.1
on
4.14
had its build status changed:
passing
to
partially failing
cdrom.0.9.1
on
5.0
had its build status changed:
not available
to
partially failing
cdrom.0.9.1
on
5.1
had its build status changed:
not available
to
partially failing
clangml-transforms.0.26
on
4.08
had its build status changed:
passing
to
partially failing
clangml-transforms.0.26
on
4.09
had its build status changed:
passing
to
partially failing
clangml-transforms.0.26
on
4.10
had its build status changed:
passing
to
partially failing
clangml-transforms.0.26
on
4.11
had its build status changed:
passing
to
partially failing
clangml-transforms.0.26
on
4.12
had its build status changed:
passing
to
partially failing
clangml-transforms.0.26
on
4.13
had its build status changed:
passing
to
partially failing
clangml-transforms.0.26
on
4.14
had its build status changed:
passing
to
partially failing
clangml-transforms.0.26
on
5.0
had its build status changed:
passing
to
partially failing
clangml.4.0.0
on
4.08
had its build status changed:
failing
to
partially failing
clangml.4.3.0
on
4.08
had its build status changed:
failing
to
partially failing
clangml.4.3.0
on
4.09
had its build status changed:
failing
to
partially failing
clangml.4.3.0
on
4.10
had its build status changed:
failing
to
partially failing
clangml.4.3.0
on
4.11
had its build status changed:
failing
to
partially failing
clangml.4.8.0
on
4.08
had its build status changed:
passing
to
partially failing
clangml.4.8.0
on
4.09
had its build status changed:
passing
to
partially failing
clangml.4.8.0
on
4.10
had its build status changed:
passing
to
partially failing
clangml.4.8.0
on
4.11
had its build status changed:
passing
to
partially failing
clangml.4.8.0
on
4.12
had its build status changed:
passing
to
partially failing
clangml.4.8.0
on
4.13
had its build status changed:
passing
to
partially failing
clangml.4.8.0
on
4.14
had its build status changed:
passing
to
partially failing
clangml.4.8.0
on
5.0
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.1
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.1
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.1
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.1
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.2
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.2
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.2
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.0.2
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.1.0
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.1.0
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.1.0
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.1.0
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.1.1
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.1.1
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.1.1
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.1.1
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.2.0
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.2.0
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.2.0
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.1.2.0
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.0.0
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.0.0
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.0.0
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.0.0
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.0
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.0
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.0
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.0
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.1
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.1
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.1
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.1
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.3
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.3
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.3
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.1.3
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.2.0
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.2.0
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.2.0
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.2.0
on
4.11
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.3.0
on
4.08
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.3.0
on
4.09
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.3.0
on
4.10
had its build status changed:
passing
to
partially failing
cohttp-mirage.2.3.0
on
4.11
had its build status changed:
passing
to
partially failing
coin.0.1.0
on
4.08
had its build status changed:
failing
to
partially failing
coin.0.1.0
on
4.09
had its build status changed:
passing
to
partially failing
coin.0.1.0
on
4.10
had its build status changed:
passing
to
partially failing
coin.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.0
on
4.08
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.0
on
4.09
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.0
on
4.10
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.0
on
4.11
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.1
on
4.08
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.1
on
4.09
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.1
on
4.10
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.1
on
4.11
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.2
on
4.08
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.2
on
4.09
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.2
on
4.10
had its build status changed:
passing
to
partially failing
conduit-mirage.2.0.2
on
4.11
had its build status changed:
passing
to
partially failing
config-file.1.1
on
4.08
had its build status changed:
passing
to
partially failing
config-file.1.1
on
4.09
had its build status changed:
passing
to
partially failing
config-file.1.1
on
4.10
had its build status changed:
passing
to
partially failing
config-file.1.1
on
4.11
had its build status changed:
passing
to
partially failing
config-file.1.1
on
4.12
had its build status changed:
passing
to
partially failing
config-file.1.1
on
4.13
had its build status changed:
passing
to
partially failing
config-file.1.1
on
4.14
had its build status changed:
passing
to
partially failing
config-file.1.1
on
5.0
had its build status changed:
not available
to
partially failing
config-file.1.2
on
4.08
had its build status changed:
passing
to
partially failing
config-file.1.2
on
4.09
had its build status changed:
passing
to
partially failing
config-file.1.2
on
4.10
had its build status changed:
passing
to
partially failing
config-file.1.2
on
4.11
had its build status changed:
passing
to
partially failing
config-file.1.2
on
4.12
had its build status changed:
passing
to
partially failing
config-file.1.2
on
4.13
had its build status changed:
passing
to
partially failing
config-file.1.2
on
4.14
had its build status changed:
passing
to
partially failing
config-file.1.2
on
5.0
had its build status changed:
not available
to
partially failing
config-file.1.2.1
on
4.08
had its build status changed:
passing
to
partially failing
config-file.1.2.1
on
4.09
had its build status changed:
passing
to
partially failing
config-file.1.2.1
on
4.10
had its build status changed:
passing
to
partially failing
config-file.1.2.1
on
4.11
had its build status changed:
passing
to
partially failing
config-file.1.2.1
on
4.12
had its build status changed:
passing
to
partially failing
config-file.1.2.1
on
4.13
had its build status changed:
passing
to
partially failing
config-file.1.2.1
on
4.14
had its build status changed:
passing
to
partially failing
config-file.1.2.1
on
5.0
had its build status changed:
not available
to
partially failing
cpm.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
cpm.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
cpm.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
cpm.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
cpm.1.0.0
on
4.12
had its build status changed:
passing
to
partially failing
cpm.1.0.0
on
4.13
had its build status changed:
passing
to
partially failing
cpm.1.0.0
on
4.14
had its build status changed:
passing
to
partially failing
cpm.1.0.0
on
5.0
had its build status changed:
not available
to
partially failing
cpm.2.0.0
on
4.08
had its build status changed:
passing
to
partially failing
cpm.2.0.0
on
4.09
had its build status changed:
passing
to
partially failing
cpm.2.0.0
on
4.10
had its build status changed:
passing
to
partially failing
cpm.2.0.0
on
4.11
had its build status changed:
passing
to
partially failing
cpm.2.0.0
on
4.12
had its build status changed:
passing
to
partially failing
cpm.2.0.0
on
4.13
had its build status changed:
passing
to
partially failing
cpm.2.0.0
on
4.14
had its build status changed:
passing
to
partially failing
cpm.2.0.0
on
5.0
had its build status changed:
not available
to
partially failing
cpm.3.0.0
on
4.08
had its build status changed:
passing
to
partially failing
cpm.3.0.0
on
4.09
had its build status changed:
passing
to
partially failing
cpm.3.0.0
on
4.10
had its build status changed:
passing
to
partially failing
cpm.3.0.0
on
4.11
had its build status changed:
passing
to
partially failing
cpm.3.0.0
on
4.12
had its build status changed:
passing
to
partially failing
cpm.3.0.0
on
4.13
had its build status changed:
passing
to
partially failing
cpm.3.0.0
on
4.14
had its build status changed:
passing
to
partially failing
cpm.3.0.0
on
5.0
had its build status changed:
not available
to
partially failing
cryptohash.0.1
on
4.08
had its build status changed:
passing
to
partially failing
cryptohash.0.1
on
4.09
had its build status changed:
passing
to
partially failing
cryptohash.0.1
on
4.10
had its build status changed:
passing
to
partially failing
cryptohash.0.1
on
4.11
had its build status changed:
passing
to
partially failing
cryptohash.0.1
on
4.12
had its build status changed:
passing
to
partially failing
cryptohash.0.1
on
4.13
had its build status changed:
passing
to
partially failing
cryptohash.0.1
on
4.14
had its build status changed:
passing
to
partially failing
cryptohash.0.1
on
5.0
had its build status changed:
not available
to
partially failing
ctypes-zarith.0.1.0
on
5.1
had its build status changed:
passing
to
partially failing
ctypes-zarith.0.2.0
on
5.1
had its build status changed:
passing
to
partially failing
cudf.0.7
on
4.08
had its build status changed:
passing
to
partially failing
cudf.0.7
on
4.09
had its build status changed:
passing
to
partially failing
cudf.0.7
on
4.10
had its build status changed:
passing
to
partially failing
cudf.0.7
on
4.11
had its build status changed:
passing
to
partially failing
cudf.0.7
on
4.12
had its build status changed:
passing
to
partially failing
cudf.0.7
on
4.13
had its build status changed:
passing
to
partially failing
cudf.0.7
on
4.14
had its build status changed:
passing
to
partially failing
cudf.0.8
on
4.08
had its build status changed:
passing
to
partially failing
cudf.0.8
on
4.09
had its build status changed:
passing
to
partially failing
cudf.0.8
on
4.10
had its build status changed:
passing
to
partially failing
cudf.0.8
on
4.11
had its build status changed:
passing
to
partially failing
cudf.0.8
on
4.12
had its build status changed:
passing
to
partially failing
cudf.0.8
on
4.13
had its build status changed:
passing
to
partially failing
cudf.0.8
on
4.14
had its build status changed:
passing
to
partially failing
current_examples.0.1
on
4.08
had its build status changed:
passing
to
partially failing
current_examples.0.1
on
4.09
had its build status changed:
passing
to
partially failing
current_examples.0.1
on
4.10
had its build status changed:
passing
to
partially failing
current_examples.0.1
on
4.11
had its build status changed:
passing
to
partially failing
current_github.0.1
on
4.08
had its build status changed:
passing
to
partially failing
current_github.0.1
on
4.09
had its build status changed:
passing
to
partially failing
current_github.0.1
on
4.10
had its build status changed:
passing
to
partially failing
current_github.0.1
on
4.11
had its build status changed:
passing
to
partially failing
daft.0.0.3
on
4.08
had its build status changed:
passing
to
partially failing
daft.0.0.3
on
4.09
had its build status changed:
passing
to
partially failing
daft.0.0.3
on
4.10
had its build status changed:
passing
to
partially failing
daft.0.0.3
on
4.11
had its build status changed:
passing
to
partially failing
daft.0.0.3
on
4.12
had its build status changed:
passing
to
partially failing
daft.0.0.3
on
4.13
had its build status changed:
passing
to
partially failing
daft.0.0.3
on
4.14
had its build status changed:
passing
to
partially failing
daft.0.0.3
on
5.0
had its build status changed:
not available
to
partially failing
deriving.0.8.1
on
4.08
had its build status changed:
passing
to
partially failing
deriving.0.8.1
on
4.09
had its build status changed:
passing
to
partially failing
deriving.0.8.1
on
4.10
had its build status changed:
passing
to
partially failing
deriving.0.8.1
on
4.11
had its build status changed:
passing
to
partially failing
deriving.0.8.1
on
4.12
had its build status changed:
passing
to
partially failing
deriving.0.8.1
on
4.13
had its build status changed:
passing
to
partially failing
deriving.0.8.1
on
4.14
had its build status changed:
passing
to
partially failing
devkit.0.6
on
4.08
had its build status changed:
failing
to
partially failing
devkit.0.6
on
4.09
had its build status changed:
failing
to
partially failing
devkit.0.6
on
4.10
had its build status changed:
failing
to
partially failing
devkit.0.6
on
4.11
had its build status changed:
failing
to
partially failing
devkit.0.7
on
4.08
had its build status changed:
failing
to
partially failing
devkit.0.7
on
4.09
had its build status changed:
failing
to
partially failing
devkit.0.7
on
4.10
had its build status changed:
failing
to
partially failing
devkit.0.7
on
4.11
had its build status changed:
failing
to
partially failing
devkit.1.0
on
4.08
had its build status changed:
failing
to
partially failing
devkit.1.0
on
4.09
had its build status changed:
failing
to
partially failing
devkit.1.0
on
4.10
had its build status changed:
failing
to
partially failing
devkit.1.0
on
4.11
had its build status changed:
failing
to
partially failing
devkit.1.2
on
4.08
had its build status changed:
passing
to
partially failing
devkit.1.2
on
4.09
had its build status changed:
passing
to
partially failing
devkit.1.2
on
4.10
had its build status changed:
passing
to
partially failing
devkit.1.2
on
4.11
had its build status changed:
passing
to
partially failing
devkit.1.2
on
4.12
had its build status changed:
passing
to
partially failing
devkit.1.2
on
4.13
had its build status changed:
passing
to
partially failing
devkit.1.2
on
4.14
had its build status changed:
passing
to
partially failing
devkit.1.20210120
on
4.08
had its build status changed:
passing
to
partially failing
devkit.1.20210120
on
4.09
had its build status changed:
passing
to
partially failing
devkit.1.20210120
on
4.10
had its build status changed:
passing
to
partially failing
devkit.1.20210120
on
4.11
had its build status changed:
passing
to
partially failing
devkit.1.20210120
on
4.12
had its build status changed:
passing
to
partially failing
devkit.1.20210120
on
4.13
had its build status changed:
passing
to
partially failing
devkit.1.20210120
on
4.14
had its build status changed:
passing
to
partially failing
devkit.1.20210517
on
4.08
had its build status changed:
passing
to
partially failing
devkit.1.20210517
on
4.09
had its build status changed:
passing
to
partially failing
devkit.1.20210517
on
4.10
had its build status changed:
passing
to
partially failing
devkit.1.20210517
on
4.11
had its build status changed:
passing
to
partially failing
devkit.1.20210517
on
4.12
had its build status changed:
passing
to
partially failing
devkit.1.20210517
on
4.13
had its build status changed:
passing
to
partially failing
devkit.1.20210517
on
4.14
had its build status changed:
passing
to
partially failing
devkit.1.3
on
4.08
had its build status changed:
passing
to
partially failing
devkit.1.3
on
4.09
had its build status changed:
passing
to
partially failing
devkit.1.3
on
4.10
had its build status changed:
passing
to
partially failing
devkit.1.3
on
4.11
had its build status changed:
passing
to
partially failing
devkit.1.3
on
4.12
had its build status changed:
passing
to
partially failing
devkit.1.3
on
4.13
had its build status changed:
passing
to
partially failing
devkit.1.3
on
4.14
had its build status changed:
passing
to
partially failing
dirsp-ps2ocaml.0.1.0
on
4.08
had its build status changed:
passing
to
partially failing
dirsp-ps2ocaml.0.1.0
on
4.09
had its build status changed:
passing
to
partially failing
dirsp-ps2ocaml.0.1.0
on
4.10
had its build status changed:
passing
to
partially failing
dirsp-ps2ocaml.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
dirsp-ps2ocaml.0.1.0
on
4.12
had its build status changed:
passing
to
partially failing
dirsp-ps2ocaml.0.1.0
on
4.13
had its build status changed:
passing
to
partially failing
dirsp-ps2ocaml.0.1.0
on
4.14
had its build status changed:
passing
to
partially failing
dirsp-ps2ocaml.0.1.0
on
5.0
had its build status changed:
not available
to
partially failing
dns-certify.4.0.0
on
4.08
had its build status changed:
passing
to
partially failing
dns-certify.4.0.0
on
4.09
had its build status changed:
passing
to
partially failing
dns-certify.4.0.0
on
4.10
had its build status changed:
passing
to
partially failing
dns-certify.4.0.0
on
4.11
had its build status changed:
passing
to
partially failing
dns-certify.4.1.0
on
4.08
had its build status changed:
passing
to
partially failing
dns-certify.4.1.0
on
4.09
had its build status changed:
passing
to
partially failing
dns-certify.4.1.0
on
4.10
had its build status changed:
passing
to
partially failing
dns-certify.4.1.0
on
4.11
had its build status changed:
passing
to
partially failing
dns-certify.4.2.0
on
4.08
had its build status changed:
passing
to
partially failing
dns-certify.4.2.0
on
4.09
had its build status changed:
passing
to
partially failing
dns-certify.4.2.0
on
4.10
had its build status changed:
passing
to
partially failing
dns-certify.4.2.0
on
4.11
had its build status changed:
passing
to
partially failing
dns-certify.4.3.0
on
4.08
had its build status changed:
passing
to
partially failing
dns-certify.4.3.0
on
4.09
had its build status changed:
passing
to
partially failing
dns-certify.4.3.0
on
4.10
had its build status changed:
passing
to
partially failing
dns-certify.4.3.0
on
4.11
had its build status changed:
passing
to
partially failing
dns-certify.4.3.1
on
4.08
had its build status changed:
passing
to
partially failing
dns-certify.4.3.1
on
4.09
had its build status changed:
passing
to
partially failing
dns-certify.4.3.1
on
4.10
had its build status changed:
passing
to
partially failing
dns-certify.4.3.1
on
4.11
had its build status changed:
passing
to
partially failing
dns-cli.4.0.0
on
4.08
had its build status changed:
passing
to
partially failing
dns-cli.4.0.0
on
4.09
had its build status changed:
passing
to
partially failing
dns-cli.4.0.0
on
4.10
had its build status changed:
passing
to
partially failing
dns-cli.4.0.0
on
4.11
had its build status changed:
passing
to
partially failing
dns-cli.4.1.0
on
4.08
had its build status changed:
passing
to
partially failing
dns-cli.4.1.0
on
4.09
had its build status changed:
passing
to
partially failing
dns-cli.4.1.0
on
4.10
had its build status changed:
passing
to
partially failing
dns-cli.4.1.0
on
4.11
had its build status changed:
passing
to
partially failing
dns-cli.4.2.0
on
4.08
had its build status changed:
passing
to
partially failing
dns-cli.4.2.0
on
4.09
had its build status changed:
passing
to
partially failing
dns-cli.4.2.0
on
4.10
had its build status changed:
passing
to
partially failing
dns-cli.4.2.0
on
4.11
had its build status changed:
passing
to
partially failing
dns-cli.4.3.0
on
4.08
had its build status changed:
passing
to
partially failing
dns-cli.4.3.0
on
4.09
had its build status changed:
passing
to
partially failing
dns-cli.4.3.0
on
4.10
had its build status changed:
passing
to
partially failing
dns-cli.4.3.0
on
4.11
had its build status changed:
passing
to
partially failing
dns-cli.4.3.1
on
4.08
had its build status changed:
passing
to
partially failing
dns-cli.4.3.1
on
4.09
had its build status changed:
passing
to
partially failing
dns-cli.4.3.1
on
4.10
had its build status changed:
passing
to
partially failing
dns-cli.4.3.1
on
4.11
had its build status changed:
passing
to
partially failing
dokeysto_lz4.3.0.0
on
4.08
had its build status changed:
passing
to
partially failing
dokeysto_lz4.3.0.0
on
4.09
had its build status changed:
passing
to
partially failing
dokeysto_lz4.3.0.0
on
4.10
had its build status changed:
passing
to
partially failing
dokeysto_lz4.3.0.0
on
4.11
had its build status changed:
passing
to
partially failing
duppy.0.7.0
on
4.08
had its build status changed:
passing
to
partially failing
duppy.0.7.0
on
4.09
had its build status changed:
passing
to
partially failing
duppy.0.7.0
on
4.10
had its build status changed:
passing
to
partially failing
duppy.0.7.0
on
4.11
had its build status changed:
passing
to
partially failing
duppy.0.7.0
on
4.12
had its build status changed:
passing
to
partially failing
duppy.0.7.0
on
4.13
had its build status changed:
passing
to
partially failing
duppy.0.7.0
on
4.14
had its build status changed:
passing
to
partially failing
duppy.0.7.0
on
5.0
had its build status changed:
not available
to
partially failing
duppy.0.7.1
on
4.08
had its build status changed:
passing
to
partially failing
duppy.0.7.1
on
4.09
had its build status changed:
passing
to
partially failing
duppy.0.7.1
on
4.10
had its build status changed:
passing
to
partially failing
duppy.0.7.1
on
4.11
had its build status changed:
passing
to
partially failing
duppy.0.7.1
on
4.12
had its build status changed:
passing
to
partially failing
duppy.0.7.1
on
4.13
had its build status changed:
passing
to
partially failing
duppy.0.7.1
on
4.14
had its build status changed:
passing
to
partially failing
duppy.0.7.1
on
5.0
had its build status changed:
not available
to
partially failing
duppy.0.7.3
on
4.08
had its build status changed:
passing
to
partially failing
duppy.0.7.3
on
4.09
had its build status changed:
passing
to
partially failing
duppy.0.7.3
on
4.10
had its build status changed:
passing
to
partially failing
duppy.0.7.3
on
4.11
had its build status changed:
passing
to
partially failing
duppy.0.7.3
on
4.12
had its build status changed:
passing
to
partially failing
duppy.0.7.3
on
4.13
had its build status changed:
passing
to
partially failing
duppy.0.7.3
on
4.14
had its build status changed:
passing
to
partially failing
duppy.0.7.3
on
5.0
had its build status changed:
not available
to
partially failing
dyntype.0.9.0
on
4.08
had its build status changed:
passing
to
partially failing
dyntype.0.9.0
on
4.09
had its build status changed:
passing
to
partially failing
dyntype.0.9.0
on
4.10
had its build status changed:
passing
to
partially failing
dyntype.0.9.0
on
4.11
had its build status changed:
passing
to
partially failing
dyntype.0.9.0
on
4.12
had its build status changed:
passing
to
partially failing
dyntype.0.9.0
on
4.13
had its build status changed:
passing
to
partially failing
dyntype.0.9.0
on
4.14
had its build status changed:
passing
to
partially failing
dyntype.0.9.0
on
5.0
had its build status changed:
not available
to
partially failing
elasticsearch-cli.0.5
on
4.08
had its build status changed:
passing
to
partially failing
elasticsearch-cli.0.5
on
4.09
had its build status changed:
passing
to
partially failing
elasticsearch-cli.0.5
on
4.10
had its build status changed:
passing
to
partially failing
elasticsearch-cli.0.5
on
4.11
had its build status changed:
passing
to
partially failing
elasticsearch-cli.0.5
on
4.12
had its build status changed:
passing
to
partially failing
elasticsearch-cli.0.5
on
4.13
had its build status changed:
passing
to
partially failing
elasticsearch-cli.0.5
on
4.14
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.0
on
4.08
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.0
on
4.09
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.0
on
4.10
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.0
on
4.11
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.0
on
4.12
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.0
on
4.13
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.0
on
4.14
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.1
on
4.08
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.1
on
4.09
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.1
on
4.10
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.1
on
4.11
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.1
on
4.12
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.1
on
4.13
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.1
on
4.14
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.2
on
4.08
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.2
on
4.09
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.2
on
4.10
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.2
on
4.11
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.2
on
4.12
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.2
on
4.13
had its build status changed:
passing
to
partially failing
elasticsearch-cli.1.2
on
4.14
had its build status changed:
passing
to
partially failing
eliom.6.10.1
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.10.1
on
4.09
had its build status changed:
passing
to
partially failing
eliom.6.10.1
on
4.10
had its build status changed:
passing
to
partially failing
eliom.6.11.0
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.11.0
on
4.09
had its build status changed:
passing
to
partially failing
eliom.6.11.0
on
4.10
had its build status changed:
passing
to
partially failing
eliom.6.12.0
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.12.0
on
4.09
had its build status changed:
passing
to
partially failing
eliom.6.12.0
on
4.10
had its build status changed:
passing
to
partially failing
eliom.6.12.1
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.12.1
on
4.09
had its build status changed:
passing
to
partially failing
eliom.6.12.1
on
4.10
had its build status changed:
passing
to
partially failing
eliom.6.12.1
on
4.11
had its build status changed:
passing
to
partially failing
eliom.6.12.4
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.12.4
on
4.09
had its build status changed:
passing
to
partially failing
eliom.6.12.4
on
4.10
had its build status changed:
passing
to
partially failing
eliom.6.12.4
on
4.11
had its build status changed:
passing
to
partially failing
eliom.6.13.1
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.13.1
on
4.09
had its build status changed:
passing
to
partially failing
eliom.6.13.1
on
4.10
had its build status changed:
passing
to
partially failing
eliom.6.13.1
on
4.11
had its build status changed:
passing
to
partially failing
eliom.6.8.0
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.8.1
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.9.1
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.9.2
on
4.08
had its build status changed:
passing
to
partially failing
eliom.6.9.3
on
4.08
had its build status changed:
passing
to
partially failing
eliom.7.0.0
on
4.08
had its build status changed:
passing
to
partially failing
eliom.7.0.0
on
4.09
had its build status changed:
passing
to
partially failing
eliom.7.0.0
on
4.10
had its build status changed:
passing
to
partially failing
eliom.7.0.0
on
4.11
had its build status changed:
passing
to
partially failing
eliom.7.0.0
on
4.12
had its build status changed:
passing
to
partially failing
extprot.1.6.0
on
4.08
had its build status changed:
passing
to
partially failing
extprot.1.6.0
on
4.09
had its build status changed:
passing
to
partially failing
extprot.1.6.0
on
4.10
had its build status changed:
passing
to
partially failing
extprot.1.6.0
on
4.11
had its build status changed:
passing
to
partially failing
extprot.1.6.0
on
4.12
had its build status changed:
passing
to
partially failing
extprot.1.6.0
on
4.13
had its build status changed:
passing
to
partially failing
extprot.1.6.0
on
4.14
had its build status changed:
passing
to
partially failing
extprot.1.7.0
on
4.08
had its build status changed:
passing
to
partially failing
extprot.1.7.0
on
4.09
had its build status changed:
passing
to
partially failing
extprot.1.7.0
on
4.10
had its build status changed:
passing
to
partially failing
extprot.1.7.0
on
4.11
had its build status changed:
passing
to
partially failing
extprot.1.7.0
on
4.12
had its build status changed:
passing
to
partially failing
extprot.1.7.0
on
4.13
had its build status changed:
passing
to
partially failing
extprot.1.7.0
on
4.14
had its build status changed:
passing
to
partially failing
extprot.1.7.0
on
5.0
had its build status changed:
not available
to
partially failing
extunix.0.1.4
on
4.08
had its build status changed:
passing
to
partially failing
extunix.0.1.4
on
4.09
had its build status changed:
passing
to
partially failing
extunix.0.1.4
on
4.10
had its build status changed:
passing
to
partially failing
extunix.0.1.4
on
4.11
had its build status changed:
passing
to
partially failing
extunix.0.1.4
on
4.12
had its build status changed:
passing
to
partially failing
extunix.0.1.4
on
4.13
had its build status changed:
passing
to
partially failing
extunix.0.1.4
on
4.14
had its build status changed:
passing
to
partially failing
extunix.0.1.5
on
4.08
had its build status changed:
passing
to
partially failing
extunix.0.1.5
on
4.09
had its build status changed:
passing
to
partially failing
extunix.0.1.5
on
4.10
had its build status changed:
passing
to
partially failing
extunix.0.1.5
on
4.11
had its build status changed:
passing
to
partially failing
extunix.0.1.5
on
4.12
had its build status changed:
passing
to
partially failing
extunix.0.1.5
on
4.13
had its build status changed:
passing
to
partially failing
extunix.0.1.5
on
4.14
had its build status changed:
passing
to
partially failing
extunix.0.1.6
on
4.08
had its build status changed:
passing
to
partially failing
extunix.0.1.6
on
4.09
had its build status changed:
passing
to
partially failing
extunix.0.1.6
on
4.10
had its build status changed:
passing
to
partially failing
extunix.0.1.6
on
4.11
had its build status changed:
passing
to
partially failing
extunix.0.1.6
on
4.12
had its build status changed:
passing
to
partially failing
extunix.0.1.6
on
4.13
had its build status changed:
passing
to
partially failing
extunix.0.1.6
on
4.14
had its build status changed:
passing
to
partially failing
facteur.0.1.0
on
4.08
had its build status changed:
passing
to
partially failing
facteur.0.1.0
on
4.09
had its build status changed:
passing
to
partially failing
facteur.0.1.0
on
4.10
had its build status changed:
passing
to
partially failing
facteur.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
flow_parser.0.159.0
on
4.11
had its build status changed:
passing
to
partially failing
flow_parser.0.159.0
on
4.12
had its build status changed:
passing
to
partially failing
fm-simplex-plugin.1.30
on
4.13
had its build status changed:
passing
to
partially failing
fm-simplex-plugin.1.30
on
4.14
had its build status changed:
passing
to
partially failing
format.0.1
on
4.08
had its build status changed:
passing
to
partially failing
format.0.1
on
4.09
had its build status changed:
passing
to
partially failing
format.0.1
on
4.10
had its build status changed:
passing
to
partially failing
format.0.1
on
4.11
had its build status changed:
passing
to
partially failing
format.0.1
on
4.12
had its build status changed:
passing
to
partially failing
format.0.1
on
4.13
had its build status changed:
passing
to
partially failing
format.0.1
on
4.14
had its build status changed:
passing
to
partially failing
format.0.1
on
5.0
had its build status changed:
not available
to
partially failing
frama-clang.0.0.14
on
4.11
is now installable. Current state is:
partially failing
frama-clang.0.0.14
on
4.12
is now installable. Current state is:
partially failing
frama-clang.0.0.14
on
4.13
is now installable. Current state is:
partially failing
frama-clang.0.0.14
on
4.14
is now installable. Current state is:
partially failing
frama-clang.0.0.14
on
5.0
is now installable. Current state is:
partially failing
frama-clang.0.0.14
on
5.1
is now installable. Current state is:
partially failing
gapi-ocaml.0.3.10
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.10
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.10
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.10
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.10
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.10
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.10
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.11
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.11
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.11
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.11
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.11
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.11
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.11
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.12
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.12
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.12
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.12
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.12
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.12
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.12
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.13
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.13
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.13
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.13
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.13
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.13
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.13
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.14
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.14
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.14
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.14
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.14
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.14
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.14
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.15
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.15
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.15
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.15
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.15
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.15
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.15
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.16
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.16
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.16
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.16
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.16
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.16
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.16
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.17
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.17
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.17
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.17
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.17
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.17
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.17
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.18
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.18
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.18
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.18
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.18
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.18
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.18
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.19
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.19
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.19
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.19
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.19
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.19
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.19
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.5
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.5
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.5
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.5
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.5
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.5
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.5
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.6
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.6
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.6
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.6
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.6
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.6
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.6
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.7
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.7
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.7
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.7
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.7
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.7
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.7
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.8
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.8
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.8
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.8
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.8
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.8
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.8
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.9
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.9
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.9
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.9
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.9
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.9
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.3.9
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.1
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.1
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.1
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.1
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.1
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.1
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.1
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.2
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.2
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.2
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.2
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.2
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.2
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.2
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.3
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.3
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.3
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.3
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.3
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.3
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.3
on
4.14
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.4
on
4.08
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.4
on
4.09
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.4
on
4.10
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.4
on
4.11
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.4
on
4.12
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.4
on
4.13
had its build status changed:
passing
to
partially failing
gapi-ocaml.0.4.4
on
4.14
had its build status changed:
passing
to
partially failing
get_line.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
get_line.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
get_line.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
get_line.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
get_line.1.0.0
on
4.12
had its build status changed:
passing
to
partially failing
get_line.1.0.0
on
4.13
had its build status changed:
passing
to
partially failing
get_line.1.0.0
on
4.14
had its build status changed:
passing
to
partially failing
get_line.1.0.0
on
5.0
had its build status changed:
not available
to
partially failing
get_line.2.1.1
on
4.08
had its build status changed:
passing
to
partially failing
get_line.2.1.1
on
4.09
had its build status changed:
passing
to
partially failing
get_line.2.1.1
on
4.10
had its build status changed:
passing
to
partially failing
get_line.2.1.1
on
4.11
had its build status changed:
passing
to
partially failing
get_line.2.1.1
on
4.12
had its build status changed:
passing
to
partially failing
get_line.2.1.1
on
4.13
had its build status changed:
passing
to
partially failing
get_line.2.1.1
on
4.14
had its build status changed:
passing
to
partially failing
get_line.2.1.1
on
5.0
had its build status changed:
not available
to
partially failing
get_line.3.0.0
on
4.08
had its build status changed:
passing
to
partially failing
get_line.3.0.0
on
4.09
had its build status changed:
passing
to
partially failing
get_line.3.0.0
on
4.10
had its build status changed:
passing
to
partially failing
get_line.3.0.0
on
4.11
had its build status changed:
passing
to
partially failing
get_line.3.0.0
on
4.12
had its build status changed:
passing
to
partially failing
get_line.3.0.0
on
4.13
had its build status changed:
passing
to
partially failing
get_line.3.0.0
on
4.14
had its build status changed:
passing
to
partially failing
get_line.3.0.0
on
5.0
had its build status changed:
not available
to
partially failing
gettext.0.3.8
on
4.08
had its build status changed:
passing
to
partially failing
gettext.0.3.8
on
4.09
had its build status changed:
passing
to
partially failing
gettext.0.3.8
on
4.10
had its build status changed:
passing
to
partially failing
gettext.0.3.8
on
4.11
had its build status changed:
passing
to
partially failing
gettext.0.3.8
on
4.12
had its build status changed:
passing
to
partially failing
gettext.0.3.8
on
4.13
had its build status changed:
passing
to
partially failing
gettext.0.3.8
on
4.14
had its build status changed:
passing
to
partially failing
git-mirage.2.0.0
on
4.08
had its build status changed:
passing
to
partially failing
git-mirage.2.0.0
on
4.09
had its build status changed:
passing
to
partially failing
git-mirage.2.0.0
on
4.10
had its build status changed:
passing
to
partially failing
git-mirage.2.0.0
on
4.11
had its build status changed:
passing
to
partially failing
git-mirage.2.1.0
on
4.08
had its build status changed:
passing
to
partially failing
git-mirage.2.1.0
on
4.09
had its build status changed:
passing
to
partially failing
git-mirage.2.1.0
on
4.10
had its build status changed:
passing
to
partially failing
git-mirage.2.1.0
on
4.11
had its build status changed:
passing
to
partially failing
git-mirage.2.1.1
on
4.08
had its build status changed:
passing
to
partially failing
git-mirage.2.1.1
on
4.09
had its build status changed:
passing
to
partially failing
git-mirage.2.1.1
on
4.10
had its build status changed:
passing
to
partially failing
git-mirage.2.1.1
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.22
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.22
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.22
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.22
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.22
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.22
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.22
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.23
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.23
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.23
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.23
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.23
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.23
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.23
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.26
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.26
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.26
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.26
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.26
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.26
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.6.26
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.1
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.1
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.1
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.1
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.1
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.1
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.1
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.11
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.11
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.11
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.11
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.11
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.11
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.11
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.13
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.13
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.13
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.13
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.13
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.13
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.13
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.14
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.14
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.14
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.14
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.14
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.14
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.14
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.15
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.15
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.15
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.15
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.15
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.15
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.15
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.16
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.16
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.16
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.16
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.16
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.16
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.16
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.17
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.17
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.17
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.17
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.17
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.17
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.17
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.18
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.18
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.18
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.18
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.18
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.18
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.18
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.19
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.19
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.19
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.19
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.19
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.19
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.19
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.2
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.2
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.2
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.2
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.2
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.2
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.2
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.20
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.20
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.20
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.20
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.20
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.20
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.20
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.21
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.21
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.21
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.21
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.21
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.21
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.21
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.22
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.22
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.22
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.22
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.22
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.22
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.22
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.23
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.23
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.23
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.23
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.23
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.23
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.23
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.24
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.24
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.24
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.24
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.24
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.24
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.24
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.25
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.25
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.25
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.25
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.25
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.25
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.25
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.26
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.26
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.26
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.26
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.26
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.26
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.26
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.27
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.27
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.27
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.27
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.27
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.27
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.27
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.28
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.28
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.28
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.28
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.28
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.28
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.28
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.29
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.29
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.29
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.29
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.29
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.29
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.29
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.3
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.3
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.3
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.3
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.3
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.3
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.3
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.30
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.30
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.30
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.30
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.30
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.30
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.30
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.4
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.4
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.4
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.4
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.4
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.4
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.4
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.5
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.5
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.5
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.5
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.5
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.5
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.5
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.6
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.6
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.6
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.6
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.6
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.6
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.6
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.7
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.7
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.7
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.7
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.7
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.7
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.7
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.8
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.8
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.8
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.8
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.8
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.8
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.8
on
4.14
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.9
on
4.08
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.9
on
4.09
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.9
on
4.10
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.9
on
4.11
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.9
on
4.12
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.9
on
4.13
had its build status changed:
passing
to
partially failing
google-drive-ocamlfuse.0.7.9
on
4.14
had its build status changed:
passing
to
partially failing
h2-mirage.0.1.0
on
4.08
had its build status changed:
passing
to
partially failing
h2-mirage.0.1.0
on
4.09
had its build status changed:
passing
to
partially failing
h2-mirage.0.1.0
on
4.10
had its build status changed:
passing
to
partially failing
h2-mirage.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
h2-mirage.0.2.0
on
4.08
had its build status changed:
passing
to
partially failing
h2-mirage.0.2.0
on
4.09
had its build status changed:
passing
to
partially failing
h2-mirage.0.2.0
on
4.10
had its build status changed:
passing
to
partially failing
h2-mirage.0.2.0
on
4.11
had its build status changed:
passing
to
partially failing
h2-mirage.0.3.0
on
4.08
had its build status changed:
passing
to
partially failing
h2-mirage.0.3.0
on
4.09
had its build status changed:
passing
to
partially failing
h2-mirage.0.3.0
on
4.10
had its build status changed:
passing
to
partially failing
h2-mirage.0.3.0
on
4.11
had its build status changed:
passing
to
partially failing
hacl-star.0.1
on
4.13
had its build status changed:
passing
to
partially failing
hacl-star.0.1.1
on
4.11
had its build status changed:
passing
to
partially failing
hacl-star.0.2.0
on
4.08
had its build status changed:
passing
to
partially failing
hacl-star.0.2.1
on
4.13
had its build status changed:
passing
to
partially failing
hashset.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
hashset.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
hashset.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
hashset.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
hashset.1.0.0
on
4.12
had its build status changed:
passing
to
partially failing
hashset.1.0.0
on
4.13
had its build status changed:
passing
to
partially failing
hashset.1.0.0
on
4.14
had its build status changed:
passing
to
partially failing
haxe.3.4.7
on
4.08
had its build status changed:
passing
to
partially failing
haxe.3.4.7
on
4.09
had its build status changed:
passing
to
partially failing
heptagon.1.03.03
on
4.08
had its build status changed:
passing
to
partially failing
heptagon.1.03.03
on
4.09
had its build status changed:
passing
to
partially failing
heptagon.1.03.03
on
4.10
had its build status changed:
passing
to
partially failing
heptagon.1.03.03
on
4.11
had its build status changed:
passing
to
partially failing
heptagon.1.03.03
on
4.12
had its build status changed:
passing
to
partially failing
heptagon.1.03.03
on
4.13
had its build status changed:
passing
to
partially failing
heptagon.1.03.03
on
4.14
had its build status changed:
passing
to
partially failing
heptagon.1.03.03
on
5.0
had its build status changed:
not available
to
partially failing
heptagon.1.03.04
on
4.08
had its build status changed:
passing
to
partially failing
heptagon.1.03.04
on
4.09
had its build status changed:
passing
to
partially failing
heptagon.1.03.04
on
4.10
had its build status changed:
passing
to
partially failing
heptagon.1.03.04
on
4.11
had its build status changed:
passing
to
partially failing
heptagon.1.03.04
on
4.12
had its build status changed:
passing
to
partially failing
heptagon.1.03.04
on
4.13
had its build status changed:
passing
to
partially failing
heptagon.1.03.04
on
4.14
had its build status changed:
passing
to
partially failing
heptagon.1.03.04
on
5.0
had its build status changed:
not available
to
partially failing
heptagon.1.04.00
on
4.08
had its build status changed:
passing
to
partially failing
heptagon.1.04.00
on
4.09
had its build status changed:
passing
to
partially failing
heptagon.1.04.00
on
4.10
had its build status changed:
passing
to
partially failing
heptagon.1.04.00
on
4.11
had its build status changed:
passing
to
partially failing
heptagon.1.04.00
on
4.12
had its build status changed:
passing
to
partially failing
heptagon.1.04.00
on
4.13
had its build status changed:
passing
to
partially failing
heptagon.1.04.00
on
4.14
had its build status changed:
passing
to
partially failing
heptagon.1.04.00
on
5.0
had its build status changed:
not available
to
partially failing
heptagon.1.05.00
on
4.08
had its build status changed:
passing
to
partially failing
heptagon.1.05.00
on
4.09
had its build status changed:
passing
to
partially failing
heptagon.1.05.00
on
4.10
had its build status changed:
passing
to
partially failing
heptagon.1.05.00
on
4.11
had its build status changed:
passing
to
partially failing
heptagon.1.05.00
on
4.12
had its build status changed:
passing
to
partially failing
heptagon.1.05.00
on
4.13
had its build status changed:
passing
to
partially failing
heptagon.1.05.00
on
4.14
had its build status changed:
passing
to
partially failing
heptagon.1.05.00
on
5.0
had its build status changed:
not available
to
partially failing
higlo.0.1
on
4.08
had its build status changed:
passing
to
partially failing
higlo.0.1
on
4.09
had its build status changed:
passing
to
partially failing
higlo.0.1
on
4.10
had its build status changed:
passing
to
partially failing
higlo.0.1
on
4.11
had its build status changed:
passing
to
partially failing
higlo.0.1
on
4.12
had its build status changed:
passing
to
partially failing
higlo.0.1
on
4.13
had its build status changed:
passing
to
partially failing
higlo.0.1
on
4.14
had its build status changed:
passing
to
partially failing
higlo.0.1
on
5.0
had its build status changed:
not available
to
partially failing
higlo.0.2
on
4.08
had its build status changed:
passing
to
partially failing
higlo.0.2
on
4.09
had its build status changed:
passing
to
partially failing
higlo.0.2
on
4.10
had its build status changed:
passing
to
partially failing
higlo.0.2
on
4.11
had its build status changed:
passing
to
partially failing
higlo.0.2
on
4.12
had its build status changed:
passing
to
partially failing
higlo.0.2
on
4.13
had its build status changed:
passing
to
partially failing
higlo.0.2
on
4.14
had its build status changed:
passing
to
partially failing
higlo.0.2
on
5.0
had its build status changed:
not available
to
partially failing
higlo.0.4
on
4.08
had its build status changed:
passing
to
partially failing
higlo.0.4
on
4.09
had its build status changed:
passing
to
partially failing
higlo.0.4
on
4.10
had its build status changed:
passing
to
partially failing
higlo.0.4
on
4.11
had its build status changed:
passing
to
partially failing
higlo.0.4
on
4.12
had its build status changed:
passing
to
partially failing
higlo.0.4
on
4.13
had its build status changed:
passing
to
partially failing
higlo.0.4
on
4.14
had its build status changed:
passing
to
partially failing
higlo.0.4
on
5.0
had its build status changed:
not available
to
partially failing
higlo.0.5
on
4.12
had its build status changed:
passing
to
partially failing
higlo.0.5
on
4.13
had its build status changed:
passing
to
partially failing
higlo.0.5
on
4.14
had its build status changed:
passing
to
partially failing
higlo.0.5
on
5.0
had its build status changed:
not available
to
partially failing
higlo.0.6
on
4.12
had its build status changed:
passing
to
partially failing
higlo.0.6
on
4.13
had its build status changed:
passing
to
partially failing
higlo.0.6
on
4.14
had its build status changed:
passing
to
partially failing
higlo.0.6
on
5.0
had its build status changed:
not available
to
partially failing
hts_shrink.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
hts_shrink.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
hts_shrink.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
hts_shrink.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
hts_shrink.2.1.0
on
4.08
had its build status changed:
passing
to
partially failing
hts_shrink.2.1.0
on
4.09
had its build status changed:
passing
to
partially failing
hts_shrink.2.1.0
on
4.10
had its build status changed:
passing
to
partially failing
hts_shrink.2.1.0
on
4.11
had its build status changed:
passing
to
partially failing
hts_shrink.2.1.0
on
4.12
had its build status changed:
passing
to
partially failing
hts_shrink.2.1.0
on
4.13
had its build status changed:
passing
to
partially failing
hts_shrink.2.1.0
on
4.14
had its build status changed:
passing
to
partially failing
integration1d.0.5
on
4.08
had its build status changed:
passing
to
partially failing
integration1d.0.5
on
4.09
had its build status changed:
passing
to
partially failing
integration1d.0.5
on
4.10
had its build status changed:
passing
to
partially failing
integration1d.0.5
on
4.11
had its build status changed:
passing
to
partially failing
integration1d.0.5
on
4.12
had its build status changed:
passing
to
partially failing
integration1d.0.5
on
4.13
had its build status changed:
passing
to
partially failing
integration1d.0.5
on
4.14
had its build status changed:
passing
to
partially failing
io.0.2.0
on
4.08
had its build status changed:
passing
to
partially failing
io.0.2.0
on
4.09
had its build status changed:
passing
to
partially failing
io.0.2.0
on
4.10
had its build status changed:
passing
to
partially failing
io.0.2.0
on
4.11
had its build status changed:
passing
to
partially failing
io.0.2.0
on
4.12
had its build status changed:
passing
to
partially failing
io.0.2.0
on
4.13
had its build status changed:
passing
to
partially failing
io.0.2.0
on
4.14
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.0
on
4.08
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.0
on
4.09
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.0
on
4.10
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.0
on
4.11
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.1
on
4.08
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.1
on
4.09
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.1
on
4.10
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.1
on
4.11
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.2
on
4.08
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.2
on
4.09
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.2
on
4.10
had its build status changed:
passing
to
partially failing
irc-client-tls.0.6.2
on
4.11
had its build status changed:
passing
to
partially failing
javalib.2.3.6
on
4.08
had its build status changed:
passing
to
partially failing
javalib.2.3.6
on
4.09
had its build status changed:
passing
to
partially failing
javalib.2.3.6
on
4.10
had its build status changed:
passing
to
partially failing
javalib.2.3.6
on
4.11
had its build status changed:
passing
to
partially failing
javalib.2.3.6
on
4.12
had its build status changed:
passing
to
partially failing
javalib.2.3.6
on
4.13
had its build status changed:
passing
to
partially failing
javalib.2.3.6
on
4.14
had its build status changed:
passing
to
partially failing
javalib.3.0
on
4.08
had its build status changed:
passing
to
partially failing
javalib.3.0
on
4.09
had its build status changed:
passing
to
partially failing
javalib.3.0
on
4.10
had its build status changed:
passing
to
partially failing
javalib.3.0
on
4.11
had its build status changed:
passing
to
partially failing
javalib.3.0
on
4.12
had its build status changed:
passing
to
partially failing
javalib.3.0
on
4.13
had its build status changed:
passing
to
partially failing
javalib.3.0
on
4.14
had its build status changed:
passing
to
partially failing
javalib.3.1
on
4.08
had its build status changed:
passing
to
partially failing
javalib.3.1
on
4.09
had its build status changed:
passing
to
partially failing
javalib.3.1
on
4.10
had its build status changed:
passing
to
partially failing
javalib.3.1
on
4.11
had its build status changed:
passing
to
partially failing
javalib.3.1
on
4.12
had its build status changed:
passing
to
partially failing
javalib.3.1
on
4.13
had its build status changed:
passing
to
partially failing
javalib.3.1
on
4.14
had its build status changed:
passing
to
partially failing
javalib.3.1
on
5.0
had its build status changed:
not available
to
partially failing
js_of_ocaml-camlp4.3.0
on
4.08
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0
on
4.09
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0
on
4.10
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0
on
4.11
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0
on
4.12
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0
on
4.13
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0
on
4.14
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.1
on
4.08
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.1
on
4.09
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.1
on
4.10
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.1
on
4.11
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.1
on
4.12
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.1
on
4.13
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.1
on
4.14
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.2
on
4.08
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.2
on
4.09
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.2
on
4.10
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.2
on
4.11
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.2
on
4.12
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.2
on
4.13
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.0.2
on
4.14
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.1.0
on
4.08
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.1.0
on
4.09
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.1.0
on
4.10
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.1.0
on
4.11
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.1.0
on
4.12
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.1.0
on
4.13
had its build status changed:
passing
to
partially failing
js_of_ocaml-camlp4.3.1.0
on
4.14
had its build status changed:
passing
to
partially failing
json-static.0.9.8
on
4.08
had its build status changed:
passing
to
partially failing
json-static.0.9.8
on
4.09
had its build status changed:
passing
to
partially failing
json-static.0.9.8
on
4.10
had its build status changed:
passing
to
partially failing
json-static.0.9.8
on
4.11
had its build status changed:
passing
to
partially failing
json-static.0.9.8
on
4.12
had its build status changed:
passing
to
partially failing
json-static.0.9.8
on
4.13
had its build status changed:
passing
to
partially failing
json-static.0.9.8
on
4.14
had its build status changed:
passing
to
partially failing
json-wheel.1.0.6+safe-string
on
4.08
had its build status changed:
passing
to
partially failing
json-wheel.1.0.6+safe-string
on
4.09
had its build status changed:
passing
to
partially failing
json-wheel.1.0.6+safe-string
on
4.10
had its build status changed:
passing
to
partially failing
json-wheel.1.0.6+safe-string
on
4.11
had its build status changed:
passing
to
partially failing
json-wheel.1.0.6+safe-string
on
4.12
had its build status changed:
passing
to
partially failing
json-wheel.1.0.6+safe-string
on
4.13
had its build status changed:
passing
to
partially failing
json-wheel.1.0.6+safe-string
on
4.14
had its build status changed:
passing
to
partially failing
jupyter-archimedes.2.3.2
on
4.08
had its build status changed:
passing
to
partially failing
jupyter-archimedes.2.3.2
on
4.09
had its build status changed:
passing
to
partially failing
jupyter-archimedes.2.3.2
on
4.10
had its build status changed:
passing
to
partially failing
jupyter-archimedes.2.3.2
on
4.11
had its build status changed:
passing
to
partially failing
jupyter-archimedes.2.3.2
on
4.12
had its build status changed:
passing
to
partially failing
jupyter-archimedes.2.3.2
on
4.13
had its build status changed:
passing
to
partially failing
kinetic-client.0.0.1
on
5.0
had its build status changed:
not available
to
partially failing
kinetic-client.0.0.9
on
5.0
had its build status changed:
not available
to
partially failing
lablgl.1.04.20120306
on
4.08
had its build status changed:
passing
to
partially failing
lablgl.1.04.20120306
on
4.09
had its build status changed:
passing
to
partially failing
lablgl.1.04.20120306
on
4.10
had its build status changed:
passing
to
partially failing
lablgl.1.04.20120306
on
4.11
had its build status changed:
passing
to
partially failing
lablgl.1.04.20120306
on
4.12
had its build status changed:
passing
to
partially failing
lablgl.1.04.20120306
on
4.13
had its build status changed:
passing
to
partially failing
lablgl.1.04.20120306
on
4.14
had its build status changed:
passing
to
partially failing
lablgl.1.05
on
4.08
had its build status changed:
passing
to
partially failing
lablgl.1.05
on
4.09
had its build status changed:
passing
to
partially failing
lablgl.1.05
on
4.10
had its build status changed:
passing
to
partially failing
lablgl.1.05
on
4.11
had its build status changed:
passing
to
partially failing
lablgl.1.05
on
4.12
had its build status changed:
passing
to
partially failing
lablgl.1.05
on
4.13
had its build status changed:
passing
to
partially failing
lablgl.1.05
on
4.14
had its build status changed:
passing
to
partially failing
lambda-runtime.0.1.0
on
4.08
had its build status changed:
passing
to
partially failing
lambda-runtime.0.1.0
on
4.09
had its build status changed:
passing
to
partially failing
lambda-runtime.0.1.0
on
4.10
had its build status changed:
passing
to
partially failing
lambda-runtime.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
lambda-runtime.0.1.0
on
4.12
had its build status changed:
passing
to
partially failing
lambda-runtime.0.1.0
on
4.13
had its build status changed:
passing
to
partially failing
lambda-runtime.0.1.0
on
4.14
had its build status changed:
passing
to
partially failing
lambdapi.2.0.0
on
4.12
had its build status changed:
passing
to
partially failing
lambdapi.2.0.0
on
4.14
had its build status changed:
passing
to
partially failing
lascar.0.5
on
4.08
had its build status changed:
passing
to
partially failing
lascar.0.5
on
4.09
had its build status changed:
passing
to
partially failing
lascar.0.5
on
4.10
had its build status changed:
passing
to
partially failing
lascar.0.5
on
4.11
had its build status changed:
passing
to
partially failing
lascar.0.5
on
4.12
had its build status changed:
passing
to
partially failing
lascar.0.5
on
4.13
had its build status changed:
passing
to
partially failing
lascar.0.5
on
4.14
had its build status changed:
passing
to
partially failing
lascar.0.5
on
5.0
had its build status changed:
not available
to
partially failing
lbfgs.0.9
on
4.08
had its build status changed:
passing
to
partially failing
lbfgs.0.9
on
4.09
had its build status changed:
passing
to
partially failing
lbfgs.0.9
on
4.10
had its build status changed:
passing
to
partially failing
lbfgs.0.9
on
4.11
had its build status changed:
passing
to
partially failing
lbfgs.0.9.1
on
4.08
had its build status changed:
passing
to
partially failing
lbfgs.0.9.1
on
4.09
had its build status changed:
passing
to
partially failing
lbfgs.0.9.1
on
4.10
had its build status changed:
passing
to
partially failing
lbfgs.0.9.1
on
4.11
had its build status changed:
passing
to
partially failing
lbfgs.0.9.1
on
4.12
had its build status changed:
passing
to
partially failing
lbfgs.0.9.1
on
4.13
had its build status changed:
passing
to
partially failing
lbfgs.0.9.1
on
4.14
had its build status changed:
passing
to
partially failing
lbfgs.0.9.1
on
5.0
had its build status changed:
not available
to
partially failing
lbfgs.0.9.2
on
4.08
had its build status changed:
passing
to
partially failing
lbfgs.0.9.2
on
4.09
had its build status changed:
passing
to
partially failing
lbfgs.0.9.2
on
4.10
had its build status changed:
passing
to
partially failing
lbfgs.0.9.2
on
4.11
had its build status changed:
passing
to
partially failing
lbfgs.0.9.2
on
4.12
had its build status changed:
passing
to
partially failing
lbfgs.0.9.2
on
4.13
had its build status changed:
passing
to
partially failing
lbfgs.0.9.2
on
4.14
had its build status changed:
passing
to
partially failing
lbfgs.0.9.2
on
5.0
had its build status changed:
not available
to
partially failing
ldap.2.4.0
on
4.08
had its build status changed:
passing
to
partially failing
ldap.2.4.0
on
4.09
had its build status changed:
passing
to
partially failing
ldap.2.4.0
on
4.10
had its build status changed:
passing
to
partially failing
ldap.2.4.0
on
4.11
had its build status changed:
passing
to
partially failing
ldap.2.4.0
on
4.12
had its build status changed:
passing
to
partially failing
ldap.2.4.0
on
4.13
had its build status changed:
passing
to
partially failing
ldap.2.4.0
on
4.14
had its build status changed:
passing
to
partially failing
ldap.2.4.1
on
4.08
had its build status changed:
passing
to
partially failing
ldap.2.4.1
on
4.09
had its build status changed:
passing
to
partially failing
ldap.2.4.1
on
4.10
had its build status changed:
passing
to
partially failing
ldap.2.4.1
on
4.11
had its build status changed:
passing
to
partially failing
ldap.2.4.1
on
4.12
had its build status changed:
passing
to
partially failing
ldap.2.4.1
on
4.13
had its build status changed:
passing
to
partially failing
ldap.2.4.1
on
4.14
had its build status changed:
passing
to
partially failing
ldap.2.4.2
on
4.08
had its build status changed:
passing
to
partially failing
ldap.2.4.2
on
4.09
had its build status changed:
passing
to
partially failing
ldap.2.4.2
on
4.10
had its build status changed:
passing
to
partially failing
ldap.2.4.2
on
4.11
had its build status changed:
passing
to
partially failing
ldap.2.4.2
on
4.12
had its build status changed:
passing
to
partially failing
ldap.2.4.2
on
4.13
had its build status changed:
passing
to
partially failing
ldap.2.4.2
on
4.14
had its build status changed:
passing
to
partially failing
letters.0.1.0
on
4.08
had its build status changed:
passing
to
partially failing
letters.0.1.0
on
4.09
had its build status changed:
passing
to
partially failing
letters.0.1.0
on
4.10
had its build status changed:
passing
to
partially failing
letters.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
letters.0.1.0
on
4.12
had its build status changed:
passing
to
partially failing
letters.0.1.0
on
4.13
had its build status changed:
passing
to
partially failing
letters.0.1.0
on
4.14
had its build status changed:
passing
to
partially failing
letters.0.1.0
on
5.0
had its build status changed:
passing
to
partially failing
letters.0.1.0
on
5.1
had its build status changed:
passing
to
partially failing
letters.0.1.1
on
4.08
had its build status changed:
passing
to
partially failing
letters.0.1.1
on
4.09
had its build status changed:
passing
to
partially failing
letters.0.1.1
on
4.10
had its build status changed:
passing
to
partially failing
letters.0.1.1
on
4.11
had its build status changed:
passing
to
partially failing
letters.0.1.1
on
4.12
had its build status changed:
passing
to
partially failing
letters.0.1.1
on
4.13
had its build status changed:
passing
to
partially failing
letters.0.1.1
on
4.14
had its build status changed:
passing
to
partially failing
letters.0.1.1
on
5.0
had its build status changed:
passing
to
partially failing
letters.0.1.1
on
5.1
had its build status changed:
passing
to
partially failing
letters.0.2.0
on
4.08
had its build status changed:
passing
to
partially failing
letters.0.2.0
on
4.09
had its build status changed:
passing
to
partially failing
letters.0.2.0
on
4.10
had its build status changed:
passing
to
partially failing
letters.0.2.0
on
4.11
had its build status changed:
passing
to
partially failing
letters.0.2.0
on
4.12
had its build status changed:
passing
to
partially failing
letters.0.2.0
on
4.13
had its build status changed:
passing
to
partially failing
letters.0.2.0
on
4.14
had its build status changed:
passing
to
partially failing
letters.0.2.0
on
5.0
had its build status changed:
passing
to
partially failing
letters.0.2.0
on
5.1
had its build status changed:
passing
to
partially failing
libsail.0.15
on
4.08
had its build status changed:
passing
to
partially failing
libsail.0.15
on
4.09
had its build status changed:
passing
to
partially failing
libsail.0.15
on
4.10
had its build status changed:
passing
to
partially failing
libsail.0.15
on
4.11
had its build status changed:
passing
to
partially failing
libsail.0.15
on
4.12
had its build status changed:
passing
to
partially failing
libsail.0.15
on
4.13
had its build status changed:
passing
to
partially failing
libsail.0.15
on
4.14
had its build status changed:
passing
to
partially failing
libsail.0.15
on
5.0
had its build status changed:
passing
to
partially failing
libsail.0.15
on
5.1
had its build status changed:
passing
to
partially failing
libsail.0.16
on
4.08
had its build status changed:
passing
to
partially failing
libsail.0.16
on
4.09
had its build status changed:
passing
to
partially failing
libsail.0.16
on
4.10
had its build status changed:
passing
to
partially failing
libsail.0.16
on
4.11
had its build status changed:
passing
to
partially failing
libsail.0.16
on
4.12
had its build status changed:
passing
to
partially failing
libsail.0.16
on
4.13
had its build status changed:
passing
to
partially failing
libsail.0.16
on
4.14
had its build status changed:
passing
to
partially failing
libsail.0.16
on
5.0
had its build status changed:
passing
to
partially failing
libsail.0.16
on
5.1
had its build status changed:
passing
to
partially failing
libsail.0.17.1
on
4.08
is now installable. Current state is:
partially failing
libsail.0.17.1
on
4.09
is now installable. Current state is:
partially failing
libsail.0.17.1
on
4.10
is now installable. Current state is:
partially failing
libsail.0.17.1
on
4.11
is now installable. Current state is:
partially failing
libsail.0.17.1
on
4.12
is now installable. Current state is:
partially failing
libsail.0.17.1
on
4.13
is now installable. Current state is:
partially failing
libsail.0.17.1
on
4.14
is now installable. Current state is:
partially failing
libsail.0.17.1
on
5.0
is now installable. Current state is:
partially failing
libsail.0.17.1
on
5.1
is now installable. Current state is:
partially failing
linksem.0.7
on
4.08
had its build status changed:
passing
to
partially failing
linksem.0.7
on
4.09
had its build status changed:
passing
to
partially failing
linksem.0.7
on
4.10
had its build status changed:
passing
to
partially failing
linksem.0.7
on
4.11
had its build status changed:
passing
to
partially failing
linksem.0.7
on
4.12
had its build status changed:
passing
to
partially failing
linksem.0.7
on
4.13
had its build status changed:
passing
to
partially failing
linksem.0.7
on
4.14
had its build status changed:
passing
to
partially failing
linksem.0.8
on
4.08
had its build status changed:
passing
to
partially failing
linksem.0.8
on
4.09
had its build status changed:
passing
to
partially failing
linksem.0.8
on
4.10
had its build status changed:
passing
to
partially failing
linksem.0.8
on
4.11
had its build status changed:
passing
to
partially failing
linksem.0.8
on
4.12
had its build status changed:
passing
to
partially failing
linksem.0.8
on
4.13
had its build status changed:
passing
to
partially failing
linksem.0.8
on
4.14
had its build status changed:
passing
to
partially failing
linksem.0.8
on
5.0
had its build status changed:
passing
to
partially failing
linksem.0.8
on
5.1
had its build status changed:
passing
to
partially failing
linwrap.0.0.1
on
4.08
had its build status changed:
passing
to
partially failing
linwrap.0.0.1
on
4.09
had its build status changed:
passing
to
partially failing
linwrap.0.0.1
on
4.10
had its build status changed:
passing
to
partially failing
linwrap.0.0.1
on
4.11
had its build status changed:
passing
to
partially failing
linwrap.0.0.1
on
4.12
had its build status changed:
passing
to
partially failing
linwrap.0.0.1
on
4.13
had its build status changed:
passing
to
partially failing
linwrap.0.0.1
on
4.14
had its build status changed:
passing
to
partially failing
linwrap.2.0.0
on
4.08
had its build status changed:
passing
to
partially failing
linwrap.2.0.0
on
4.09
had its build status changed:
passing
to
partially failing
linwrap.2.0.0
on
4.10
had its build status changed:
passing
to
partially failing
linwrap.2.0.0
on
4.11
had its build status changed:
passing
to
partially failing
linwrap.2.0.0
on
4.12
had its build status changed:
passing
to
partially failing
linwrap.2.0.0
on
4.13
had its build status changed:
passing
to
partially failing
linwrap.2.0.0
on
4.14
had its build status changed:
passing
to
partially failing
linwrap.4.0.0
on
4.08
had its build status changed:
passing
to
partially failing
linwrap.4.0.0
on
4.09
had its build status changed:
passing
to
partially failing
linwrap.4.0.0
on
4.10
had its build status changed:
passing
to
partially failing
linwrap.4.0.0
on
4.11
had its build status changed:
passing
to
partially failing
linwrap.4.0.0
on
4.12
had its build status changed:
passing
to
partially failing
linwrap.4.0.0
on
4.13
had its build status changed:
passing
to
partially failing
linwrap.4.0.0
on
4.14
had its build status changed:
passing
to
partially failing
linwrap.5.0.0
on
4.08
had its build status changed:
passing
to
partially failing
linwrap.5.0.0
on
4.09
had its build status changed:
passing
to
partially failing
linwrap.5.0.0
on
4.10
had its build status changed:
passing
to
partially failing
linwrap.5.0.0
on
4.11
had its build status changed:
passing
to
partially failing
linwrap.5.0.0
on
4.12
had its build status changed:
passing
to
partially failing
linwrap.5.0.0
on
4.13
had its build status changed:
passing
to
partially failing
linwrap.5.0.0
on
4.14
had its build status changed:
passing
to
partially failing
lustre-v6.1.737
on
4.08
had its build status changed:
passing
to
partially failing
lustre-v6.1.737
on
4.09
had its build status changed:
passing
to
partially failing
lustre-v6.1.737
on
4.10
had its build status changed:
passing
to
partially failing
lustre-v6.1.737
on
4.11
had its build status changed:
passing
to
partially failing
lustre-v6.1.737
on
4.12
had its build status changed:
passing
to
partially failing
lustre-v6.1.737
on
4.13
had its build status changed:
passing
to
partially failing
lutils.1.44
on
4.08
had its build status changed:
passing
to
partially failing
lutils.1.44
on
4.09
had its build status changed:
passing
to
partially failing
lutils.1.44
on
4.10
had its build status changed:
passing
to
partially failing
lutils.1.44
on
4.11
had its build status changed:
passing
to
partially failing
lutils.1.44
on
4.12
had its build status changed:
passing
to
partially failing
lutils.1.44
on
4.13
had its build status changed:
passing
to
partially failing
lutin.2.56
on
4.08
had its build status changed:
passing
to
partially failing
lutin.2.56
on
4.09
had its build status changed:
passing
to
partially failing
lutin.2.56
on
4.10
had its build status changed:
passing
to
partially failing
lutin.2.56
on
4.11
had its build status changed:
passing
to
partially failing
lutin.2.70.4
on
4.08
had its build status changed:
passing
to
partially failing
lutin.2.70.4
on
4.09
had its build status changed:
passing
to
partially failing
lutin.2.70.4
on
4.10
had its build status changed:
passing
to
partially failing
lutin.2.70.4
on
4.11
had its build status changed:
passing
to
partially failing
lwt_camlp4.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
lwt_camlp4.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
lwt_camlp4.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
lwt_camlp4.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
lwt_camlp4.1.0.0
on
4.12
had its build status changed:
passing
to
partially failing
lwt_camlp4.1.0.0
on
4.13
had its build status changed:
passing
to
partially failing
lwt_camlp4.1.0.0
on
4.14
had its build status changed:
passing
to
partially failing
lwt_named_threads.0.1
on
4.08
had its build status changed:
passing
to
partially failing
lwt_named_threads.0.1
on
4.09
had its build status changed:
passing
to
partially failing
lwt_named_threads.0.1
on
4.10
had its build status changed:
passing
to
partially failing
lwt_named_threads.0.1
on
4.11
had its build status changed:
passing
to
partially failing
macaque.0.7.2
on
4.08
had its build status changed:
passing
to
partially failing
macaque.0.7.2
on
4.09
had its build status changed:
passing
to
partially failing
macaque.0.7.2
on
4.10
had its build status changed:
passing
to
partially failing
macaque.0.7.2
on
4.11
had its build status changed:
passing
to
partially failing
macaque.0.7.2
on
4.12
had its build status changed:
passing
to
partially failing
macaque.0.7.2
on
4.13
had its build status changed:
passing
to
partially failing
macaque.0.7.2
on
4.14
had its build status changed:
passing
to
partially failing
macaque.0.7.4
on
4.08
had its build status changed:
passing
to
partially failing
macaque.0.7.4
on
4.09
had its build status changed:
passing
to
partially failing
macaque.0.7.4
on
4.10
had its build status changed:
passing
to
partially failing
macaque.0.7.4
on
4.11
had its build status changed:
passing
to
partially failing
macaque.0.7.4
on
4.12
had its build status changed:
passing
to
partially failing
macaque.0.7.4
on
4.13
had its build status changed:
passing
to
partially failing
macaque.0.7.4
on
4.14
had its build status changed:
passing
to
partially failing
macaque.0.8
on
4.08
had its build status changed:
passing
to
partially failing
macaque.0.8
on
4.09
had its build status changed:
passing
to
partially failing
macaque.0.8
on
4.10
had its build status changed:
passing
to
partially failing
macaque.0.8
on
4.11
had its build status changed:
passing
to
partially failing
macaque.0.8
on
4.12
had its build status changed:
passing
to
partially failing
macaque.0.8
on
4.13
had its build status changed:
passing
to
partially failing
macaque.0.8
on
4.14
had its build status changed:
passing
to
partially failing
memcad.1.1.0
on
4.08
had its build status changed:
passing
to
partially failing
memcad.1.1.0
on
4.09
had its build status changed:
passing
to
partially failing
memcad.1.1.0
on
4.10
had its build status changed:
passing
to
partially failing
memcad.1.1.0
on
4.11
had its build status changed:
passing
to
partially failing
memcad.1.1.0
on
4.12
had its build status changed:
passing
to
partially failing
memcad.1.1.0
on
4.13
had its build status changed:
passing
to
partially failing
memcad.1.1.0
on
4.14
had its build status changed:
passing
to
partially failing
mikmatch.1.0.9
on
4.08
had its build status changed:
passing
to
partially failing
mikmatch.1.0.9
on
4.09
had its build status changed:
passing
to
partially failing
mikmatch.1.0.9
on
4.10
had its build status changed:
passing
to
partially failing
mikmatch.1.0.9
on
4.11
had its build status changed:
passing
to
partially failing
mikmatch.1.0.9
on
4.12
had its build status changed:
passing
to
partially failing
mikmatch.1.0.9
on
4.13
had its build status changed:
passing
to
partially failing
mikmatch.1.0.9
on
4.14
had its build status changed:
passing
to
partially failing
mikmatch.1.0.9
on
5.0
had its build status changed:
not available
to
partially failing
minicli.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
minicli.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
minicli.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
minicli.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
minicli.1.0.0
on
4.12
had its build status changed:
passing
to
partially failing
minicli.1.0.0
on
4.13
had its build status changed:
passing
to
partially failing
minicli.1.0.0
on
4.14
had its build status changed:
passing
to
partially failing
minicli.1.0.0
on
5.0
had its build status changed:
not available
to
partially failing
minicli.1.0.0
on
5.1
had its build status changed:
not available
to
partially failing
minicli.2.0.0
on
4.08
had its build status changed:
passing
to
partially failing
minicli.2.0.0
on
4.09
had its build status changed:
passing
to
partially failing
minicli.2.0.0
on
4.10
had its build status changed:
passing
to
partially failing
minicli.2.0.0
on
4.11
had its build status changed:
passing
to
partially failing
minicli.2.0.0
on
4.12
had its build status changed:
passing
to
partially failing
minicli.2.0.0
on
4.13
had its build status changed:
passing
to
partially failing
minicli.2.0.0
on
4.14
had its build status changed:
passing
to
partially failing
minicli.2.0.0
on
5.0
had its build status changed:
not available
to
partially failing
minicli.2.0.0
on
5.1
had its build status changed:
not available
to
partially failing
minicli.3.0.0
on
4.08
had its build status changed:
passing
to
partially failing
minicli.3.0.0
on
4.09
had its build status changed:
passing
to
partially failing
minicli.3.0.0
on
4.10
had its build status changed:
passing
to
partially failing
minicli.3.0.0
on
4.11
had its build status changed:
passing
to
partially failing
minicli.3.0.0
on
4.12
had its build status changed:
passing
to
partially failing
minicli.3.0.0
on
4.13
had its build status changed:
passing
to
partially failing
minicli.3.0.0
on
4.14
had its build status changed:
passing
to
partially failing
minicli.3.0.0
on
5.0
had its build status changed:
not available
to
partially failing
minicli.3.0.0
on
5.1
had its build status changed:
not available
to
partially failing
minicli.4.0.0
on
4.08
had its build status changed:
passing
to
partially failing
minicli.4.0.0
on
4.09
had its build status changed:
passing
to
partially failing
minicli.4.0.0
on
4.10
had its build status changed:
passing
to
partially failing
minicli.4.0.0
on
4.11
had its build status changed:
passing
to
partially failing
minicli.4.0.0
on
4.12
had its build status changed:
passing
to
partially failing
minicli.4.0.0
on
4.13
had its build status changed:
passing
to
partially failing
minicli.4.0.0
on
4.14
had its build status changed:
passing
to
partially failing
minicli.4.0.0
on
5.0
had its build status changed:
not available
to
partially failing
minicli.4.0.0
on
5.1
had its build status changed:
not available
to
partially failing
minivpt.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
minivpt.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
minivpt.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
minivpt.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
minivpt.1.0.0
on
4.12
had its build status changed:
passing
to
partially failing
minivpt.1.0.0
on
4.13
had its build status changed:
passing
to
partially failing
minivpt.1.0.0
on
4.14
had its build status changed:
passing
to
partially failing
minivpt.1.0.0
on
5.0
had its build status changed:
not available
to
partially failing
minivpt.1.0.0
on
5.1
had its build status changed:
not available
to
partially failing
minivpt.2.0.0
on
4.08
had its build status changed:
passing
to
partially failing
minivpt.2.0.0
on
4.09
had its build status changed:
passing
to
partially failing
minivpt.2.0.0
on
4.10
had its build status changed:
passing
to
partially failing
minivpt.2.0.0
on
4.11
had its build status changed:
passing
to
partially failing
minivpt.2.0.0
on
4.12
had its build status changed:
passing
to
partially failing
minivpt.2.0.0
on
4.13
had its build status changed:
passing
to
partially failing
minivpt.2.0.0
on
4.14
had its build status changed:
passing
to
partially failing
minivpt.2.0.0
on
5.0
had its build status changed:
not available
to
partially failing
minivpt.2.0.0
on
5.1
had its build status changed:
not available
to
partially failing
mirage-conduit.1.0.3
on
4.08
had its build status changed:
passing
to
partially failing
mirage-conduit.1.0.3
on
4.09
had its build status changed:
passing
to
partially failing
mirage-conduit.1.0.3
on
4.10
had its build status changed:
passing
to
partially failing
mirage-conduit.1.0.3
on
4.11
had its build status changed:
passing
to
partially failing
mirage-conduit.1.3.0
on
4.08
had its build status changed:
passing
to
partially failing
mirage-conduit.1.3.0
on
4.09
had its build status changed:
passing
to
partially failing
mirage-conduit.1.3.0
on
4.10
had its build status changed:
passing
to
partially failing
mirage-conduit.1.3.0
on
4.11
had its build status changed:
passing
to
partially failing
mirage-conduit.3.0.0
on
4.08
had its build status changed:
passing
to
partially failing
mirage-conduit.3.0.0
on
4.09
had its build status changed:
passing
to
partially failing
mirage-conduit.3.0.0
on
4.10
had its build status changed:
passing
to
partially failing
mirage-conduit.3.0.0
on
4.11
had its build status changed:
passing
to
partially failing
mirage-conduit.3.0.1
on
4.08
had its build status changed:
passing
to
partially failing
mirage-conduit.3.0.1
on
4.09
had its build status changed:
passing
to
partially failing
mirage-conduit.3.0.1
on
4.10
had its build status changed:
passing
to
partially failing
mirage-conduit.3.0.1
on
4.11
had its build status changed:
passing
to
partially failing
mirage-conduit.3.1.0
on
4.08
had its build status changed:
passing
to
partially failing
mirage-conduit.3.1.0
on
4.09
had its build status changed:
passing
to
partially failing
mirage-conduit.3.1.0
on
4.10
had its build status changed:
passing
to
partially failing
mirage-conduit.3.1.0
on
4.11
had its build status changed:
passing
to
partially failing
mirage-conduit.3.2.0
on
4.08
had its build status changed:
passing
to
partially failing
mirage-conduit.3.2.0
on
4.09
had its build status changed:
passing
to
partially failing
mirage-conduit.3.2.0
on
4.10
had its build status changed:
passing
to
partially failing
mirage-conduit.3.2.0
on
4.11
had its build status changed:
passing
to
partially failing
mirage-qubes-ipv4.0.6
on
4.08
had its build status changed:
passing
to
partially failing
mirage-qubes-ipv4.0.6
on
4.09
had its build status changed:
passing
to
partially failing
mirage-qubes-ipv4.0.6
on
4.10
had its build status changed:
passing
to
partially failing
mirage-qubes-ipv4.0.6
on
4.11
had its build status changed:
passing
to
partially failing
mirage-qubes-ipv4.0.6.1
on
4.08
had its build status changed:
passing
to
partially failing
mirage-qubes-ipv4.0.6.1
on
4.09
had its build status changed:
passing
to
partially failing
mirage-qubes-ipv4.0.6.1
on
4.10
had its build status changed:
passing
to
partially failing
mirage-qubes-ipv4.0.6.1
on
4.11
had its build status changed:
passing
to
partially failing
mldonkey.3.1.7-2
on
4.08
had its build status changed:
failing
to
partially failing
mldonkey.3.1.7-2
on
4.09
had its build status changed:
failing
to
partially failing
monorobot.0.1
on
4.08
had its build status changed:
passing
to
partially failing
monorobot.0.1
on
4.09
had its build status changed:
passing
to
partially failing
monorobot.0.1
on
4.10
had its build status changed:
passing
to
partially failing
monorobot.0.1
on
4.11
had its build status changed:
passing
to
partially failing
monorobot.0.1
on
4.12
had its build status changed:
passing
to
partially failing
monorobot.0.1
on
4.13
had its build status changed:
passing
to
partially failing
monorobot.0.1
on
4.14
had its build status changed:
passing
to
partially failing
mtl.1.0.0
on
4.08
had its build status changed:
passing
to
partially failing
mtl.1.0.0
on
4.09
had its build status changed:
passing
to
partially failing
mtl.1.0.0
on
4.10
had its build status changed:
passing
to
partially failing
mtl.1.0.0
on
4.11
had its build status changed:
passing
to
partially failing
mtl.1.0.0
on
4.12
had its build status changed:
passing
to
partially failing
mtl.1.0.0
on
4.13
had its build status changed:
passing
to
partially failing
mtl.1.0.0
on
4.14
had its build status changed:
passing
to
partially failing
objsize.0.18
on
4.08
had its build status changed:
passing
to
partially failing
objsize.0.18
on
4.09
had its build status changed:
passing
to
partially failing
objsize.0.18
on
4.10
had its build status changed:
passing
to
partially failing
objsize.0.18
on
4.11
had its build status changed:
passing
to
partially failing
objsize.0.18
on
4.12
had its build status changed:
passing
to
partially failing
objsize.0.18
on
4.13
had its build status changed:
passing
to
partially failing
objsize.0.18
on
4.14
had its build status changed:
passing
to
partially failing
objsize.0.18
on
5.0
had its build status changed:
not available
to
partially failing
obus.1.1.8
on
4.08
had its build status changed:
passing
to
partially failing
obus.1.1.8
on
4.09
had its build status changed:
passing
to
partially failing
obus.1.1.8
on
4.10
had its build status changed:
passing
to
partially failing
obus.1.1.8
on
4.11
had its build status changed:
passing
to
partially failing
ocaml-http.0.1.6
on
4.08
had its build status changed:
passing
to
partially failing
ocaml-http.0.1.6
on
4.09
had its build status changed:
passing
to
partially failing
ocaml-http.0.1.6
on
4.10
had its build status changed:
passing
to
partially failing
ocaml-http.0.1.6
on
4.11
had its build status changed:
passing
to
partially failing
ocaml-http.0.1.6
on
4.12
had its build status changed:
passing
to
partially failing
ocaml-http.0.1.6
on
4.13
had its build status changed:
passing
to
partially failing
ocaml-http.0.1.6
on
4.14
had its build status changed:
passing
to
partially failing
ocamldap.2.3.0
on
4.08
had its build status changed:
passing
to
partially failing
ocamldap.2.3.0
on
4.09
had its build status changed:
passing
to
partially failing
ocamldap.2.3.0
on
4.10
had its build status changed:
passing
to
partially failing
ocamldap.2.3.0
on
4.11
had its build status changed:
passing
to
partially failing
ocamldap.2.3.0
on
4.12
had its build status changed:
passing
to
partially failing
ocamldap.2.3.0
on
4.13
had its build status changed:
passing
to
partially failing
ocamldap.2.3.0
on
4.14
had its build status changed:
passing
to
partially failing
ocamldap.transition
on
4.08
had its build status changed:
passing
to
partially failing
ocamldap.transition
on
4.09
had its build status changed:
passing
to
partially failing
ocamldap.transition
on
4.10
had its build status changed:
passing
to
partially failing
ocamldap.transition
on
4.11
had its build status changed:
passing
to
partially failing
ocamldap.transition
on
4.12
had its build status changed:
passing
to
partially failing
ocamldap.transition
on
4.13
had its build status changed:
passing
to
partially failing
ocamldap.transition
on
4.14
had its build status changed:
passing
to
partially failing
ocamldsort.0.15.0
on
4.08
had its build status changed:
passing
to
partially failing
ocamldsort.0.15.0
on
4.09
had its build status changed:
passing
to
partially failing
ocamldsort.0.15.0
on
4.10
had its build status changed:
passing
to
partially failing
ocamldsort.0.15.0
on
4.11
had its build status changed:
passing
to
partially failing
ocamldsort.0.15.0
on
4.12
had its build status changed:
passing
to
partially failing
ocamldsort.0.15.0
on
4.13
had its build status changed:
failing
to
partially failing
ocamldsort.0.15.0
on
4.14
had its build status changed:
passing
to
partially failing
ocamldsort.0.15.0
on
5.0
had its build status changed:
not available
to
partially failing
ocamldsort.0.16.0
on
4.08
had its build status changed:
passing
to
partially failing
ocamldsort.0.16.0
on
4.09
had its build status changed:
passing
to
partially failing
ocamldsort.0.16.0
on
4.10
had its build status changed:
passing
to
partially failing
ocamldsort.0.16.0
on
4.11
had its build status changed:
passing
to
partially failing
ocamldsort.0.16.0
on
4.12
had its build status changed:
passing
to
partially failing
ocamldsort.0.16.0
on
4.13
had its build status changed:
passing
to
partially failing
ocamldsort.0.16.0
on
4.14
had its build status changed:
passing
to
partially failing
ocamldsort.0.16.0
on
5.0
had its build status changed:
not available
to
partially failing
ocamlrss.2.1.0
on
4.08
had its build status changed:
passing
to
partially failing
ocamlrss.2.1.0
on
4.09
had its build status changed:
passing
to
partially failing
ocamlrss.2.1.0
on
4.10
had its build status changed:
passing
to
partially failing
ocamlrss.2.1.0
on
4.11
had its build status changed:
passing
to
partially failing
ocamlrss.2.1.0
on
4.12
had its build status changed:
passing
to
partially failing
ocamlrss.2.1.0
on
4.13
had its build status changed:
passing
to
partially failing
ocamlrss.2.1.0
on
4.14
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.0
on
4.08
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.0
on
4.09
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.0
on
4.10
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.0
on
4.11
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.0
on
4.12
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.0
on
4.13
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.0
on
4.14
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.1
on
4.08
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.1
on
4.09
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.1
on
4.10
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.1
on
4.11
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.1
on
4.12
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.1
on
4.13
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.1
on
4.14
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.2
on
4.08
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.2
on
4.09
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.2
on
4.10
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.2
on
4.11
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.2
on
4.12
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.2
on
4.13
had its build status changed:
passing
to
partially failing
ocamlrss.2.2.2
on
4.14
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.2
on
4.08
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.2
on
4.09
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.2
on
4.10
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.2
on
4.11
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.2
on
4.12
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.2
on
4.13
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.2
on
4.14
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.2
on
5.0
had its build status changed:
not available
to
partially failing
ocamlscript.2.0.4
on
4.08
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.4
on
4.09
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.4
on
4.10
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.4
on
4.11
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.4
on
4.12
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.4
on
4.13
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.4
on
4.14
had its build status changed:
passing
to
partially failing
ocamlscript.2.0.4
on
5.0
had its build status changed:
not available
to
partially failing
ocapic.3.4
on
4.08
had its build status changed:
passing
to
partially failing
ocapic.3.5
on
4.08
had its build status changed:
passing
to
partially failing
ocapic.3.5
on
4.09
had its build status changed:
passing
to
partially failing
ocapic.3.5
on
4.10
had its build status changed:
passing
to
partially failing
ocapic.3.5
on
4.11
had its build status changed:
passing
to
partially failing
ocapic.3.5
on
4.12
had its build status changed:
passing
to
partially failing
ocapic.3.5
on
4.13
had its build status changed:
passing
to
partially failing
ocapic.3.5
on
4.14
had its build status changed:
passing
to
partially failing
ocsigen-start.2.15.1
on
4.08
had its build status changed:
failing
to
partially failing
ocsigen-start.2.15.1
on
4.09
had its build status changed:
failing
to
partially failing
ocsigen-start.2.15.1
on
4.10
had its build status changed:
failing
to
partially failing
ocsigen-start.2.16.0
on
4.08
had its build status changed:
failing
to
partially failing
ocsigen-start.2.16.0
on
4.09
had its build status changed:
failing
to
partially failing
ocsigen-start.2.16.0
on
4.10
had its build status changed:
failing
to
partially failing
ocsigen-start.2.16.1
on
4.08
had its build status changed:
failing
to
partially failing
ocsigen-start.2.16.1
on
4.09
had its build status changed:
failing
to
partially failing
ocsigen-start.2.16.1
on
4.10
had its build status changed:
failing
to
partially failing
ocsigen-start.2.18.0
on
4.08
had its build status changed:
failing
to
partially failing
ocsigen-start.2.18.0
on
4.09
had its build status changed:
failing
to
partially failing
ocsigen-start.2.18.0
on
4.10
had its build status changed:
failing
to
partially failing
ocsigen-start.2.18.0
on
4.11
had its build status changed:
failing
to
partially failing
ocsigen-start.2.19.2
on
4.08
had its build status changed:
failing
to
partially failing
ocsigen-start.2.19.2
on
4.09
had its build status changed:
failing
to
partially failing
ocsigen-start.2.19.2
on
4.10
had its build status changed:
failing
to
partially failing
ocsigen-start.2.19.2
on
4.11
had its build status changed:
failing
to
partially failing
ocsigen-start.2.19.3
on
4.08
had its build status changed:
failing
to
partially failing
ocsigen-start.2.19.3
on
4.09
had its build status changed:
failing
to
partially failing
ocsigen-start.2.19.3
on
4.10
had its build status changed:
failing
to
partially failing
ocsigen-start.2.19.3
on
4.11
had its build status changed:
failing
to
partially failing
ocsigen-start.2.21.1
on
4.08
had its build status changed:
failing
to
partially failing
ocsigen-start.2.21.1
on
4.09
had its build status changed:
failing
to
partially failing
ocsigen-start.2.21.1
on
4.10
had its build status changed:
failing
to
partially failing
ocsigen-start.2.21.1
on
4.11
had its build status changed:
failing
to
partially failing
ocsigen-start.4.0.0
on
4.08
had its build status changed:
failing
to
partially failing
ocsigen-start.4.0.0
on
4.09
had its build status changed:
failing
to
partially failing
ocsigen-start.4.0.0
on
4.10
had its build status changed:
failing
to
partially failing
ocsigen-start.4.0.0
on
4.11
had its build status changed:
failing
to
partially failing
ocsigen-start.4.0.1
on
4.08
had its build status changed:
failing
to
partially failing
ocsigen-start.4.0.1
on
4.09
had its build status changed:
failing
to
partially failing
ocsigen-start.4.0.1
on
4.10
had its build status changed:
failing
to
partially failing
ocsigen-start.4.0.1
on
4.11
had its build status changed:
failing
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:
passing
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:
passing
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:
passing
to
partially failing
ocsigen-start.4.6.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.4.6.0
on
4.10
had its build status changed:
passing
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
had its build status changed:
passing
to
partially failing
ocsigen-start.6.0.1
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.6.0.1
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.6.0.1
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.6.0.1
on
4.12
had its build status changed:
passing
to
partially failing
ocsigen-start.6.0.1
on
4.13
had its build status changed:
passing
to
partially failing
ocsigen-start.6.0.1
on
4.14
had its build status changed:
passing
to
partially failing
ocsigen-start.6.1.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-start.6.1.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-start.6.1.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-start.6.1.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigen-start.6.1.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigen-start.6.1.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigen-start.6.1.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.2.1
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.3.1
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.3.2
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.3.3
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.4.1
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.4.3
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.4.3
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.4.3
on
4.10
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.5.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.5.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigen-toolkit.2.5.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigenserver.2.12.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigenserver.2.12.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigenserver.2.12.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigenserver.2.12.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigenserver.2.12.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigenserver.2.12.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigenserver.2.12.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigenserver.2.13.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigenserver.2.13.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigenserver.2.13.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigenserver.2.13.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigenserver.2.13.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigenserver.2.13.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigenserver.2.13.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigenserver.2.14.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigenserver.2.14.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigenserver.2.14.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigenserver.2.14.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigenserver.2.14.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigenserver.2.14.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigenserver.2.14.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigenserver.2.15.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigenserver.2.15.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigenserver.2.15.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigenserver.2.15.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigenserver.2.15.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigenserver.2.15.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigenserver.2.15.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.1
on
4.08
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.1
on
4.09
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.1
on
4.10
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.1
on
4.11
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.1
on
4.12
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.1
on
4.13
had its build status changed:
passing
to
partially failing
ocsigenserver.2.16.1
on
4.14
had its build status changed:
passing
to
partially failing
ocsigenserver.2.17.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigenserver.2.17.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigenserver.2.17.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigenserver.2.17.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigenserver.2.17.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigenserver.2.17.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigenserver.2.17.0
on
4.14
had its build status changed:
passing
to
partially failing
ocsigenserver.2.18.0
on
4.08
had its build status changed:
passing
to
partially failing
ocsigenserver.2.18.0
on
4.09
had its build status changed:
passing
to
partially failing
ocsigenserver.2.18.0
on
4.10
had its build status changed:
passing
to
partially failing
ocsigenserver.2.18.0
on
4.11
had its build status changed:
passing
to
partially failing
ocsigenserver.2.18.0
on
4.12
had its build status changed:
passing
to
partially failing
ocsigenserver.2.18.0
on
4.13
had its build status changed:
passing
to
partially failing
ocsigenserver.2.18.0
on
4.14
had its build status changed:
passing
to
partially failing
octez.17.3
on
4.14
had its build status changed:
internal failure
to
partially failing
ocveralls.0.1.0
on
4.08
had its build status changed:
passing
to
partially failing
ocveralls.0.1.0
on
4.09
had its build status changed:
passing
to
partially failing
ocveralls.0.1.0
on
4.10
had its build status changed:
passing
to
partially failing
ocveralls.0.1.0
on
4.11
had its build status changed:
passing
to
partially failing
ocveralls.0.1.0
on
4.12
had its build status changed:
passing
to
partially failing
ocveralls.0.1.0
on
4.13
had its build status changed:
passing
to
partially failing
ocveralls.0.1.0
on
4.14
had its build status changed:
passing
to
partially failing
ocveralls.0.1.0
on
5.0
had its build status changed:
not available
to
partially failing
ocveralls.0.2.0
on
4.08
had its build status changed:
passing
to
partially failing
ocveralls.0.2.0
on
4.09
had its build status changed:
passing
to
partially failing
ocveralls.0.2.0
on
4.10
had its build status changed:
passing
to
partially failing
ocveralls.0.2.0
on
4.11
had its build status changed:
passing
to
partially failing
ocveralls.0.2.0
on
4.12
had its build status changed:
passing
to
partially failing
ocveralls.0.2.0
on
4.13
had its build status changed:
passing
to
partially failing
ocveralls.0.2.0
on
4.14
had its build status changed:
passing
to
partially failing
ocveralls.0.2.0
on
5.0
had its build status changed:
not available
to
partially failing
ocveralls.0.2.1
on
4.08
had its build status changed:
passing
to
partially failing
ocveralls.0.2.1
on
4.09
had its build status changed:
passing
to
partially failing
ocveralls.0.2.1
on
4.10
had its build status changed:
passing
to
partially failing
ocveralls.0.2.1
on
4.11
had its build status changed:
passing
to
partially failing
ocveralls.0.2.1
on
4.12
had its build status changed:
passing
to
partially failing
ocveralls.0.2.1
on
4.13
had its build status changed:
passing
to
partially failing
ocveralls.0.2.1
on
4.14
had its build status changed:
passing
to
partially failing
ocveralls.0.2.1
on
5.0
had its build status changed:
not available
to
partially failing
ocveralls.0.3.0
on
4.08
had its build status changed:
passing
to
partially failing
ocveralls.0.3.0
on
4.09
had its build status changed:
passing
to
partially failing
ocveralls.0.3.0
on
4.10
had its build status changed:
passing
to
partially failing
ocveralls.0.3.0
on
4.11
had its build status changed:
passing
to
partially failing
ocveralls.0.3.0
on
4.12
had its build status changed:
passing
to
partially failing
ocveralls.0.3.0
on
4.13
had its build status changed:
passing
to
partially failing
ocveralls.0.3.0
on
4.14
had its build status changed:
passing
to
partially failing
ocveralls.0.3.0
on
5.0
had its build status changed:
not available
to
partially failing
ocveralls.0.3.1
on
4.08
had its build status changed:
passing
to
partially failing
ocveralls.0.3.1
on
4.09
had its build status changed:
passing
to
partially failing
ocveralls.0.3.1
on
4.10
had its build status changed:
passing
to
partially failing
ocveralls.0.3.1
on
4.11
had its build status changed:
passing
to
partially failing
ocveralls.0.3.1
on
4.12
had its build status changed:
passing
to
partially failing
ocveralls.0.3.1
on
4.13
had its build status changed:
passing
to
partially failing
ocveralls.0.3.1
on
4.14
had its build status changed:
passing
to
partially failing
ocveralls.0.3.1
on
5.0
had its build status changed:
not available
to
partially failing
ocveralls.0.3.2
on
4.08
had its build status changed:
passing
to
partially failing
ocveralls.0.3.2
on
4.09
had its build status changed:
passing
to
partially failing
ocveralls.0.3.2
on
4.10
had its build status changed:
passing
to
partially failing
ocveralls.0.3.2
on
4.11
had its build status changed:
passing
to
partially failing
ocveralls.0.3.2
on
4.12
had its build status changed:
passing
to
partially failing
ocveralls.0.3.2
on
4.13
had its build status changed:
passing
to
partially failing
ocveralls.0.3.2
on
4.14
had its build status changed:
passing
to
partially failing
ocveralls.0.3.2
on
5.0
had its build status changed:
not available
to
partially failing
ocveralls.0.3.3
on
4.08
had its build status changed:
passing
to
partially failing
ocveralls.0.3.3
on
4.09
had its build status changed:
passing
to
partially failing
ocveralls.0.3.3
on
4.10
had its build status changed:
passing
to
partially failing
ocveralls.0.3.3
on
4.11
had its build status changed:
passing
to
partially failing
ocveralls.0.3.3
on
4.12
had its build status changed:
passing
to
partially failing
ocveralls.0.3.3
on
4.13
had its build status changed:
passing
to
partially failing
ocveralls.0.3.3
on
4.14
had its build status changed:
passing
to
partially failing
ocveralls.0.3.3
on
5.0
had its build status changed:
not available
to
partially failing
ocveralls.0.3.4
on
4.08
had its build status changed:
passing
to
partially failing
ocveralls.0.3.4
on
4.09
had its build status changed:
passing
to
partially failing
ocveralls.0.3.4
on
4.10
had its build status changed:
passing
to
partially failing
ocveralls.0.3.4
on
4.11
had its build status changed:
passing
to
partially failing
ocveralls.0.3.4
on
4.12
had its build status changed:
passing
to
partially failing
ocveralls.0.3.4
on
4.13
had its build status changed:
passing
to
partially failing
ocveralls.0.3.4
on
4.14
had its build status changed:
passing
to
partially failing
ocveralls.0.3.4
on
5.0
had its build status changed:
not available
to
partially failing
orm.0.7.0
on
4.08
had its build status changed:
passing
to
partially failing
orm.0.7.0
on
4.09
had its build status changed:
passing
to
partially failing
orm.0.7.0
on
4.10
had its build status changed:
passing
to
partially failing
orm.0.7.0
on
4.11
had its build status changed:
passing
to
partially failing
orm.0.7.0
on
4.12
had its build status changed:
passing
to
partially failing
orm.0.7.0
on
4.13
had its build status changed:
passing
to
partially failing
orm.0.7.0
on
4.14
had its build status changed:
passing
to
partially failing
orm.0.7.0
on
5.0
had its build status changed:
not available
to
partially failing
orm.0.7.1
on
4.08
had its build status changed:
passing
to
partially failing
orm.0.7.1
on
4.09
had its build status changed:
passing
to
partially failing
orm.0.7.1
on
4.10
had its build status changed:
passing
to
partially failing
orm.0.7.1
on
4.11
had its build status changed:
passing
to
partially failing
orm.0.7.1
on
4.12
had its build status changed:
passing
to
partially failing
orm.0.7.1
on
4.13
had its build status changed:
passing
to
partially failing
orm.0.7.1
on
4.14
had its build status changed:
passing
to
partially failing
orm.0.7.1
on
5.0
had its build status changed:
not available
to
partially failing
otoggl.0.3.2
on
4.08
had its build status changed:
passing
to
partially failing
otoggl.0.3.2
on
4.09
had its build status changed:
passing
to
partially failing
otoggl.0.3.2
on
4.10
had its build status changed:
passing
to
partially failing
otoggl.0.3.2
on
4.11
had its build status changed:
passing
to
partially failing
otoggl.0.3.2
on
4.12
had its build status changed:
passing
to
partially failing
otoggl.0.3.2
on
4.13
had its build status changed:
passing
to
partially failing
otoggl.0.3.2
on
4.14
had its build status changed:
passing
to
partially failing
owl-ode-sundials.0.0.7
on
4.08
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.7
on
4.09
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.7
on
4.10
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.7
on
4.11
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.7
on
4.12
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.7
on
4.13
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.9
on
4.08
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.9
on
4.09
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.9
on
4.10
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.9
on
4.11
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.9
on
4.12
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.0.9
on
4.13
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.1.0
on
4.08
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.1.0
on
4.09
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.1.0
on
4.10
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.1.0
on
4.11
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.1.0
on
4.12
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.1.0
on
4.13
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.2.0
on
4.08
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.2.0
on
4.09
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.2.0
on
4.10
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.2.0
on
4.11
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.2.0
on
4.12
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.2.0
on
4.13
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.3.0
on
4.08
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.3.0
on
4.09
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.3.0
on
4.10
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.3.0
on
4.11
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.3.0
on
4.12
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.3.0
on
4.13
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.4.0
on
4.10
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.4.0
on
4.11
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.4.0
on
4.12
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.4.0
on
4.13
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.5.0
on
4.10
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.5.0
on
4.11
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.5.0
on
4.12
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.5.0
on
4.13
had its build status changed:
internal failure
to
partially failing
owl-ode-sundials.0.5.0
on
4.14
had its build status changed:
internal failure
to
partially failing
pa_comprehension.0.4
on
4.08
had its build status changed:
passing
to
partially failing
pa_comprehension.0.4
on
4.09
had its build status changed:
passing
to
partially failing
pa_comprehension.0.4
on
4.10
had its build status changed:
passing
to
partially failing
pa_comprehension.0.4
on
4.11
had its build status changed:
passing
to
partially failing
pa_comprehension.0.4
on
4.12
had its build status changed:
passing
to
partially failing
pa_comprehension.0.4
on
4.13
had its build status changed:
passing
to
partially failing
pa_comprehension.0.4
on
4.14
had its build status changed:
passing
to
partially failing
pa_comprehension.0.4
on
5.0
had its build status changed:
not available
to
partially failing
pa_monad_custom.v6.0.0
on
4.08
had its build status changed:
passing
to
partially failing
pa_monad_custom.v6.0.0
on
4.09
had its build status changed:
passing
to
partially failing
pa_monad_custom.v6.0.0
on
4.10
had its build status changed:
passing
to
partially failing
pa_monad_custom.v6.0.0
on
4.11
had its build status changed:
passing
to
partially failing
pa_monad_custom.v6.0.0
on
4.12
had its build status changed:
passing
to
partially failing
pa_monad_custom.v6.0.0
on
4.13
had its build status changed:
passing
to
partially failing
pa_monad_custom.v6.0.0
on
4.14
had its build status changed:
passing
to
partially failing
pa_monad_custom.v6.0.0
on
5.0
had its build status changed:
not available
to
partially failing
pa_ppx_ag.0.08
on
4.10
had its build status changed:
passing
to
partially failing
pa_ppx_ag.0.08
on
4.11
had its build status changed:
passing
to
partially failing
pa_ppx_ag.0.08
on
4.12
had its build status changed:
passing
to
partially failing
pa_ppx_ag.0.08
on
4.13
had its build status changed:
passing
to
Home|Differences with the last checks|Previous runs Home|Differences with the last checks|Previous runs