[v16] Fix TestRootX11ForwardPermissions
#50229
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Joerger
added
no-changelog
fheinecke
approved these changes
Dec 13, 2024
avatus
approved these changes
Dec 13, 2024
public-teleport-github-review-bot
bot
removed request for
hugoShaka and
atburke
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
This was referenced Dec 13, 2024
tigrato
approved these changes
Dec 13, 2024
Joerger
force-pushed
the
joerger/fix-TestRootX11ForwardPermissions
branch
from
211628a to
8045df4
Compare
|
I spent a good chunk of yesterday and this morning trying to find the cause of the new test failure to no success. My hunch thus far is that the test fixture is not properly set up to connect with the temporary |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix
TestRootX11ForwardPermissionsby using a temporary generated user instead of a hard coded UID.This is not a backport, the issue only affect v15/16. v17/master has a remade test that uses the same generated user strategy.
Depends on #50997 (temporarily cherry-picked in)