aboutsummaryrefslogtreecommitdiff
path: root/conformance/failure_list_csharp.txt
Commit message (Collapse)AuthorAgeFilesLines
* Down-integrate from google3.Feng Xiao2018-08-081-6/+0
|
* Enable ignoring unknown in json parsing in php (#4839)Paul Yang2018-07-091-0/+6
| | | | | | | | | | * Enable ignoring unknown in json parsing in php * Update generated descriptor files * Update failure list for other languages. * Remove unnecessary php files
* Add unknown field support for csharp (#3936)Jie Luo2017-12-131-1/+0
| | | Add unknown field support for csharp
* Reserve unknown in Ruby (#3763)Paul Yang2017-10-261-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | * Reserve unknown in ruby * Revert ruby tests. Wait for cpp impl for conformance test * Add conformance test for preserving unknown * Add unknown field conformance test to csharp failure list. * Fix comments * Fix comment * Fix comments * Fix typo * Use stringsink_string directly * Mark hd unused * Remove unused encodeunknown_handlerfunc
* Merge remote-tracking branch 'origin/3.4.x' into mergemasterJisi Liu2017-08-181-0/+2
|\
| * Update conformance tests again.Jisi Liu2017-07-251-0/+2
| |
| * Merge from masterJisi Liu2017-07-251-6/+5
| |
| * Update conformance testsJisi Liu2017-07-191-0/+2
| |
* | Detect invalid tags with a field number of 0 in C#Jon Skeet2017-08-111-5/+0
| | | | | | | | | | | | | | | | Previously we only rejected the tag if the tag itself was 0, i.e. field=0, type=varint. The type doesn't matter: field 0 is always invalid. This removes the last of the C# conformance failures.
* | change csharp failure listYilun Chong2017-07-051-4/+1
| |
* | add some test proto2 supported, add js proto2 supported, fixed some errorYilun Chong2017-06-301-4/+8
|/
* Update C# conformance failure list.Feng Xiao2017-03-291-0/+4
|
* Update conformance failure lists.Feng Xiao2016-11-181-6/+0
|
* Fix jenkins tests.Feng Xiao2016-11-151-0/+4
|
* Update conformance test failure listJon Skeet2016-11-031-4/+0
|
* Fix bugs for csharp and ruby for internal integration.Bo Yang2016-10-101-4/+6
|
* Add note about JSON tests maybe being wrong. (#1992)Thomas Van Lenten2016-08-231-3/+0
| | | | | | | | Add note about JSON tests maybe being wrong. - Add note about the JSON test maybe not being correct yet. - Add test to checks the generated names for double underscores to be sure they are what is expected.
* Regenerate conformance files to include extra oneof fields.Jon Skeet2016-08-151-20/+0
| | | | | | This should fix the failures in the conformance tests - although it highlights the problem that we need to do this when changing the conformance.proto file...
* Add more types to the zero oneof cases.Thomas Van Lenten2016-08-111-0/+20
| | | | | | Incase the different runtimes have different generation/implementations for for the different primitive field types, cover a larger range of the proto types in the oneof zero tests.
* Amend the conformance tests to only use Int64/Uint64 non-wrapped values ↵Jon Skeet2016-07-311-4/+0
| | | | | | | | | | which (#1164) can reasonably be expected to be interoperable. (The fact that not all Int64/Uint64 values *can* be exactly represented in IEEE-754 and thus interoperably amongst JSON implementations is precisely the reason for wrapping them when we serialize... it shouldn't be a surprise that we can't round-trip in unwrapped form for all values.)
* Fixed Python by updating failure lists and fixed a few broken tests.Josh Haberman2016-06-031-5/+0
| | | | | Python 2.x doesn't detect unpaired surrogates so we have to do that manually.
* Remove now-fixed conformance errors.Jon Skeet2016-01-151-73/+0
|
* Conformance: Update C# failure list to reflect which tests currently pass.Josh Haberman2016-01-121-89/+2
|
* Updated C#'s failure list, and added missing file.Josh Haberman2016-01-111-0/+176
|
* Validate that after reading a message, we've consumed as many bytes as we ↵Jon Skeet2015-08-051-22/+0
| | | | | | expected to. We should now have no conformance failures.
* Added C# conformance tests.Jon Skeet2015-08-051-0/+22
The tests are run from Travis in the same way as on other platforms. Currently some expected failures - but only expected in that they're what we got to start with. Will try to fix them in other pull requests.