microsoft / microsoft/go

Test flaky: `crypto/tls:spectre.TestServerResumptionDisabled/TLSv12#01` (linux-amd64 nocgo (ubuntu) [systemcrypto])

Open
#2,212 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Flaky Test
Dominant language
Go
Stars
431
Forks
44
Avg merge
21h 18m
Merged PRs (30d)
30

Description

https://dev.azure.com/dnceng-public/public/_build/results?buildId=1350871&view=ms.vss-test-web.build-test-results-tab&runId=37737326&paneView=debug&resultId=199544

=== RUN   TestServerResumptionDisabled/TLSv12#01
=== PAUSE TestServerResumptionDisabled/TLSv12#01
=== CONT  TestServerResumptionDisabled/TLSv12#01
    handshake_test.go:274: write mismatch: expected 1403030001011603030040000000000000000000000000000000004abff12b6aafe5b95169383ea347bf0b678315e091c6b3cbfc240531b7513dfabb089af9f8892af15ab1a81aedaa63001703030040000000000000000000000000000000008037dcf6b1a280910ec971c61c1e451450cd3985738af590752805ab69ae1abdb9ee39e83f2d734d21fa2e05b4a10264150303003000000000000000000000000000000000141ef764d847a693aa03aa7cf3a2fbb86fcff20de42dd1d667f36befe35ddc5b, got 1503030002022f
    handshake_server_test.go:720: Error from Server.Write: 'crypto/rsa: decryption error'
    handshake_test.go:290: closed with unfinished flows
--- FAIL: TestServerResumptionDisabled/TLSv12#01 (0.00s)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Azure build failure and the referenced tests in handshake_test.go and handshake_server_test.go. Run TestServerResumptionDisabled/TLSv12#01 in the linux-amd64 nocgo systemcrypto configuration and investigate the write mismatch and RSA decryption error. Done means the targeted test completes without an unfinished flow or intermittent failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cryptography, security, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.