New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CoreGx Package Submission #1445
Comments
Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
Add SSH keys to your GitHub account. SSH keys |
A reviewer has been assigned to your package. Learn what to expect IMPORTANT: Please read the instructions for setting |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "skipped, ERROR". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 804475d BiocSubmission: Version number to |
1 similar comment
Received a valid push; starting a build. Commits are: 804475d BiocSubmission: Version number to |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "ABNORMAL". Please see the build report for more details. |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "ABNORMAL". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 97ea3a9 BiocSub: Version bump to |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "ABNORMAL". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: e63565d BiocSub: Revert dependency to |
1 similar comment
Received a valid push; starting a build. Commits are: e63565d BiocSub: Revert dependency to |
Received a valid push; starting a build. Commits are: 7d824dd BiocSub: 1 hr no build report? Retriggering build ... |
1 similar comment
Received a valid push; starting a build. Commits are: 7d824dd BiocSub: 1 hr no build report? Retriggering build ... |
Hi @nturaga, I am not receiving build reports for my recent commits. Also bioc-issue-bot is making two comments per commit. Could be a problem with bioc-issue-bot? Please advise. |
Are you bumping the version number each time? |
Yes. I even did an arbitray bump to retrigger the build on your servers. I get the 'valid push; starting build' comment and email, but no build report is ever posted. |
Try to reenable your hook |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "skipped, ERROR, WARNINGS". Please see the build report for more details. |
^ CoreGx rebuild with no errors or warnings NEWS: I was able to parse the news file after installing the package using utils::news(); please let me know if this is not what you meant R:
vignette:
|
Received a valid push; starting a build. Commits are: aa902fd Add: New branch plus version bump |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. Congratulations! The package built without errors or warnings Please see the build report for more details. |
^ RadioGx passing with no warnings or errors NEWS: I updated the news file to display without warnings, but for some reason, it didn't make it through my merge; I will update it to the working version on the next push R:
vignette:
|
Received a valid push; starting a build. Commits are: 3755de9 Add: Development branch while Bioconductor submiss... |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "WARNINGS". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 7153a4e Fix: Version bump to trigger rebuild |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. Congratulations! The package built without errors or warnings Please see the build report for more details. |
Our current Bioconductor package PharmacoGx has significant updates that depend on CoreGx. Since we removed it from CRAN for this submission, we are unable to update the package until CoreGx is available on Bioconductor. Given it is the last day for package acceptance is there any chance to expedite acceptance of CoreGx? We put a lot of effort into the PharmacoGx changes and would very much like them to be available in this release. If it means resubmitting RadioGx and ToxicoGx separately that is acceptable. Thanks either way. |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. Congratulations! The package built without errors or warnings Please see the build report for more details. |
Hi, Let's do that. Let's get the review of CoreGx in and keep ToxicoGx and RadioGx seperate. That way, you can meet your urgency for the PharmacoGx package. I'll only review CoreGx now. |
I really appreciate it. Should we resubmit ToxicoGx/RadioGx as separate issues or will we just continue here later? |
Just delete the comments which add ToxicoGx and RadioGx as additional packages. And submit them as seperate issues. I'll review CoreGx and try to get it to you as soon as possible. |
Hi @ChristopherEeles , I'm ok accepting the package for now since there is a time crunch. I have to point out a few things and insist you do them.
Please make these improvements ASAP. |
Your package has been accepted. It will be added to the Thank you for contributing to Bioconductor! |
Thanks, Nitesh! I will improve the vignette by the end of next week. As for unit tests, we already have a bunch written that we can migrate from PharmacoGx. Our goal will be to hit 90% coverage for all three packages before the next Bioconductor release. How long until CoreGx will be available as a dependency? Will it be today or tomorrow? |
The master branch of your GitHub repository has been added to Bioconductor's git repository. To use the git.bioconductor.org repository, we need an 'ssh' key to associate with your github user name. If your GitHub account already has ssh public keys (https://github.com/ChristopherEeles.keys is not empty), then no further steps are required. Otherwise, do the following: See further instructions at https://bioconductor.org/developers/how-to/git/ for working with this repository. See especially https://bioconductor.org/developers/how-to/git/new-package-workflow/ to keep your GitHub and Bioconductor repositories in sync. Your package will be included in the next nigthly 'devel' build (check-out from git at about 6 pm Eastern; build completion around 2pm Eastern the next day) at https://bioconductor.org/checkResults/ (Builds sometimes fail, so ensure that the date stamps on the main landing page are consistent with the addition of your package). Once the package builds successfully, you package will be available for download in the 'Devel' version of Bioconductor using https://bioconductor.org/packages/CoreGx If you have any questions, please contact the bioc-devel mailing list (https://stat.ethz.ch/mailman/listinfo/bioc-devel); this issue will not be monitored further. |
Update the following URL to point to the GitHub repository of
the package you wish to submit to Bioconductor
Confirm the following by editing each check box to '[x]'
I understand that by submitting my package to Bioconductor,
the package source and all review commentary are visible to the
general public.
I have read the Bioconductor Package Submission
instructions. My package is consistent with the Bioconductor
Package Guidelines.
I understand that a minimum requirement for package acceptance
is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS.
Passing these checks does not result in automatic acceptance. The
package will then undergo a formal review and recommendations for
acceptance regarding other Bioconductor standards will be addressed.
My package addresses statistical or bioinformatic issues related
to the analysis and comprehension of high throughput genomic data.
I am committed to the long-term maintenance of my package. This
includes monitoring the support site for issues that users may
have, subscribing to the bioc-devel mailing list to stay aware
of developments in the Bioconductor community, responding promptly
to requests for updates from the Core team in response to changes in
R or underlying software.
I am familiar with the essential aspects of Bioconductor software
management, including:
months, for bug fixes.
(optionally via GitHub).
For help with submitting your package, please subscribe and post questions
to the bioc-devel mailing list.
The text was updated successfully, but these errors were encountered: