md5 sums do not appear to work (trac #378)

[cloudy-bot]

reported by: @CloudyLex

I have done two tests to check the behavior of the md5 checksums. First was a checkout of the tag for c17 rc1, on cloud9. Marios and I did several changes to the data files and no comment was generated. I also tried this on a Mac with same result. We edited the stout masterlist and changed one of the stout atomic data files.

Migrated from https://www.nublado.org/ticket/378

{
    "status": "closed",
    "changetime": "2019-02-04T12:08:14Z",
    "_ts": "1549282094687722",
    "description": "I have done two tests to check the behavior of the md5 checksums.  First was a checkout of the tag for c17 rc1, on cloud9.  Marios and I did several changes to the data files and no comment was generated.  I also tried this on a Mac with same result.  We edited the stout masterlist and changed one of the stout atomic data files.",
    "reporter": "gary",
    "cc": "",
    "resolution": "fixed",
    "time": "2017-01-04T23:05:14Z",
    "component": "etc",
    "summary": "md5 sums do not appear to work",
    "priority": "major",
    "keywords": "",
    "version": "trunk",
    "milestone": "c17 branch",
    "owner": "nobody",
    "type": "defect - wrong answer"
}

[cloudy-bot]

@peter-van-hoof-noaccount commented:

The checksum tests are only executed when either lgRelease or lgReleaseBranch is true. So the md5 checksum test is executed on c17_branch and the upcoming c17.00 release, but not c17 rc1 since the latter has neither lgRelease or lgReleaseBranch set.

The test is only carried out for the masterlist files. Regular data files are currently not checked. This would create an additional overhead on reading the data files that would likely be noticeable.

[cloudy-bot]

@peter-van-hoof-noaccount commented:

In r11504 and r11505 the code has been changed to set lgReleaseBranch to true for beta releases. This implies that the md5sum checks are now carried out for release candidates as well.

[cloudy-bot]

• @CloudyLex commented:

Turns out that the md5 sums were not tested in release candidates. Peter modified the code to do this in the future.

• @CloudyLex changed resolution from "" to "fixed"
• @CloudyLex changed status from "new" to "closed"

[cloudy-bot]

@peter-van-hoof-noaccount commented:

Checking all data files was committed in r11510 and r11511.

[cloudy-bot]

• @peter-van-hoof-noaccount commented:

Milestone renamed

• @peter-van-hoof-noaccount changed milestone from "C17_branch" to "c17 branch"