search for: wait_for

Hi all, In GOOS[1] they use an assertion called assertEventually which samples the system for a success state until a certain timeout has elapsed. This allows you to synchronise the tests with asynchronous code. Do we have an equivalent of that in the Ruby / RSpec world already? I know capybara has wait_until { } but that''s fairly rudimentary - the failure message isn''t very

...erial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. This race condition can be easily reproduced by hot plugging a number of virtio-blk disks. Also in systemd, there used to be a related workaround in udev rules called 'WAIT_FOR="serial"', but it is removed in later versions. Now let's generate a KOBJ_CHANGE event after the attributes are ready. Signed-off-by: Fam Zheng <famz at redhat.com> --- drivers/block/virtio_blk.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/block/virtio_...

...erial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. This race condition can be easily reproduced by hot plugging a number of virtio-blk disks. Also in systemd, there used to be a related workaround in udev rules called 'WAIT_FOR="serial"', but it is removed in later versions. Now let's generate a KOBJ_CHANGE event after the attributes are ready. Signed-off-by: Fam Zheng <famz at redhat.com> --- drivers/block/virtio_blk.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/block/virtio_...

.../dev/disk/by-id/ entry doesn't always get > > created. > > > > This race condition can be easily reproduced by hot plugging a number of > > virtio-blk disks. > > > > Also in systemd, there used to be a related workaround in udev rules > > called 'WAIT_FOR="serial"', but it is removed in later versions. > > > > Now let's generate a KOBJ_CHANGE event after the attributes are ready. > > The same race is present in other drivers as well, e.g. nvme. Please > find a way to make this work properly without needing t...

.../dev/disk/by-id/ entry doesn't always get > > created. > > > > This race condition can be easily reproduced by hot plugging a number of > > virtio-blk disks. > > > > Also in systemd, there used to be a related workaround in udev rules > > called 'WAIT_FOR="serial"', but it is removed in later versions. > > > > Now let's generate a KOBJ_CHANGE event after the attributes are ready. > > The same race is present in other drivers as well, e.g. nvme. Please > find a way to make this work properly without needing t...

Hello testers, 4.0.0-rc3 was just tagged from the branch at r296762. This is a release candidate in the real sense: if no major issues show up with this one, it is the version that will be released. Please let me know if you find any issues, including in release notes or documentation, which will be on the pre-release web site later today. Please build, test, and upload binaries to the sftp

...ting a backup to .ssh/authorized_keys-2013-07-01.bak if not already done today... Uploading keys to .ssh/authorized_keys-new... File does exist and has correct size, moving to .ssh/authorized_keys... .ssh/authorized_keys-new .ssh/authorized_keys /usr/lib/ruby/vendor_ruby/net/sftp/session.rb:846:in `wait_for': Net::SFTP::StatusException (4, "failure") (Net::SFTP::StatusException) from /usr/lib/ruby/vendor_ruby/net/sftp/session.rb:590:in `rename!' from ./distkeys:210:in `block in commit' from /usr/lib/ruby/vendor_ruby/net/sftp/request.rb:87:in `call'...

...g > on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get > created. > > This race condition can be easily reproduced by hot plugging a number of > virtio-blk disks. > > Also in systemd, there used to be a related workaround in udev rules > called 'WAIT_FOR="serial"', but it is removed in later versions. > > Now let's generate a KOBJ_CHANGE event after the attributes are ready. The same race is present in other drivers as well, e.g. nvme. Please find a way to make this work properly without needing to hack every driver to se...

...always get > > > created. > > > > > > This race condition can be easily reproduced by hot plugging a number of > > > virtio-blk disks. > > > > > > Also in systemd, there used to be a related workaround in udev rules > > > called 'WAIT_FOR="serial"', but it is removed in later versions. > > > > > > Now let's generate a KOBJ_CHANGE event after the attributes are ready. > > > > The same race is present in other drivers as well, e.g. nvme. Please > > find a way to make this work p...

...d is tmpfs mount. This command causes > balloon to require deflation. > tysand at vm grep Mem /proc/meminfo > MemTotal: ? ? ? ?8172852 kB > MemFree: ? ? ? ? ?138932 kB > MemAvailable: ? ? ?83428 kB > tysand at vm ~ $ grep Mem /proc/meminfo > free(): invalid pointer > -bash: wait_for: No record of process 5415 > free(): invalid pointer > > Or similarly, I've seen SSH terminate with: > tysand at vm:~$ grep Mem /proc/meminfo > *** stack smashing detected ***: <unknown> terminated > > Presumably the stack smashing and "free(): invalid pointer&...

On 09/14/2019 02:36 AM, Tyler Sanderson wrote: > Hello, I'm curious about the intent of VIRTIO_BALLOON_F_FREE_PAGE_HINT > (commit > <https://github.com/torvalds/linux/commit/86a559787e6f5cf662c081363f64a20cad654195#diff-fd202acf694d9eba19c8c64da3e480c9>). > > > My understanding is that this mechanism works similarly to the > existing inflate/deflate queues. Pages

On 09/14/2019 02:36 AM, Tyler Sanderson wrote: > Hello, I'm curious about the intent of VIRTIO_BALLOON_F_FREE_PAGE_HINT > (commit > <https://github.com/torvalds/linux/commit/86a559787e6f5cf662c081363f64a20cad654195#diff-fd202acf694d9eba19c8c64da3e480c9>). > > > My understanding is that this mechanism works similarly to the > existing inflate/deflate queues. Pages

...hared_future/get.pass.cpp libc++ :: std/thread/futures/futures.shared_future/move_assign.pass.cpp libc++ :: std/thread/futures/futures.shared_future/move_ctor.pass.cpp libc++ :: std/thread/futures/futures.shared_future/wait.pass.cpp libc++ :: std/thread/futures/futures.shared_future/wait_for.pass.cpp libc++ :: std/thread/futures/futures.shared_future/wait_until.pass.cpp libc++ :: std/thread/futures/futures.task/futures.task.members/assign_move.pass.cpp libc++ :: std/thread/futures/futures.task/futures.task.members/ctor_func.pass.cpp libc++ :: std/thread/futures/futures....

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>

Hi all, First thing first: It works, I now no longer have a few dropped frames every 10s on my testbox here with the pageflip i-g-t tests. Random notes: - New design has per-crtc locks to protect the crtc input-side (pageflip, cursor) for r/w and the output state of the crtc (mode, dpms) as read-only. It also required completely revamped fb lifecycle management, those are now refcounted

The race condition is noticed between disk_add() and disk attributes, on virtio-blk hotplug. Userspace listens to the KOBJ_ADD uevent generated in add_disk(). At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. As pointed out by Christoph Hellwig in the specific fix [1], virtio-blk

The race condition is noticed between disk_add() and disk attributes, on virtio-blk hotplug. Userspace listens to the KOBJ_ADD uevent generated in add_disk(). At that point we haven't created the serial attribute file, therefore depending on how fast udev reacts, the /dev/disk/by-id/ entry doesn't always get created. As pointed out by Christoph Hellwig in the specific fix [1], virtio-blk