[Bug 51782] New: The ws2_32:sock output is too big in Wine

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51782

Bug ID: 51782
           Summary: The ws2_32:sock output is too big in Wine
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: winsock
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

ws2_32:sock outputs ~29kB of data. This is too much and contributes in pushing
the WineTest reports above the 1.5MB limit.

The traces break down as follows:
 0kB  failures
24kB  todos
 5kB  traces
 0kB  test framework (summary lines, etc.)

Note that this predates the double-free ws2_32:sock crash (bug 51778): the
crash backtrace just took the place of the todos/traces that are no longer
being run.

Time to fix Wine to reduce the number of todos!

[Bug 51782] The ws2_32:sock output is too big in Wine

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51782

François Gouget  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |source, testcase

[Bug 51782] The ws2_32:sock output is too big in Wine

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51782

Zebediah Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail],
                   |                            |[e-mail]
            Version|unspecified                 |6.17

--- Comment #1 from Zebediah Figura  ---
ws2_32:sock has always had a bunch, but the bulk of it now is
test_sockopt_validity, for options we don't implement.

I don't think we really want to spend effort on implementing these, though.
Maybe the best thing to do is shorten the todo messages a bit.