[Bioc-devel] Submission #128 (gDRplots): macOS and Windows check runners resolve release, Linux resolves devel

[Arek Gładki]

Hello,

I maintain gDRplots, submitted on 4 August (BiocContributions issue #128).
Two of the three check platforms have been failing since submission, and I
think the cause is on the infrastructure side rather than in my package, so
I'd like to ask about it here.

In a single r-universe run, the runners resolve Bioconductor dependencies
from two different branches:

  linux-release-x86_64    bioconductor.posit.co/packages/devel
gDRtestData 1.11.7   OK
  macos-release-arm64     bioconductor.posit.co/packages/3.23
 gDRtestData 1.10.0   ERROR
  windows-release-x86_64  bioconductor.posit.co/packages/3.23
 gDRtestData 1.10.0   ERROR

My examples use a directory that was added to gDRtestData during the
current devel cycle, so system.file() finds it on Linux and returns "" on
macOS and Windows. That single difference is the only ERROR left on either
platform.

Is this intentional? It doesn't look specific to gDRplots — any submission
depending on something added to a Bioconductor package during the current
cycle would fail on exactly those two platforms and pass on the third.

And a related question I genuinely don't know the answer to: is a clean
build on all platforms a precondition for a reviewer being assigned, or can
review start in parallel? My submission has been in pre-review for four
weeks and I'd like to know whether I'm waiting on this or on something else.

I do have a local workaround — guarding the affected examples so they skip
when the data isn't installed — but I'd rather not push it if the runners
are meant to resolve devel, since it would just hide the difference.

Thanks,
Arek Gladki

	[[alternative HTML version deleted]]