Ticket #6003 (closed: fixed)
MPI build package version number is lagging actual version
| Reported by: | Russell Taylor | Owned by: | Russell Taylor |
|---|---|---|---|
| Priority: | major | Milestone: | Release 2.3 |
| Component: | Mantid | Keywords: | MPI |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Michael Reuter |
Description
For example, last night's build created packages and a modulefile with the version 2.2.963, whereas the actual version number (shown correctly if you start up the mantid build) was 2.2.977.
The problem is that all the CPack configuration is taking place before the PatchVersionNumber.cmake file has been created/updated.
Change History
comment:2 Changed 8 years ago by Russell Taylor
Re #6003. Move creation point of file holding patch version number.
This is so that it is created before cpack configuration for the MPI-enabled build.
Changeset: 3099cb399141c68658a7927e8bd69bf967308642
comment:3 Changed 8 years ago by Russell Taylor
- Status changed from accepted to verify
- Resolution set to fixed
To test, look at https://builds.sns.gov/view/Framework%20only/job/ornl_clean_rhel6_mpi_systemtested/ and verify that the artifacts there carry the same version number as the latest nightly build at http://download.mantidproject.org/ (assuming the most recent set of nightly builds were successful, of course).
comment:4 Changed 8 years ago by Vickie Lynch
- Status changed from verify to verifying
- Tester set to Vickie Lynch
comment:5 Changed 8 years ago by Vickie Lynch
- Status changed from verifying to verify
- Tester Vickie Lynch deleted
One version is 1077 and the other is 1088, so I am not sure if this is OK
comment:6 Changed 8 years ago by Russell Taylor
OK, my testing instructions fell down in the case where nightly builds are manually kicked off out of the normal schedule, or if they fail in one place but not the other.
So another way to check this is to log onto fermi, load a recent version and check that the version number is the same when doing an import mantid (it's logged at information level). Or look at the mpi build against ornl_clean_rhel6_systemtested and see that version numbers match. For example, compare the October 27 MPI build artifact with the one here.
comment:7 Changed 8 years ago by Michael Reuter
- Status changed from verify to verifying
- Tester set to Michael Reuter
comment:8 Changed 8 years ago by Michael Reuter
- Status changed from verifying to closed
I've built the MPI code and compared the artifact version number with that reported by the standard build of MantidPlot and they are the same.
comment:9 Changed 8 years ago by Russell Taylor
Re #6003. Move creation point of file holding patch version number.
This is so that it is created before cpack configuration for the MPI-enabled build.
Changeset: 3099cb399141c68658a7927e8bd69bf967308642
comment:10 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 6849
