-
Notifications
You must be signed in to change notification settings - Fork 341
Improve wording of progress update #8093
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
Improve wording of progress update #8093
Conversation
... assuming that nobody outside of LLDB developers knows what a "compile unit import" is.
@swift-ci test |
compile_unit->GetPrimaryFile().GetFilename().GetCString(), | ||
cu_imports.size()); | ||
std::string category = "Importing Swift module dependencies for "; | ||
category += compile_unit->GetPrimaryFile().GetFilename(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would main.swift
always be the primary filename here? The category would be "Importing Swift module dependencies for main.swift" which I think works as a category name (as opposed to "Importing Swift module dependencies for"), I just wanna make sure that the filename here wouldn't change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea is we're debugging main.swift
, which contains
import Foundation
import Cocoa
and then we should get:
Importing Swift module dependencies for main.swift: Foundation
Importing Swift module dependencies for main.swift: Cocoa
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, in short: yes!
@@ -38,14 +38,16 @@ def test_swift_progress_report(self): | |||
"Loading Swift module", | |||
"Importing modules used in expression", | |||
"Setting up Swift reflection", | |||
"Getting Swift compile unit imports", | |||
"Importing Swift module dependencies for main.swift", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: We're only doing partial string matching on the test so we could have drop the file name at the end.
Improve wording of progress update assuming that nobody outside of LLDB developers knows what a "compile unit import" is.