Search results

...this disk image to qemu via '''-hdb'''(need further changes if need virtio block device) == Enable virtio block and network device ==

-----BEGIN PGP PUBLIC KEY BLOCK----- -----END PGP PUBLIC KEY BLOCK-----

| style="color:red" | BLOCK | style="color:red"| BLOCK

bi: Blocks received from a block device (blocks/s). bo: Blocks sent to a block device (blocks/s).

* 1 Two positions terminal block

| 　||CrownBay||bgcolor="red" |BLOCK||emgd crownbay build failed; matchbox-panel segfault; S3 fail on B0 board | '''ADT'''||　||bgcolor="red" |BLOCK||i686 toolchain not copied to sharing folder; unfs does not work with qemup

...s to call aio_error with argument aiocbp which does not point at a control block for an asynchronous I/O request, and expect error EINVAL. call aio_return with with argument aiocbp which does not point at a control block for an asynchronous I/O request, and expect error EINVAL. But this is optio

|| fcntl16 || NEW || || fcntl16 0 TINFO : Entering block 1 fcntl16 0 TINFO : Exiting block 1

modified: ../block/blkdebug.c modified: ../block/blkverify.c

...ilding. QA tested 4 QEMU and 3 non-intel BSPs, as well as ADT. There are 3 BLOCK bugs reported. The qemuarm/mips sato-sdk images build failed due to depende ...ilding. QA tested 4 QEMU and 3 non-intel BSPs, as well as ADT. There are 3 BLOCK bugs reported. The qemuarm/mips sato-sdk images build failed due to depende

The network based PR service is a missing building block in the current poky build system to enable the "basichash" ''BB_SIGNATURE_H

...ostly modify that mechanism. Major optional parameters, like disabling the block layer perhaps, will be created as peers to the <code>small</code> mechanism

: ''Block-based'' update mechanisms directly modify blocks in the partition(s) that t : The partition which contains the OS. May be strictly read-only (block-based update mechanisms) or read/write (file-based). Some update mechanisms

...of sentences of the same quoted text, you should move below that relevant block again. Do not reply below the whole of the quoted text. Also remove any irr

...p to the agenda, don't rathole on bug resolution, and stay within our time block.

I found that the kernel will block early in the boot process when entropy is restricted, e.g.:

...ings with Sphinx built-in, for example they can be used/nested inside code-block sections. Another mechanism was implemented so that we can continue to use .. code-block::

{% block extraheadcontent %} {% block title %}{{title}}{% endblock %}

...sts/culling1<br />memcheck/tests/error_counts<br />memcheck/tests/describe-block<br />massif/tests/long-time<br />memcheck/tests/descr_belowsp<br />memcheck

...s to call aio_error with argument aiocbp which does not point at a control block for an asynchronous I/O request, and expect error EINVAL. call aio_return with with argument aiocbp which does not point at a control block for an asynchronous I/O request, and expect error EINVAL. But this is optio

|| fcntl16 || NAB || || fcntl16 0 TINFO : Entering block 1 fcntl16 0 TINFO : Exiting block 1

This is the weekly test report for Yocto 1.1 M2 RC1 build. There are 2 new BLOCK bugs and 1 new NORMAL bug found in this testing. All BSP sato-sdk images ha ...build could not work and one new LTP failure found with new kernel. The 2 BLOCK issues on have been addressed and a new build is ready for QA testing. Exce

...p to the agenda, don't rathole on bug resolution, and stay within our time block.

...9FF14" | All high features are completed except bug 5827 which is does not block the release.

...if possible. || bgcolor="#39FF14" | It is getting worse but not enough to block release - Done - https://wiki.yoctoproject.org/charts/perf_milestone/perfor

...lt contains specific operations performed upon each I/O submitted into the block I/O layer. Due to the record (block, cache or buffer),

'''Priority:''' 1 = Must have, 2 = Nice to have but wouldn't block a release, 3 = Lower priority, desired, defined plan, 4 = Worthwhile ideas,

...Symlink <br /> 4 - Socket <br /> 5 - Fifo <br /> 6 - Character <br /> 7 - Block

|| '''OLVER Core Tests''' || v 4.1.4-1 || Failures: 9 || Failures: 11 || Block

'''Priority:''' 1 = Must have, 2 = Nice to have but wouldn't block a release, 3 = Lower priority, desired, defined plan, 4 = Worthwhile ideas,

block:block_rq_abort [Tracepoint event] block:block_rq_requeue [Tracepoint event]

1. If there's nothing major that should block the release, the program manager will notify QA to continue with a full-pas

and then many dedicate a block of time (a week) where the distro team

...om testing but these are both relatively minor issues that are unlikely to block release. ...ions, nobody is available to dive in and debug this immediately so it will block M3.

...codebase. Some issues were found with artefact publication but nothing to block the rc1 as yet. ...to be blocked on locale issues which may prove tricky to resolve and will block M3 as we need the glibc upgrade for various reasons.

...ests/amd64/insn_mmx<br />none/tests/bug234814<br />memcheck/tests/describe-block<br />memcheck/tests/linux/timerfd-syscall<br />drd/tests/pth_spinlock<br />

...st regressions but these look intermittent in nature and hence unlikely to block release ...which continue to cause major problems with master too. These will have to block the M3 build/release.

...ead with the release ASAP. As such, if anyone has things they think should block release, please let us know. **virtio block device issues in qemu we’re hoping are fixed in qemu 7.1.0

...PRC, we do a crash course in ""dealing with OE"" and then many dedicate a block of time (a week) where the distro team comes up with a patch set we then pr

...sts/amd64/insn_mmx<br />none/tests/munmap_exe<br />memcheck/tests/describe-block<br />none/tests/pth_rwlock<br />memcheck/tests/linux/timerfd-syscall<br />d

...sts/amd64/insn_mmx<br />none/tests/munmap_exe<br />memcheck/tests/describe-block<br />none/tests/pth_rwlock<br />memcheck/tests/linux/timerfd-syscall<br />d

...PRC, we do a crash course in ""dealing with OE"" and then many dedicate a block of time (a week) where the distro team comes up with a patch set we then pr

...t kernel upgrade on centos8 causing testsdk to fail. This will also likely block M1 as builds fail with the issue and we’d have to disable autobuilder wor

...r. The failure seems consistent on AB but unreproducible on my machine: IP block of some kind? * glibc-locale do_package failure "memory clobbered past end of allocated block" already filed - https://bugzilla.yoctoproject.org/show_bug.cgi?id=8973