Kernel 6.7 Test Week is underway!

2024-01-26 Thread Sumantro Mukherjee
Hey Folks,

As most of you might know, Kernel 6.7 Test Week is currently happening[0]
I have figured out that, I can't login to FAS from the Kernel Test
Result site[1].
If you are also someone who is stuck, please follow the infra issue
filed here[2].
And please submit the results here[3]

If you have still not participated and have some free time, we urge you to
take part in testing!

We are also sorry for the inconvenience caused due to login issues.
Thanks for testing :)

[0] http://fedoraproject.org/wiki/Test_Day:2024-01-21_Kernel_6.7_Test_Week
[1] https://apps.fedoraproject.org/kerneltest/
[2] https://pagure.io/fedora-infrastructure/issue/11744
[3] https://testdays.fedoraproject.org/events/173
-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv8 0/2] Add new os-build targets: rt-devel and automotive-devel

2024-01-26 Thread Don Zickus (via Email Bridge)
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2732#note_1746337464

@scweaver - big update.  most of it is just using 'local'.  But alot more
robustness around missing branches.  Then the rebases keep breaking because
things are corrupted, so removed a bunch of fragile ideas.  Now the thing can
corrupt all its branches and rebuild itself successfully.  I think i just need
to add the .gitlab-ci.yaml changes for the cronjob piece.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[OS-BUILD PATCHv8 2/2] Add new os-build targets: rt-devel and automotive-devel

2024-01-26 Thread Don Zickus (via Email Bridge)
From: Don Zickus 

Add new os-build targets: rt-devel and automotive-devel

This is an attempt to automate the rt and automotive devel branches
using the upstream linux-rt-devel tree as the base combined with
os-build.

The overall process isn't too complicated but there are enough steps to
make it compilicated.

Steps:
* map upstream linux-rt-devel to master-rt branch
* update os-build
* grab linux version from master-rt and os-build
* if version the same then merge os-build and master-rt to
  os-build-rt-automated
* else merge tag kernel-N.V.0-0 and master-rt to os-build-rt-automated until
  master-rt is update to os-build
* merge os-build-rt-automated into os-build-rt-devel
* merge os-build-rt-automated into os-build-automotive-devel
* run the generate pending-rhel config scripts on rt-devel and
  automotive-devel

The script has beginning logic to handle rebasing if necessary when the
rt-devel branch transitions from os-build-stable (linux-stable) to linux
master again.

NOTE: The script uses kernel-N.V.0-0 which is rebased after os-build
linux-x.y GA is created but before linux-x.y+1 pre-rc1 merges happen.
The reason for this is because linux-stable-x.y doesn't exist until
linux-x.y+1-rc1 exists thus leaving linux-stable-x.y-1 in the meantime.
An awkward gap exists, use kernel-N.V.0-0 as the base.

The script has no effect on the day-to-day operations of os-build.  They
are designed to be run from a gitlab cron job and update in the
background.  Once they are deemed stable, adding ARK MRs that target
either os-build-rt-devel or os-build-automotive-devel will be possible
and those branches can start proper parallel developement with os-build.

Signed-off-by: Don Zickus 

diff --git a/redhat/scripts/ci/ark-ci-env.sh b/redhat/scripts/ci/ark-ci-env.sh
index blahblah..blahblah 100644
--- a/redhat/scripts/ci/ark-ci-env.sh
+++ b/redhat/scripts/ci/ark-ci-env.sh
@@ -8,24 +8,188 @@ die()
 
 ci_pre_check()
 {
-   if test -n "${TO_PUSH}"; then
-   if test -z "${GITLAB_PROJECT_URL}" || test -z 
"$GITLAB_PROJECT_PUSHURL"; then
-   echo "To enable git-push, please run:"
-   echo "git remote add gitlab "
-   echo "git remote set-url --push gitlab "
+   if test -z "${GITLAB_PROJECT_URL}" || test -z 
"$GITLAB_PROJECT_PUSHURL"; then
+echo "To enable git-push, please run:"
+   echo "git remote add gitlab "
+   echo "git remote set-url --push gitlab "
+   if test -n "${TO_PUSH}"; then
die "Misconfigured 'gitlab' entry for git"
fi
 fi
 git diff-index --quiet HEAD || die "Dirty tree, please clean before 
merging."
 }
 
+# wrapper around branches that may not be exist yet
+ark_git_branch()
+{
+   local target_branch="$1"
+   local source_branch="$2"
+
+   # switch to branch if it exists otherwise create and set to source
+   # branch
+   git show-ref -q --heads "$target_branch" || \
+   git branch "$target_branch" "$source_branch"
+}
+
+# GitLab can only mirror one project at a time.  This wrapper function does
+# the mirroring for any other branches.
+ark_git_mirror()
+{
+   local target_branch="$1"
+   local upstream_tree="$2"
+   local source_branch="$3"
+   local reset_branch="$4"
+
+   prev_branch="$(git rev-parse --abbrev-ref HEAD)"
+   remote_branch="$upstream_tree/$source_branch"
+   ark_git_branch "$target_branch" "$remote_branch"
+   git checkout "$target_branch"
+   git fetch "$upstream_tree" "$source_branch"
+   if test -z "$reset_branch"; then
+   git merge "$remote_branch" || die "git merge $remote_branch 
failed"
+   else
+   git reset --hard "$remote_branch" || die "git reset 
$remote_branch failed"
+   fi
+   git checkout "$prev_branch"
+}
+
+# Merge wrapper in case issues arise
+ark_git_merge()
+{
+   local source_branch="$1"
+   local target_branch="$2"
+   local reset_branch="$3"
+
+   prev_branch="$(git rev-parse --abbrev-ref HEAD)"
+   ark_git_branch "$target_branch" "$source_branch"
+   git checkout "$target_branch"
+   if test -n "$reset_branch"; then
+   # there are cases when the initial merge is a reset
+   git reset --hard "$source_branch"  || die "git reset 
$source_branch failed"
+   elif ! git merge -m "Merge '$source_branch' into '$target_branch'" 
"$source_branch"; then
+   git merge --abort
+   printf "Merge conflict; halting!\n"
+   printf "To reproduce:\n"
+   printf "* git checkout %s\n" "${target_branch}"
+   printf "* git merge %s\n" "${source_branch}"
+   die "Merge conflicts"
+   fi
+
+   git checkout "$prev_branch"
+   return 0
+}
+
+ark_git_rebase()
+{
+   local branch="$1"
+   local upstream="$2"
+   local base="$3"
+
+   

[OS-BUILD PATCHv8 1/2] Add python3-pyyaml to buildreqs for kernel-docs

2024-01-26 Thread Don Zickus (via Email Bridge)
From: Justin M. Forbes 

Add python3-pyyaml to buildreqs for kernel-docs

Upstream commit f061c9f7d058f added a script to parse the Netlink YAML
specs and generate RST files.  As a result, we need python3-pyyaml for
"make htmldocs" to succeed.

Signed-off-by: Justin M. Forbes 

diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template
index blahblah..blahblah 100644
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -673,7 +673,7 @@ BuildRequires: bpftool
 BuildRequires: rsync
 %endif
 %if %{with_doc}
-BuildRequires: xmlto, asciidoc, python3-sphinx, python3-sphinx_rtd_theme
+BuildRequires: xmlto, asciidoc, python3-sphinx, python3-sphinx_rtd_theme, 
python3-pyyaml
 %endif
 %if %{with_sparse}
 BuildRequires: sparse

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2732
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[OS-BUILD PATCHv8 0/2] Add new os-build targets: rt-devel and automotive-devel

2024-01-26 Thread Don Zickus (via Email Bridge)
From: Don Zickus on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2732

This is an attempt to automate the rt and automotive devel branches
using the upstream linux-rt-devel tree as the base combined with
os-build.

The overall process isn't too complicated but there are enough steps to
make it compilicated.

Steps:
* map upstream linux-rt-devel to master-rt branch
* update os-build
* grab linux version from master-rt and os-build
* if version the same then merge os-build and master-rt to
  os-build-rt-automated
* else merge linux-stable and master-rt to os-build-rt-automated until
  master-rt is update to os-build
* merge os-build-rt-automated into os-build-rt-devel
* merge os-build-rt-automated into os-build-automotive-devel
* run the generate pending-rhel config scripts on rt-devel and
  automotive-devel

The script has beginning logic to handle rebasing if necessary when the
rt-devel branch transitions from linux-stable to linux master again.

The script has no effect on the day-to-day operations of os-build.  They
are designed to be run from a gitlab cron job and update in the
background.  Once they are deemed stable, adding ARK MRs that target
either os-build-rt-devel or os-build-automotive-devel will be possible
and those branches can start proper parallel developement with os-build.

Signed-off-by: Don Zickus 

---
 redhat/scripts/ci/ark-ci-env.sh   |  178 -
 redhat/scripts/ci/ark-merge-rt.sh |  173 
 redhat/kernel.spec.template   |2 +-
 3 files changed, 345 insertions(+), 8 deletions(-)
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv8 0/3] redhat/Makefile: fix and clean up some of the logic

2024-01-26 Thread via Email Bridge
From: Ondrej Mosnáček on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2892#note_1746180214

OK, I missed that `create-data.sh` runs the `make setup-source` multiple times
in parallel (and I failed to test it with `-j`). Here is a second take that
should address that problem: !2913
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[OS-BUILD PATCHv2 4/4] redhat/Makefile: remove an unused target

2024-01-26 Thread via Email Bridge
From: Ondrej Mosnacek 

redhat/Makefile: remove an unused target

The $(REDHAT)/rpm/SOURCES/$(SPECFILE) target, which just aliases
dist-sources seems to serve no actual purpose, so remove it.

Signed-off-by: Ondrej Mosnacek 

diff --git a/redhat/Makefile b/redhat/Makefile
index blahblah..blahblah 100644
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -832,11 +832,6 @@ _dist-brew _dist-koji: _dist-%: dist-vr-check dist-srpm
 _distg-brew _distg-koji: _distg-%: dist-vr-check
$* $(BUILD_PROFILE) build $(BUILD_FLAGS) --scratch $(BUILD_TARGET) 
"$(RHGITURL)?redhat/koji#$(RHGITCOMMIT)"
 
-.PHONY: $(REDHAT)/rpm/SOURCES/$(SPECFILE)
-$(REDHAT)/rpm/SOURCES/$(SPECFILE):
-   @echo "dist-sources"
-   @$(MAKE) dist-sources
-
 dist-git-test: export RH_DIST_GIT_TEST="1"
 dist-git-test: dist-git
 

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2913
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[OS-BUILD PATCHv2 3/4] redhat/Makefile: fix setup-source and document its caveat

2024-01-26 Thread via Email Bridge
From: Ondrej Mosnacek 

redhat/Makefile: fix setup-source and document its caveat

The current definition of setup-source is racy, since it may cause
dist-clean-sources and _setup-source to be "built" in parallel and the
former caould then remove the results of the latter. Fix it to ensure
the right ordering and document the condition that must be preserved to
keep dist-clean-sources from racing with other targets.

_setup-source (and this race) has been introduced in commit 0cce4209d1cc
("redhat/Makefile: Split up setup-source target") in order to be called
from redhat/self-test/data/create-data.sh, where multiple source preps
can run in parallel. Make create-data.sh call the full setup-source and
use the existing RHSELFTESTDATA variable as an indication that
dist-clean-sources should be skipped.

Fixes: 0cce4209d1cc ("redhat/Makefile: Split up setup-source target")
Signed-off-by: Ondrej Mosnacek 

diff --git a/redhat/Makefile b/redhat/Makefile
index blahblah..blahblah 100644
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -574,10 +574,11 @@ dist-clean-configs:
@cd $(REDHAT)/configs; rm -f kernel-*.config kernel-*.config.orig 
kernel-*.config.tmp partial-*-snip.config
 
 dist-clean-sources:
+# skip dist-clean-sources when generating test data to prevent race condition
+ifndef RHSELFTESTDATA
@rm -f $(RPM)/SPECS/*
-   @for i in $(SOURCES)/*; do \
-   rm -f $$i; \
-   done;
+   @rm -f $(SOURCES)/*
+endif
 
 dist-clean-rpmdirs:
@for i in $(RPM)/{BUILD,SRPMS,RPMS,SPECS}/*; do \
@@ -638,7 +639,11 @@ dist-get-buildreqs: setup-source
echo "PASS: All build dependencies found."; \
fi
 
-_setup-source: dist-git-version-check
+# IMPORTANT: All targets whose recipes read/modify files under $(SOURCES)
+# MUST depend on setup-source (at least indirectly). Otherwise such
+# recipes may be ordered before/in parallel with dist-clean-sources
+# (prerequisite of setup-source), which would then delete their results.
+setup-source: dist-clean-sources dist-git-version-check
@if [ ! -e $(REDHAT)/$(SPECFILE).template ]; then \
echo "Creating $(REDHAT)/$(SPECFILE).template as a copy of 
$(REDHAT)/kernel.spec.template"; \
cp $(REDHAT)/kernel.spec.template 
$(REDHAT)/$(SPECFILE).template; \
@@ -660,8 +665,6 @@ _setup-source: dist-git-version-check
@$(REDHAT)/scripts/genspec/genspec.sh
@cp $(SOURCES)/$(SPECFILE) $(SOURCES)/../SPECS/
 
-setup-source: dist-clean-sources _setup-source
-
 generate-testpatch-tmp:
@$(GIT) diff --no-renames HEAD ":(exclude,top).get_maintainer.conf" \
":(exclude,top).gitattributes" \
diff --git a/redhat/self-test/data/create-data.sh 
b/redhat/self-test/data/create-data.sh
index blahblah..blahblah 100755
--- a/redhat/self-test/data/create-data.sh
+++ b/redhat/self-test/data/create-data.sh
@@ -28,7 +28,7 @@ specfile_helper () {
 
specfilename=$1
cp ./kernel.spec.template "${varfilename}.spec.template"
-   make RHSELFTESTDATA=1 SPECFILE="${specfilename}.spec" DIST="${DIST}" 
DISTRO="${DISTRO}" HEAD="${commit}" _setup-source
+   make RHSELFTESTDATA=1 SPECFILE="${specfilename}.spec" DIST="${DIST}" 
DISTRO="${DISTRO}" HEAD="${commit}" setup-source
grep -Fvx -f "${specfilename}.spec.template" 
"${sources}/${specfilename}.spec" > "${destdir}"/"${specfilename}".spec
# Ignore bpftoolversion definition as it may change.
sed -i '/^%define bpftoolversion /d' "${destdir}"/"${specfilename}".spec

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2913
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[OS-BUILD PATCHv2 2/4] redhat/Makefile: fix race condition when making the KABI tarball

2024-01-26 Thread via Email Bridge
From: Ondrej Mosnacek 

redhat/Makefile: fix race condition when making the KABI tarball

The recipe for $(KABI_TARBALL) references the kabi/kabi-current file,
but it doesn't depend on the target that creates it (dist-kabi), leading
to possible build failures under parallel build (make -j). Fix it by
making $(KABI_TARBALL) depend on dist-kabi.

Signed-off-by: Ondrej Mosnacek 

diff --git a/redhat/Makefile b/redhat/Makefile
index blahblah..blahblah 100644
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -603,7 +603,7 @@ $(TARBALL):
@scripts/create-tarball.sh
 
 .PHONY: $(KABI_TARBALL)
-$(KABI_TARBALL):
+$(KABI_TARBALL): dist-kabi
@(cd kabi && tar -cJf $(KABI_TARBALL) kabi-rhel$(RHEL_MAJOR)* 
kabi-current)
 
 .PHONY: $(KABIDW_TARBALL)

--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2913
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[OS-BUILD PATCHv2 1/4] redhat/Makefile: refactor KABI tarball creation

2024-01-26 Thread via Email Bridge
From: Ondrej Mosnacek 

redhat/Makefile: refactor KABI tarball creation

Place $(KABI_TARBALL) and $(KABIDW_TARBALL) in $(REDHAT) instead of
$(SOURCES) and only link/copy them into $(SOURCES) in _setup-source,
same as is done with $(TARBALL).

This allows removing duplicate steps to make the KABI tarballs from
_setup-source, while avoiding a race with dist-clean-sources (which
could otherwise remove the tarballs after being created, because
setup-source depends on it).

Signed-off-by: Ondrej Mosnacek 

diff --git a/redhat/Makefile b/redhat/Makefile
index blahblah..blahblah 100644
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -331,9 +331,9 @@ endif
 TARFILE:=linux-$(SPECTARFILE_RELEASE).tar.xz
 TARBALL:=$(REDHAT)/$(TARFILE)
 
-KABI_TARBALL:=$(SOURCES)/kernel-abi-stablelists-$(SPECKABIVERSION).tar.xz
+KABI_TARBALL:=$(REDHAT)/kernel-abi-stablelists-$(SPECKABIVERSION).tar.xz
 KABIDW := $(REDHAT)/kabi-dwarf
-KABIDW_TARBALL:=$(SOURCES)/kernel-kabi-dw-$(SPECKABIVERSION).tar.xz
+KABIDW_TARBALL:=$(REDHAT)/kernel-kabi-dw-$(SPECKABIVERSION).tar.xz
 
 # Taken from tools/lib/bpf/Makefile
 SPECBPFTOOLVERSION:=$(shell \
@@ -586,6 +586,8 @@ dist-clean-rpmdirs:
 
 dist-clean: dist-clean-sources dist-clean-configs dist-clean-rpmdirs
@rm -f $(REDHAT)/linux-*.tar.xz
+   @rm -f $(REDHAT)/kernel-abi-stablelists-*.tar.xz
+   @rm -f $(REDHAT)/kernel-kabi-dw-*.tar.xz
 
 dist-stub-key:
@echo "Copying pre-generated keys";
@@ -668,8 +670,9 @@ generate-testpatch-tmp:
":(exclude,top)Makefile.rhelver" \
":(exclude,top)redhat" > $(TESTPATCH).tmp
 
-sources-rh: $(TARBALL) generate-testpatch-tmp setup-source dist-configs-check
-   @cp -l $(TARBALL) $(SOURCES)/ || cp $(TARBALL) $(SOURCES)/
+sources-rh: $(TARBALL) $(KABI_TARBALL) $(KABIDW_TARBALL) 
generate-testpatch-tmp setup-source dist-configs-check
+   @cp -l $(TARBALL) $(KABI_TARBALL) $(KABIDW_TARBALL) $(SOURCES)/ || \
+   cp $(TARBALL) $(KABI_TARBALL) $(KABIDW_TARBALL) $(SOURCES)/
@touch $(TESTPATCH)
@diff $(TESTPATCH).tmp $(TESTPATCH) > /dev/null || \
echo "WARNING: There are uncommitted changes in your tree or 
the changes are not in sync with linux-kernel-test.patch.  Either commit the 
changes or run 'make dist-test-patch'"
@@ -711,11 +714,6 @@ sources-rh: $(TARBALL) generate-testpatch-tmp setup-source 
dist-configs-check
cp kabi/Module.kabi_$$KABIARCH $(SOURCES)/; \
cp kabi/Module.kabi_dup_$$KABIARCH $(SOURCES)/; \
done
-   @(cd kabi && tar -cJf $(KABI_TARBALL) kabi-rhel$(RHEL_MAJOR)* 
kabi-current)
-   @if [ ! -d $(KABIDW)/base ]; then \
-   mkdir -p $(KABIDW)/base; \
-   fi
-   @(cd kabi-dwarf && tar -cJf $(KABIDW_TARBALL) base run_kabi-dw.sh)
 
 dist-sources: dist-kabi dist-kabi-dup sources-rh
 
diff --git a/redhat/self-test/data/centos-2585cf9dfaad.el7 
b/redhat/self-test/data/centos-2585cf9dfaad.el7
index blahblah..blahblah 100644
--- a/redhat/self-test/data/centos-2585cf9dfaad.el7
+++ b/redhat/self-test/data/centos-2585cf9dfaad.el7
@@ -35,12 +35,12 @@ INCLUDE_FEDORA_FILES=1
 INCLUDE_RHEL_FILES=1
 INCLUDE_RT_FILES=1
 KABIDW=../redhat/kabi-dwarf
-KABIDW_TARBALL=../redhat/rpm/SOURCES/kernel-kabi-dw-5.16.0-0.rc5.6.test.el7.tar.xz
+KABIDW_TARBALL=../redhat/kernel-kabi-dw-5.16.0-0.rc5.6.test.el7.tar.xz
 KABI_CROSS_COMPILE=/usr/bin/aarch64-linux-gnu- /usr/bin/ppc64le-linux-gnu- 
/usr/bin/s390x-linux-gnu-
 KABI_CROSS_COMPILE_PREFIX=/usr/bin/
 KABI_CROSS_COMPILE_SUFFIX=-linux-gnu-
 KABI_SUPPORTED_ARCHS=aarch64 ppc64le s390x x86_64
-KABI_TARBALL=../redhat/rpm/SOURCES/kernel-abi-stablelists-5.16.0-0.rc5.6.test.el7.tar.xz
+KABI_TARBALL=../redhat/kernel-abi-stablelists-5.16.0-0.rc5.6.test.el7.tar.xz
 LANG=C
 LOCVERFILE=../localversion
 MACH=x86_64
diff --git a/redhat/self-test/data/centos-2585cf9dfaad.fc25 
b/redhat/self-test/data/centos-2585cf9dfaad.fc25
index blahblah..blahblah 100644
--- a/redhat/self-test/data/centos-2585cf9dfaad.fc25
+++ b/redhat/self-test/data/centos-2585cf9dfaad.fc25
@@ -35,12 +35,12 @@ INCLUDE_FEDORA_FILES=1
 INCLUDE_RHEL_FILES=1
 INCLUDE_RT_FILES=1
 KABIDW=../redhat/kabi-dwarf
-KABIDW_TARBALL=../redhat/rpm/SOURCES/kernel-kabi-dw-5.16.0-0.rc5.6.test.fc25.tar.xz
+KABIDW_TARBALL=../redhat/kernel-kabi-dw-5.16.0-0.rc5.6.test.fc25.tar.xz
 KABI_CROSS_COMPILE=/usr/bin/aarch64-linux-gnu- /usr/bin/ppc64le-linux-gnu- 
/usr/bin/s390x-linux-gnu-
 KABI_CROSS_COMPILE_PREFIX=/usr/bin/
 KABI_CROSS_COMPILE_SUFFIX=-linux-gnu-
 KABI_SUPPORTED_ARCHS=aarch64 ppc64le s390x x86_64
-KABI_TARBALL=../redhat/rpm/SOURCES/kernel-abi-stablelists-5.16.0-0.rc5.6.test.fc25.tar.xz
+KABI_TARBALL=../redhat/kernel-abi-stablelists-5.16.0-0.rc5.6.test.fc25.tar.xz
 LANG=C
 LOCVERFILE=../localversion
 MACH=x86_64
diff --git a/redhat/self-test/data/centos-78e36f3b0dae.el7 
b/redhat/self-test/data/centos-78e36f3b0dae.el7
index blahblah..blahblah 100644
--- a/redhat/self-test/data/centos-78e36f3b0dae.el7
+++ 

[OS-BUILD PATCHv2 0/4] redhat/Makefile: fix and clean up some of the logic (v2)

2024-01-26 Thread via Email Bridge
From: Ondrej Mosnáček on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2913

Since !2892 was buggy and had to be reverted, this is a second attempt,
hopefully correct this time.

---
 redhat/self-test/data/centos-2585cf9dfaad.el7  |   4 +-
 redhat/self-test/data/centos-2585cf9dfaad.fc25 |   4 +-
 redhat/self-test/data/centos-78e36f3b0dae.el7  |   4 +-
 redhat/self-test/data/centos-78e36f3b0dae.fc25 |   4 +-
 redhat/self-test/data/centos-df0cc57e057f.el7  |   4 +-
 redhat/self-test/data/centos-df0cc57e057f.fc25 |   4 +-
 redhat/self-test/data/centos-fce15c45d3fb.el7  |   4 +-
 redhat/self-test/data/centos-fce15c45d3fb.fc25 |   4 +-
 redhat/self-test/data/create-data.sh   |   2 +-
 redhat/self-test/data/fedora-2585cf9dfaad.el7  |   4 +-
 redhat/self-test/data/fedora-2585cf9dfaad.fc25 |   4 +-
 redhat/self-test/data/fedora-78e36f3b0dae.el7  |   4 +-
 redhat/self-test/data/fedora-78e36f3b0dae.fc25 |   4 +-
 redhat/self-test/data/fedora-df0cc57e057f.el7  |   4 +-
 redhat/self-test/data/fedora-df0cc57e057f.fc25 |   4 +-
 redhat/self-test/data/fedora-fce15c45d3fb.el7  |   4 +-
 redhat/self-test/data/fedora-fce15c45d3fb.fc25 |   4 +-
 redhat/self-test/data/rhel-2585cf9dfaad.el7|   4 +-
 redhat/self-test/data/rhel-2585cf9dfaad.fc25   |   4 +-
 redhat/self-test/data/rhel-78e36f3b0dae.el7|   4 +-
 redhat/self-test/data/rhel-78e36f3b0dae.fc25   |   4 +-
 redhat/self-test/data/rhel-df0cc57e057f.el7|   4 +-
 redhat/self-test/data/rhel-df0cc57e057f.fc25   |   4 +-
 redhat/self-test/data/rhel-fce15c45d3fb.el7|   4 +-
 redhat/self-test/data/rhel-fce15c45d3fb.fc25   |   4 +-
 redhat/Makefile|  38 +++--
 26 files changed, 66 insertions(+), 70 deletions(-)
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[OS-BUILD PATCH 0/4] redhat/Makefile: fix and clean up some of the logic (v2)

2024-01-26 Thread via Email Bridge
From: Ondrej Mosnáček on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2913

Since !2892 was buggy and had to be reverted, this is a second attempt,
hopefully correct this time.

---
 redhat/self-test/data/centos-2585cf9dfaad.el7  |   4 +-
 redhat/self-test/data/centos-2585cf9dfaad.fc25 |   4 +-
 redhat/self-test/data/centos-78e36f3b0dae.el7  |   4 +-
 redhat/self-test/data/centos-78e36f3b0dae.fc25 |   4 +-
 redhat/self-test/data/centos-df0cc57e057f.el7  |   4 +-
 redhat/self-test/data/centos-df0cc57e057f.fc25 |   4 +-
 redhat/self-test/data/centos-fce15c45d3fb.el7  |   4 +-
 redhat/self-test/data/centos-fce15c45d3fb.fc25 |   4 +-
 redhat/self-test/data/create-data.sh   |   2 +-
 redhat/self-test/data/fedora-2585cf9dfaad.el7  |   4 +-
 redhat/self-test/data/fedora-2585cf9dfaad.fc25 |   4 +-
 redhat/self-test/data/fedora-78e36f3b0dae.el7  |   4 +-
 redhat/self-test/data/fedora-78e36f3b0dae.fc25 |   4 +-
 redhat/self-test/data/fedora-df0cc57e057f.el7  |   4 +-
 redhat/self-test/data/fedora-df0cc57e057f.fc25 |   4 +-
 redhat/self-test/data/fedora-fce15c45d3fb.el7  |   4 +-
 redhat/self-test/data/fedora-fce15c45d3fb.fc25 |   4 +-
 redhat/self-test/data/rhel-2585cf9dfaad.el7|   4 +-
 redhat/self-test/data/rhel-2585cf9dfaad.fc25   |   4 +-
 redhat/self-test/data/rhel-78e36f3b0dae.el7|   4 +-
 redhat/self-test/data/rhel-78e36f3b0dae.fc25   |   4 +-
 redhat/self-test/data/rhel-df0cc57e057f.el7|   4 +-
 redhat/self-test/data/rhel-df0cc57e057f.fc25   |   4 +-
 redhat/self-test/data/rhel-fce15c45d3fb.el7|   4 +-
 redhat/self-test/data/rhel-fce15c45d3fb.fc25   |   4 +-
 redhat/Makefile|  38 +++--
 26 files changed, 66 insertions(+), 70 deletions(-)
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv8 0/3] redhat/Makefile: fix and clean up some of the logic

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2892#note_1746082497

https://gitlab.com/redhat/red-hat-ci-tools/kernel/cki-internal-pipelines/cki-
trusted-contributors/-/jobs/6016814624 is one example. Basically the self-test
script creates the data files to test. With this change the script calls 'make
setup-source' which now depends on 'make clean-sources' which deletes anything
created (the data files to test).
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv8 0/3] redhat/Makefile: fix and clean up some of the logic

2024-01-26 Thread via Email Bridge
From: Ondrej Mosnáček on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2892#note_1746039228

That's unfortunate :/ Can you point me to a specific pipeline that failed?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv8 0/3] redhat/Makefile: fix and clean up some of the logic

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2892#note_1745969503

This had to be reverted. It turns out that fixing this race put a new race in
which caused CKI to fail more often than not.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745521167

Indeed they are, the turned off are for other places where tools are turned
off.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745480146

now I'm totally confused  - the link above has
libperf-6.8.0-0.rc1.20240125git6098d87eaf31.15.eln134.aarch64.rpm, is that the
wrong package?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745476990

I have looked at them, and they are off for eln. As you can see from the ELN
build linked above, we do not build libperf on ELN. I don't think that CKI is
actually failing on libperf here for ELN. It is failing on cross compile
issues.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745461956

@jmflinuxtx checking Koji,
https://koji.fedoraproject.org/koji/buildinfo?buildID=2378291 is the latest
ELN kernel build and has the `libperf` subpackage. Which build did you check
that included this MR but did have the `libperf` subpackage successfully
disabled?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745452056

- for tracking: https://gitlab.com/cki-project/pipeline-
definition/-/issues/223
- move `--with libperf` to native tools stage: https://gitlab.com/cki-
project/pipeline-definition/-/merge_requests/1879

I'm still confused why this is affecting the ELN builds, rpmbuild is called
via `rpmbuild --rebuild --target ppc64le --with cross --with up --with base
--without bpftool --without selftests --without ipaclones --without perf
--without tools --without trace --without debug --without arm64_16k --without
arm64_64k --without realtime --without zfcpdump`
[[1]](https://gitlab.com/redhat/red-hat-ci-tools/kernel/cki-internal-
pipelines/cki-trusted-contributors/-/jobs/6000516388#L91) which does not
include `--with libperf` at all, @jmflinuxtx could you take a look at the
conditionals in the spec file again?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Scott Weaver (via Email Bridge)
From: Scott Weaver on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745295177

Ah. Ok so that explains why it's not in ark yet. So we can leave it off for
ELN and handle it in RHEL10 then.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745290922

@scweaver It may be, but when I emailed acme about it, he said it wasn't ready
to be turned on. I am guessing it is moving too quickly and RHEL 10 will be
enabled with a specific ABI?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745288040

I suppose so. I am guessing this is because we don't add --without libperf
which is a new option now. Realistically libperf is turned off for ELN now
though so, not sure why it is being built.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745285135

ack; so iiuc

- Fedora/Rawhide pipelines should enable native tools builds, so that the
tools subpackage building is handled the same way as for ELN, where it
_normally_ is working correctly
- somehow this MR is breaking the libperf build even for ELN, but maybe this
is because it was not enabled before at all

?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Scott Weaver (via Email Bridge)
From: Scott Weaver on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745281940

We are building the libperf package in cs9 but somehow missed porting that to
ark. So we should have it enable for ELN.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745279374

When I say "turn on tools" I mean simply enabling those subpackages in Fedora.
Most (excluding libperf) have always been enabled in ELN, but Fedora used a
separate package to build them.  Fedora is getting rid of that separate
package and wishes to build the tools subpackages as part of kernel now.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745275743

I do not. with_libperf is only set for Fedora at the moment.  If ELN/Rawhide
want to turn it on, the would need to do so with another MR.  This can be seen
in the resulting builds from koji where ELN does not build libperf packages,
but Fedora does.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745272834

@jmflinuxtx for Fedora, the CKI pipelines do not use native tools builds; when
you say "turn on tools", do you want to enable the native tools build in the
CKI pipelines, or do you expect this to work in a cross-compile setup?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745269333

@jmflinuxtx as the MR only talks about Fedora, do you expect the spec file
changes to affect ELN in any way?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745264889

@dzickusrh ^ do you have an idea why the cross compiler is not correctly
selected here after the changes even for ELN?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745263209

yes, this looks like a cross-compiler mixup
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745260387

I meant actual builds in koji.
https://koji.fedoraproject.org/koji/buildinfo?buildID=2378280 for Rawhide and
https://koji.fedoraproject.org/koji/buildinfo?buildID=2378291 for ELN. As can
be seen there, this MR does exactly what it aims to do. No build failures. CKI
is the issue here, not this MR.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745249324

at what CKI pipeline are you looking from https://gitlab.com/cki-
project/kernel-ark/-/pipelines?page=1=all=ark-latest?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745226469

There are, which makes no sense, as this MR is "include in release" and
neither Fedora or ELN builds failed yesterday with this MR included.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745213110

looking at the failing pipelines, there are some for ELN that are now failing
as well 樂:

> 00:06:29 cc1: error: bad value ‘z15’ for ‘-mtune=’ switch
00:06:29 cc1: note: valid arguments to ‘-mtune=’ switch are: nocona core2
nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell
core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client
rocketlake icelake-server cascadelake tigerlake cooperlake sapphirerapids
emeraldrapids alderlake raptorlake meteorlake graniterapids graniterapids-d
bonnell atom silvermont slm goldmont goldmont-plus tremont gracemont
sierraforest grandridge knl knm intel x86-64 eden-x2 nano nano-1000 nano-2000
nano-3000 nano-x2 eden-x4 nano-x4 lujiazui k8 k8-sse3 opteron opteron-sse3
athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3
bdver4 znver1 znver2 znver3 znver4 btver1 btver2 generic native
00:06:29 make[2]: *** [/tmp/rpmbuild/BUILD/kernel-6.8.0-0.rc1.615d30064886.13.
test/linux-6.8.0-0.rc1.615d30064886.13.test.eln.s390x/tools/build/Makefile.bui
ld:106: core.o] Error 1
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745186783

It will be needed for all other MRs after this is merged, it just was not
needed before this MR.
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [OS-BUILD PATCHv2 0/4] Add libperf packages and build kernel tools for Fedora

2024-01-26 Thread Michael Hofmann (via Email Bridge)
From: Michael Hofmann on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2907#note_1745089468

when you say "for this MR", do you mean that this is not going to be needed
for other MRs going in later, and for the Rawhide/ELN baseline builds?
--
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to kernel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue