On Wed, Mar 22, 2017 at 03:08:00PM +0300, Oleg Artemiev wrote: > > why do you have to reboot? > Cost of reboot in __understanding__ what the hell is the reason is > less than cost of restoring correct state after reboot. > > I feel like queue in some code is failing to grow. > Usually I detect such things via load testing. > > As a QA professional I'm ready to commit to: > > 1) run (some times within free time) load tests > 2) provide nummeric results (not raw logs!) on my dom0 - no VM names. > Only symbolic handles I'm ok to publish are qubes OS internals - no VM > names and similar personal stuff. > > Only if I do understand the code . Thus the load testing code and > final summary report must be available to me + no pipes to pass > numbers via any protocol into internet or tor. > Better if applied by python, nodejs,bash, or ruby or erlang language .
let me try again:
- how does the reboots happen? you said "you have to reboot", did you mean the
machine just sponteaniously reboots and thus forces you into reboots?
- is there anything special you are doing when this happen or does it happen
"randomly"?
--
cheers,
Holger
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/20170322123230.GA28199%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
