bioc-registry observer

r-universe build tracking — polls every 15 min, archives on change

bioc 68986021884a

2954packages
61not propagated
2h agolast change
1000+observations
2749propagated
119seeded from Bioconductor
26built by bioc-build
configOKNOTEWARNINGERRORFAILUREFAIL
bioc-checks46849051305121
linux-devel-arm641182291353402
linux-devel-x86_64907130251818202
linux-release-arm641242281343002
linux-release-x86_64935130451015803
macos-oldrel-arm647401082428180043
macos-oldrel-x86_6411519514334030
macos-release-arm647551109428166017
macos-release-x86_6412220814431012
source27650018900
wasm-release2408000070
windows-devel-arm6411120813547016
windows-devel-x86_647331087435203020
windows-oldrel-x86_647411069435187144
windows-release-arm6411820014142016
windows-release-x86_647561085433183021
why are packages not propagated? i

A package propagates when all of the following hold. R 4.6 is the gating R for bioc, resolved from config.yaml at evaluate time — the bioc→R mapping shifts with the R release cycle.

  1. _status is success and the build reported at least one job.
  2. Checks pass on at least one architecture: linux, windows or mac. An architecture passes when its gating jobs are free of ERROR, FAIL and FAILURE (NOTE and WARNING pass). Gating jobs run R 4.6.x on: source + linux x86_64, windows x86_64, macOS arm64 — matching what production BBS tests.
  3. The version is a strict bump over the version already propagated.

Only the passing architectures propagate. The source tarball always rides with an eligible package; binaries for a failing architecture are simply not available until a later version passes there. The passing set is recorded per entry in the index (archs).

Advisory, never blocking: BiocCheck (bioc-checks) and wasm, plus other R lines, arm64 linux, macOS x86_64 and windows arm64. These are tracked and the BiocCheck verdict is recorded in the index, but they cannot stop propagation — mirroring BBS, which excludes BiocCheck from the propagation decision. Most ERRORs in the table above are BiocCheck.

not propagated (61)

BAGS, BP4RNAseq, BeadArrayUseCases, BiocSet, CENTREprecomputed, COMPASS, ChIPComp, ChIPXpressData, CytoMethIC, ELMER, GOfuncR, HMP2Data, HiCDataHumanIMR90, KnowSeq, MetaProViz, OSCA.advanced, OSCA.basic, OSCA.intro, OSCA.workflows, OSTA, RTCGA.CNV, RTCGA.PANCAN12, RTCGA.RPPA, RTCGA.clinical, RTCGA.mRNA, RTCGA.methylation, RTCGA.miRNASeq, RTCGA.mutations, RTCGA.rnaseq, SVMDO, SingleMoleculeFootprinting, TCGAWorkflow, VaSP, adductomicsR, artMS, beer, consensusDE, csawBook, curatedMetagenomicData, customProDB, cytofWorkflow, decoupleR, dorothea, fluentGenomics, healthyControlsPresenceChecker, iBBiG, linkSet, lipidr, moanin, mosbi, netZooR, pgxRpi, randRotation, rqubic, runibic, signifinder, simpleSingleCell, smokingMouse, stJoincount, tidytof, wppi

recent observations

bioc-release 1618b3051ad6

2895packages
50not propagated
2h agolast change
1000+observations
2673propagated
148seeded from Bioconductor
24built by bioc-build
configOKNOTEWARNINGERRORFAILUREFAIL
bioc-checks18627041282130
linux-devel-arm64922491343002
linux-devel-x86_64801134751120201
linux-release-arm641002471382002
linux-release-x86_64830135451416301
macos-oldrel-arm646561128408167062
macos-oldrel-x86_649820614123038
macos-release-arm646591156420170016
macos-release-x86_649922714520014
source27290016600
wasm-release2352000071
windows-devel-arm648921913443020
windows-devel-x86_646291141421213117
windows-oldrel-x86_646501120421180151
windows-release-arm649621714330020
windows-release-x86_646511147427180018
why are packages not propagated? i

A package propagates when all of the following hold. R 4.6 is the gating R for bioc-release, resolved from config.yaml at evaluate time — the bioc→R mapping shifts with the R release cycle.

  1. _status is success and the build reported at least one job.
  2. Checks pass on at least one architecture: linux, windows or mac. An architecture passes when its gating jobs are free of ERROR, FAIL and FAILURE (NOTE and WARNING pass). Gating jobs run R 4.6.x on: source + linux x86_64, windows x86_64, macOS arm64 — matching what production BBS tests.
  3. The version is a strict bump over the version already propagated.

Only the passing architectures propagate. The source tarball always rides with an eligible package; binaries for a failing architecture are simply not available until a later version passes there. The passing set is recorded per entry in the index (archs).

Advisory, never blocking: BiocCheck (bioc-checks) and wasm, plus other R lines, arm64 linux, macOS x86_64 and windows arm64. These are tracked and the BiocCheck verdict is recorded in the index, but they cannot stop propagation — mirroring BBS, which excludes BiocCheck from the propagation decision. Most ERRORs in the table above are BiocCheck.

not propagated (50)

BP4RNAseq, BPRMeth, BiRewire, BubbleTree, CENTREprecomputed, ChIPXpressData, CytoMethIC, DeconRNASeq, GEOexplorer, HD2013SGI, HMP2Data, HiBED, IMAS, MetaNeighbor, MineICA, OMA, OSCA.advanced, OSCA.intro, OSCA.multisample, OSCA.workflows, OSTA, Organism.dplyr, RcisTarget, RforProteomics, RgnTX, RiboProfiling, SGCP, SQLDataFrame, SigFuge, TCGAWorkflow, barcodetrackR, biodbChebi, consensusDE, csawBook, cummeRbund, cytofWorkflow, debCAM, dorothea, granulator, hca, macrophage, mfa, microSTASIS, motifbreakR, netZooR, receptLoss, simpleSingleCell, soGGi, spatzie, tidytof

recent observations