Skip to content

Conversation

@michael-weng
Copy link
Contributor

  • Validate the workflow of user calling the Swift: Run Build/Clean Build/Debug Build commands.
  • Ensure Swift: Run Build will not get blocked by pre-set breakpoint.
  • Ensure Swift: Clean Build will result in a cleaned up .build folder.
  • Ensure Swift: Debug Build will stop on a breakpoint and resume.

Issue: #1184

- Validate the workflow of user calling the
Swift: Run Build/Clean Build/Debug Build commands.
- Ensure Swift: Run Build will not get blocked by pre-set breakpoint.
- Ensure Swift: Clean Build will result in a cleaned up .build folder.
- Ensure Swift: Debug Build will stop on a breakpoint and resume.

Issue: swiftlang#1184
- Added comments for clarification
- Added utilities to listen for dap message, this is useful for test
synchronization. Code takes inspiration from
swiftlang#1126
- Minor cosmetic change to utilies/commands.ts
Copy link
Contributor

@award999 award999 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

otherwise looks good

const result = vscode.commands.executeCommand(Commands.DEBUG);
expect(result).to.eventually.be.true;

await bpPromise.then(() => continueSession());
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we're hitting breakpoints, crossing into smoke level, let's create a smoke suite and put that there

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought that's what @slow do right now?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

still should split into separate suite. Is it actually slow or just trying to keep out of CI build?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are we trying to achieve to split this into a separate suite? Is it for dependency management?

Given the test run fast and this is a command that should probably always work, I am not sure if we want keep this out of CI.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will leave this for until long term approach is decided

returned, causing restore of setting being not awaitable
- Make makeDebugConfigurations to be awaitable
- Change launch to also update the key for ASLR disable settings
- Make the test properly set up and reset the settings that update the
launch config
@award999 award999 merged commit d6590e8 into swiftlang:main Nov 8, 2024
15 checks passed
@michael-weng michael-weng deleted the build_cmd_itest branch November 8, 2024 20:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants