Log of /temp_trunk_copy/esysUtils/test/EsysExceptionTest.cpp
Parent Directory
|
Revision Log
Revision
1384 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Fri Jan 11 02:29:38 2008 UTC
(13 years, 3 months ago)
by
phornby
File length: 1128 byte(s)
Diff to
previous 1312
Make a temp copy of the trunk before checking in the windows changes
Revision
1312 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Mon Sep 24 06:18:44 2007 UTC
(13 years, 6 months ago)
by
ksteube
Original Path:
trunk/esysUtils/test/EsysExceptionTest.cpp
File length: 1128 byte(s)
Diff to
previous 700
The MPI branch is hereby closed. All future work should be in trunk.
Previously in revision 1295 I merged the latest changes to trunk into trunk-mpi-branch.
In this revision I copied all files from trunk-mpi-branch over the corresponding
trunk files. I did not use 'svn merge', it was a copy.
Revision
700 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Apr 6 00:13:40 2006 UTC
(15 years ago)
by
gross
Original Path:
trunk/esysUtils/test/EsysExceptionTest.cpp
File length: 413 byte(s)
Copied from:
trunk/esysUtils/test/EsysException/EsysExceptionTest.cpp revision 699
Diff to
previous 207
A few changes in the build mechanism and the file structure so scons can build release tar files:
* paso/src/Solver has been moved to paso/src
* all test_.py are now run_.py files and are assumed to be passing python tests. they can run by
scons py_tests and are part of the release test set
* escript/py_src/test_ are moved to escript/test/python and are installed in to the build directory
(rather then the PYTHONPATH).
* all py files in test/python which don't start with run_ or test_ are now 'local_py_tests'. they are installed i
by not run automatically.
* CppUnitTest is now treated as a escript module (against previous decisions).
* scons realse builds nor tar/zip files with relvant source code (src and tests in seperate files)
the python tests don't pass yet due to path problems.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
enter a numeric revision.