Displaying 6 results from an estimated 6 matches for "naiveschedul".
Did you mean:
naivescheduler
2017 Apr 03
3
Very hard to reproduce bug (?) in R-devel
...lem. We can't be sure, but the error
message suggests that a promise is getting evaluated with the wrong
environment.
Here's the relevant output from the tests:
1. Error: pool scheduler: schedules things in the right order
(@test-scheduling.R#13)
could not find function "task"
1: naiveScheduler$protect({
scheduleTask(1000, function() {
results <<- c(results, 3L)
})
scheduleTask(100, function() {
results <<- c(results, 2L)
})
scheduleTask(10, function() {
results <<- c(results, 1L)
})
}) at te...
2017 Apr 05
6
Very hard to reproduce bug (?) in R-devel
...--
20170405-182559.456628-17 --3--
20170405-182729.456318-16 --1--
20170405-182729.456318-16 --2--
20170405-182729.456318-16 --3--
--2--
20170405-182549.466875-18 --3--
1. Error: pool scheduler: schedules things in the right order
(@test-scheduling.R#13)
could not find function "task"
1: naiveScheduler$protect({
scheduleTask(1e+05, function() {
results <<- c(results, 3L)
})
scheduleTask(10000, function() {
results <<- c(results, 2L)
})
scheduleTask(10, function() {
results <<- c(results, 1L)
})
}) at...
2017 Apr 03
0
Very hard to reproduce bug (?) in R-devel
...r
> message suggests that a promise is getting evaluated with the wrong
> environment.
>
> Here's the relevant output from the tests:
> 1. Error: pool scheduler: schedules things in the right order
> (@test-scheduling.R#13)
> could not find function "task"
> 1: naiveScheduler$protect({
> scheduleTask(1000, function() {
> results <<- c(results, 3L)
> })
> scheduleTask(100, function() {
> results <<- c(results, 2L)
> })
> scheduleTask(10, function() {
> results <&l...
2017 Apr 05
2
Very hard to reproduce bug (?) in R-devel
On Wed, Apr 5, 2017 at 2:24 PM, Robert McGehee <rmcgehee at walleyetrading.net>
wrote:
> Winston,
> I had a similar experience to you tracking down an insanely difficult bug
> in my R code that "disappeared" whenever slight changes were made to the
> script (e.g. like adding cat() statements). In my case, it coincided with
> my over-eager compilation of R and its
2017 Apr 05
0
Very hard to reproduce bug (?) in R-devel
...--
20170405-182559.456628-17 --3--
20170405-182729.456318-16 --1--
20170405-182729.456318-16 --2--
20170405-182729.456318-16 --3--
--2--
20170405-182549.466875-18 --3--
1. Error: pool scheduler: schedules things in the right order
(@test-scheduling.R#13)
could not find function "task"
1: naiveScheduler$protect({
scheduleTask(1e+05, function() {
results <<- c(results, 3L)
})
scheduleTask(10000, function() {
results <<- c(results, 2L)
})
scheduleTask(10, function() {
results <<- c(results, 1L)
})
}) at...
2017 Apr 04
2
Very hard to reproduce bug (?) in R-devel
>
>
>>
I've done some more investigation into the problem, and it is very
difficult to pin down. What it looks like is happening is roughly like this:
- `p` is an environment and `p$e` is also an environment.
- There is a loop. In each iteration, it looks for one item in `p$e`, saves
it in a variable `x`, then removes that item from `p$e`. Then it invokes
`x()`. The loop runs