Search results

|| 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