Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
llvm-epi-0.8
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Roger Ferrer
llvm-epi-0.8
Commits
030709d0
Commit
030709d0
authored
14 years ago
by
Johnny Chen
Browse files
Options
Downloads
Patches
Plain Diff
test_set_output_path() should restore the original setting of target.process.output-path
after running the program. llvm-svn: 116873
parent
49249493
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
lldb/test/settings/TestSettings.py
+3
-0
3 additions, 0 deletions
lldb/test/settings/TestSettings.py
with
3 additions
and
0 deletions
lldb/test/settings/TestSettings.py
+
3
−
0
View file @
030709d0
...
@@ -120,6 +120,9 @@ class SettingsCommandTestCase(TestBase):
...
@@ -120,6 +120,9 @@ class SettingsCommandTestCase(TestBase):
self
.
runCmd
(
"
run
"
,
RUN_SUCCEEDED
)
self
.
runCmd
(
"
run
"
,
RUN_SUCCEEDED
)
# Restore the original setting now that the program has been run.
self
.
runCmd
(
"
settings set -r target.process.output-path
"
)
# The 'stdout.txt' file should now exist.
# The 'stdout.txt' file should now exist.
self
.
assertTrue
(
os
.
path
.
isfile
(
"
stdout.txt
"
),
self
.
assertTrue
(
os
.
path
.
isfile
(
"
stdout.txt
"
),
"'
stdout.txt
'
exists due to target.process.output-path.
"
)
"'
stdout.txt
'
exists due to target.process.output-path.
"
)
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment