[yocto] [yocto-autobuilder-helper][PATCH 1/2] scripts/generate-testresult-index.py: fix typo in template var name

From: Alexis Lothoré Signed-off-by: Alexis Lothoré --- scripts/generate-testresult-index.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/generate-testresult-index.py b/scripts/generate-testresult-index.py index 1fc9f41..09d2edb 100755 ---

[yocto] [yocto-autobuilder-helper][PATCH 0/2] expose regression reports on web page

From: Alexis Lothoré Regression reports are currently stored alongside test reports and other artifacts on the autobuilder artifacts web page. This small update propose to add a link to the regression report (when available) on main non-release page ([1]) instead of having to manually navigate

[yocto] [yocto-autobuilder-helper][PATCH 2/2] scripts/generate-testresult-index.py: expose regression reports on web page

From: Alexis Lothoré When available, expose tesresult-regressions-report.txt on non-release web page, as it is done for many other artifacts currently Signed-off-by: Alexis Lothoré --- scripts/generate-testresult-index.py | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff

[yocto] [yocto-autobuilder-helper][PATCH 3/3] scripts/send_qa_email: return previous tag when running a non-release master build

From: Alexis Lothoré Some nightly builders are configured in yocto-autobuilder2 to run master builds. Those build parameters currently skip all branches of get_regression_base_and_target, which then return None, while the caller expects a base and target tuple Set default behaviour to return

[yocto] [yocto-autobuilder-helper][PATCH 0/3] fix regression reporting for nightly build

From: Alexis Lothoré It has been observed that regression reporting is currently failing on nightly builds ([1]). Those builds parameters are currently not properly managed by the base and target computation for regression reports. Add default behaviour to generate report against last tag [1]

[yocto] [yocto-autobuilder-helper][PATCH 2/3] scripts/test_send_qa_email.py: allow tests with non static results

From: Alexis Lothoré When the test assert is about a tag in Poky, the result will not be the same depending on existing tags at the time of running tests. Add a LAST_TAG marker to loosen constraints but still allow to tests for general cases (e.g. : test that tag-depending tests does not return

[yocto] [yocto-autobuilder-helper][PATCH 1/3] scripts/test_utils: test master nightly build case

From: Alexis Lothoré Signed-off-by: Alexis Lothoré --- scripts/test_utils.py | 10 ++ 1 file changed, 10 insertions(+) diff --git a/scripts/test_utils.py b/scripts/test_utils.py index ab91e3b..d02e9b2 100755 --- a/scripts/test_utils.py +++ b/scripts/test_utils.py @@ -99,6 +99,16 @@

Re: [yocto] [yocto-autobuilder-helper][PATCH 0/8] fix regression reports generation on "master-next" branches

Hi Richard, On 3/22/23 10:41, Richard Purdie wrote: > On Mon, 2023-03-13 at 15:51 +0100, Alexis Lothoré via > lists.yoctoproject.org wrote: >> From: Alexis Lothoré >> >> This series fixes regression report generation on "next" branches, as raised >> in >> [1]. >> >> The first five patches are

Re: linux headers

On 3/21/23 04:26, lacsaP Patatetom wrote: hi everybody, my development workstation is running 6.1.20-1-lts and I made linux-lts-ro-6.1.15-1-x86_64.pkg.tar.zst and linux-lts-ro-headers-6.1.15-1-x86_64.pkg.tar.zst packages on it : if now I want to compile on this development workstation

[yocto] [yocto-autobuilder-helper][PATCH 1/1] config.json: fix A. Belloni configuration for regression reporting

From: Alexis Lothoré There is a typo in BUILD_HISTORY_FORKPUSH, leading to failures on Autobuilder when trying to generate regression reports: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/a-full/yocto-autobuilder-helper/scripts/send-qa-email", line 213, in

Re: linux headers

if I understand correctly, I can install my package linux-lts-perso-6.1.15-2-x86_64.pkg.tar.zst, boot on it (eg. "my" kernel) and continue to use the binaries present on my system while they have not been compiled with its (new) headers and especially for the binaries that call the

Re: linux headers

On 3/20/23 06:44, lacsaP Patatetom wrote: Please don't top post on mailing lists. I don't understand what 'problem' you are speaking of. All you've asked is if you can install a kernel headers from a different build - the general answer is "no" - don't ever do that. I already

Re: linux headers

On 3/20/23 05:27, lacsaP Patatetom wrote: hi, - When you change the source you must also bump pkgrel as the package is now different. - If you want to build your own version of an Arch package, you should not use same package name as the official Arch package - this will only lead to

Re: [tor-relays] AirTor/ATOR continues to pester Tor relay operators, promising donations

On Freitag, 17. März 2023 17:25:10 CET Bauruine wrote: > ... but I'll > just keep "mining" consensus weight. Because you don't need a modified > version of Tor and you don't need the blockchain for that. Just download > the consensus and look at the consensus weight and you have your proof > of

Re: Orphaning packages

On 3/14/23 12:50, Tobias Powalowski wrote: Hi guys, early spring cleanup on my adopted packages: .. - mdadm Thanks for all the work you've put into Arch Tobias - it is very much appreciated. Of the packages you listed, I sure hope mdadm will be picked up - this quite obviously is a very

Re: [ping][vect-patterns] Refactor widen_plus/widen_minus as internal_fns

Hi Richard, I'm only picking this up now. Just going through your earlier comments and stuff and I noticed we didn't address the situation with the gimple::build. Do you want me to add overloaded static member functions to cover all gimple_build_* functions, or just create one to replace

Re: GESO (6) - Spring Cemetery stroll

> On 14 Mar 2023, at 02:50, Rick Womer wrote: > > I took my camera for a walk on a lovely afternoon a week ago. These > were my favorites. > > https://rickwomer.smugmug.com/2023/March-2023/Woodland-Cemetery-3-6-23/ > Nice and pleasing images Rick! It sure seems like lovely weather ;-)

[PATCH] ifcvt: Lower bitfields only if suitable for scalar register [PR tree/109005]

This patch fixes the condition check for eligilibity of lowering bitfields, where before we would check for non-BLKmode types, in the hope of excluding unsuitable aggregate types, we now check directly the representative is not an aggregate type, i.e. suitable for a scalar register. I tried

[yocto] [yocto-autobuilder-helper][PATCH 8/8] config: flag A. Belloni master-next branch as testing branch

From: Alexis Lothoré Add "abelloni/master-next" branch from poky-contrib in configuration so that regression reports are generated when testing for patches Signed-off-by: Alexis Lothoré --- config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.json

[yocto] [yocto-autobuilder-helper][PATCH 6/8] scripts/send-qa-email: fix testing branches regression reporting

From: Alexis Lothoré d6018b891a3b7c62c7a2883c7fb9ae55e66f1363 broke regression reporting for testing branches (e.g: master-next in poky, ross/mut in poky-contrib) by ignoring the comparebranch returned by utils.getcomparison branch Fix regression reporting for those branches by using

[yocto] [yocto-autobuilder-helper][PATCH 7/8] scripts/test_send_qa_email.py: add tests for base/target pair guessing

From: Alexis Lothoré Signed-off-by: Alexis Lothoré --- scripts/test_send_qa_email.py | 21 + 1 file changed, 21 insertions(+) diff --git a/scripts/test_send_qa_email.py b/scripts/test_send_qa_email.py index 48bca98..ccdcba6 100755 --- a/scripts/test_send_qa_email.py +++

[yocto] [yocto-autobuilder-helper][PATCH 5/8] scripts/send-qa-email: add tests for is_release_version

From: Alexis Lothoré Signed-off-by: Alexis Lothoré --- scripts/test_send_qa_email.py | 10 ++ 1 file changed, 10 insertions(+) diff --git a/scripts/test_send_qa_email.py b/scripts/test_send_qa_email.py index c1347fb..48bca98 100755 --- a/scripts/test_send_qa_email.py +++

[yocto] [yocto-autobuilder-helper][PATCH 4/8] scripts/send-qa-email: protect is_release_version from None value

From: Alexis Lothoré Signed-off-by: Alexis Lothoré --- scripts/send_qa_email.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/send_qa_email.py b/scripts/send_qa_email.py index 320ff24..540eb94 100755 --- a/scripts/send_qa_email.py +++ b/scripts/send_qa_email.py @@

[yocto] [yocto-autobuilder-helper][PATCH 0/8] fix regression reports generation on "master-next" branches

From: Alexis Lothoré This series fixes regression report generation on "next" branches, as raised in [1]. The first five patches are preparatory updates for the real fix, being either refactoring, cleanup or unit tests addition to better understand how integration branches are used in

[yocto] [yocto-autobuilder-helper][PATCH 2/8] scripts/send-qa-email: remove unused variable

From: Alexis Lothoré Signed-off-by: Alexis Lothoré --- scripts/send_qa_email.py | 1 - 1 file changed, 1 deletion(-) diff --git a/scripts/send_qa_email.py b/scripts/send_qa_email.py index 7999c1b..96225a8 100755 --- a/scripts/send_qa_email.py +++ b/scripts/send_qa_email.py @@ -83,7 +83,6 @@

[yocto] [yocto-autobuilder-helper][PATCH 1/8] scripts/utils: add unit tests for getcomparisonbranch

From: Alexis Lothoré Signed-off-by: Alexis Lothoré --- scripts/test_utils.py | 104 ++ 1 file changed, 104 insertions(+) create mode 100755 scripts/test_utils.py diff --git a/scripts/test_utils.py b/scripts/test_utils.py new file mode 100755 index

[yocto] [yocto-autobuilder-helper][PATCH 3/8] scripts/send-qa-email: invert boolean logic for release check

From: Alexis Lothoré is_non_release_version has an inverted logic which makes its reuse quite confusing Transform it as is_release_version and let caller do the negation if needed Signed-off-by: Alexis Lothoré --- scripts/send_qa_email.py | 6 +++--- 1 file changed, 3 insertions(+), 3

Re: Wifi Networking Regression in linux-6.2.3

On 3/13/23 05:56, Genes Lists wrote: On 3/13/23 03:00, David Bohman wrote: There is a fairly serious regression in linux-6.2.3 that kills wifi: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79d1ed5ca7db67d48e870c979f0e0f6b0947944a Hi David:  I am sure

Re: Wifi Networking Regression in linux-6.2.3

On 3/13/23 03:00, David Bohman wrote: There is a fairly serious regression in linux-6.2.3 that kills wifi: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=79d1ed5ca7db67d48e870c979f0e0f6b0947944a Hi David: I am sure this commit is in 6.2.3 and all later stable

Re: [tor-relays] Confusing bridge signs...

On Sonntag, 12. März 2023 04:45:21 CET Keifer Bly wrote: > I do not use any scripts to start tor, I just type tor to start the process > on debian. That's where your problems begin. You start a 2nd tor process as root that doesn't take the default configs from:

Re: [tor-relays] Relay requirements

On Dienstag, 7. März 2023 13:31:13 CET mail--- via tor-relays wrote: > Running a few relays on 1-2 CPU cores with limited RAM is > fine, but just keep an eye on it and don't run other memory intensive stuff > on the server (like DNS query caching, which can take quite some RAM as > well). A

Re: [tor-relays] Confusing bridge signs...

On Mittwoch, 8. März 2023 18:13:01 CET Keifer Bly wrote: > Strangely, nothing whatsoever is being written to the notices.log file, > upon checking it it is completely empty, nothing there. That can't be, please post: ~# ls -A /var/log/tor In general, everything is always written to

Re: [tor-relays] Relay requirements

On Dienstag, 7. März 2023 03:00:49 CET Sydney wrote: > Newbie here. No network experience but already running 2 TOR instances: 1 > TOR service + 1 bridge. Never mix different relay types under one IP. > I would like to "upgrade" to TOR relays but have a few questions relating to > hardware needs.

Re: archlinux-keyring-wkd-sync returns 87 errors

Curious - Are you able to ping the WKD webserver from failing machine? ping openpgpkey.archlinux.org

Re: archlinux-keyring-wkd-sync returns 87 errors

On 3/10/23 05:39, Łukasz Michalski wrote: A and B. Both updated at the same time. On A service works, on B it fails. I have similar situation. On a machine that had fails running manually worked fine. What happens if you run manually? /usr/bin//archlinux-keyring-wkd-sync best gene

[OE-core] [PATCH] scripts/yocto_testresults_query.py: set proper branches when using resulttool

From: Alexis Lothoré The script currently only works if base and target can be found on default branches. It breaks if we try to generate a regression report between revisions that live on different branches (as needed on integration and testing branches). For example, the following command:

[RFC 6/X] omp: Allow creation of simd clones from omp declare variant with -fopenmp-simd flag

Hi, This RFC is to propose relaxing the flag needed to allow the creation of simd clones from omp declare variants, such that we can use -fopenmp-simd rather than -fopenmp. This should only change the behaviour of omp simd clones and should not enable any other openmp functionality, though I

[RFC 5/X] omp: Create simd clones from 'omp declare variant's

Hi, This RFC extends the omp-simd-clone pass to create simd clones for functions with 'omp declare variant' pragmas that contain simd constructs. This patch also implements AArch64's use for this functionality. This requires two extra pieces of information be kept for each simd-clone, a

[RFC 4/X] omp, aarch64: Add SVE support for 'omp declare simd' [PR 96342]

Hi, This patch adds SVE support for simd clone generation when using 'omp declare simd'. The design is based on what was discussed in PR 96342, but I did not look at YangYang's patch as I wasn't sure of whether that code's copyright had been assigned to FSF. This patch also is not in

[PATCH 3/X] parloops: Allow poly number of iterations

Hi, This patch modifies this function in parloops to allow it to handle loops with poly iteration counts. gcc/ChangeLog: * tree-parloops.cc (try_transform_to_exit_first_loop_alt): Handle poly nits. Is this OK for Stage 1?diff --git a/gcc/tree-parloops.cc b/gcc/tree-parloops.cc

[PATCH 2/X] parloops: Copy target and optimizations when creating a function clone

Hi, This patch makes sure we copy over DECL_FUNCTION_SPECIFIC_{TARGET,OPTIMIZATION} in parloops when creating function clones. This is required for SVE clones as we will need to enable +sve for them, regardless of the current target options. I don't actually need the 'OPTIMIZATION' for this

[PATCH 1/X] omp: Replace simd_clone_subparts with TYPE_VECTOR_SUBPARTS

Hi, This patch replaces the uses of simd_clone_subparts with TYPE_VECTOR_SUBPARTS and removes the definition of the first. gcc/ChangeLog: * omp-sind-clone.cc (simd_clone_subparts): Remove. (simd_clone_init_simd_arrays): Replace simd_clone_subparts with TYPE_VECTOR_SUBPARTS.

[RFC 0/X] Implement GCC support for AArch64 libmvec

Hi all, This is a series of patches/RFCs to implement support in GCC to be able to target AArch64's libmvec functions that will be/are being added to glibc. We have chosen to use the omp pragma '#pragma omp declare variant ...' with a simd construct as the way for glibc to inform GCC what

Re: PESO: Invaders!

> On 5 Mar 2023, at 14:12, Alan C wrote: > > We were graced by the appearance of Guinea Fowl with chicks. Nice one Alan! Saw lots of those, sometimes in flocks of hundreds, last year in the Kalahari Desert (Deception Valley, Botswana). > They have a hard time around here with all the

Re: Dual Root setup

All I gave updated the code and now provide an inotify based daemon to sync alternate s - and a systemd service unit to run it. I would very much appreciate if others ran this - by using the test option it does nothing but prints what would happen. And can be run as non-root user. It is

Re: Dual Root setup

On 3/7/23 03:50, Óscar García Amor wrote: El lun, 06-03-2023 a las 21:30 -0500, Jonathan Whitlock escribió: This is about having a computer that is resilient to root drive failure. This is in addition to doing backups, certainly not a replacement :) gene

Re: Dual Root setup

On 3/4/23 12:56, Genes Lists wrote: I know there's lots of info available about dual boot - but not much I could find on Dual Root. What is Dual Root?    This is a machine with 2 "root" disks where the second one is a hot standby - in event of root disk failure the secon

Re: Dual Root setup

On 3/6/23 02:50, Óscar García Amor wrote: Interesting, I'll take a look at it when you upload the code. I'd appreciate wider testing on the code - we all know that just because it works for me, doesn't mean it will work everywhere with certainty. It would be super helpful if others can

Re: [gentoo-user] Setting a fixed nameserver for openvpn

On 06/03/2023 11:08, Peter Humphrey wrote: On Monday, 6 March 2023 10:56:37 GMT Wols Lists wrote: On 06/03/2023 10:06, Michael wrote: I suspect the behaviour you noticed is related to FF functionality like TRR (Trusted Recursive Resolver) farming all your DNS queries over to the cloudfarce

Re: [gentoo-user] Setting a fixed nameserver for openvpn

On 06/03/2023 10:06, Michael wrote: On Monday, 6 March 2023 08:24:35 GMT Wols Lists wrote: On 06/03/2023 08:08, Neil Bothwick wrote: On Mon, 6 Mar 2023 07:54:51 +, Wols Lists wrote: There's another file - can't remember its name - that tells your resolver what to try in what order

Re: [gentoo-user] Setting a fixed nameserver for openvpn

On 06/03/2023 08:08, Neil Bothwick wrote: On Mon, 6 Mar 2023 07:54:51 +, Wols Lists wrote: There's another file - can't remember its name - that tells your resolver what to try in what order - the hosts file, dns, what dhcp told you, etc etc, so your resolver might not be using dns the way

Re: [gentoo-user] Setting a fixed nameserver for openvpn

On 05/03/2023 18:41, Dale wrote: I edited the file they say with kwrite.  Even after I restart openvpn, the IP they want is there but it doesn't use it according to the site they sent for me to check it with.  It shows other IP addresses.  I'm sure I'm missing something, likely something simple,

Re: Dual Root setup

I have updated the notes which now shows the original way but also the approach suggested by Oscar (thank you) - this is a superior method but bit more painful for existing installs. This way has on each disk along with btrfs raid1 for the rest basically. I have a working example doing

[tor-relays] D5A3882CBDBE4CAD2F9DDA2AB80FE761BEDC3F11 is spoofing my contact info

This is _not_ my relay: https://metrics.torproject.org/rs.html#details/D5A3882CBDBE4CAD2F9DDA2AB80FE761BEDC3F11 https://nusenu.github.io/OrNetStats/w/relay/D5A3882CBDBE4CAD2F9DDA2AB80FE761BEDC3F11.html -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!

Re: Dual Root setup

On 3/5/23 07:11, Óscar García Amor wrote: In fact at hook level you can put one like in the example of the manual ml Yes I agree that Hooks are useful, but they do only catch things on package updates as far as I know. If you want to catch manual changes, like an edit to a loader file, then

Re: Dual Root setup

On 3/5/23 07:11, Óscar García Amor wrote: Thanks Oscar - I edited my notes to show this as the preferred approach. Still needs more write up but I thought it best to get it up sooner than later. Do you know if it would work to use separate /boot partitions, as I mention above, (each

Re: Dual Root setup

On 3/5/23 05:13, Óscar García Amor wrote: ... The method is simple as you simply need two partitions on the two disks. The first one on each disk is the ESP and the second one is the one you are going to use for the btrfs raid. Then you simply mount the raid1 between both partitions btrfs[1] and

Re: [tor-relays] Confusing bridge signs...

On Samstag, 4. März 2023 02:09:19 CET Keifer Bly wrote: > Wheres the pastebin page? Thanks. $websearch pastebin https://paste.debian.net/ https://paste.systemli.org/ https://pastebin.mozilla.org/ ... -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom!

Re: Dual Root setup

On 3/4/23 18:22, Genes Lists wrote: But your cautionary comment is definitely something to keep an eye on. I already have these concerns noted at the bottom of the notes - since you pointed it out, It would be better for me to highlight them and move them earlier in the notes. thanks

Re: Dual Root setup

On 3/4/23 18:08, Łukasz Michalski wrote: I have this setup on all servers that do not have battery backed HW raid cards and use mdadm there. I use systemd-boot as bootloader. Works well and can be done on existing system with just a single reboot. It is not easy - you have to create degraded

Re: Dual Root setup

On 3/4/23 13:21, Uwe Sauter wrote: The usual Linux MD-RAID can have its metadata placed on different positions in the partition (see man (8) mdadm, option "-e, --metadata"). This is intriguing for sure but to be honest it has a bit of a brittle, hacky feel to it. My own preference is

Re: Dual Root setup

On 3/4/23 13:21, Uwe Sauter wrote: The usual Linux MD-RAID can have its metadata placed on different positions in the partition (see man (8) mdadm, option "-e, --metadata"). Knowing this it is no problem to create a partition on each disk of type EF00, create a RAID1 with metadata version

Re: Dual Root setup

On 3/4/23 13:05, Genes Lists wrote: Could be wrong, but I don't believe the is on RAID1 is it? Dual root is dual everything - esp, root, boot, the whole lot. You can clearly have an esp on each raid disk, so this could work as well - recovery might be little different than what I did

Re: Dual Root setup

On 3/4/23 13:00, Uwe Sauter wrote: Hi Gene, out of curiosity: where do you see the advantages of such a setup compared to having your root filesystem on a RAID1? , Could be wrong, but I don't believe the is on RAID1 is it? Dual root is dual everything - esp, root, boot, the whole lot.

Re: [AFMUG] Indoor Cat5 distributor

We’ve got some non shielded cable under our Apex9 brand.  Could sell it for a good price.  We’ve been sitting on it for some time.Marc Negri is in copy (not a list member) and his number is (561) 200-3642Jeff BroadwickCTIconnect312-205-2519 Office574-220-7826 Celljbroadw...@cticonnect.comOn Mar 3,

Re: [tor-relays] Confusing bridge signs...

On Dienstag, 28. Februar 2023 19:02:38 CET Keifer Bly wrote: > Yep, and after that the same still happens, it is still going offline In the syslog is why tor aborts. To help you, you should post your logs to a pastbin page. From the start of the tor daemon until it goes offline. -- ╰_╯ Ciao

Re: [PATCH] simplify-rtx: Fix VOIDmode operand handling in simplify_subreg [PR108805]

Committed attached patch. On 02/03/2023 10:13, Richard Sandiford wrote: "Andre Vieira (lists)" writes: Hey both, Sorry about that, don't know how I missed those. Just running a test on that now and will commit when it's done. I assume the comment and 0 -> byte change can be se

[yocto] [yocto-autobuilder-helper][PATCH 1/1] scripts/send-qa-email: use yocto_testresults_query.py for sha1 resolution

From: Alexis Lothoré A new tool named yocto_testresults_query.py has been integrated in poky as a thin wrapper between send-qa-email and resulttool. The new tool is in charge of converting tags/branches names to SHA1 revisions and to call resulttool with those revisions Remove any code related

Re: [PATCH] simplify-rtx: Fix VOIDmode operand handling in simplify_subreg [PR108805]

Hey both, Sorry about that, don't know how I missed those. Just running a test on that now and will commit when it's done. I assume the comment and 0 -> byte change can be seen as obvious, especially since it was supposed to be in my original patch... On 27/02/2023 15:46, Richard Sandiford

Re: [PATCH] amdgcn: Enable SIMD vectorization of math functions

On 01/03/2023 10:01, Andrew Stubbs wrote: > On 28/02/2023 23:01, Kwok Cheung Yeung wrote: >> Hello >> >> This patch implements the TARGET_VECTORIZE_BUILTIN_VECTORIZED_FUNCTION >> target hook for the AMD GCN architecture, such that when vectorized, >> calls to builtin standard math functions

Re: [OE-core] [PATCH 0/6] keep reducing regression reports noise

Hello Tim, On 3/1/23 07:24, Tim Orling wrote: > On Tue, Feb 28, 2023 at 10:10 AM Alexis Lothoré via lists.openembedded.org > > > wrote: > > From: Alexis Lothoré > > >

Re: What is/are the IPv4 addresses used by archlinux-keyring-wkd-sync? I need to tell iptables

On 2/26/23 22:23, David C. Rankin wrote: David - I emailed you an nftables script off-list - if its not in your spam folder, you may find it useful. Happy to share on list of course, but for now thought it better not to. best, gene

[OE-core] [PATCH 1/6] scripts/resulttool: call fixup_ptest_names in regression_common

From: Alexis Lothoré ptests names not only need to be fixed for regression based on git testresults but also for testsresults provided "manually" Move ptests naming fixup in regression_common to share the fixup between both regression use cases Signed-off-by: Alexis Lothoré ---

[OE-core] [PATCH 3/6] oeqa/selftest/resulttool: fix fake data

From: Alexis Lothoré resulttool searches for "status" field, not "STATUS", in results. This fix is more to avoid confusion than fixing anything, since the updated tests are about regression.can_be_compared, which does not check for "status" Signed-off-by: Alexis Lothoré ---

[OE-core] [PATCH 3/6] oeqa/selftest/resulttool: fix fake data used for testing

From: Alexis Lothoré resulttool searches for "status" field, not "STATUS", in results. This fix is more to avoid confusion than fixing anything, since the updated tests are about regression.can_be_compared, which does not check for "status" Signed-off-by: Alexis Lothoré ---

[OE-core] [PATCH 6/6] scripts/resulttool: do not count newly passing tests as regressions

From: Alexis Lothoré resulttool regression module simply compare a base test status to a target test result status. This approach raises many false positives since all XXX -> PASS transitions (XXX being any status different from PASS) are flagged as regression. - Do not list XXX -> PASS

[OE-core] [PATCH 2/6] oeqa/selftest/resulttool: fix ptest tests

From: Alexis Lothoré There are multiple issues with the tests for the ptest fixup mechanism introduced in c45d58f003e8d8b323169ca9d479dc49c43a9974: - the feature does not impact regression.can_be_compared but directly the comparison step in regression.regression_common - the "status" field was

[OE-core] [PATCH 4/6] scripts/resulttool: fix ptests results containing a non reproducible path

From: Alexis Lothoré Some ptests results may be wrongly sampled, resulting in some part of the error being propagated in test name. For example: "ptestresult.binutils-ld.in testcase

[OE-core] [PATCH 5/6] oeqa/selftest/resulttool: add test for error propagation in test name filtering

From: Alexis Lothoré Signed-off-by: Alexis Lothoré --- .../oeqa/selftest/cases/resulttooltests.py| 24 +++ 1 file changed, 24 insertions(+) diff --git a/meta/lib/oeqa/selftest/cases/resulttooltests.py b/meta/lib/oeqa/selftest/cases/resulttooltests.py index

[OE-core] [PATCH 0/6] keep reducing regression reports noise

From: Alexis Lothoré Hello, here is another batch of fixes to reduce noise in regression reports. Fixes are directly linked to main noise sources seen in 4.2_M3 regression report ([1]). - fix some existing selftests for resulttool - add more filters for ptests incorrectly logging failures. The

[OE-core] [PATCH 2/6] oeqa/selftest/resulttool: fix ptest filtering tests

From: Alexis Lothoré There are multiple issues with the tests for the ptest fixup mechanism introduced in c45d58f003e8d8b323169ca9d479dc49c43a9974: - the feature does not impact regression.can_be_compared but directly the comparison step in regression.regression_common - the "status" field was

Re: Discourse

On 27/02/2023 09:58, Andrew Bernard wrote: Not sure where my brain has been holidaying lately - I had the idea you can't import mbox format lists into Discourse and even gave what I thought were reasons you can't. This it totally wrong. Discourse does have an import mechanism for loading

[OE-core] [PATCH 2/2] oeqa/selftest/resulttool: add test for metadata filtering on regression

From: Alexis Lothoré Multiple filters have been added to resulttool to ensure that test results are compared only to relevant older tests results Add some unit tests about added filters: - tests should only be compared when machine matches - tests run as oeselftest should only be compared when

[OE-core] [PATCH 1/2] scripts/yoct_testresults_query: manage base/target revision not found

From: Alexis Lothoré If yocto_testresults_query.py is run from oe-core instead of poky, the script will very likely fail since poky tags do no exist in oe-core. If one or both revisions are not found, log the error and a suggestion about the reason (the script being run in oe-core instead of

[OE-core] [PATCH 0/2] scripts: yocto_testresults_query fixes and resulttool missing tests

From: Alexis Lothoré Hello, this series is a small follow-up to [1] - add explicit error when running yocto_testresults_query.py from oe-core instead of poky. Since the tool is working with git references from poky, it will not manage to resolve SHA-1 in oe-core - add tests for new

Re: What is/are the IPv4 addresses used by archlinux-keyring-wkd-sync? I need to tell iptables

On 2/26/23 17:29, David C. Rankin wrote: ... The issue is I block most of RIPE, I don't do business overseas, rarely outside Texas. I keep iptables stats on the number of intrusion attempts from RIPE,These intrusion attempts are inbound and it is indeed not uncommon to 'block' ingress SYN

Re: What is/are the IPv4 addresses used by archlinux-keyring-wkd-sync? I need to tell iptables

On 2/26/23 06:32, David Runge wrote: On 2023-02-26 10:22:08 (+0100), Markus Schaaf wrote: Am 26.02.23 um 04:00 schrieb David C. Rankin: Arch devs, ... iptables not to block them so my logs quit filling up with errors. I may be off base here but I'll ask anyway. Assuming you, as is

Re: [OE-core] [PATCH v3 0/6] scripts/resulttool/regression: add metadata filtering

Hello Richard, On 2/26/23 13:15, Richard Purdie wrote: > On Sat, 2023-02-25 at 16:59 +0100, Alexis Lothoré wrote: >> Hello Richard, >> as usual, thanks for the prompt feedback ! >> >> On 2/25/23 13:32, Richard Purdie wrote: >>> On Sat, 2023-02-25 at 09:15 +, Richard Purdie via >>>

Re: [vpp-dev] [vpp-build] VPP build error on Ubuntu 22.04

Hi Dave, i have apply the patch and the build process has no more errors. All .deb packages are created. Thank you very much. -- Jens -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22627): https://lists.fd.io/g/vpp-dev/message/22627 Mute This

Re: [tor-relays] Confusing bridge signs...

On Freitag, 24. Februar 2023 04:11:27 CET Keifer Bly wrote: > Yes, the limit is 50GB per month, but for some reason the distribution > mechanism is not updating and the bridge keeps going offline despite the > new torrc. What comes to my mind without logs (& your 'killall -HUP' of a systemd

Re: [tor-relays] Frantech (was Re: Confusing bridge signs)

On Freitag, 24. Februar 2023 14:19:13 CET Jeff Teitel wrote: > On Fri, Feb 24, 2023 at 12:10 AM Marco wrote: > > Yes, Frantech should actually be avoided. But in Miami there are few Tor > > relays. A SLICE 512 for $2.00/m or $20.00/y is sufficient for a bridge. > >

Re: [OE-core] [PATCH v3 0/6] scripts/resulttool/regression: add metadata filtering

Hello Richard, as usual, thanks for the prompt feedback ! On 2/25/23 13:32, Richard Purdie wrote: > On Sat, 2023-02-25 at 09:15 +, Richard Purdie via > lists.openembedded.org wrote: >> On Fri, 2023-02-24 at 18:06 +, Richard Purdie via >> lists.openembedded.org wrote: >>> Hi Alexis, >>>

Re: Discourse

On 25/02/2023 13:34, Jean Abou Samra wrote: Le samedi 25 février 2023 à 16:56 +0330, Omid Mo'menzadeh a écrit : Hi all, Speaking up as one of the silent majority on this topic, now that it's mentioned, as I think I have two cents to add. I personally wouldn't be against Discourse, as I find

Re: One to remember linux 6.1.12.arch1-1 and linux-lts 6.1.13-1

On 2/24/23 21:01, David C. Rankin wrote: ..   Here is to hoping 6.2 doesn't bring a lot of surprises and kernel module issues... FYI - I've been running 6.2 on several machines for a while now and they are running smooth as silk. gene

Re: pacman -Syu fails - python-augeas (existing files) needed by certbot-apache?

On 2/24/23 19:41, David C. Rankin wrote: All, error: failed to commit transaction (conflicting files) python-scapy: /usr/lib/python3.10/site-packages/test/__init__.py exists ...   The python-augeas package is needed by certbot-apache. How to resolve the conflict? Hi Its a conflict

[OE-core] [PATCH v3 6/6] oeqa/selftest: add test for yocto_testresults_query.py

From: Alexis Lothoré Add some tests for new yocto_testresults_query.py helper. First test is taken from yocto-autobuilder-helper feature which has moved in yocto_testresults_query Signed-off-by: Alexis Lothoré --- .../cases/yoctotestresultsquerytests.py | 39 +++ 1 file

[OE-core] [PATCH v3 4/6] oeqa/selftest/resulttool: add test for metadata filtering on regression

From: Alexis Lothoré Introduce new tests for the metadata-based filtering added for oeselftest results Signed-off-by: Alexis Lothoré --- .../oeqa/selftest/cases/resulttooltests.py| 137 ++ 1 file changed, 137 insertions(+) diff --git

[OE-core] [PATCH v3 5/6] scripts: add new helper for regression report generation

From: Alexis Lothoré Add yocto-testresults-query script. This is a thin wrapper over resulttool which is able to translate tags or branch name to specific revisions, and then to work with those "guessed" revisions with resulttool Signed-off-by: Alexis Lothoré ---

[OE-core] [PATCH v3 1/6] scripts/oe-selftest: append metadata to tests results

From: Alexis Lothoré Many stored results TEST_TYPE are set to "oeselftest", however all those tests are not run with the same sets of parameters, so those tests results may not be comparable. Attach relevant parameters as tests metadata to allow identifying tests configuration so we can compare

[OE-core] [PATCH v3 3/6] scripts/resulttool/regression: add metadata filtering for oeselftest

From: Alexis Lothoré When generating regression reports, many false positive can be observed since some tests results are compared while the corresponding tests sets are not the same, as it can be seen for example for oeselftest tests (oeselftest is run multiple time but with different

<    4   5   6   7   8   9   10   11   12   13   >