Bioconductor Single Package Builder - Build History

Snapshot Date: 
URL:  https://git.bioconductor.org/packages/NanoStringExperiment
Last Changed Rev:  / Revision: 
Last Changed Date: 

Hostname OS /Arch BUILD CHECK BUILD BIN POST-PROCESSING
nebbiolo1 Linux (Ubuntu 20.04.4 LTS)/x86_64   OK     ERROR     skipped     OK  
merida1 macOS 10.14.6 Mojave/x86_64   OK     ERROR     OK     OK  

nebbiolo1 Summary

[top]

Package: NanoStringExperiment
Version: 0.99.3
RVersion: 4.2
BiocVersion: 3.15
BuildCommand: /home/biocbuild/bbs-3.15-bioc/R/bin/R CMD build --keep-empty-dirs --no-resave-data NanoStringExperiment
BuildTime: 1 minutes 5.70 seconds
CheckCommand: BiocCheckGitClone('NanoStringExperiment') && /home/biocbuild/bbs-3.15-bioc/R/bin/R CMD check --no-vignettes --timings NanoStringExperiment_0.99.3.tar.gz && BiocCheck('NanoStringExperiment_0.99.3.tar.gz', `new-package`=TRUE)
CheckTime: 6 minutes 23.65 seconds
BuildBinCommand:
BuildBinTime:
PackageFileSize: 1298.58 KiB
BuildID:: NanoStringExperiment_20220420212018
PreProcessing: Starting Git clone. Installing dependencies. Checking Git Clone. Installing package: NanoStringExperiment. Starting Build package. Starting Check package.
PostProcessing: Finished Git clone. Package type: Software. Installing dependency status: 0. Checking git clone status: 0. Installing package status: 0. Build Package status: 0. Checking Package status: 1.

nebbiolo1 BUILD SRC output

[top]

===============================

 R CMD BUILD

===============================

* checking for file ‘NanoStringExperiment/DESCRIPTION’ ... OK
* preparing ‘NanoStringExperiment’:
* checking DESCRIPTION meta-information ... OK
* installing the package to build vignettes
* creating vignettes ... OK
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
* looking to see if a ‘data/datalist’ file should be added
* building ‘NanoStringExperiment_0.99.3.tar.gz’


nebbiolo1 CHECK output

[top]

===============================

 BiocCheckGitClone('NanoStringExperiment')

===============================

─ BiocCheckVersion: 1.31.37
─ BiocVersion: 3.15
─ Package: NanoStringExperiment
─ PackageVersion: 0.99.3
─ sourceDir: /home/pkgbuild/packagebuilder/workers/jobs/2602/603c8e0e823a15846ca2562aca580676095751f4/NanoStringExperiment
─ platform: unix
─ isTarBall: FALSE

* Checking valid files...
* Checking for stray BiocCheck output folders...
* Checking DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for valid maintainer...
* Checking CITATION...

─ BiocCheck results ──
0 ERRORS | 0 WARNINGS | 0 NOTES

For more details, run
    browseVignettes(package = 'BiocCheck')




===============================

 R CMD CHECK

===============================

* using log directory ‘/home/pkgbuild/packagebuilder/workers/jobs/2602/603c8e0e823a15846ca2562aca580676095751f4/NanoStringExperiment.Rcheck’
* using R version 4.2.0 beta (2022-04-12 r82161)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘NanoStringExperiment/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘NanoStringExperiment’ version ‘0.99.3’
* package encoding: UTF-8
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘NanoStringExperiment’ can be installed ... [45s/45s] OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... NOTE
License components which are templates and need '+ file LICENSE':
  MIT
* checking top-level files ... NOTE
File
  LICENSE
is not mentioned in the DESCRIPTION file.
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [35s/36s] NOTE
copyRowNames: no visible global function definition for ‘DataFrame’
as.list,NanoStringExperiment: no visible global function definition for
  ‘as’
controlSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
endogenousSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
experimentData,NanoStringExperiment: no visible global function
  definition for ‘metadata’
housekeepingSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
munge,NanoStringExperiment: no visible global function definition for
  ‘update’
munge,NanoStringExperiment: no visible global function definition for
  ‘DataFrame’
munge,NanoStringExperiment: no visible global function definition for
  ‘as’
negativeControlSubset,NanoStringExperiment: no visible binding for
  global variable ‘CodeClass’
nonControlSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
phenoData,NanoStringExperiment: no visible global function definition
  for ‘metadata’
phenoData<-,NanoStringExperiment-ANY: no visible global function
  definition for ‘metadata’
positiveControlSubset,NanoStringExperiment: no visible binding for
  global variable ‘CodeClass’
protocolData,NanoStringExperiment: no visible global function
  definition for ‘metadata’
protocolData<-,NanoStringExperiment-ANY: no visible global function
  definition for ‘metadata’
signatureSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
varLabels,NanoStringExperiment: no visible global function definition
  for ‘metadata’
varLabels<-,NanoStringExperiment: no visible global function definition
  for ‘metadata’
with,NanoStringExperiment: no visible global function definition for
  ‘as’
Undefined global functions or variables:
  CodeClass DataFrame as metadata update
Consider adding
  importFrom("methods", "as")
  importFrom("stats", "update")
to your NAMESPACE file (and ensure that your DESCRIPTION Imports field
contains 'methods').
* checking Rd files ... [0s/0s] OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking contents of ‘data’ directory ... OK
* checking data for non-ASCII characters ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [102s/102s] OK
Examples with CPU (user + system) or elapsed time > 5s
                 user system elapsed
sampleMetadata 15.826  0.163  15.996
assayData       6.697  2.872   9.569
esBy            3.651  1.580   5.231
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... OK
* checking running R code from vignettes ... SKIPPED
* checking re-building of vignette outputs ... SKIPPED
* checking PDF version of manual ... OK
* DONE

Status: 3 NOTEs
See
  ‘/home/pkgbuild/packagebuilder/workers/jobs/2602/603c8e0e823a15846ca2562aca580676095751f4/NanoStringExperiment.Rcheck/00check.log’
for details.






===============================

 BiocCheck('NanoStringExperiment_0.99.3.tar.gz')

===============================

─ BiocCheckVersion: 1.31.37
─ BiocVersion: 3.15
─ Package: NanoStringExperiment
─ PackageVersion: 0.99.3
─ sourceDir: /tmp/RtmpKyIB8E/file5611d25478af4/NanoStringExperiment
─ installDir: /tmp/RtmpKyIB8E/file5611d623aebcf
─ BiocCheckDir: /home/pkgbuild/packagebuilder/workers/jobs/2602/603c8e0e823a15846ca2562aca580676095751f4/NanoStringExperiment.BiocCheck
─ platform: unix
─ isTarBall: TRUE

* Installing package...
* Checking package dependencies...
* Checking if other packages can import this one...
* Checking to see if we understand object initialization...
    * NOTE: Consider clarifying how 1 object(s) are initialized. Maybe
      it is part of a data set loaded with data(), or perhaps part of
      an object referenced in with() or within().
* Checking for deprecated package usage...
* Checking for remote package usage...
* Checking for 'LazyData: true' usage...
* Checking version number...
* Checking for version number mismatch...
* Checking new package version number...
* Checking R version dependency...
    * NOTE: Update R version dependency from 3.6 to 4.2.0.
* Checking package size...
* Checking individual file sizes...
* Checking biocViews...
* Checking that biocViews are present...
* Checking package type based on biocViews...
    Software
* Checking for non-trivial biocViews...
* Checking that biocViews come from the same category...
* Checking biocViews validity...
* Checking for recommended biocViews...
    * NOTE: Consider adding these automatically suggested biocViews:
      Coverage
Search 'biocViews' at https://contributions.bioconductor.org
* Checking build system compatibility...
* Checking for blank lines in DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for proper Description: field...
* Checking for whitespace in DESCRIPTION field names...
* Checking that Package field matches directory/tarball name...
* Checking for Version field...
* Checking for valid maintainer...
* Checking License: for restrictive use...
* Checking for pinned package versions...
* Checking DESCRIPTION/NAMESPACE consistency...
* Checking .Rbuildignore...
* Checking for stray BiocCheck output folders...
* Checking vignette directory...
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of NanoStringExperiment...
* Checking coding practice...
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
    * NOTE: Recommended function length <= 50 lines.There are 1
      functions > 50 lines.
* Checking man page documentation...
    * NOTE: Consider adding runnable examples to the following man
      pages which document exported objects:
      normalize.Rd, setQCFlags.Rd
* Checking package NEWS...
* Checking unit tests...
    * NOTE: Consider adding unit tests. We strongly encourage them. See
      http://bioconductor.org/developers/how-to/unitTesting-guidelines/.
* Checking skip_on_bioc() in tests...
* Checking formatting of DESCRIPTION, NAMESPACE, man pages, R source,
  and vignette source...
    * NOTE: Consider multiples of 4 spaces for line indents; 91 lines
      (2%) are not.
    See http://bioconductor.org/developers/how-to/coding-style/
    See styler package: https://cran.r-project.org/package=styler as
      described in the BiocCheck vignette.
* Checking if package already exists in CRAN...
* Checking if new package already exists in Bioconductor...
* Checking for bioc-devel mailing list subscription...
    Maintainer is subscribed to bioc-devel.
* Checking for support site registration...
    Maintainer is registered at support site.
    * ERROR: Maintainer must add package name to Watched Tags on the
      support site; Edit your Support Site User Profile to add Watched
      Tags.

─ BiocCheck results ──
1 ERRORS | 0 WARNINGS | 7 NOTES

See the NanoStringExperiment.BiocCheck folder and run
    browseVignettes(package = 'BiocCheck')
for details.

nebbiolo1 BUILD BIN output

[top]


                				

merida1 Summary

[top]

Package: NanoStringExperiment
Version: 0.99.3
RVersion: 4.2
BiocVersion: 3.15
BuildCommand: /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD build --keep-empty-dirs --no-resave-data NanoStringExperiment
BuildTime: 1 minutes 18.83 seconds
CheckCommand: BiocCheckGitClone('NanoStringExperiment') && /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R CMD check --no-vignettes --timings --no-multiarch NanoStringExperiment_0.99.3.tar.gz && BiocCheck('NanoStringExperiment_0.99.3.tar.gz', `new-package`=TRUE)
CheckTime: 9 minutes 50.63 seconds
BuildBinCommand: /Users/biocbuild/BBS/utils/build-universal.sh NanoStringExperiment_0.99.3.tar.gz /Library/Frameworks/R.framework/Versions/Current/Resources/bin/R libdir
BuildBinTime: 0 minutes 49.54 seconds
PackageFileSize: 1299.25 KiB
BuildID:: NanoStringExperiment_20220420212018
PreProcessing: Starting Git clone. Installing dependencies. Checking Git Clone. Installing package: NanoStringExperiment. Starting Build package. Starting Check package. Starting Build package.
PostProcessing: Finished Git clone. Package type: Software. Installing dependency status: 0. Checking git clone status: 0. Installing package status: 0. Build Package status: 0. Checking Package status: 1. Build Package status: 0.

merida1 BUILD SRC output

[top]

===============================

 R CMD BUILD

===============================

* checking for file ‘NanoStringExperiment/DESCRIPTION’ ... OK
* preparing ‘NanoStringExperiment’:
* checking DESCRIPTION meta-information ... OK
* installing the package to build vignettes
* creating vignettes ... OK
* checking for LF line-endings in source and make files and shell scripts
* checking for empty or unneeded directories
* looking to see if a ‘data/datalist’ file should be added
* building ‘NanoStringExperiment_0.99.3.tar.gz’


merida1 CHECK output

[top]

===============================

 BiocCheckGitClone('NanoStringExperiment')

===============================

─ BiocCheckVersion: 1.31.37
─ BiocVersion: 3.15
─ Package: NanoStringExperiment
─ PackageVersion: 0.99.3
─ sourceDir: /Users/pkgbuild/packagebuilder/workers/jobs/2602/603c8e0e823a15846ca2562aca580676095751f4/NanoStringExperiment
─ platform: unix
─ isTarBall: FALSE

* Checking valid files...
* Checking for stray BiocCheck output folders...
* Checking DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for valid maintainer...
* Checking CITATION...

─ BiocCheck results ──
0 ERRORS | 0 WARNINGS | 0 NOTES

For more details, run
    browseVignettes(package = 'BiocCheck')




===============================

 R CMD CHECK

===============================

* using log directory ‘/Users/pkgbuild/packagebuilder/workers/jobs/2602/603c8e0e823a15846ca2562aca580676095751f4/NanoStringExperiment.Rcheck’
* using R version 4.2.0 beta (2022-04-12 r82161)
* using platform: x86_64-apple-darwin17.0 (64-bit)
* using session charset: UTF-8
* using option ‘--no-vignettes’
* checking for file ‘NanoStringExperiment/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘NanoStringExperiment’ version ‘0.99.3’
* package encoding: UTF-8
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘NanoStringExperiment’ can be installed ... [51s/52s] OK
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking ‘build’ directory ... OK
* checking DESCRIPTION meta-information ... NOTE
License components which are templates and need '+ file LICENSE':
  MIT
* checking top-level files ... NOTE
File
  LICENSE
is not mentioned in the DESCRIPTION file.
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [48s/49s] NOTE
copyRowNames: no visible global function definition for ‘DataFrame’
as.list,NanoStringExperiment: no visible global function definition for
  ‘as’
controlSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
endogenousSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
experimentData,NanoStringExperiment: no visible global function
  definition for ‘metadata’
housekeepingSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
munge,NanoStringExperiment: no visible global function definition for
  ‘update’
munge,NanoStringExperiment: no visible global function definition for
  ‘DataFrame’
munge,NanoStringExperiment: no visible global function definition for
  ‘as’
negativeControlSubset,NanoStringExperiment: no visible binding for
  global variable ‘CodeClass’
nonControlSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
phenoData,NanoStringExperiment: no visible global function definition
  for ‘metadata’
phenoData<-,NanoStringExperiment-ANY: no visible global function
  definition for ‘metadata’
positiveControlSubset,NanoStringExperiment: no visible binding for
  global variable ‘CodeClass’
protocolData,NanoStringExperiment: no visible global function
  definition for ‘metadata’
protocolData<-,NanoStringExperiment-ANY: no visible global function
  definition for ‘metadata’
signatureSubset,NanoStringExperiment: no visible binding for global
  variable ‘CodeClass’
varLabels,NanoStringExperiment: no visible global function definition
  for ‘metadata’
varLabels<-,NanoStringExperiment: no visible global function definition
  for ‘metadata’
with,NanoStringExperiment: no visible global function definition for
  ‘as’
Undefined global functions or variables:
  CodeClass DataFrame as metadata update
Consider adding
  importFrom("methods", "as")
  importFrom("stats", "update")
to your NAMESPACE file (and ensure that your DESCRIPTION Imports field
contains 'methods').
* checking Rd files ... [1s/1s] OK
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking contents of ‘data’ directory ... OK
* checking data for non-ASCII characters ... OK
* checking data for ASCII and uncompressed saves ... OK
* checking installed files from ‘inst/doc’ ... OK
* checking files in ‘vignettes’ ... OK
* checking examples ... [157s/171s] OK
Examples with CPU (user + system) or elapsed time > 5s
                             user system elapsed
sampleMetadata             17.869  0.178  18.801
assayData                  14.338  1.959  17.596
esBy                        8.990  1.022  10.699
featureMetadata             7.729  0.085   8.353
design                      6.840  0.058   7.558
experimentMetadata          5.208  0.060   5.519
NanoStringExperiment-class  4.532  0.069   5.014
* checking for unstated dependencies in vignettes ... OK
* checking package vignettes in ‘inst/doc’ ... OK
* checking running R code from vignettes ... SKIPPED
* checking re-building of vignette outputs ... SKIPPED
* checking PDF version of manual ... OK
* DONE

Status: 3 NOTEs
See
  ‘/Users/pkgbuild/packagebuilder/workers/jobs/2602/603c8e0e823a15846ca2562aca580676095751f4/NanoStringExperiment.Rcheck/00check.log’
for details.






===============================

 BiocCheck('NanoStringExperiment_0.99.3.tar.gz')

===============================

─ BiocCheckVersion: 1.31.37
─ BiocVersion: 3.15
─ Package: NanoStringExperiment
─ PackageVersion: 0.99.3
─ sourceDir: /var/folders/7y/c__3_48d5y18p1_rhfs_4x9c0000gt/T//RtmphboI71/file15e4d57291968/NanoStringExperiment
─ installDir: /var/folders/7y/c__3_48d5y18p1_rhfs_4x9c0000gt/T//RtmphboI71/file15e4d25d97eee
─ BiocCheckDir: /Users/pkgbuild/packagebuilder/workers/jobs/2602/603c8e0e823a15846ca2562aca580676095751f4/NanoStringExperiment.BiocCheck
─ platform: unix
─ isTarBall: TRUE

* Installing package...
* Checking package dependencies...
* Checking if other packages can import this one...
* Checking to see if we understand object initialization...
    * NOTE: Consider clarifying how 1 object(s) are initialized. Maybe
      it is part of a data set loaded with data(), or perhaps part of
      an object referenced in with() or within().
* Checking for deprecated package usage...
* Checking for remote package usage...
* Checking for 'LazyData: true' usage...
* Checking version number...
* Checking for version number mismatch...
* Checking new package version number...
* Checking R version dependency...
    * NOTE: Update R version dependency from 3.6 to 4.2.0.
* Checking package size...
* Checking individual file sizes...
* Checking biocViews...
* Checking that biocViews are present...
* Checking package type based on biocViews...
    Software
* Checking for non-trivial biocViews...
* Checking that biocViews come from the same category...
* Checking biocViews validity...
* Checking for recommended biocViews...
    * NOTE: Consider adding these automatically suggested biocViews:
      Coverage
Search 'biocViews' at https://contributions.bioconductor.org
* Checking build system compatibility...
* Checking for blank lines in DESCRIPTION...
* Checking if DESCRIPTION is well formatted...
* Checking for proper Description: field...
* Checking for whitespace in DESCRIPTION field names...
* Checking that Package field matches directory/tarball name...
* Checking for Version field...
* Checking for valid maintainer...
* Checking License: for restrictive use...
* Checking for pinned package versions...
* Checking DESCRIPTION/NAMESPACE consistency...
* Checking .Rbuildignore...
* Checking for stray BiocCheck output folders...
* Checking vignette directory...
* Checking whether vignette is built with 'R CMD build'...
* Checking package installation calls in R code...
* Checking for library/require of NanoStringExperiment...
* Checking coding practice...
* Checking parsed R code in R directory, examples, vignettes...
* Checking function lengths...
    * NOTE: Recommended function length <= 50 lines.There are 1
      functions > 50 lines.
* Checking man page documentation...
    * NOTE: Consider adding runnable examples to the following man
      pages which document exported objects:
      normalize.Rd, setQCFlags.Rd
* Checking package NEWS...
* Checking unit tests...
    * NOTE: Consider adding unit tests. We strongly encourage them. See
      http://bioconductor.org/developers/how-to/unitTesting-guidelines/.
* Checking skip_on_bioc() in tests...
* Checking formatting of DESCRIPTION, NAMESPACE, man pages, R source,
  and vignette source...
    * NOTE: Consider multiples of 4 spaces for line indents; 91 lines
      (2%) are not.
    See http://bioconductor.org/developers/how-to/coding-style/
    See styler package: https://cran.r-project.org/package=styler as
      described in the BiocCheck vignette.
* Checking if package already exists in CRAN...
* Checking if new package already exists in Bioconductor...
* Checking for bioc-devel mailing list subscription...
    Maintainer is subscribed to bioc-devel.
* Checking for support site registration...
    Maintainer is registered at support site.
    * ERROR: Maintainer must add package name to Watched Tags on the
      support site; Edit your Support Site User Profile to add Watched
      Tags.

─ BiocCheck results ──
1 ERRORS | 0 WARNINGS | 7 NOTES

See the NanoStringExperiment.BiocCheck folder and run
    browseVignettes(package = 'BiocCheck')
for details.

merida1 BUILD BIN output

[top]

===============================

 R CMD BUILD

===============================

>>>>>>> 
>>>>>>> INSTALLATION WITH 'R CMD INSTALL --preclean --no-multiarch --library=libdir NanoStringExperiment_0.99.3.tar.gz'
>>>>>>> 

* installing *source* package ‘NanoStringExperiment’ ...
** using staged installation
** R
** data
** inst
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded from temporary location
** testing if installed package can be loaded from final location
** testing if installed package keeps a record of temporary installation path
* DONE (NanoStringExperiment)