Chromium Code Reviews Chromium Code Reviews
Issue 5137008:
Automating the poor man's trybot. (Closed)
Base URL: svn://chrome-svn/chrome/trunk/src/| OLD | NEW |
|---|---|
| 1 ### Copyright (c) 2009 The Chromium Authors. All rights reserved. | 1 @ECHO OFF |
| 2 ### Use of this source code is governed by a BSD-style license that can be | 2 REM Copyright (c) 2009 The Chromium Authors. All rights reserved. |
| 3 ### found in the LICENSE file. | 3 REM Use of this source code is governed by a BSD-style license that can be |
| 4 ### | 4 REM found in the LICENSE file. |
| 5 ### Purpose of this file: If you have IE9 on your machine, not all of | 5 REM |
| 6 ### the Chrome Frame tests will currently pass. The instructions | 6 REM Purpose of this file: If you have IE9 on your machine, not all of |
| 7 ### below, and the xcopy exclusion filter at the bottom of the file, | 7 REM the Chrome Frame tests will currently pass. To run the tests on |
| 8 ### will help you run the CF tests on a machine different from your | 8 REM a VM or separate machine, you need to copy a bunch of things over |
| 9 ### build machine, e.g. on a VM. | 9 REM (the tests run slowly or flakily over a network drive). |
| 10 ### | 10 REM |
| 11 ### Name of this file: poor_mans_trybot.txt (i.e. it is the file you | 11 REM To facilitate running the tests on a separate machine, Run this |
| 12 ### use as the exclude list for the xcopy commands below). | 12 REM batch file on a VM or a separate machine, that has a drive mapped |
| 13 ### | 13 REM to your dev machine (so that it can access your dev workspace). |
| 14 ### If you find this useful, feel free to automate further, but note | 14 REM |
| 15 ### that we expect to set up a trybot for the CF tests soon. | 15 REM Before running this file, you need to build all the chrome_frame |
| 16 ### | 16 REM targets plus chrome.dll and chrome.exe on your dev machine. Run |
| 17 ### On a Windows Vista machine (or VM) with IE8 and FF 3.6 installed, | 17 REM the copy of this file that exists in the same workspace that you |
| 18 ### do the following (adapt to your own paths - j:\src\ybc is the root | 18 REM want to test. |
| 19 ### of a Chrome checkout where you have just built all the | 19 REM |
| 20 ### chrome_frame targets plus chrome.dll and chrome.exe). | 20 REM NOTE: I've seen cases where a Vista VM under Virtual PC will fail |
| 21 ### | 21 REM to copy all of the files from the dev machine, and doing e.g. |
| 22 ### c: | 22 REM [ dir j:\src\chrome\src\chrome\debug ] (assuming j:\src\chrome\src |
| 23 ### mkdir \trybot | 23 REM is your workspace on the dev machine) shows an empty filing listing |
| 24 ### cd \trybot | 24 REM when run from the VM, whereas your workspace actually just built |
| 25 ### rmdir /s /q base | 25 REM a ton of stuff in that directory. Just be aware of it, and check |
| 26 ### rmdir /s /q chrome\debug | 26 REM what files you actually have in the local copy on the VM after |
| 27 ### rmdir /s /q chrome_frame | 27 REM running this script. If you encounter this issue, a reboot of the |
| 28 ### mkdir base | 28 REM VM seems to help. |
| 29 ### mkdir chrome\debug | |
| 30 ### mkdir chrome_frame\test\data | |
| 31 ### mkdir chrome_frame\test\html_util_test_data | |
| 32 ### copy j:\src\ybc\src\chrome\base\base_paths_win.cc base\base_paths_win.cc | |
| 33 ### xcopy j:\src\ybc\src\chrome\debug chrome\debug /E \ | |
| 34 ### /EXCLUDE:j:\src\ybc\src\chrome_frame\test\poor_mans_trybot.txt | |
| 35 ### xcopy j:\src\ybc\src\chrome_frame\test\data chrome_frame\test\data /E | |
| 36 ### xcopy j:\src\ybc\src\chrome_frame\test\html_util_test_data \ | |
| 37 ### chrome_frame\test\html_util_test_data /E | |
| 38 ### copy j:\src\ybc\src\chrome_frame\CFInstance.js chrome_frame\CFInstance.js | |
| 39 ### copy j:\src\ybc\src\chrome_frame\CFInstall.js chrome_frame\CFInstall.js | |
| 40 ### | |
| 41 ### (in admin prompt) | |
| 42 ### cd chrome\debug\servers && regsvr32 npchrome_frame.dll | |
| 43 ### | |
| 44 ### (in regular prompt) | |
| 45 ### chrome\debug\chrome_frame_unittests.exe | |
| 46 ### chrome\debug\chrome_frame_tests.exe | |
| 47 | 29 |
| 48 \lib\ | 30 setlocal |
| 49 \obj\ | 31 set CLIENT_ROOT=%~dp0%..\.. |
| 50 \installer_archive\ | 32 |
| 51 .obj | 33 @ECHO ON |
| 52 .lib | 34 c: |
| 53 .pdb | 35 mkdir \trybot |
| 54 .ilk | 36 cd \trybot |
| 55 .pyd | 37 rmdir /s /q base |
| 56 .7z | 38 rmdir /s /q chrome\debug |
|
amit
2010/11/19 21:49:01
would it be easy to support this debug or release
| |
| 57 .idb | 39 rmdir /s /q chrome_frame |
| 58 .res | 40 mkdir base |
| 59 .manifest | 41 mkdir chrome\debug |
| 60 _i.c | 42 mkdir chrome_frame\test\data |
| 61 _p.c | 43 mkdir chrome_frame\test\html_util_test_data |
| 62 .h | 44 copy %CLIENT_ROOT%\base\base_paths_win.cc base\base_paths_win.cc |
| 63 .cc | 45 xcopy %CLIENT_ROOT%\chrome\debug chrome\debug /E /EXCLUDE:%CLIENT_ROOT%\chrome_f rame\test\poor_mans_trybot_xcopy_filter.txt |
| 64 .vcproj | 46 xcopy %CLIENT_ROOT%\chrome_frame\test\data chrome_frame\test\data /E |
| 65 .user | 47 xcopy %CLIENT_ROOT%\chrome_frame\test\html_util_test_data chrome_frame\test\html _util_test_data /E |
| 66 .sln | 48 copy %CLIENT_ROOT%\chrome_frame\CFInstance.js chrome_frame\CFInstance.js |
| 67 .gyp | 49 copy %CLIENT_ROOT%\chrome_frame\CFInstall.js chrome_frame\CFInstall.js |
| 68 BuildLog.htm | 50 @ECHO OFF |
| 51 echo ************************************ | |
| 52 echo DO THE FOLLOWING IN AN ADMIN PROMPT: | |
| 53 echo ************************************ | |
| 54 echo regsvr32 \trybot\chrome\debug\servers\npchrome_frame.dll | |
| 55 echo ********************************* | |
| 56 echo THEN DO THIS IN A REGULAR PROMPT: | |
| 57 echo ********************************* | |
| 58 echo chrome\debug\chrome_frame_unittests.exe | |
| 59 echo chrome\debug\chrome_frame_tests.exe | |
| OLD | NEW |
