| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
It was silently failing when ifconfig is not installed, and we
already depend on ip in that command.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If parsing the spec causes something to be printed, it ends up in stdout
together with the result of the query:
rpmspec -q --qf %{NVR}.src.rpm --srpm SPECS/golang-x-vuln.spec 2>/dev/null
Setting %{thisgofilelist} = devel.file-list
Setting %{currentgoipath} = golang.org/x/vuln
Setting %{currentgosourcedir} = /home/pterjan/rpmbuild/BUILD/golang-x-vuln-1.1.4-build/vuln-1.1.4
Setting %{currentgofilelist} = devel.file-list
Setting %{currentversion} = 1.1.4
Setting %{currentgoldflags} = -X golang.org/x/vuln/version=1.1.4
golang-x-vuln-1.1.4-1.mga10.src.rpm
Work around this by keeping only the last line
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
%{?_isa} macro on armv7hl
|
| |
|
|
|
|
|
|
|
|
|
| |
This unifies logdir name too as some logs were in different
directories, and uses the same behaviour for all srpms.
Building a src.rpm with svn revision like "@42:foo-42-1.src.rpm"
used to use a directory "foo-42-1" while building "foo-42-1.src.rpm"
would use the directory "foo-42-1.src.rpm". In order to not break
Mageia's build system and UI the first one was picked and they
will now both use "foo-42-1".
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Usage:
$ cancel_build 20231231211004.pterjan.duvel.1487312
*: [cancel_build] check uploads tree
I: [cancel_build] check dir: /var/lib/schedbot/uploads/done
I: [cancel_build] check dir: /var/lib/schedbot/uploads/todo
I: [cancel_build] Failing 20231231211004.pterjan.duvel.1487312 and cleaning up done architectures
I: [cancel_build] Killing process 1146007 on rabbit2 (building for arch "i586")
I: [cancel_build] Killing process 2204767 on ecosse0 (building for arch "x86_64")
I: [cancel_build] Killing process 3092253 on ociaa1-a (building for arch "aarch64")
I: [cancel_build] Killing process 3092165 on ociaa1-b (building for arch "armv7hl")
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
A new config option (backoff_delays) was added to ulri.
It contains a list of delays (in seconds) between retries and default to
[5*60, 30*60, 60*60, 120*60] (5m, 30m, 1h, 2h).
When reaching the end of the list, we fail permanently.
To never retry, set it to [].
To retry forever, set it to undef.
|
| |
|
|
|
| |
Currently we when building a tmpdir, making a tar of it, deleting it
and then untar into the target.
|
| |
|
|
|
| |
We may still use the wrong chroot but at least the .tar shoudl not be
corrupted.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
An error was not set when failing in %prep or %generate_buildrequires
while trying to generate dynamic buildrequires. This causes iurt to
assume it's a retriable install_deps_failure.
Set the failure to build_failure when what fails is rpmbuild -br
rather than installing the packages.
|
| | |
|
| | |
|
| |
|
|
|
| |
The main scripts (iurt/ulri/emi) were not covered by tests, only
the libs.
|
| | |
|
| |
|
|
| |
Currently we always get install_deps_failure which is retriable.
|
| | |
|
| |
|
|
|
| |
Do not remove lock file and mark build as done until we copied all
the files.
|
| | |
|
| |
|
|
| |
See https://fedoraproject.org/wiki/Changes/DynamicBuildRequires
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
sout("foo || bar") was fetching the output of:
ssh -x user@host foo || bar
instead of:
ssh -x user@host "foo || bar"
This means we were considering the remote command to have failed
when ssh to the machine to check status was failing.
|
| |
|
|
|
|
|
| |
The call wasn't matching the function signature thus breaking cleaning
chroots.
Bug introducted in commit 69e74732d254c75adc20afc25a8729ca568be832
I wonder why nobody saw it before ??
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This can be used for example by
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This will fix packages not marked as noarch but having only
noarch subpackages, even if we still end up wasting resources.
The only risk I see is if the noarch packages get built on all
mandatory architectures first, upload starts and other architectures
complete in hte middle, however this should not modify the files being
uploaded, we use a temporary file and rename so it should be fine.
|
| |
|
|
|
| |
Some packages use macros for Name and those can change based on
the distro version.
|
| | |
|
| | |
|
| |
|
|
| |
We were using --target <arch of the chroot used to build>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|