SOMns
SOMns copied to clipboard
smarr
SOMns: A Newspeak for Concurrency Research
This pull request fixes a corner case in which the receiver-side rr is not able to capture and reproduce message orderings accurately. The problem can occur when the following conditions...
PR #348 is extending the DynamicMetrics tool to measure actor-specific issues. While doing this work, I noticed the DyM does not correctly report the call targets anymore. This broke between...
With #378 coverage tracking wasn't ported to GitHub actions, mostly because the setup seems to be defunct. Should restore it and get proper integration with GitHub again.
In https://github.com/SOM-st/TruffleSOM/pull/47, TruffleSOM uses a "better" approach to initialize the unsafe accesses for the object model. Instead of needing instances of objects, which have their own virtual methods, we can...
The new uniform record&replay (#337) does not yet handle external events, including the timer. We essentially need to reimplement the timer using the new tracing infrastructure in `TracingActivityThread`. This will...
An earlier attempt to investigate the issue lead me to add try/finally around sensitive operations in the `ObjectTransitionSafepoint`, and I initially thought that would fix it, the test started to...
- add five SOMns applications and tests. These applications feature asynchronous message passing using actors. The goal is to use them later for a user study to evaluate the debugging...
Linux-only (I assume) A call to `ant native` after an `ant clobber` makes the build fail with the following error: ``` native: [exec] Error: Invalid Path entry /home/sopi/Documents/Experiments/SOMns/libs/truffle/substratevm/mxbuild/linux-amd64/SVM_HOSTED_NATIVE/linux-amd64 [exec] Caused...
When not using the launcher script `som`, we seem to have a few issues. - `./som-native` errors with a NPE - having som-native in another folder gives a cryptic error...
Pull request to fix a bug in the `AsyncTestCase` class related to the failed assertions. The `onError` block of the `runUsing` method declares `e` as the variable for the exception...