-
Notifications
You must be signed in to change notification settings - Fork 215
test: QA-103 manually set game location to manage a game #23697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Changes from 4 commits
af57f32
c4cb592
20d506a
666d9fb
2d98cf3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| import type { ElectronApplication } from "@playwright/test"; | ||
|
|
||
| export async function stubOpenDialog( | ||
| vortexApp: ElectronApplication, | ||
| filePath: string, | ||
| ): Promise<void> { | ||
| await vortexApp.evaluate(({ dialog }, path) => { | ||
| dialog.showOpenDialog = () => Promise.resolve({ canceled: false, filePaths: [path] }); | ||
| }, filePath); | ||
| } |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| <?xml version="1.0" encoding="utf-8"?> | ||
| <!-- | ||
| Declare the package source explicitly so the build does not depend on | ||
| machine-level NuGet configuration. Machines with no configured sources | ||
| (seen on dev machines and CI runners) otherwise fail restore with NU1100, | ||
| which used to silently ship a Vortex build without dotnetprobe. | ||
| --> | ||
| <configuration> | ||
| <packageSources> | ||
| <clear /> | ||
| <add key="nuget.org" value="https://api.nuget.org/v3/index.json" /> | ||
| </packageSources> | ||
| </configuration> | ||
|
Comment on lines
+1
to
+13
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What was the issue encountered? I don't remember having a need for a machine wide configuration, but I don't mind this
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. From what I could tell, the failure was NU1100 on restore. My machine had no NuGet sources configured at all (dotnet nuget list source showed "No sources found"), so the restore failed, and because the build script swallowed the error, Vortex got built without the probe. I suspect the platform-cluster runner might have the same issue but I haven't been able to confirm that. I'm honestly not sure how my machine ended up with no sources, so this felt like the safest way to make the probe build not depend on machine config. It should only apply to dotnetprobe, so other .NET builds shouldn't be affected, but happy to change the approach if you'd rather handle it differently.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the platform-cluster runner is an intentionally minimal ubuntu runner which never provisions .NET SDK; this obviously means that workflow will always fail until the runner gets updated to include the SDK OR we update the e2e workflow to provision .NET SDK ourselves on linux environments. My suggestion is to have it provisioned on the runner rather than us modifying this workflow and porbably others in the future whenever that runner is being used with .NET builds. |
||
Uh oh!
There was an error while loading. Please reload this page.