Ticket #6168 (closed: fixed)
Add perf timing view for system tests
| Reported by: | Nick Draper | Owned by: | Russell Taylor |
|---|---|---|---|
| Priority: | critical | Milestone: | Release 3.0 |
| Component: | Framework | Keywords: | Maintenance |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Wenduo Zhou |
Description
Add a similar view to the performance tests to the system tests. Again focus on one environment.
Change History
comment:4 Changed 8 years ago by Russell Taylor
Committed against wrong ticket.....
Re #6198. Remove plot that takes a long time to generate.
The creation of this plot appears to take about 1/3 of the total time of the make_report script for the ORNL performance tests job. It's at the bottom of the main HTML report page and I don't think I've ever looked at it.
Changeset: 7ad97fcc51dfa5e51f5a2c238c309184bc15d307
comment:5 Changed 8 years ago by Russell Taylor
Re #6168. Exit with a code that's the Mantid revision number.
I need to get hold of this to pass into a performance db.
Changeset: fad6f843175e3a765bb239e7cbd9a98b735e0951
comment:6 Changed 8 years ago by Russell Taylor
Revert "Re #6168. Exit with a code that's the Mantid revision number."
Seems like that's not going to work because Jenkins will see it as a failure even if I capture the return code in a variable. Guess I'll just have to do it via a file.
This reverts commit fad6f843175e3a765bb239e7cbd9a98b735e0951.
Changeset: 81d7fd17fbb0ebe0304294d76a5c1a0750d03ba3
comment:7 Changed 8 years ago by Russell Taylor
Re #6168. Write out a file with the revision number in it.
Changeset: 3a274d11f2d34ddba536c8128e6721e84ad0f6d0
comment:8 Changed 7 years ago by Russell Taylor
- Milestone changed from Release 2.5 to Release 2.6
Move the tickets I'm definitely not going to do this iteration so that I can better see the ones that I might.
comment:9 Changed 7 years ago by Nick Draper
- Priority changed from blocker to critical
- Keywords Maintenance added
comment:10 Changed 7 years ago by Russell Taylor
Re #6168. Copy over code to track performance from main repository.
It's not ideal to fork things in this way, but I don't want to have to check out the mantid repository in order to run this on the system tests.
Changeset: 39ca32c781ec38df2e44fecfb4541940ea35c8ce
comment:16 Changed 7 years ago by Russell Taylor
Re #6168. Move README file to the place I meant to put it.
Changeset: 000d8d786546f7fbce14310eb7f911cfed61ca1d
comment:17 Changed 7 years ago by Russell Taylor
- Status changed from inprogress to verify
- Resolution set to fixed
Tester: The branch is feature/6168_performance_timing in the systemtests repository, although all but the last 2 commits pre-date our current workflow so are already in master.
This one is easy to test. Look at https://builds.sns.gov/job/ornl_test_rhel6_develop/ and follow the 'System tests performance' link to see the report that mirrors the one we have for our cxxtest performance tests.
Reports for other platforms (notably in our windows job: https://builds.sns.gov/view/Develop%20Clean/job/ornl_test_windows7_develop/) and for ISIS jobs will follow later.
comment:18 Changed 7 years ago by Wenduo Zhou
- Status changed from verify to verifying
- Tester set to Wenduo Zhou
comment:19 Changed 7 years ago by Wenduo Zhou
The report of system test is similar to that for unit test. Thus ticket is closed.
comment:20 Changed 7 years ago by Wenduo Zhou
- Status changed from verifying to closed
Merge remote-tracking branch 'origin/feature/6168_performance_timing'
comment:21 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 7014
Moved at the code freeze for release 2.4