Archived issue #0032404
Draw - problems with definition of cpulimit in tests
Description
cpulitit in tests ranges from 1 second to 167 minutes.
In some groups, it is not defined at all (hlr)
See attached cpulimt.xlsx
In the event of infinite loops (CR29059_5), a very large value of cpulimit or the absence of its definition stops testing for a very long time.
This is especially important for testing in Jenkins
It is proposed to redefine cpulimit for sufficient minimum values
In some groups, it is not defined at all (hlr)
See attached cpulimt.xlsx
In the event of infinite loops (CR29059_5), a very large value of cpulimit or the absence of its definition stops testing for a very long time.
This is especially important for testing in Jenkins
It is proposed to redefine cpulimit for sufficient minimum values
Steps to reproduce
Not required
Public activity
11 archived notes
Participants are labeled by their role within this record.
Branch [archived branch] has been created by Participant.
[revision removed]
Detailed log of new commits:
Author: Author
Date: Mon May 31 11:20:59 2021 +0300
0032404: Draw - problems with definition of cpulimit in tests
[revision removed]
Detailed log of new commits:
Author: Author
Date: Mon May 31 11:20:59 2021 +0300
0032404: Draw - problems with definition of cpulimit in tests
Branch [archived branch] has been updated by Participant.
[revision removed]
Detailed log of new commits:
Author: Author
Date: Mon May 31 13:38:49 2021 +0300
Printing Elapsed Time
[revision removed]
Detailed log of new commits:
Author: Author
Date: Mon May 31 13:38:49 2021 +0300
Printing Elapsed Time
Memory - 16 Gb
Disk - SSD
Video - GeForce 1060
testex4 - CPU - 4 core
Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz 3.10
Elapsed time ~ 4 hours
testex2 (jenkins-test-08) CPU - 6 core
Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz 3.00
Elapsed time ~ infinity
I couldn't wait for the tests to complete
See attached file - testex2
A lot of test are killed by cpulimit >= 2500
Disk - SSD
Video - GeForce 1060
testex4 - CPU - 4 core
Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz 3.10
Elapsed time ~ 4 hours
testex2 (jenkins-test-08) CPU - 6 core
Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz 3.00
Elapsed time ~ infinity
I couldn't wait for the tests to complete
See attached file - testex2
A lot of test are killed by cpulimit >= 2500
testex2 (jenkins-test-08) CPU - 6 core
An attempt to perform all tests with cyclic dependencies led to the station crash with its shutdown due to the exhaustion of station resources
The station restart is possible only from the office
An attempt to perform all tests with cyclic dependencies led to the station crash with its shutdown due to the exhaustion of station resources
The station restart is possible only from the office
Branch [archived branch] has been updated forcibly by Participant.
[revision removed]
[revision removed]
Branch [archived branch] has been updated forcibly by Participant.
[revision removed]
[revision removed]
Branch [archived branch] has been updated forcibly by Participant.
[revision removed]
[revision removed]
Kirill,
I corrected all the tests with cpulimit >= 1000 to 1000 in OCCT and Products except ifc.
There is one very long test ifc doc_1 B4 where I redefined cpulimit to 1400.
And I added cpulimit to hlr test grid.
http://jenkins-test-08.nnov.opencascade.com/view/CR32404-CR32404/
I tried to execute tests on OCCT compiled in debug mode. The tests take about 16 hours.
And although indeed some tests break off after changing the cpulimite to 1000.
But testing in debug fashion is not debugged at all. Many tests fail due to unchanged cpulimit, some fail due to errors.
I corrected all the tests with cpulimit >= 1000 to 1000 in OCCT and Products except ifc.
There is one very long test ifc doc_1 B4 where I redefined cpulimit to 1400.
And I added cpulimit to hlr test grid.
http://jenkins-test-08.nnov.opencascade.com/view/CR32404-CR32404/
I tried to execute tests on OCCT compiled in debug mode. The tests take about 16 hours.
And although indeed some tests break off after changing the cpulimite to 1000.
But testing in debug fashion is not debugged at all. Many tests fail due to unchanged cpulimit, some fail due to errors.
Lets take the patch.
Will see how to adopt testing if new values will cause problems.
For testing Debug builds one may set an environment CSF_CPULIMIT_FACTOR variable to value larger than 1x.
Will see how to adopt testing if new values will cause problems.
For testing Debug builds one may set an environment CSF_CPULIMIT_FACTOR variable to value larger than 1x.
Combination -
OCCT branch : [archived branch]
master SHA - [revision removed]
[revision removed]
Products branch : [archived branch] SHA - [revision removed]
was compiled on Linux, MacOS and Windows platforms and tested in optimize mode.
Number of compiler warnings:
No new/fixed warnings
Regressions/Differences/Improvements:
No regressions/differences
CPU differences:
Debian80-64:
OCCT
Total CPU difference: 17401.600000000442 / 17450.34000000035 [-0.28%]
Products
Total CPU difference: 11508.180000000091 / 11477.640000000127 [+0.27%]
Windows-64-VC14:
OCCT
Total CPU difference: 19191.265625 / 19269.40625 [-0.41%]
Products
Total CPU difference: 12883.6875 / 12905.015625 [-0.17%]
Image differences :
No differences that require special attention
Memory differences :
No differences that require special attention
OCCT branch : [archived branch]
master SHA - [revision removed]
[revision removed]
Products branch : [archived branch] SHA - [revision removed]
was compiled on Linux, MacOS and Windows platforms and tested in optimize mode.
Number of compiler warnings:
No new/fixed warnings
Regressions/Differences/Improvements:
No regressions/differences
CPU differences:
Debian80-64:
OCCT
Total CPU difference: 17401.600000000442 / 17450.34000000035 [-0.28%]
Products
Total CPU difference: 11508.180000000091 / 11477.640000000127 [+0.27%]
Windows-64-VC14:
OCCT
Total CPU difference: 19191.265625 / 19269.40625 [-0.41%]
Products
Total CPU difference: 12883.6875 / 12905.015625 [-0.17%]
Image differences :
No differences that require special attention
Memory differences :
No differences that require special attention
Branch [archived branch] has been deleted by Participant.
[revision removed]
[revision removed]
Related records