diff options
author | Christopher Baines <mail@cbaines.net> | 2019-12-27 14:05:12 +0000 |
---|---|---|
committer | Christopher Baines <mail@cbaines.net> | 2019-12-27 14:05:12 +0000 |
commit | f56935a8a6893ca27b8bebea15c452167764f901 (patch) | |
tree | fe9e50af68bb726d86a79f6fcdc3f8348e062260 /sqitch | |
parent | 6c1adfa9e6625616b973527edd9996417d3b2212 (diff) | |
download | data-service-f56935a8a6893ca27b8bebea15c452167764f901.tar data-service-f56935a8a6893ca27b8bebea15c452167764f901.tar.gz |
Change the language around reproducibility/matching outputs
It's more accurate to describe the specifics of the relevant data here through
terms like "matching" and "not matching", as a statement that something built
reproducibility needs to be made alongside the test conditions. So just say
that build outputs matched, or didn't match, as this is more descriptive of
the data available.
Diffstat (limited to 'sqitch')
0 files changed, 0 insertions, 0 deletions