This repository has been archived by the owner on Apr 19, 2019. It is now read-only.
jenkins-upstream-monitor-master-1151 #212
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ostroproject-ci
force-pushed
the
ci-upstream-monitor-master
branch
18 times, most recently
from
8e4b724
to
63e051b
Compare
ostroproject-ci
force-pushed
the
ci-upstream-monitor-master
branch
4 times, most recently
from
521bb64
to
a28e1b0
Compare
|
added python-git on builders to get oe-selftest running; test this please |
ostroproject-ci
force-pushed
the
ci-upstream-monitor-master
branch
7 times, most recently
from
122e02d
to
6d49013
Compare
…r the non-x86 BSPs Bump to the latest stable kernel for 4.1, 4.4, 4,9 and 4.10. Also set the default kernel to 4.10. (From meta-yocto rev: fbb8276e16976b5188efe5a9ee9bdda1ff44d931) Signed-off-by: Kevin Hao <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
Since the genericx86*.conf file directly set PREFERRED_VERSION remove it from here to avoid confusion. (From meta-yocto rev: 2383d50b084cafdf04f7bd15ea732cd98982625b) Signed-off-by: Saul Wold <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
(From meta-yocto rev: f011bc3caa0734a90d41e96aac302d1a3dc04c51) Signed-off-by: Armin Kuster <[email protected]> Signed-off-by: Ross Burton <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
…onf files In machine configuration files, there is no need to use OVERRIDES that match the precise machine being defined, so remove them for clarity and consistency from these lines in those respective files: PREFERRED_VERSION_linux-yocto_genericx86-64 ?= "4.10%" PREFERRED_VERSION_linux-yocto_genericx86 ?= "4.10%" UBOOT_MACHINE_mpc8315e-rdb = "MPC8315ERDB_config" (From meta-yocto rev: 035d4e7763171068d2b4df0622b6cc0fc1cf4b32) Signed-off-by: Robert P. J. Day <[email protected]> Signed-off-by: Ross Burton <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
New set of templates that target the 4.10 kernel version. [YOCTO #11174] (From meta-yocto rev: 8a11b0cc2a1bfaab25200c251b301c812141ba58) Signed-off-by: Leonardo Sandoval <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
Updating the kernel templates (those use by the yocto-bsp script) is a mechanical process (and prone to errors) which consists of copying latest kernel template then applying string replacements from old to new kernel version. This script collects these commands allowing quick updates in the future. (From meta-yocto rev: 450313d9d8bb1e728ed5a7208decd30f50633be1) Signed-off-by: Leonardo Sandoval <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
…ates Currently, SRCREV is set to AUTOREV, causing mismatch between PV and the kernel version shown in the makefile (see below to see the bitbake log). The solution is to skip this check, suggesting to remove it once SRCREV is locked. ERROR: linux-yocto-4.10+gitAUTOINC+01f18cba44_53be19cad6-r0.1 do_kernel_version_sanity_check: Package Version (4.10+gitAUTOINC+01f18cba44_53be19cad6) does not match of kernel being built (4.10.5). Please update the PV variable to match the kernel source or set KERNEL_VERSION_SANITY_SKIP="1" in your recipe. ERROR: linux-yocto-4.10+gitAUTOINC+01f18cba44_53be19cad6-r0.1 do_kernel_version_sanity_check: Function failed: do_kernel_version_sanity_check (log file is located at /home/lsandov1/poky2/build/tmp/work/myqemu-poky-linux/linux-yocto/4.10+gitAUTOINC+01f18cba44_53be19cad6-r0.1/temp/log.do_kernel_version_sanity_check.26904) ERROR: Logfile of failure stored in: /home/lsandov1/poky2/build/tmp/work/myqemu-poky-linux/linux-yocto/4.10+gitAUTOINC+01f18cba44_53be19cad6-r0.1/temp/log.do_kernel_version_sanity_check.26904 ERROR: Task (/home/lsandov1/poky2/meta/recipes-kernel/linux/linux-yocto_4.10.bb:do_kernel_version_sanity_check) failed with exit code '1 [YOCTO #11064] (From meta-yocto rev: 79bfd911f826c6c7e26827bb200dd69e6f567b17) Signed-off-by: Leonardo Sandoval <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
We have 4.1 (LTSI), 4.4 (LTS), 4.9 (LTS/LTSI) and 4.10 available in master. 4.8 is no longer required, so we drop the recipe to keep the version selection under control. (From meta-yocto rev: 8be1b026d1f56ef18d19fae90cbae45bd7dd97c7) Signed-off-by: Richard Purdie <[email protected]>
…software package recipes (From meta-yocto rev: 6edf4e6bf8202378069496eda9f30b9ff7ef85f2) Signed-off-by: Leonardo Sandoval <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
….1 Updates to Linux 4.1.38 (From meta-yocto rev: 2a532145978940adb73e435ab44116e730d49a43) Signed-off-by: Alejandro Hernandez <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
….9 Updates to Linux 4.9.17 (From meta-yocto rev: 1dc5a4e88d35b51dd6f871f7d1f8b949d5b83f06) Signed-off-by: Alejandro Hernandez <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
….10 Updates to Linux 4.10.5 (From meta-yocto rev: 582958c2113ae0d0f968da48270307160ff61526) Signed-off-by: Alejandro Hernandez <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
….4 Updates to Linux 4.4.56 (From meta-yocto rev: 327840b481d4d82f68aae5aa84c0aed16ebec035) Signed-off-by: Alejandro Hernandez <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
Since we do not set the 64 bit flags, newer kernels seem to build 64bit config files by default. This is due to a hard-coded uname -m check that selects the KBUILD_DEFCONFIG based on the host, not the cross target. Similar to e9ec769926b2378e63380bd7762ce7ce201af151 in the yocto-kernel-cache repo (From meta-yocto rev: e35017cc67f6d3c5cc00488d3460de0dcec773b3) Signed-off-by: Saul Wold <[email protected]> Signed-off-by: Ross Burton <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
python-pyqt in meta-qt4 is about to require sip 4.19 that only meta-oe provides; as we only bring in meta-qt4 for LSB, there's no need to be building this as part of world and it would fail without meta-oe anyway. (From meta-yocto rev: 202598d670a1d335d2a8de7685244fa7f480bd26) Signed-off-by: Paul Eggleton <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
After the change in kernel commit a291b6b3d287 ("ARM: dts:
am335x-boneblack: Add blue-and-red-wiring -property to LCDC node"),
the pixel format we support for 32bit bpp has been changed from
XRGB8888 to XBGR8888. But the fbdev created by modesetting driver use
the XRGB8888 format by default, this causes the X malfunction. There is
no easy way to adjust the pixel format of the fbdev created by the
modesetting driver. So we create a xorg.conf to use the 16bit bpp to
work around this issue.
[YOCTO #11267]
(From meta-yocto rev: 1ef8a9584298a8745a28c0c92fa3ecbf92ffe494)
Signed-off-by: Kevin Hao <[email protected]>
Signed-off-by: Richard Purdie <[email protected]>
…r the non-x86 BSPs Bump to the latest stable kernel for 4.4, 4,9 and 4.10. (From meta-yocto rev: ee6e8f2926a7e2bd02b6b7991ba30ea6e6c9f2f2) Signed-off-by: Kevin Hao <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
Updates to Linux 4.4.60 (From meta-yocto rev: 1199d8da4cce623adc09c074e4c747e672e3eb78) Signed-off-by: Alejandro Hernandez <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
Updates to Linux 4.9.21 (From meta-yocto rev: 6a64ad7c034250c122e72e8473ef7de11430b1a1) Signed-off-by: Alejandro Hernandez <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
Updates to Linux 4.10.9 (From meta-yocto rev: f2b6a42f6842e28c448a11a6778d140f984b6d3d) Signed-off-by: Alejandro Hernandez <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
…s, ttf-bitstream-vera and which (From meta-yocto rev: c6bbd7f45260d0921ad1c5f8c1f1f7846aa42270) Signed-off-by: Leonardo Sandoval <[email protected]> Signed-off-by: Ross Burton <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
…r the non-x86 BSPs Bump to the latest stable kernel for 4.4, 4,9 and 4.10. (From meta-yocto rev: d45f5894d8f73425b47e3cacbe07d0d5cf36dcd2) Signed-off-by: Kevin Hao <[email protected]> Signed-off-by: Richard Purdie <[email protected]>
(From meta-java rev: 92aa80f6556debb7477c507a6802321623baea4a) Signed-off-by: Jed <[email protected]> Signed-off-by: Maxin B. John <[email protected]>
Add missing dependencies in order to build according to latest changes done in poky where all dependencies must be installed relative to recipe WORKDIR. (From meta-java rev: 2ca320b5740dc0620661561cb3394ba41b375e0c) Signed-off-by: Adrian Calianu <[email protected]> Signed-off-by: Maxin B. John <[email protected]>
(From meta-java rev: 67e48693501bddb80745b9735b7b3d4d28dce9a1) Signed-off-by: Adrian Calianu <[email protected]> Signed-off-by: Maxin B. John <[email protected]>
Fix build issues according to latest poky changes where all dependencies must be installed into recipe work folder. (From meta-java rev: c8606edaae36528c9e6dc3f3f51a3c8814e2c7f8) Signed-off-by: Adrian Calianu <[email protected]> Signed-off-by: Maxin B. John <[email protected]>
The following oe-core commit made asbolute symlink an error: commit 3eee8e99e114b3db8b718834ca52da8d2919b83f sstate: Make absolute symlinks an error Fix this by inheritting relative_symlinks class: ERROR: jikes-native-1.22-r0 do_populate_sysroot: sstate found an absolute path symlink (From meta-java rev: a8e6753b5912afe7fe273a76a919a20db2d713c7) Signed-off-by: Maxin B. John <[email protected]>
(From meta-java rev: 6eed0bbfa831f736bbab4d285c57deeec8f5d562) Signed-off-by: Zhenhua Luo <[email protected]> Signed-off-by: Maxin B. John <[email protected]>
ostroproject-ci
force-pushed
the
ci-upstream-monitor-master
branch
from
9797122
to
3b01749
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.