[WIP] fix deadlock in AtomTable::build_with
This commit is contained in:
@@ -1,5 +1,4 @@
|
||||
use crate::helper::{load_module_test, run_top_level_test_no_args, run_top_level_test_with_args};
|
||||
use scryer_prolog::machine::Machine;
|
||||
use serial_test::serial;
|
||||
|
||||
// issue #857
|
||||
@@ -171,16 +170,3 @@ fn call_0() {
|
||||
" error(existence_error(procedure,call/0),call/0).\n",
|
||||
);
|
||||
}
|
||||
|
||||
// issue #1206
|
||||
#[serial]
|
||||
#[test]
|
||||
#[should_panic(expected = "Overwriting atom table base pointer")]
|
||||
fn atomtable_is_not_concurrency_safe() {
|
||||
// this is basically the same test as scryer_prolog::atom_table::atomtable_is_not_concurrency_safe
|
||||
// but for this integration test scryer_prolog is compiled with cfg!(not(test)) while for the unit test it is compiled with cfg!(test)
|
||||
// as the atom table implementation differ between cfg!(test) and cfg!(not(test)) both test serve a pourpose
|
||||
// Note: this integration test itself is compiled with cfg!(test) independent of scryer_prolog itself
|
||||
let _machine_a = Machine::with_test_streams();
|
||||
let _machine_b = Machine::with_test_streams();
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user