QCryptographicHash test: remove the moreThan4GiBOfData(SHA512) check from the CI
It timed out the other day on the CI. Even the SHA-1 check took 137s (with a 300s timeout). Skip the SHA-512 test on the CI, but keep it for manual runs. Change-Id: I49792ac9bcab6512e1803f66cd986b2830e634c0 Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io> (cherry picked from commit c6e092a5f84b7fc72556897b50c7697152967925) Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
This commit is contained in:
parent
3bc70954ee
commit
84e1fa3800
@ -453,8 +453,11 @@ void tst_QCryptographicHash::moreThan4GiBOfData_data()
|
||||
row(QCryptographicHash::Md4);
|
||||
row(QCryptographicHash::Md5);
|
||||
row(QCryptographicHash::Sha1);
|
||||
// this is already significantly slower, but important (O(min)
|
||||
row(QCryptographicHash::Sha512);
|
||||
if (!qgetenv("QTEST_ENVIRONMENT").split(' ').contains("ci")) {
|
||||
// This is important but so slow (O(minute)) that, on CI, it tends to time out.
|
||||
// Retain it for manual runs, all the same, as most dev machines will be fast enough.
|
||||
row(QCryptographicHash::Sha512);
|
||||
}
|
||||
// the rest is just too slow
|
||||
#else
|
||||
QSKIP("This test is 64-bit only.");
|
||||
|
Loading…
x
Reference in New Issue
Block a user