aboutsummaryrefslogtreecommitdiff
path: root/support
Commit message (Collapse)AuthorAgeFilesLines
* support/gnuconfig: reference the correct sha1 we're usingGravatar Yann E. MORIN2020-05-091-1/+1
| | | | | | | | | | | | In commit ff9f778c66f4 (support/gnuconfig: update to 2019-05-28), we forgot to update the README to reference the sha1 we're using, keeping the old one from 2016... Update it now. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: test_lua_utf8: fix test after bump to lua-utf8 0.1.2Gravatar Francois Perrad2020-04-271-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | The commit 0f0649140f73645f4cd00c9c0d27c50e9fa1caf9 introduced a change in the module name: utf8 -> lua-utf8. The packages-file-list.txt show the change in the files intalled on the rootfs: [lua-utf8 0.1.2-2 latest version] lua-utf8,./usr/lib/luarocks/rocks-5.1/luautf8/0.1.2-2/doc/LICENSE lua-utf8,./usr/lib/luarocks/rocks-5.1/luautf8/0.1.2-2/doc/README.md lua-utf8,./usr/lib/luarocks/rocks-5.1/luautf8/0.1.2-2/luautf8-0.1.2-2.rockspec lua-utf8,./usr/lib/luarocks/rocks-5.1/luautf8/0.1.2-2/rock_manifest lua-utf8,./usr/lib/lua/5.1/lua-utf8.so [lua-utf8 1.2-0 previous version] lua-utf8,./usr/lib/luarocks/rocks-5.1/utf8/1.2-0/doc/README.md lua-utf8,./usr/lib/luarocks/rocks-5.1/utf8/1.2-0/utf8-1.2-0.rockspec lua-utf8,./usr/lib/luarocks/rocks-5.1/utf8/1.2-0/rock_manifest lua-utf8,./usr/lib/lua/5.1/utf8.so Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/526036036 Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/scripts/boot-qemu-image.py: wait before using expectGravatar Romain Naour2020-04-221-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As reported by a gitlab runtime test [1] and on the mailing list [2], some runtime tests are failing on slow host machines when the qemu-system-<arch> is missing on the host. The boot-qemu-image.py script need to wait some time after calling pexpect.spawn() in order to make sure that the qemu process has been executed in start-qemu.sh. If start-qemu.sh failed due to missing qemu-system binary an exception will be thrown by child.expect() and should be catched by the error handling (pexpect.EOF). After spending a lot of time to investigate with Yann E. MORIN [3]. It seems that short-lived child processes are a corner-case that is not very correctly handled... Without adding a sleep(1), child.expect() can trigger an exception before setting the exitstatus of the spawned process. This issue can be reproduced on a gitlab runner or by adding "exit 1" in the first line of start-qemu.sh (after the shebang). There is even the same workaround in some pexpect examples [4]. Thanks to Yann for the help while investigating the issue. Tested: https://gitlab.com/kubu93/buildroot/pipelines/138472925 [1] https://gitlab.com/kubu93/buildroot/pipelines/135487475 [2] http://lists.busybox.net/pipermail/buildroot/2020-April/280037.html [3] http://patchwork.ozlabs.org/project/buildroot/patch/20200418161023.1221799-1-romain.naour@gmail.com/ [4] https://github.com/pexpect/pexpect/blob/master/examples/ssh_tunnel.py#L80 Fixes: https://gitlab.com/kubu93/buildroot/-/jobs/509053135 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Yann E. MORIN <yann.morin.1998@free.fr> [yann.morin.1998@free.fr: reorder imports] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* support/scripts/boot-qemu-image.py: boot Qemu images with Qemu-system.Gravatar Jugurtha BELKALEM2020-04-131-0/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This script is intended to be used by gitlab CI to test at runtime Qemu images generated by Buildroot's Qemu defconfigs. This allows to troubleshoot different issues that may be associated with defective builds by lanching a qemu machine, sending root password, waiting for login shell and then perform a shutdown. This script is inspired by toolchain builder [1] and the Buildroot testing infrastructure. The gitlab CI will call this script for each defconfig build but only Qemu defconfig will be runtime tested, all others defconfig are ignored. Some Qemu defconfig must be used with a specific Qemu version (fork) that is not always available, so the script doesn't error out when it can't spawn a missing command. That condition is anyway printed in the log. Finally, the script start Qemu like it's done for the Buildroot testing infrastructure (using pexpect). Note: We noticed some timeout issues with pexpect when the Qemu machine is powered off. That's because Qemu process doesn't stop even if the system is halted (after "System halted"). So the script doesn't error out when such timeout occure. The behaviour depends on the architecture emulated by Qemu. [1] https://github.com/bootlin/toolchains-builder/blob/master/build.sh Signed-off-by: Jugurtha BELKALEM <jugurtha.belkalem@smile.fr> Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* support/scripts/pkg-stats: add tilde '~' expansion for pathesGravatar Heiko Thiery2020-04-121-3/+7
| | | | | | | | | | | | | | | | | | | When the 'nvd-path', 'json' and 'html' are used like this: --html ~/foo then the tilde expansion is properly done by the shell. However, when they are used like this: --html=~/foo The shell doesn't do the tilde expansion, and pkg-stats doesn't do it. This commit modifies pkg-stats to ensure that tilde expansion is done when parsing the 'nvd-path', 'json' and 'html' arguments. Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com> [Thomas: improve commit log] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: test_python_django: use the timeout_multiplier valueGravatar Romain Naour2020-04-121-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As reported by our gitlab runtime test [1] and on the mailing list [2], the test_python_django is failing due to django server taking a lot of time to start. Since the django server is started in background through pexpect, we can't easily wait for the last startup line: "January 01, 1970 - 00:00:41 Django version 3.0.4, using settings 'testsite.settings' Starting development server at http://0.0.0.0:1234/ Quit the server with CONTROL-C." In the failing gitlab job, we don't see such lines. If we increase a lot the timout, the test passes. Use timeout_multiplier introduced by [3] in order to adjust the timeout. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/488816222 Tested: https://gitlab.com/kubu93/buildroot/-/jobs/507458355 [1] https://gitlab.com/buildroot.org/buildroot/-/jobs/488816222 [2] http://lists.busybox.net/pipermail/buildroot/2020-April/279598.html [3] 6e45e33f27d5ae6fa0ab5aad3f032d886a886037 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/python-txaio: drop python 2 supportGravatar James Hilliard2020-04-111-11/+0
| | | | | | | | | | | | | | As of upstream commit 735eb608637e7bbab4082a541ac802cc919fec22, available since version v20.1.1, support for Python 2.x has been dropped, and Python >= 3.5 is required. So we make python-txaio depend on python3, and remove the python2 test of python-txaio. We also remove the python-six dependency which is no longer used by txaio, since upstream commit 62b0e7eaa22769687df1de8f57374cb0a42bdc4d. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Reviewed-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/python-autobahn: drop python 2 supportGravatar James Hilliard2020-04-081-10/+0
| | | | | | | | | | | | | | | | | Upstream commit https://github.com/crossbario/autobahn-python/commit/c0223223f865603ce192e6d5cdbcf74849a4cdd8, which has been part of the releases since v20.1.2 has dropped support for Python 2.x. So python-autobahn is now only available for Python 3.x. We therefore remove the Python 2.x autobahn tests, and while at it, drop the python-six dependency, which is no longer needed since upstream commit https://github.com/crossbario/autobahn-python/commit/79bd2ba41b83950614a2928eeda4704c1d149a20, part of the releases since v20.1.3. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: check if the defconfig provided for testing is validGravatar Romain Naour2020-04-061-0/+20
| | | | | | | | | | | | | | | | Currently, the build continue even if some symbols disapear from the generated dot config file (.config). This patch add a new check in order to stop the test if one of the provided symbol is missing. This must be treated as error. For example, if a symbol disapear due to new dependency constraints. Inspired by is_toolchain_usable() function from genrandconfig: https://git.busybox.net/buildroot/tree/utils/genrandconfig?h=2020.02#n164 Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: don't use TestPythonPackageBase.config and linaro toolchainGravatar Romain Naour2020-04-061-8/+6
| | | | | | | | | | | | | | | | | | | | | | | | | TestPythonPackageBase.config provide already the basic uClibc toolchain. So by adding the symbols for the linaro toolchain some warning are printed at while loading the configuration: .config:16:warning: override: reassigning to symbol BR2_TOOLCHAIN_EXTERNAL .config:16:warning: override: BR2_TOOLCHAIN_EXTERNAL changes choice state .config:17:warning: override: reassigning to symbol BR2_TARGET_ROOTFS_CPIO .config:21:warning: override: BR2_TOOLCHAIN_EXTERNAL_LINARO_ARM changes choice state So, some symbol disapear from the generated dot config (.config) leading to an error due to a new check in the testsuite infra. Since this test should use the Linaro toolchain, remove TestPythonPackageBase.config add BR2_arm=y and disable the rootfs tar option. While at it, re-order the options so that they appear in the same order as they appear in a defconfig. Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Adam Duskett <Aduskett@gmail.com> Cc: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: test_lxc: use ARM arm external toolchainGravatar Romain Naour2020-04-061-0/+2
| | | | | | | | | | | | | | | | | | | Until now, the lxc test was using the ARM CodeSourcery 2014.05 armv5 toolchain. But the recent systemd version bump to 245 added a toolchain dependency on systemd package due to build issues with gcc < 5.0. Before [1] the lxc test was failing to build with the ARM CodeSourcery 2014.05 toolchain. After [1], the test is faling at runtime since the "BR2_INIT_SYSTEMD=y" symbol disapear from the dot config (.config) due to the new toolchain dependency. Fix this by using the same toolchain as for the systemd tests [2] [1] 2196ee25ff29c87001a42a382655d5b52d5de3c4 [2] b3d979c0d1b10de501576644e7dcdba708889b0c Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: test_tmux: remove BR2_GENERATE_LOCALEGravatar Romain Naour2020-04-061-1/+0
| | | | | | | | | | | | | | | | The BR2_GENERATE_LOCALE can only be used by uClibc based toolchains with the internal toolchain backend [1]. The test_tmux is using a external uClibc toolchain, so the "BR2_GENERATE_LOCALE="en_US.UTF-8"" line disapear from the generated dot config (.config) leading to an error due to a new check in the testsuite infra. [1] https://git.buildroot.net/buildroot/commit/?id=bd0ffe2206fbd32baf7f4a1dc5fde81cfad70462 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: test_glxinfo: remove BR2_TOOLCHAIN_EXTERNAL_LOCALEGravatar Romain Naour2020-04-061-4/+0
| | | | | | | | | | | | | | | | | | The BR2_TOOLCHAIN_EXTERNAL_LOCALE is only defined for uClibc based custom external toolchains. The test_glxinfo is using a glibc toolchain, so the "# BR2_TOOLCHAIN_EXTERNAL_LOCALE is not set" line disapear from the generated dot config (.config) leading to an error due to a new check in the testsuite infra. There is the same problem with: BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG=y BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS=y BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_NPTL=y Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: test_syslinux: remove BR2_TOOLCHAIN_EXTERNAL_LOCALEGravatar Romain Naour2020-04-061-4/+0
| | | | | | | | | | | | | | | | | | | The BR2_TOOLCHAIN_EXTERNAL_LOCALE is only defined for uClibc based custom external toolchains. The test_syslinux is using a glibc toolchain, so the "# BR2_TOOLCHAIN_EXTERNAL_LOCALE is not set" line disapear from the generated dot config (.config) leading to an error due to a new check in the testsuite infra. There is the same problem with: BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG=y BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS=y BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_NPTL=y Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: test_syslinux: fix flake8 errorsGravatar Romain Naour2020-04-061-5/+10
| | | | | | | | | Reported by gitlab: https://gitlab.com/kubu93/buildroot/-/jobs/499374911 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: fix systemd test by using a more recent gccGravatar Romain Naour2020-04-051-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As reported on the mailing list [0], there is a build issue with systemd 245 when using gcc < 5.0, due to the following build issue: ../src/shared/gpt.c:7:9: error: initializer element is not constant { GPT_ROOT_X86, "root-x86" }, The pre-built external toolchain we have for armv5 (the default with just BR2_arm=y) is a very old toolchain from CodeSourcery, which has a gcc 4.8; we have no other pre-built toolchains for armv5, except by using a custom one, like those from the Bootlin toolchain builder. But using a custom toolchain is not nice, as we want our runtime test to test nominal configurations. So, switch the systemd tests to use a Cortex-A9, so that we can use the ARM 2019.12 toolchain, and with VFP, so that it can boot in the qemu vexpress machine we use for the test-cases. Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/498144403 https://gitlab.com/buildroot.org/buildroot/-/jobs/498144405 https://gitlab.com/buildroot.org/buildroot/-/jobs/498144406 https://gitlab.com/buildroot.org/buildroot/-/jobs/498144408 https://gitlab.com/buildroot.org/buildroot/-/jobs/498144410 https://gitlab.com/buildroot.org/buildroot/-/jobs/498144412 [0] http://lists.busybox.net/pipermail/buildroot/2020-April/278931.html Signed-off-by: Romain Naour <romain.naour@gmail.com> [yann.morin.1998@free.fr: - just use cortex-a9_VFP, instead of using a bootlin toolchain - adapt the commit log accordingly ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* support/testing: add build tests for the syslinux bootloaderGravatar Thomas Petazzoni2020-04-041-0/+83
| | | | | | | | | | | | | | This commit adds four new tests for the syslinux bootloader: - Building on x86, for legacy BIOS - Building on x86, for EFI BIOS - Building on x86-64, for legacy BIOS - Building on x86-64, for EFI BIOS Runtime testing in Qemu would certainly be possible, but is left as a future addition to these tests. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: update basic toolchain to bootlin bleeding-edge 2018.11-1Gravatar Romain Naour2020-04-041-4/+4
| | | | | | | | | | | | | | | | | Update the toolchain being used by the testsuite infra. The new toolchain 2018.11-1 is based on gcc 8.2, uClibc-ng 1.0.30, linux-headers 4.14 and binutils 2.31.1. Enable BR2_TOOLCHAIN_HAS_THREADS_DEBUG that is now required. The old toolchain 2017.05 is based on gcc 4.9, uClibc-ng 1.0.25, linux-headers 3.10 and binutils 2.27. Tested with gitlab https://gitlab.com/kubu93/buildroot/pipelines/132376578 Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/config-fragments/autobuild: update OpenRISC toolchainGravatar Thomas Petazzoni2020-04-021-1/+1
| | | | | | | | | Following commit eee96b0f0ad224b3e09a9b98c26d056e18f17fd5 that adds a gcc patch for OpenRISC, the OpenRISC pre-built toolchain was rebuilt. Let's use this new toolchain version for the autobuilders. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* Makefile: make-4.3 now longer un-escapes \# in macrosGravatar Yaroslav Syrytsia2020-03-311-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | make-4.3 shipped with a backward incompatible change in how sharp signs are handled in macros. Previously, up to make 4.2, the sharp sign would always start a comment, unless backslash-escaped, even in a macro or a fucntion call. Now, the sharp sign is no longer starting a comment when it appears inside such a macro or function call. This behaviour was supposed to be in force since 3.81, but was not; 4.3 fixed the code to match the doc. As such, use of external toolchains is broken, as we use the sharp sign in the copy_toolchain_sysroot macro, in shell variable expansion to strip off any leading /: ${target\#/}. Fix that by applying the workaround suggested in the release annoucement [0], by using a variable to hold a sharp sign. [0] https://lists.gnu.org/archive/html/info-gnu/2020-01/msg00004.html Signed-off-by: Yaroslav Syrytsia <me@ys.lc> [yann.morin.1998@free.fr: - move the SHARP_SIGN definition out of Makefile and into support/ - expand the commit log ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* support/testing/tests/package/sample_gst1_python.py: fix flake8 errorsGravatar Adam Duskett2020-03-291-1/+1
| | | | | | | | | | | The older version of flake8 on the autobuilders does not support typehints. As such, flake8 throws the following error when scanning sample_gst1_python: E999 SyntaxError: invalid syntax Remove the typehinting from on_message to fix this issue. Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: fix test_gst1_pythonGravatar Adam Duskett2020-03-272-4/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The config is missing the following packages: - BR2_PACKAGE_GST1_PLUGINS_BASE This is needed for the videotestsrc plugin which provides videotestsrc. - BR2_PACKAGE_GST1_PLUGINS_BAD This is needed for the debugutils plugin which provides fakevideosink. - BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_VIDEOTESTSRC videotestsrcplugin used by the example pipeline. - BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_DEBUGUTILS fakevideosink plugin used by the example pipeline. The sample was also amended to fix: - no call to main. - using autovideosink instead of fakevideosink. Using Fakevideoskink is preferred because its primary purpose is for debugging and sample pipelines. Autovideosink does not work because there is no video output device. - No function on_message. Without this function, the script fails because of the missing function. - The script sets the pipeline to Gst.State.EOS instead of Gst.State.NULL which results in a failed pipeline state. When the state is set to NULL, gstreamer automatically calls EOS. Manually setting the pipeline state to EOS results in the following error: Trying to dispose element sink, but it is in PLAYING instead of the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. A refcounting bug may also cause this problem in the application or some element. In addition, the default timeout is set too low and would result in a test failure, this has been changed to 200 seconds. These issues are now properly fixed, and the sample script passes. Signed-off-by: Adam Duskett <Aduskett@gmail.com> [yann.morin.1998@free.fr: - meld the two patches together - add the print() in the on_demand callback ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* Revert "package/perl-crypt-ssleay: new package"Gravatar Thomas De Schampheleire2020-03-261-43/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 25033cfb8612c6d0f45c89806f7e0669ffbf0e8a. This perl package is deprecated and gives following recommendations while building: *** THIS IS NOT AN ERROR, JUST A MESSAGE FOR YOUR INFORMATION *** Do you really need Crypt::SSLeay? Starting with version 6.02 of LWP, https support was unbundled into LWP::Protocol::https. This module specifies as one of its prerequisites IO::Socket::SSL which is automatically used by LWP::UserAgent unless this preference is overridden separately. IO::Socket::SSL is a more complete implementation, and, crucially, it allows hostname verification. Crypt::SSLeay does not support this. At this point, Crypt::SSLeay is maintained to support existing software that already depends on it. However, it is possible that your software does not really depend on Crypt::SSLeay, only on the ability of LWP::UserAgent class to communicate with sites over SSL/TLS. If are using version LWP 6.02 or later, and therefore have installed LWP::Protocol::https and its dependencies, and do not explicitly use Net::SSL before loading LWP::UserAgent, or override the default socket class, you are probably using IO::Socket::SSL and do not really need Crypt::SSLeay. Before installing Crypt::SSLeay, you may want to try specifying a dependency on LWP::Protocol::https. Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: add netdata testGravatar Marcin Niestroj2020-03-241-0/+23
| | | | | Signed-off-by: Marcin Niestroj <m.niestroj@grinn-global.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing/tests/package/test_python_gobject.py: fix flake8 warningGravatar Thomas Petazzoni2020-03-241-0/+1
| | | | | | | | Fixes: support/testing/tests/package/test_python_gobject.py:4:1: E302 expected 2 blank lines, found 1 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing/tests/package/test_gst1_python.py: fix flake8 warningGravatar Thomas Petazzoni2020-03-241-1/+0
| | | | | | | | Fixes: support/testing/tests/package/test_gst1_python.py:29:1: W391 blank line at end of file Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing/tests/package/sample_python_gobject.py: fix flake8 warningsGravatar Thomas Petazzoni2020-03-241-1/+3
| | | | | | | | | | Fixes: support/testing/tests/package/sample_python_gobject.py:5:1: E302 expected 2 blank lines, found 1 support/testing/tests/package/sample_python_gobject.py:8:7: E111 indentation is not a multiple of four support/testing/tests/package/sample_python_gobject.py:11:1: E305 expected 2 blank lines after class or function definition, found 1 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing/tests/package/sample_gst1_python.py: fix flake8 warningsGravatar Thomas Petazzoni2020-03-241-3/+2
| | | | | | | | | | | | | | | | | Fixes the following flake8 warnings: support/testing/tests/package/sample_gst1_python.py:5:1: F401 'time' imported but unused support/testing/tests/package/sample_gst1_python.py:7:1: E402 module level import not at top of file support/testing/tests/package/sample_gst1_python.py:21:12: W292 no newline at end of file For the E402 warning, we add a "noqa" marker, as we really want the gi.require_version() to be before. There is still one remaining warning to be fixed: support/testing/tests/package/sample_gst1_python.py:18:28: F821 undefined name 'on_message' Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing/tests/init/init_openrc: fix flake8 F401 warningGravatar Thomas Petazzoni2020-03-241-1/+0
| | | | | | | | Fixes: support/testing/tests/init/test_openrc.py:1:1: F401 'infra.basetest' imported but unused Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/scripts/pkg-stats: fix flake8 E722 warningGravatar Thomas Petazzoni2020-03-241-1/+1
| | | | | | | | | | | | | | | | | | | | | flake8 complains with: support/scripts/pkg-stats:339:13: E722 do not use bare 'except' Due to the construct: try: something except: print("some message") raise Which is in fact OK because the exception is re-raised. This issue is discussed at https://github.com/PyCQA/pycodestyle/issues/703, and the general agreement is that these "bare except" are OK, and should be ignored from flake8 using a noqa statement. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/scripts/pkg-stats: fix flake8 E501 warningGravatar Thomas Petazzoni2020-03-241-1/+2
| | | | | | | | Fixes: support/scripts/pkg-stats:281:133: E501 line too long (139 > 132 characters) Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/scripts/pkg-stats: fix flake8 E117 warningGravatar Thomas Petazzoni2020-03-241-1/+1
| | | | | | | | Fixes: support/scripts/pkg-stats:146:17: E117 over-indented Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/scripts/pkg-stats: fix flake8 E302 warningGravatar Thomas Petazzoni2020-03-241-0/+1
| | | | | | | | Fixes: support/scripts/pkg-stats:57:1: E302 expected 2 blank lines, found 1 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/scripts/pkg-stats: fix flake8 E402 warningGravatar Thomas Petazzoni2020-03-241-1/+1
| | | | | | | | | | | | flake8 complains with: pkg-stats:38:1: E402 module level import not at top of file This is due to sys.path.append() being before the import from getdeveloperlib, but we really need this sys.path.append() to be before, so let's ignore this flake8 warning. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing/: change python-gobject to use prebuilt kernelGravatar Adam Duskett2020-03-221-16/+9
| | | | | | | | | | | | | | | | Currently, we build a complete AArch64 system, including a kernel. This can take quite some time. Switch to an armv7 system, which allows us to use one a prebuilt kernel, thus significantly reducing the test time. Signed-off-by: Adam Duskett <Aduskett@gmail.com> [yann.morin.1998@free.fr: - use a standalone config; don't inherit from TestPythonPackageBase - use the default external toolchain (ARM, not Linaro) - rewrite commit log ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* support/testing: add gst1-python test caseGravatar Adam Duskett2020-03-222-0/+50
| | | | | | | | This test case runs a simple pipeline for 100 frames to ensure that gst1-python works properly. Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* support/config-fragments: update Buildroot toolchains to 2020.02Gravatar Thomas Petazzoni2020-03-2132-55/+55
| | | | | | | | | This commit updates all our toolchain configuration fragments for pre-built Buildroot toolchains to use toolchains built with Buildroot 2020.02. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* support/scripts/check-kernel-headers.sh: do not print error for loose checksGravatar Thomas Petazzoni2020-03-211-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | The C program inside check-kernel-headers.sh has two checking mode: a strict and a loose one. In strict mode, we want the kernel headers version declared by the user to match exactly the one of the toolchain. In loose mode, we want the kernel headers version of the toolchain to be greater than or equal to the one declared by the user: this is used when we have a toolchain that has newer headers than the latest version known by Buildroot. However, in loose mode, we continue to show the "Incorrect kernel headers version" message, even though we then return a zero error code. This is very confusing: you see an error displayed on the terminal, but the build goes on. We fix that by first doing the loose check first, and returning 0 if it succeeds. And then we move on with the strict check where we want the version to be identical. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* package/lua-lyaml: new packageGravatar Francois Perrad2020-03-201-0/+27
| | | | | Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* support/testing: add missing test file for perl-html-parserGravatar Thomas De Schampheleire2020-03-151-0/+20
| | | | | | | | | | | This file was created by utils/scancpan while adding other packages but apparently not yet added in the repo. Assign this test case to Bernd in the DEVELOPERS file since he is listed as the maintainer for this package. Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/perl-crypt-ssleay: new packageGravatar Thomas De Schampheleire2020-03-151-0/+43
| | | | | | | | Added via utils/scancpan, adding a host dependency to perl-try-tiny and target dependency to openssl. Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/perl-lwp-protocol-https: new packageGravatar Thomas De Schampheleire2020-03-151-0/+42
| | | | | | | | | Dependency for perl-crypt-ssleay (added in subsequent commit). Added via utils/scancpan, without changes. Signed-off-by: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
* package/python-gobject: bump version to 3.36.0Gravatar Adam Duskett2020-03-122-5/+38
| | | | | | | | | | | | | | | | | | | | | | | Other changes: - Convert the package to a meson package. - Remove 0001-add-PYTHON_INCLUDES-override.patch as it no longer applies. - Add gobject-introspection as a dependency. - Add the package under myself in the DEVELOPERS file. Because gobject-introspection is now a dependency of python-gobject, the test must be updated at the same time. - Change TestPythonPy2Gobject to TestPythonPy3Gobject as gobject-introspection requires python3. - Refactor test_python_gobject.py to no longer inherit the TestPythonPackageBase class, as this class uses a base config that does not support gobject-introspection. - Update sample_python_gobject to use Glib to find the path of sh. Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* support/testing: add openrc testsGravatar Adam Duskett2020-03-111-0/+51
| | | | | | | | | | Two simple tests to ensure that openrc boots without any services crashing with a read only and a read write filing system. Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Carlos Santos <unixmania@gmail.com> [yann.morin.1998@free.fr: really check the init process] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
* Merge branch 'next'Gravatar Peter Korsgaard2020-03-091-54/+187
|\ | | | | | | Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
| * support/scripts/pkg-stats: add list of status checks to the json outputGravatar Heiko Thiery2020-03-071-0/+6
| | | | | | | | | | Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
| * support/scripts/pkg-stats: set status to 'na' for virtual packagesGravatar Heiko Thiery2020-03-071-0/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If there is no infra set or infra is virtual the status is set to 'na'. This is done for the follwing checks: - license - license-files - hash - hash-license - patches - version Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
| * support/scripts/pkg-stats: add defconfig supportGravatar Heiko Thiery2020-03-071-2/+41
| | | | | | | | | | | | | | Scan configs directory and create Defconfig objects. Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
| * support/scripts/pkg-stats: store pkg dir pathGravatar Heiko Thiery2020-03-071-0/+1
| | | | | | | | | | | | | | | | | | | | This value can be used for later processing. In the buildroot-stats application this is used to create links pointing to the git repo of buildroot. Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
| * support/scripts/pkg-stats: add package count to statsGravatar Heiko Thiery2020-03-071-0/+1
| | | | | | | | | | Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>