Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Prefer the new -anyInitialize argument over -preInitialize when using the Eagle shell, where applicable. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
d0f59a690b53fdfecbc5aa1c2aa32fd7 |
| User & Date: | mistachkin 2013-12-18 08:01:03 |
Context
|
2013-12-19
| ||
| 09:47 | Remove several prologue overrides from the Eagle vendor script now that beta 29 is checked-in. check-in: ebbd7bca45 user: mistachkin tags: trunk | |
| 02:14 | Use the current isolation level when enlisting into an existing transaction. Fix for [56b42d99c1]. Still needs tests. check-in: 4f050c73ff user: mistachkin tags: tkt-56b42d99c1 | |
|
2013-12-18
| ||
| 08:01 | Prefer the new -anyInitialize argument over -preInitialize when using the Eagle shell, where applicable. check-in: d0f59a690b user: mistachkin tags: trunk | |
| 05:33 | Update Eagle in externals to the pending beta 29 release. check-in: c0de75b66e user: mistachkin tags: trunk | |
Changes
Changes to Setup/test_all.bat.
105 105 REM determine that testing is being performed in batch mode. 106 106 REM 107 107 SET TEST_ALL=1 108 108 109 109 FOR %%C IN (%TEST_CONFIGURATIONS%) DO ( 110 110 FOR %%Y IN (%YEARS%) DO ( 111 111 IF NOT DEFINED NOMANAGEDONLY ( 112 - %__ECHO% Externals\Eagle\bin\EagleShell.exe -preInitialize "set test_year {%%Y}; set test_configuration {%%C}" -file "%TEST_FILE%" 112 + %__ECHO% Externals\Eagle\bin\EagleShell.exe -anyInitialize "set test_year {%%Y}; set test_configuration {%%C}" -file "%TEST_FILE%" 113 113 114 114 IF ERRORLEVEL 1 ( 115 115 ECHO Testing of "%%Y/%%C" managed-only assembly failed. 116 116 GOTO errors 117 117 ) 118 118 ) 119 119
Changes to Tests/common.eagle.
23 23 # NOTE: See if the "year" setting has been overridden by the user (e.g. 24 24 # on the command line). This helps control exactly which set of 25 25 # binaries we are testing, those produced using the Visual Studio 26 26 # 2005, 2008, 2010, 2012, or 2013 build systems. To override this 27 27 # value via the command line, enter a command similar to one of 28 28 # the following (all on one line): 29 29 # 30 - # EagleShell.exe -preInitialize "set test_year 2005" 30 + # EagleShell.exe -anyInitialize "set test_year 2005" 31 + # -file .\path\to\all.eagle 32 + # 33 + # EagleShell.exe -anyInitialize "set test_year 2008" 34 + # -file .\path\to\all.eagle 35 + # 36 + # EagleShell.exe -anyInitialize "set test_year 2010" 31 37 # -file .\path\to\all.eagle 32 38 # 33 - # EagleShell.exe -preInitialize "set test_year 2008" 39 + # EagleShell.exe -anyInitialize "set test_year 2012" 34 40 # -file .\path\to\all.eagle 35 41 # 36 - # EagleShell.exe -preInitialize "set test_year 2010" 42 + # EagleShell.exe -anyInitialize "set test_year 2013" 37 43 # -file .\path\to\all.eagle 38 44 # 39 - # EagleShell.exe -preInitialize "set test_year 2012" 40 - # -file .\path\to\all.eagle 41 - # 42 - # EagleShell.exe -preInitialize "set test_year 2013" 43 - # -file .\path\to\all.eagle 44 - # 45 - # EagleShell.exe -preInitialize "unset -nocomplain test_year" 45 + # EagleShell.exe -anyInitialize "unset -nocomplain test_year" 46 46 # -file .\path\to\all.eagle 47 47 # 48 48 if {[info exists ::test_year] && [string length $::test_year] > 0} then { 49 49 # 50 50 # NOTE: Use the specified test year. If this variable is not set, the 51 51 # default value will be based on whether or not Eagle has been 52 52 # compiled against the CLR v2.0 or CLR v4.0. ................................................................................ 148 148 # NOTE: See if the "configuration" setting has been overridden by the 149 149 # user (e.g. on the command line). This helps control exactly 150 150 # which set of binaries we are testing (i.e. those built in the 151 151 # "Debug" or "Release" build configurations). To override this 152 152 # value via the command line, enter a command similar to one of 153 153 # the following (all on one line): 154 154 # 155 - # EagleShell.exe -preInitialize "set test_configuration Debug" 155 + # EagleShell.exe -anyInitialize "set test_configuration Debug" 156 156 # -file .\path\to\all.eagle 157 157 # 158 - # EagleShell.exe -preInitialize "set test_configuration Release" 158 + # EagleShell.exe -anyInitialize "set test_configuration Release" 159 159 # -file .\path\to\all.eagle 160 160 # 161 161 # EagleShell.exe -file .\path\to\all.eagle -preTest 162 162 # "unset -nocomplain test_configuration" 163 163 # 164 164 if {[info exists ::test_configuration] && \ 165 165 [string length $::test_configuration] > 0} then {
Changes to www/test.wiki.
91 91 92 92 <li> 93 93 To test binaries built with MSBuild 3.5 or Visual Studio 2008 (i.e. because 94 94 the default is to test binaries built with MSBuild 4.0 or Visual Studio 95 95 2010) add the following command line argument right after 96 96 "Externals\Eagle\bin\EagleShell.exe" in either of the above 97 97 command lines: 98 - <b>-preInitialize "set test_year 2008"</b> 98 + <b>-anyInitialize "set test_year 2008"</b> 99 99 </li> 100 100 101 101 <li> 102 102 To test binaries built in the "Debug" build configuration (i.e. 103 103 because the default is to test binaries built in the "Release" 104 104 build configuration) add the following command line argument right after 105 105 "Externals\Eagle\bin\EagleShell.exe" in either of the above 106 106 command lines: 107 - <b>-preInitialize "set test_configuration Debug"</b> 107 + <b>-anyInitialize "set test_configuration Debug"</b> 108 108 </li> 109 109 110 110 <li> 111 111 Make sure all tests pass; the log file 112 112 "%TEMP%\EagleShell.exe.test.<pid>.log" may be checked if any 113 113 errors should occur. EagleTest should produce "success" messages 114 114 very similar to the following:<br /><br /> 115 115 PASSED: 116<br /> 116 116 TOTAL: 116<br /> 117 117 PASS PERCENTAGE: 100%<br /> 118 118 OVERALL RESULT: SUCCESS<br /> 119 119 </li> 120 120 </ol>