-
Notifications
You must be signed in to change notification settings - Fork 21
Fix hanging issues in integration tests #558
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
Changes from all commits
006059c
f11cc92
801c801
89ffca7
749f940
2a93960
40f2486
c56f6b7
a64a25e
d2a0ce4
1b54e66
edcc0d7
de31833
83b8e6d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -42,19 +42,25 @@ impl DummyArkFrontend { | |
let frontend = DummyFrontend::new(); | ||
let connection_file = frontend.get_connection_file(); | ||
|
||
// Start the kernel in this thread so that panics are propagated | ||
crate::start::start_kernel( | ||
connection_file, | ||
vec![ | ||
String::from("--interactive"), | ||
String::from("--vanilla"), | ||
String::from("--no-save"), | ||
String::from("--no-restore"), | ||
], | ||
None, | ||
SessionMode::Console, | ||
false, | ||
); | ||
|
||
// Start the REPL in a background thread, does not return and is never joined | ||
stdext::spawn!("dummy_kernel", || { | ||
crate::start::start_kernel( | ||
connection_file, | ||
vec![String::from("--no-save"), String::from("--no-restore")], | ||
None, | ||
SessionMode::Console, | ||
false, | ||
); | ||
RMain::start(); | ||
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 am mildly concerned about the fact that But we typically think of I feel like its probably ok? Maybe 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 was wondering about that too, but I couldn't move it to the But I think that's ok because R is ready to receive input or be accessed with well protected (top-level exec) API calls even if the REPL has not been started yet. |
||
}); | ||
lionel- marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
// Wait for startup to complete | ||
RMain::wait_r_initialized(); | ||
Comment on lines
-55
to
-56
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. Remove |
||
|
||
frontend.complete_initialization(); | ||
frontend | ||
} | ||
|
Uh oh!
There was an error while loading. Please reload this page.