Opened 17 years ago
Closed 15 years ago
#153 closed defect (fixed)
get_revision_number doesn't get revision # if executed with IDLE or emacs
Reported by: | ole | Owned by: | ole |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Functionality and features | Version: | |
Severity: | normal | Keywords: | |
Cc: |
Description
Running script through IDLE resulted in sww file with revision_number = "None".
Running from the DOS prompt was OK.
The example was dam_sample.py in
Gneiss\gem5nhi\inundation\sandpits\onielsen\anuga_work\development\dam_test_from_brad_2007
Change History (6)
comment:1 Changed 17 years ago by duncan
- Owner changed from duncan to ole
- Priority changed from normal to highest
- Summary changed from Revision number not stored in sww when using IDLE to get_revision_number doesn't get revision # if executed with IDLE or emacs
comment:2 Changed 17 years ago by anonymous
- Priority changed from highest to low
comment:3 Changed 17 years ago by ole
- Owner changed from ole to duncan
- Priority changed from low to normal
comment:4 Changed 17 years ago by anonymous
- Owner changed from duncan to Ole
Yes, there is a test for get_revision_number. If test_all.py is executed the way the recent run was executed, does the get_revision_number test fail?
comment:5 Changed 17 years ago by ole
- Owner changed from Ole to ole
- Status changed from new to assigned
The reason was that code run on a compute node won't have access to svn in general. Maybe, we need to store it in a file every time we update the same way it is done with distributions.
comment:6 Changed 15 years ago by nariman
- Resolution set to fixed
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
A recent run on the tornado cluster also had "None" as revision number. Do we have a test? Could we perhaps throw a warning if this is the case?