Recent <a href="https://travis-ci.org/PredictiveEcology/SpaDES.core/builds/272262991"

I tracked this down. downloadData() and <code class="

checksums giving different results about spades.core HOT 5 CLOSED

predictiveecology commented on July 30, 2024

checksums giving different results

from spades.core.

Comments (5)

achubaty commented on July 30, 2024

package versions that changed between passing and failing builds:

> pass[ids,]
           package.version       date
DiagrammeR           0.9.1 2017-08-21
scales               0.4.1 2016-11-09
tibble               1.3.3 2017-05-28
tidyr                0.7.0 2017-08-16
tidyselect           0.1.1 2017-07-24
> fail[ids,]
           package.version       date
DiagrammeR           0.9.2 2017-09-06
scales               0.5.0 2017-08-24
tibble               1.3.4 2017-08-22
tidyr                0.7.1 2017-09-01
tidyselect           0.2.0 2017-08-30

from spades.core.

achubaty commented on July 30, 2024

I tracked this down. downloadData() and checksums() work fine. The issue was that our test module hadn't been updated to account for the changes made to the SpaDES package (the test maps are no longer in SpaDES, but in quickPlot).

from spades.core.

achubaty commented on July 30, 2024

not sure if the test files moved to quickPlot are different versions than the ones previously used, but a checksum difference is still present:

> checksums(m, tmpdir)
Checking local files...
Finished checking local files.
# A tibble: 2 x 7
# Groups:   expectedFile [2]
  result       expectedFile         actualFile       checksum.x       checksum.y
   <chr>              <chr>              <chr>            <chr>            <chr>
1   FAIL            DEM.tif            DEM.tif 77c56d42fecac5b1 e4d30fe96b0d8229
2   FAIL habitatQuality.tif habitatQuality.tif f21251dcdf23dde0 9ae65632d305afc8
# ... with 2 more variables: algorithm.x <chr>, algorithm.y <chr>