version 1.1.1.1, 2005/02/12 13:09:20
|
version 1.2, 2005/02/24 09:05:08
|
|
|
%META:TOPICINFO{author="MarvChiang" date="1108183528" format="1.0" version="1.9"}% |
%META:TOPICINFO{author="MarvChiang" date="1109083914" format="1.0" version="1.15"}% |
%META:TOPICPARENT{name="WebHome"}% | %META:TOPICPARENT{name="WebHome"}% |
<h2><a name="Proposed_Timeline"> </a> Proposed Timeline </h2> | <h2><a name="Proposed_Timeline"> </a> Proposed Timeline </h2> |
| |
|
|
</tr> | </tr> |
| |
<tr> | <tr> |
<td valign=top bgcolor=CCDDFF><b>2005-2-25</b></td> |
<td valign=top bgcolor=CCDDFF><b>2005-3-4</b></td> |
<td align=center valign=top bgcolor=DDFFCC>7%</td> | <td align=center valign=top bgcolor=DDFFCC>7%</td> |
<td bgcolor=FFFFCC><ul><li> Run tests on Linux.</li> | <td bgcolor=FFFFCC><ul><li> Run tests on Linux.</li> |
<li>Run the same tests on Linux.</li> | <li>Run the same tests on Linux.</li> |
|
|
</tr> | </tr> |
| |
<tr> | <tr> |
<td valign=top bgcolor=CCDDFF><b>2005-3-4</b></td> |
<td valign=top bgcolor=CCDDFF><b>2005-3-11</b></td> |
<td align=center valign=top bgcolor=DDFFCC>3%</td> | <td align=center valign=top bgcolor=DDFFCC>3%</td> |
<td bgcolor=FFFFCC><ul><li> Submit conformance test and bug report to wineHQ.</li> | <td bgcolor=FFFFCC><ul><li> Submit conformance test and bug report to wineHQ.</li> |
<li>Add more test cases if necessary and resubmit.</li></ul></td> | <li>Add more test cases if necessary and resubmit.</li></ul></td> |
|
|
</pre> | </pre> |
</li> | </li> |
| |
|
<li> |
|
Test cases for WSAAsyncSelect(): |
|
<pre> |
|
1. Success - returns 0 |
|
2. Fail - returns SOCKET_ERROR |
|
a. WAStartup was not called successfullly |
|
b. invalid socket |
|
c. invalud handler |
|
</pre> |
|
</li> |
| |
|
</ul> |
| |
| |
| |
</ul> |
|
| |
<h2> Grade Spreadsheet </h2> |
<p /> |
|
<strong>2005-02-18:</strong> |
|
<ul> |
|
<li>The debugging phase is taking longer than expected, mainly because our |
|
tests have to call 9 APIs, which is considerably more than Dan's |
|
original suggestion of 2 or 3. We also underestimated the complexity of testing asynchronous I/O with |
|
winsock, and have been trying to resolve asynchronous-specific API issues. Finally, we've spent some time trying to simulate inputs/environments for certain |
|
tests cases that are not straight-forward (for example: network is not |
|
ready; too many processes accessing a socket, etc) |
| |
* [[%ATTACHURL%/wine1_status.xls][wine1_status.xls]]: WINE 1 - Grade File |
We are currently proposing a schedule revision. We would like to extend our current milestone to next week due to the above issues. This will not impact our final submission since we have allocated almost two weeks at the end for debugging. Our goal is to be done with the Windows conformance code by early next week so that we can still maintain a generous buffer and stay ahead. |
|
|
|
|
|
</li> |
|
</uL> |
|
|
|
|
|
<p /> |
|
<strong>2005-02-22:</strong> |
|
<ul> |
|
<li> |
|
Finished programming client and server test apps in Visual Studio using asynchronous I/O. Currently the application sends out 100 bytes in 32 byte chunks. More updates on this soon. |
|
</li> |
|
</ul> |
| |
%META:FILEATTACHMENT{name="wine1_status.xls" attr="" comment="WINE 1 - Grade File" date="1108186049" path="C:\Documents and Settings\Mogs\Desktop\wine1_status.xls" size="15360" user="MarvChiang" version="1.2"}% |
|