System.Data.SQLite
Check-in [d0f59a690b]
Not logged in

Overview
Comment: Prefer the new -anyInitialize argument over -preInitialize when using the Eagle shell, where applicable. Tarball | ZIP archive | SQL archive family | ancestors | descendants | both | files | file ages | folders d0f59a690b53fdfecbc5aa1c2aa32fd70c1b7003 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 106 107 108 109 110 111 112 113 114 115 116 117 118 119  REM determine that testing is being performed in batch mode. REM SET TEST_ALL=1 FOR %%C IN (%TEST_CONFIGURATIONS%) DO ( FOR %%Y IN (%YEARS%) DO ( IF NOT DEFINED NOMANAGEDONLY ( %__ECHO% Externals\Eagle\bin\EagleShell.exe -preInitialize "set test_year {%%Y}; set test_configuration {%%C}" -file "%TEST_FILE%" IF ERRORLEVEL 1 ( ECHO Testing of "%%Y/%%C" managed-only assembly failed. GOTO errors ) )   |  105 106 107 108 109 110 111 112 113 114 115 116 117 118 119  REM determine that testing is being performed in batch mode. REM SET TEST_ALL=1 FOR %%C IN (%TEST_CONFIGURATIONS%) DO ( FOR %%Y IN (%YEARS%) DO ( IF NOT DEFINED NOMANAGEDONLY ( %__ECHO% Externals\Eagle\bin\EagleShell.exe -anyInitialize "set test_year {%%Y}; set test_configuration {%%C}" -file "%TEST_FILE%" IF ERRORLEVEL 1 ( ECHO Testing of "%%Y/%%C" managed-only assembly failed. GOTO errors ) ) 

Changes to Tests/common.eagle.

 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 ... 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165   # NOTE: See if the "year" setting has been overridden by the user (e.g. # on the command line). This helps control exactly which set of # binaries we are testing, those produced using the Visual Studio # 2005, 2008, 2010, 2012, or 2013 build systems. To override this # value via the command line, enter a command similar to one of # the following (all on one line): # # EagleShell.exe -preInitialize "set test_year 2005" # -file .\path\to\all.eagle # # EagleShell.exe -preInitialize "set test_year 2008" # -file .\path\to\all.eagle # # EagleShell.exe -preInitialize "set test_year 2010" # -file .\path\to\all.eagle # # EagleShell.exe -preInitialize "set test_year 2012" # -file .\path\to\all.eagle # # EagleShell.exe -preInitialize "set test_year 2013" # -file .\path\to\all.eagle # # EagleShell.exe -preInitialize "unset -nocomplain test_year" # -file .\path\to\all.eagle # if {[info exists ::test_year] && [string length $::test_year] > 0} then { # # NOTE: Use the specified test year. If this variable is not set, the # default value will be based on whether or not Eagle has been # compiled against the CLR v2.0 or CLR v4.0. ................................................................................ # NOTE: See if the "configuration" setting has been overridden by the # user (e.g. on the command line). This helps control exactly # which set of binaries we are testing (i.e. those built in the # "Debug" or "Release" build configurations). To override this # value via the command line, enter a command similar to one of # the following (all on one line): # # EagleShell.exe -preInitialize "set test_configuration Debug" # -file .\path\to\all.eagle # # EagleShell.exe -preInitialize "set test_configuration Release" # -file .\path\to\all.eagle # # EagleShell.exe -file .\path\to\all.eagle -preTest # "unset -nocomplain test_configuration" # if {[info exists ::test_configuration] && \ [string length$::test_configuration] > 0} then {   | | | | | | | |  23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 ... 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165   # NOTE: See if the "year" setting has been overridden by the user (e.g. # on the command line). This helps control exactly which set of # binaries we are testing, those produced using the Visual Studio # 2005, 2008, 2010, 2012, or 2013 build systems. To override this # value via the command line, enter a command similar to one of # the following (all on one line): # # EagleShell.exe -anyInitialize "set test_year 2005" # -file .\path\to\all.eagle # # EagleShell.exe -anyInitialize "set test_year 2008" # -file .\path\to\all.eagle # # EagleShell.exe -anyInitialize "set test_year 2010" # -file .\path\to\all.eagle # # EagleShell.exe -anyInitialize "set test_year 2012" # -file .\path\to\all.eagle # # EagleShell.exe -anyInitialize "set test_year 2013" # -file .\path\to\all.eagle # # EagleShell.exe -anyInitialize "unset -nocomplain test_year" # -file .\path\to\all.eagle # if {[info exists ::test_year] && [string length $::test_year] > 0} then { # # NOTE: Use the specified test year. If this variable is not set, the # default value will be based on whether or not Eagle has been # compiled against the CLR v2.0 or CLR v4.0. ................................................................................ # NOTE: See if the "configuration" setting has been overridden by the # user (e.g. on the command line). This helps control exactly # which set of binaries we are testing (i.e. those built in the # "Debug" or "Release" build configurations). To override this # value via the command line, enter a command similar to one of # the following (all on one line): # # EagleShell.exe -anyInitialize "set test_configuration Debug" # -file .\path\to\all.eagle # # EagleShell.exe -anyInitialize "set test_configuration Release" # -file .\path\to\all.eagle # # EagleShell.exe -file .\path\to\all.eagle -preTest # "unset -nocomplain test_configuration" # if {[info exists ::test_configuration] && \ [string length$::test_configuration] > 0} then { 

Changes to www/test.wiki.

 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120  
• To test binaries built with MSBuild 3.5 or Visual Studio 2008 (i.e. because the default is to test binaries built with MSBuild 4.0 or Visual Studio 2010) add the following command line argument right after "Externals\Eagle\bin\EagleShell.exe" in either of the above command lines: -preInitialize "set test_year 2008"
• To test binaries built in the "Debug" build configuration (i.e. because the default is to test binaries built in the "Release" build configuration) add the following command line argument right after "Externals\Eagle\bin\EagleShell.exe" in either of the above command lines: -preInitialize "set test_configuration Debug"
• Make sure all tests pass; the log file "%TEMP%\EagleShell.exe.test.<pid>.log" may be checked if any errors should occur. EagleTest should produce "success" messages very similar to the following:

PASSED: 116
TOTAL: 116
PASS PERCENTAGE: 100%
OVERALL RESULT: SUCCESS
•   | |  91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120  
• To test binaries built with MSBuild 3.5 or Visual Studio 2008 (i.e. because the default is to test binaries built with MSBuild 4.0 or Visual Studio 2010) add the following command line argument right after "Externals\Eagle\bin\EagleShell.exe" in either of the above command lines: -anyInitialize "set test_year 2008"
• To test binaries built in the "Debug" build configuration (i.e. because the default is to test binaries built in the "Release" build configuration) add the following command line argument right after "Externals\Eagle\bin\EagleShell.exe" in either of the above command lines: -anyInitialize "set test_configuration Debug"
• Make sure all tests pass; the log file "%TEMP%\EagleShell.exe.test.<pid>.log" may be checked if any errors should occur. EagleTest should produce "success" messages very similar to the following:

PASSED: 116
TOTAL: 116
PASS PERCENTAGE: 100%
OVERALL RESULT: SUCCESS
•