Threads and loops and testing (order and timing) - determining expected behaviour

Support, Help & Resources
1

Salutations Sonic Wizards and wicked smart cool folks :pray:

Apologies if this is already explained ad nauseum, taking it all back to basics, trying to grasp what’s going.

  • I’m using the log panel and the order of output there (and thread name / time log info) to try and understand what’s happening
  • If I add code to a workspace buffer and run with no threads or loops*, the code outputs as expected :+1:

*added a do loop that could repeatedly perform a task that might affect the virtual time (post processing)


puts 1,2,3
puts '4 5 6'
1000.times do
  #sleep
  #sync
  #
end

puts "virtual time #{vt}"
  • If I add even just one named thread, order of output can vary between runs!
    (:information_source: running and stopping and inspecting output)
puts 1,2,3
puts '4 5 6'
1000.times do
  #sleep
  #sync
  #
end

puts "virtual time #{vt}"


in_thread(name: :t1) do
  puts 't1 '
end
  1. Is this expected behaviour?
  2. (If expected) Can this be explained?
  3. Is it possible to override , eg force ordering logic?

running version v4.4

I’ve read a lot about lots, but want to keep it simple, so a 10 year old and I can comprehend!

TlDr: How to synchronise loops (in threads) and multiple named threads to start together (eg at time 0), and control/predict the order in which they will be executed and results output ?

Many thanks :ok_hand: