mllg / batchtools

Tools for computation on batch systems
https://mllg.github.io/batchtools/
GNU Lesser General Public License v3.0
171 stars 51 forks source link

Registry not writeable #184

Closed dajmcdon closed 6 years ago

dajmcdon commented 6 years ago

I ran a number of jobs using batchtools v0.9.6. I then updated to v0.9.8 (CRAN version) to access the unwrap function. However, I now get the following:

> loadRegistry('newBatch/cplrWithDeviance/')
Reading registry in read-only mode
Updating registry internals
Recalculating job hashes
Updating problems
Renaming memory column in data base
Renaming memory column in update files
Error in setnames(x, "memory", "mem.used") : 
  Items of 'old' not found in column names: memory
> sessionInfo()
R version 3.3.1 (2016-06-21)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Red Hat Enterprise Linux Server release 6.9 (Santiago)

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C               LC_TIME=en_US.UTF-8       
 [4] LC_COLLATE=en_US.UTF-8     LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8   
 [7] LC_PAPER=en_US.UTF-8       LC_NAME=C                  LC_ADDRESS=C              
[10] LC_TELEPHONE=C             LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C       

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
[1] cplr_0.1.3          batchtools_0.9.8    data.table_1.10.4-3

loaded via a namespace (and not attached):
 [1] Rcpp_0.12.16      prettyunits_1.0.2 crayon_1.3.2      digest_0.6.12     withr_2.1.1      
 [6] assertthat_0.2.0  rappdirs_0.3.1    R6_2.2.2          backports_1.1.2   magrittr_1.5     
[11] progress_1.1.2    debugme_1.1.0     stringi_1.1.5     brew_1.0-6        checkmate_1.8.5  
[16] tools_3.3.1       yaml_2.1.16       base64url_1.2    
mllg commented 6 years ago

This is strange and should not happen. I made the update routine more robust in the current devel version to avoid this problem.

Alternatively, you could just move or delete all pending status update files in [file.dir]/updates and try again. Probably some of them are broken.

dajmcdon commented 6 years ago

Deleting worked (I think). Thanks for the prompt response and a great package!

mllg commented 6 years ago

Ok great. Will push a more robust version to CRAN soon.