Upgrade less from 481 to 487.
License checksum changes are not related to license changes.
(From OE-Core rev: 5d8be59d2f3430439868926d1424420d6a78a1b5)
Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtiff/tif_predict.h, libtiff/tif_predict.c:
Replace assertions by runtime checks to avoid assertions in debug mode,
or buffer overflows in release mode. Can happen when dealing with
unusual tile size like YCbCr with subsampling.
External References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-9535
Patch from:
3ca657a8796a984bf790
(From OE-Core rev: 61d3feb9cad9f61f6551b43f4f19bfa33cadd275)
Signed-off-by: Mingli Yu <Mingli.Yu@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The existing sed expression can match expressions like
--sysroot=/some/path/xxx-linux/ which clearly isn't intended and
injects incorrect paths into LDFLAGS.
Fix this in the same way we address the problem in CFLAGS. This fixes corrupt
build paths and incorrect paths in .la files amongst other issues.
(From OE-Core rev: 9a8382422ddbb0972dc25b752204f4908bb9857c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A SSTATEPOSTINSTFUNCS function here is overkill, just do this in a
do_install_append_class-native and create relative symlinks rather
than absolute ones which would then have to be relocated.
(From OE-Core rev: 518e8d0216b0f42f574e42288804f553b9ff6f99)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This hasn't been used in years and isn't referenced anywhere, drop
the definition.
(From OE-Core rev: 68258f856f08f35813964e58ef761471e29373ad)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Historically the processing of kernel meta data contained some
commands that exited with a non-zero return code. Special processing
was required to properly deal with their exit.
That is no longer true, and instead of handling all return codes
and doing an explicit 'exit' call, we can remove set -e from the
routine and have all errors be trapped and stop processing.
(From OE-Core rev: 476ffd57cf5b6fba40d4e3f5dd913824ab8a8d3d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Lernel meta-data that has patches, but no branches, can trigger an
error due to no branch specific patch queue.
This error then cascades to more issues since the tools are using
a named file in /tmp to store and display error messages to the
user.
We fix both issues though the following kern tools tweaks:
commit bd9e1d6c9b0a34ff3e19a06999aaf57ffadfd04c
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Fri Dec 2 13:09:40 2016 -0500
scc: use mktemp for consolidated output capture
To provide useful error messages the tools dump pre-processed
files and messages to a temporary file. If multiple users are
doing builds, this means they either race, or can have permissions
issues.
By creating the temporary file via mktemp, we avoid both issues.
(We also make sure to clean these up on exit, or /tmp will get
polluted quickly).
commit a287da4bfe0b4acb8f2b0627bd8e7abd1a1dde26
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Fri Dec 2 13:08:08 2016 -0500
patch: do not assume a branch specific patch queue is needed
When processing input files per-branch and global patch queues are
generated. If the meta-data has not created any branches in the
repo, no branch specific queue is required.
The tools assumed that one is always valid, and hence would throw a
non-zero exit code and stop processing.
By testing for a named per-branch queue, we avoid this issue.
(From OE-Core rev: 0fd7da7375f0dcc59b56791fd482de557507c04c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Integrating the 4.8.9 and 4.8.10 -stable updates. The commit log is
as follows:
cf5ae2989a32 Linux 4.8.10
5cd8f6788ff3 usb: gadget: f_fs: stop sleeping in ffs_func_eps_disable
e2458382c792 usb: gadget: f_fs: edit epfile->ep under lock
e34a0f1c53b5 sparc64: Delete now unused user copy fixup functions.
af97481a6f5b sparc64: Delete now unused user copy assembler helpers.
ac663c54f40b sparc64: Convert U3copy_{from,to}_user to accurate exception reporting.
d91bb7a87e26 sparc64: Convert NG2copy_{from,to}_user to accurate exception reporting.
a15859f9d839 sparc64: Convert NGcopy_{from,to}_user to accurate exception reporting.
bb522726d311 sparc64: Convert NG4copy_{from,to}_user to accurate exception reporting.
b0580eadc19f sparc64: Convert U1copy_{from,to}_user to accurate exception reporting.
50e927483ccf sparc64: Convert GENcopy_{from,to}_user to accurate exception reporting.
620ec41010d1 sparc64: Convert copy_in_user to accurate exception reporting.
bf4d0da8e800 sparc64: Prepare to move to more saner user copy exception handling.
bbbab9f59ea7 sparc64: Delete __ret_efault.
81a91edbb91a sparc64: Handle extremely large kernel TLB range flushes more gracefully.
7f8a50eb38d3 sparc64: Fix illegal relative branches in hypervisor patched TLB cross-call code.
f7ef55af2f1b sparc64: Fix instruction count in comment for __hypervisor_flush_tlb_pending.
2a28ab3d4148 sparc64: Fix illegal relative branches in hypervisor patched TLB code.
f4fb552a033e sparc64: Handle extremely large kernel TSB range flushes sanely.
51915c6d9070 sparc: Handle negative offsets in arch_jump_label_transform
da6fe239ceff spi: spidev_test: fix build with musl libc
4ea98e573d65 net: stmmac: Fix lack of link transition for fixed PHYs
150b491b1b88 sctp: change sk state only when it has assocs in sctp_shutdown
5235fcfa6cf8 bnx2: Wait for in-flight DMA to complete at probe stage
6523ff2e27fe Revert "bnx2: Reset device during driver initialization"
224fb8cbefb2 mlxsw: spectrum_router: Correctly dump neighbour activity
9092bbd64bd9 mlxsw: spectrum: Fix refcount bug on span entries
5712922773b5 Revert "include/uapi/linux/atm_zatm.h: include linux/time.h"
2b5f22e4f7fd tcp: take care of truncations done by sk_filter()
22a78d4c7f43 ipv4: use new_gw for redirect neigh lookup
bccb4093d464 net: __skb_flow_dissect() must cap its return value
a1632e969a55 net: icmp_route_lookup should use rt dev to determine L3 domain
9885f474d92b sock: fix sendmmsg for partial sendmsg
b78ba0a0f231 fib_trie: Correct /proc/net/route off by one error
92fd1c1f2fd2 net: icmp6_send should use dst dev to determine L3 domain
09ee09498bca bpf: fix htab map destruction when extra reserve is in use
de289ad2e575 sctp: assign assoc_id earlier in __sctp_connect
76b5fee5cfa0 ipv6: dccp: add missing bind_conflict to dccp_ipv6_mapped
84d9c612bb7a ipv6: dccp: fix out of bound access in dccp_v6_err()
ba93cf7d2118 dccp: fix out of bound access in dccp_v4_err()
378a61101374 dccp: do not send reset to already closed sockets
72b03e549b95 dccp: do not release listeners too soon
b3523a0773ed tcp: fix return value for partial writes
1f49cc6fa91c ipv4: allow local fragmentation in ip_finish_output_gso()
842a858fa048 tcp: fix potential memory corruption
fc3b825f2c81 ip6_tunnel: Clear IP6CB in ip6tunnel_xmit()
f5f4b71d5632 bgmac: stop clearing DMA receive control register right after it is set
0c7f764d2c6a net: mangle zero checksum in skb_checksum_help()
ac22a3ba0796 net: clear sk_err_soft in sk_clone_lock()
5b078dc6fb64 dctcp: avoid bogus doubling of cwnd after loss
876577321657 Linux 4.8.9
07d00beb1e04 netfilter: fix namespace handling in nf_log_proc_dostring
8ef009e09c13 drm/i915: Fix mismatched INIT power domain disabling during suspend
88a45e5d2c0d drm/amdgpu: fix a vm_flush fence leak
25ed6e4b0b65 drm/amdgpu: fix fence slab teardown
de5e9aa77a3c NFSv4.1: work around -Wmaybe-uninitialized warning
18c801047a18 libceph: fix legacy layout decode with pool 0
53c1792b94da memcg: prevent memcg caches to be both OFF_SLAB & OBJFREELIST_SLAB
02e1ee6b3e1c mmc: mxs: Initialize the spinlock prior to using it
ce0702e35aeb pinctrl: iproc: Fix iProc and NSP GPIO support
320244ac9eb6 ASoC: sun4i-codec: return error code instead of NULL when create_card fails
2140d4fd9277 ASoC: Intel: Skylake: Always acquire runtime pm ref on unload
5037fdbc62c2 gpio: of: fix GPIO drivers with multiple gpio_chip for a single node
7a9239fd0480 gpio/mvebu: Use irq_domain_add_linear
6de98e87effb batman-adv: Modify neigh_list only with rcu-list functions
a3f000ce7b44 ACPI/PCI: pci_link: Include PIRQ_PENALTY_PCI_USING for ISA IRQs
6c76dd0c7066 ACPI/PCI: pci_link: penalize SCI correctly
86c711665c84 ACPI/PCI/IRQ: assign ISA IRQ directly during early boot stages
ad185d9251e1 ACPI / APEI: Fix incorrect return value of ghes_proc()
b55ebc89ab1d mmc: sdhci-msm: Fix error return code in sdhci_msm_probe()
85284c0850f9 i40e: fix call of ndo_dflt_bridge_getlink()
1242c9dfab0c hwrng: core - Don't use a stack buffer in add_early_randomness()
c1a2ada73dac lib/genalloc.c: start search from start of chunk
06bb5ebedbb4 s390/dumpstack: restore reliable indicator for call traces
1ef1bd02ad23 rtc: pcf2123: Add missing error code assignment before test
4baabb72e9dd clk: samsung: clk-exynos-audss: Fix module autoload
3bbdbd8aa3c8 x86/build: Fix build with older GCC versions
f5eadc27a60c Revert "clocksource/drivers/timer_sun5i: Replace code by clocksource_mmio_init"
645a6b823739 nvme: Delete created IO queues on reset
07c4cbe01341 svcrdma: Tail iovec leaves an orphaned DMA mapping
4131e00a436e svcrdma: Skip put_page() when send_reply() fails
755ab7aa1466 mei: bus: fix received data size check in NFC fixup
d1b564536c6a perf top: Fix refreshing hierarchy entries on TUI
6ac4e06b717f Input: synaptics-rmi4 - fix error handling in I2C transport driver
d3716f1b3e4b Input: synaptics-rmi4 - fix error handling in SPI transport driver
66503ec38f34 watchdog: core: Fix devres_alloc() allocation size
c5e9e5cc8cd1 agp/intel: Flush chipset writes after updating a single PTE
813617a4c8dc iommu/vt-d: Fix dead-locks in disable_dmar_iommu() path
b6ef0b142208 iommu/amd: Free domain id when free a domain of struct dma_ops_domain
2ef38255b588 iommu/io-pgtable-arm: Check for v7s-incapable systems
d3d9428d7133 xprtrdma: Fix DMAR failure in frwr_op_map() after reconnect
31c749bee3de xprtrdma: use complete() instead complete_all()
67080e2785a3 drm/amd: fix scheduler fence teardown order v2
b0da5ab2ffb5 drm/amdgpu: fix sched fence slab teardown
920a85ba4306 tty/serial: at91: fix hardware handshake on Atmel platforms
9d76a886eb2f drm/amdgpu: fix crash in acp_hw_fini
6e652d18d73d drm/amdgpu: disable runtime pm in certain cases
8c8fdc683295 drm/i915/dp: Extend BDW DP audio workaround to GEN9 platforms
db8e005bf2ba drm/i915/dp: BDW cdclk fix for DP audio
f50b7450a8e4 drm/i915: Respect alternate_ddc_pin for all DDI ports
e1b24f6a0b3c drm/radeon: disable runtime pm in certain cases
eb13abb0e515 KVM: arm/arm64: vgic: Prevent access to invalid SPIs
2850fad5acb0 scsi: scsi_dh_alua: Fix a reference counting bug
5fac70d772a4 scsi: scsi_dh_alua: fix missing kref_put() in alua_rtpg_work()
f29bcd11a170 scsi: mpt3sas: Fix for block device of raid exists even after deleting raid disk
b2040deabb07 scsi: qla2xxx: Fix scsi scan hang triggered if adapter fails during init
1281b9683f96 iio: st_sensors: fix scale configuration for h3lis331dl
4dfb6d1dd11d iio: orientation: hid-sensor-rotation: Add PM function (fix non working driver)
341c5534edad iio: hid-sensors: Increase the precision of scale to fix wrong reading interpretation.
b9d031f354da cdc-acm: fix uninitialized variable
c480880cd12c clk: qoriq: Don't allow CPU clocks higher than starting value
ee27fd32c499 toshiba-wmi: Fix loading the driver on non Toshiba laptops
f713523a234c drbd: Fix kernel_sendmsg() usage - potential NULL deref
31da266e4b9a usb: gadget: u_ether: remove interrupt throttling
264e4131a167 USB: cdc-acm: fix TIOCMIWAIT
c12c24eeaf77 usb: dwc3: Fix error handling for core init
6b95417150b7 staging: nvec: remove managed resource from PS2 driver
82239ab105a5 Revert "staging: nvec: ps2: change serio type to passthrough"
529789866abe drivers: staging: nvec: remove bogus reset command for PS/2 interface
dea774aac054 staging: comedi: ni_tio: fix buggy ni_tio_clock_period_ps() return value
5d510185f99a staging: sm750fb: Fix bugs introduced by early commits
45983d678b70 staging: iio: ad5933: avoid uninitialized variable in error case
5289e59246dd mmc: mmc: Use 500ms as the default generic CMD6 timeout
ce4dfe7d927e mmc: sdhci: Fix unexpected data interrupt handling
bde8d3f73375 mmc: sdhci: Fix CMD line reset interfering with ongoing data transfer
10d24701f3f4 cpupower: Correct return type of cpu_power_is_cpu_online() in cpufreq-set
f062e738c19b pinctrl: cherryview: Prevent possible interrupt storm on resume
1d99fe3317e3 pinctrl: cherryview: Serialize register access in suspend/resume
f5ad96462615 arc: Implement arch-specific dma_map_ops.mmap
004e7c97f181 PCI: Don't attempt to claim shadow copies of ROM
7fac0361f94e ARC: timer: rtc: implement read loop in "C" vs. inline asm
4058116db4d0 s390/hypfs: Use get_free_page() instead of kmalloc to ensure page alignment
2f3e0b82ebe9 coredump: fix unfreezable coredumping task
d6ee4f47e2e7 mm/hugetlb: fix huge page reservation leak in private mapping error paths
e87bf4f558f1 mm: hwpoison: fix thp split handling in memory_failure()
67c79e166d46 swapfile: fix memory corruption via malformed swapfile
c87739e5d029 shmem: fix pageflags after swapping DMA32 object
5b5243b606ec mm, frontswap: make sure allocated frontswap map is assigned
2e594273d4c5 dib0700: fix nec repeat handling
9964230320d5 ASoC: cs4270: fix DAPM stream name mismatch
9386a722d250 ALSA: info: Limit the proc text input size
c3ea1b15b71e ALSA: info: Return error for invalid read/write
(From OE-Core rev: b5e43be6aaf912cf6c679ee98ed61cf34dd00ee8)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As of html5lib 0.9999999/1.0b8 (released on July 14, 2016), some modules
have moved from _base to base. Handle this, while staying compatible
with earlier versions.
(Bitbake rev: 1679188f9c55c615cae780f2b5e6852dea9cf2ec)
Signed-off-by: Daniel Lublin <daniel@lublin.se>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We assume that the value taken by variable v can be string,
integer or any type which can be marshalled by xmlrpc. This
change would help us to convert the non marshallable types
to string. So that we don't get exception from xmlrpc.
[YOCTO #10740]
(Bitbake rev: efb0e47479b3526bc047112f7200087c5844bba4)
Signed-off-by: Sujith H <sujith.h@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Adds the ability to specify a Selenium Docker container server as
a driver. This allows for repeatable tests independent of host.
Currently we assume you are using the Firefox container. Instructions
are located in the README in tests/browser.
(Bitbake rev: 7df842f8f8b2ae640109ed06729ab59c9469fc64)
Signed-off-by: brian avery <brian.avery@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The parameters to Python string formatting need to be inside a tuple.
(Bitbake rev: 3c82af11b89cf251c3e56725a1eed2d3f4bd835b)
Signed-off-by: Ismo Puustinen <ismo.puustinen@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The current disk usage is interesting and may be worth logging over
time as part of the build statistics. Instead of re-implementing the
code and the configuration option (BB_DISKMON_DIRS), the information
gathered by monitordisk.py is made available to buildstats.bbclass via
a new event.
This has pros and cons:
- there is already a useful default configuration for "interesting" directories
- no code duplication
- on the other hand, users cannot configure recording separately from
monitoring (probably not that important)
(Bitbake rev: f065ac17d0031dca6309ddbff18c8792630de865)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There's no need to encode and decode the hash key as a single string,
a tuple works just fine. Iterating over entries can be written more
concisely.
Entries in the stat results are integers, not floating point values.
(Bitbake rev: 3c943e989964382c0b819d92de26a0c914ebed33)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Hooking the disk monitor into the regular heatbeat event instead
of the runqueue solves two problems:
- When there is just one long running task which fills up the disk,
the previous approach did not notice that until after the completion
of the task because _execute_runqueue() only gets called on task
state changes. As a result, aborting a build did not work in this
case.
- When there are many short-lived tasks, disk space was getting
checked very frequently. When the storage that is getting checked
is on an NFS server, that can lead to noticable traffic to the
server.
(Bitbake rev: 4547eea26803a9cd355d8b045197bcbdbb36a9ad)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The intended usage is for recording current system statistics from
/proc in buildstats.bbclass during a build and for improving the
BB_DISKMON_DIRS implementation.
All other existing hooks are less suitable because they trigger at
unpredictable rates: too often can be handled by doing rate-limiting
in the event handler, but not often enough (for example, when there is
only one long-running task) cannot because the handler does not get
called at all.
The implementation of the new heartbeat event hooks into the cooker
process event queue. The process already wakes up every 0.1s, which is
often enough for the intentionally coarse 1s delay between
heartbeats. That value was chosen to keep the overhead low while still
being frequent enough for the intended usage.
If necessary, BB_HEARTBEAT_EVENT can be set to a float specifying
the delay in seconds between these heartbeat events.
(Bitbake rev: 7cf22ea057d28c54bd98dc1ab7a43402a29ff1f5)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Setting WKS_FILE variable in qemux86-64 made wic test to
use wrong wks file to produce an image and resulted in
test_qemu failure.
Used conditional assignment in qemux86-64 and explicitly
set WKS_FILE in wic testing suite to make the suite to use
wic-image-minimal.wsk. This should fix test_qemu failure.
(From OE-Core rev: 3bca4d18c2712e3b154bacfb917f0a749ebaddeb)
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The do_deploy runs depmodwrapper which requires
pkgdata/kernel-depmod/kernel-abiversion, which is generated by
PACKAGEFUNCS. So we need let do_deploy depend on do_packagedata.
This can fix the errors which happens sometimes when kernel upgrades:
DEBUG: Executing shell function do_deploy
Error: Kernel version 4.8.8-WR9.0.0.1_standard does not match kernel-abiversion (4.8.8-WR9.0.0.0_standard)
And we only see this error when kernel upgrades and rebuild, but doesn't
see it in a normal build, this is becuase depmodwrapper doesn't exit
error when kernel-depmod/kernel-abiversion doesn't exit, it just prints
an error which should go into log.do_deploy:
if [ ! -r /path/to/sysroots/qemux86-64/pkgdata/kernel-depmod/kernel-abiversion ]; then
echo "Unable to read: /path/to/sysroots/qemux86-64/pkgdata/kernel-depmod/kernel-abiversion" >&2
else
[foo]
fi
We can see that there is no "exit 1", I guess it was designed to let it
can run without kernel-abiversion
(From OE-Core rev: 64148a30397b8c92414262c0d414d103d2b97ddd)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
While I couldn't find explicit documentation, it appears
that the list of MACHINEOVERRIDES should be sorted from
less specific to more specific left to right, so that
more specific overrides take precedence.
(From OE-Core rev: 59c724db5628775e77fa090183897c6ae0fdf9a8)
Signed-off-by: André Draszik <adraszik@tycoint.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Required for meta-swupd performance enhancements: in meta-swupd, the
so called "mega" image contains a rootfs with all files that can
potentially be installed on a device. Other virtual image recipes need
a subset of those files or directories, and a partial extraction from
a single tar archive is faster than letting all virtual image recipes
share access to a directory under a single pseudo instance.
It may be necessary to extract a directory with all of its attributes
without the content of the directory, hence this patch. Upstream
agreed to consider merging such a patch (see
https://groups.google.com/forum/#!topic/libarchive-discuss/JO3hqSaAVfs)
but has been slow in actually commenting on it, so for now it has
to be carried as distro patch.
(From OE-Core rev: 53126f0fbc63148cc5b22605ffbdf54d0610b545)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is a simultaneous upgrade for python 2 and 3 over setuptools.
(From OE-Core rev: f0c75fecdf15453c5fb252eb9f3de3ea9ce5169b)
Signed-off-by: Edwin Plauchu <edwin.plauchu.camacho@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently run-postinsts script has code to run postinst scripts
via opkg/dpkg configure but that code is never used. The advantage
of using package managers instead of just executing the scripts is
to keep the package manager DB updated.
Fix the script so that the package managers are used when appropriate.
Also use $localstatedir for the opkg runtime file location.
Fixes [YOCTO #10478].
(From OE-Core rev: b645919f173512f9e75aeb26348d60b63dcdc53c)
Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
TUNE_FEATURES is include in BUILDCFG_VARS, so any whitespace is
visible to the user during the build process. Remove the extra
whitespace added during the 2.1 development cycle:
http://git.openembedded.org/openembedded-core/commit/?id=f774b44fa007a2a756ada892ede832b1251d940c
For consistency, squash whitespace within PACKAGE_EXTRA_ARCHS strings
too.
(From OE-Core rev: 5610c6397ee098dd998b7417b343494de77179f9)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pre-processing /proc data during the build considerably reduces the
amount of data written to disk: 176KB instead of 4.7MB for a 20
minuted build. Parsing also becomes faster.
buildstats.bbclass only writes the reduced logs now, but support for
the full /proc files is kept around as reference.
(From OE-Core rev: b5e47df9af1ebbb477074587fdeae17eb2f55582)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pre-processing /proc data during the build considerably reduces the
amount of data written to disk: 176KB instead of 4.7MB for a 20
minuted build. Parsing also becomes faster.
The disk monitor log added another 16KB in that example build. The
overall buildstat was 20MB, so the overhead for monitoring system
utilization is small enough that it can be enabled by default.
(From OE-Core rev: b17812385cd55e81066d3ceda92dffdc6e5564da)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The internal representation after parsing now matches exactly
what the drawing code needs, thus speeding up drawing a bit.
However, the main motivation is to store exactly that required
information in a more compact file.
(From OE-Core rev: ca06e67a0bb5820b38fda4c8dfee20764c1e59ae)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This adds a new, separate chart showing the amount of disk space used
over time for each volume monitored during the build. The hight of the
graph entries represents the delta between current usage and minimal
usage during the build.
That's more useful than showing just the current usage, because then a
graph showing changes in the order of MBs in a volume that is several
GB large would be just flat.
The legend shows the maximum of those deltas, i.e. maximum amount of
space needed for the build. Minor caveat: sampling of disk space usage
starts a bit later than the initial task, so the displayed value may
be slightly lower than the actual amount of space needed because
sampling does not record the actual initial state.
(From OE-Core rev: 263d189d066b578debf08b2bd07494a69b70f70d)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When matching fails, m.group(0) is invalid and can't be used in the
error message.
(From OE-Core rev: ddfea21e06a2e6b1a1e766969f8c134a6de7388a)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Hooks into the new monitordisk.py event and records the used space for
each volume. That is probably the only relevant value when it comes to
visualizing the build and recording more would only increase disk
usage.
(From OE-Core rev: 21a5b569370f47cc02291e1d8b76fe43faa04ea6)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The only real change is the addition of two if checks that skips the
corresponding drawing code when there is no data.
(From OE-Core rev: 1658fd5e9ca1ba793cae604c2a395d54e3ec9056)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This enables rendering of the original bootchart charts for CPU, disk
and memory usage. It depends on the /proc samples recorded by the
updated buildstats.bbclass. Currently, empty charts CPU and disk usage
charts are drawn if that data is not present; the memory chart already
gets skipped when there's no data, which will also have to be added
for the other two.
(From OE-Core rev: 233d3e50b361feea07803a9c0f2a691e687c6cd5)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The code did not handle x scaling correctly when drawing starts at
some time larger than zero, i.e. it worked for normal bootchart data,
but not for the system statistics recorded by buildstats.bbclass.
(From OE-Core rev: 166f8f9aaa1f01fc6d6a5451f8f06b815c51ffae)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Substracting curr_y when determining the hight of the process chart is
wrong because the height is independent of the position where the
chart is about to be drawn. It happens to work at the moment because
curr_y is always 10 when render_processes_chart() gets called. But it
leads to a negative height when other charts are drawn above it, and
then the grid gets drawn on top of those other charts.
Substracting some constant is relevant because otherwise the box is
slightly larger than the process bars. Not sure exactly where that
comes from (text height?); leg_s seems a suitable constant and happens
to be 10, so everything still gets rendered exactly as before.
(From OE-Core rev: b6bb690728c329ae448f89a1b68298c6dd8a573a)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
/proc/[diskstats|meminfo|stat] get sampled and written to the same
proc_<filename>.log files as during normal bootchat logging. This will
allow rendering the CPU, disk and memory usage charts.
Right now sampling happens once a second, triggered by the heartbeat
event.That produces quite a bit of data for long builds, which will be
addressed in a separate commit by storing the data in a more compact
form.
(From OE-Core rev: 6f4e8180b5b4857eaf6caf410fd3a4a41ed85930)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The warning occurs when the GPT image is not the same size than the
media into which it's being flashed, causing the backup GPT table
not being at the end of the disk. However, this is expected as the
image is created before having the information about the destination
media. The error is harmless, so it will be whitelisted.
Fixes [YOCTO 10481].
(From OE-Core rev: 5cc5cdc788308a79f8f0706e6d794c602ef427ed)
Signed-off-by: Jair Gonzalez <jair.de.jesus.gonzalez.plascencia@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The iwlwifi module of any given kernel has a minimum and maximum
supported firmware version. The kernel begins by attempting to load the
maximum version, and decrements until it is successful. The 4.8 kernel's
maximum supported firmware version is 24, but thus far only 22 has been
released, meaning we get errors for 24 and 23.
Filter out iwlwifi firmware load error messages, as they are not
necessarily indicative of real problems.
(From OE-Core rev: 7df570c2310efac8f9898da15deaac2b7df16655)
Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When creating a patch set with cover letter using the
send-pull-request script, both the "In-Reply-To" and "References"
headers are appended twice in patch 2 and subsequent.
That's because git-format-patch already inserted them and then
git-send-email repeats that. Suppressing mail threading in
git-send-email with --no-thread avoids the problem and is the
right solution because it works regardless whether git-send-email is
called once or twicee.
Repeating these headers is a violation of RFC 2822 and can confuse
mail programs. For example, Patchwork does not detect a patch series
problem when there are these extra headers.
[YOCTO #10718]
(From OE-Core rev: 303a1aa3df43eb0b693d8602062fa33c4a08fdd6)
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
BBVERSIONS is moderately horrible and it doesn't appear to be actually used by
anyone, so remove it to simplify the finalise codepaths.
(Bitbake rev: 0bb188f01e396052b127e170a25246d79a6d6741)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Huang Qiyu
Mingli Yu
Ross Burton
Richard Purdie
Bruce Ashfield
Daniel Lublin
Sujith H
brian avery
Ismo Puustinen
Patrick Ohly
Ed Bartosh
Chen Qi
Linus Svensson
Robert Yang
André Draszik
Khem Raj
Edwin Plauchu
Jussi Kukkonen
Andre McCurdy
Jair Gonzalez
California Sullivan