File issues publicly for 'ActiveIssues' in tests

[cheenamalhotra]

Opening issue to track this effort, ref: #3012 (comment)_

I would suggest we file issues publicly and address them as we go.

[MichelZ]

Cool. Can I get the description for these ActiveIssue ID's:
5538
5539
5540
12167
12219
31754

Thx :)

[David-Engel]

@MichelZ

Issue	Title	Description
5538	SplitPacketTest in netfx	AlmostFullHeaderTest() fails on ubuntu
5539	SqlNotificationTest fails in netfx	variation: Test_SingleDependency_Timeout
5540	DataStreamTest in SCOOB fails	RunAllTestsForSingleServer_TCP variation fails with this exception: Microsoft.Data.SqlClient.SqlException : A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) 2018-11-19T22:31:46.1819832Z ---- System.ComponentModel.Win32Exception : The specified network name is no longer available
12167	Named pipe's read timeout is not considered in managed SNI	Encrypt=true; TrustServerCertificate=true; using (SqlConnection con = new SqlConnection(/* named pipe connection string*/)) { con.Open(); using (SqlCommand cmd = con.CreateCommand()) { cmd.CommandTimeout = 1; cmd.CommandText = "WAITFOR DELAY '00:00:20';select * from Customers"; // our expectation is to get a timeout failure here! } } A child investigation task says: NamedPipeClientStream does not support ReadTimeout. It should be refactored using the BeginRead and EndRead.
12219	'insert bulk' does not allow ORDER hints for identity columns	insert bulk will return an error message when an ORDER hint is given for an identity column and the query is not executed. This differs from BULK INSERT, which ignores the ORDER hint but still executes the query.
31754	CertificateTest tests are broken	OpeningConnectionWitHNICTest and OpenningConnectionWithGoodCertificateTest are both broken and fail if the TCPConnectionString doesn't include TrustServerCertificate=true. The tests are supposed to install a self-signed certificate to the localhost SQL Server instance and add it to the root cert store so that it is trusted by the system. But it doesn't work and needs to be fixed. I think the same functionality is mostly covered by the tests in the CertificateTestWithTdsServer test class. But we should validate to be certain and possibly fix these tests so that we avoid introducing a regression. RemoteCertificateNameMismatchErrorTest was already flagged as an active issue (26934), but I can't find that issue number anywhere, so including it here.

Note: If anyone is wondering what "SCOOB" is, it was the code name for the MDS project. SqlClient Out Of Box. (Box being Windows / .NET Framework.)