IRC Transcript
Results that match 'execution':
| July 26, 2010 | |
| CIA-86: bp-ruby: Gary MacDonald master * ra5f05ad / tests/build.xml : win32 test execution fix - http://bit.ly/cBuEOR | |
| CIA-86: bp-python: Gary MacDonald master * r9480e4c / tests/build.xml : win32 test execution fix - http://bit.ly/c35feF | |
| CIA-86: bp-imagealter: Gary MacDonald master * r2eb2547 / test/build.xml : win32 test execution fix - http://bit.ly/aKyO11 | |
| July 20, 2010 | |
| CIA-87: bp-imagealter: Gary MacDonald master * rc72d906 / (build.xml src/build.xml test/build.xml): antify test execution - http://bit.ly/crSkdQ | |
| CIA-87: bp-ruby: Gary MacDonald master * r6e08127 / (build.xml src/build.xml tests/build.xml): antify test execution - http://bit.ly/aNKhLo | |
| May 11, 2010 | |
| lth: "There are inherent race conditions between calling this function and termination of the plugin instance. The browser might not execute calls successfully registered with this API call during plugin termination. Plugins should perform appropriate synchronization with the code in their NPP_Destroy() routine to ensure correct execution and avoid memory leaks." | |
| March 25, 2010 | |
| CIA-12: platform: augment the linux runloop to add a means for threadhopper to use it to *hop* to threads of execution upon which a RunLoop has been installed. | |
| February 18, 2010 | |
| lth: if you had three trials, randomized execution order, and then re-ordered or highlighted the winner somehow | |
| lth: multiple trials and randomized execution order | |
| January 27, 2010 | |
| lth: ok Sputnick, for when you check logs here, this example demonstrates both on win32 and osx how to invoke a script and get the results of execution into your ruby service: | |
| January 13, 2010 | |
| lth: dgrigsby: from me, with love: http://browserplus.l |
|
| August 13, 2009 | |
| lth: I guess that *could* get tricky when you talk about synchronously invoking other code... but that would be the only way I could think of making background execution kick | |
| lth: what's the crux of your issue? no background execution of ruby threads? | |
