Visit https://build.opensuse.org/package/live_build_log/network:osmocom:nightly/os...
Package network:osmocom:nightly/osmo-trx failed to build in xUbuntu_16.04/x86_64
Check out the package for editing: osc checkout network:osmocom:nightly osmo-trx
Last lines of build log: [ 408s] #define HAVE_SYS_TYPES_H 1 [ 408s] #define HAVE_SYS_STAT_H 1 [ 408s] #define HAVE_STDLIB_H 1 [ 408s] #define HAVE_STRING_H 1 [ 408s] #define HAVE_MEMORY_H 1 [ 408s] #define HAVE_STRINGS_H 1 [ 408s] #define HAVE_INTTYPES_H 1 [ 408s] #define HAVE_STDINT_H 1 [ 408s] #define HAVE_UNISTD_H 1 [ 408s] #define HAVE_DLFCN_H 1 [ 408s] #define LT_OBJDIR ".libs/" [ 408s] #define STDC_HEADERS 1 [ 408s] #define HAVE_BYTESWAP_H 1 [ 408s] #define TIME_WITH_SYS_TIME 1 [ 408s] [ 408s] configure: exit 1 [ 408s] dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking returned exit code 1 [ 408s] debian/rules:6: recipe for target 'build' failed [ 408s] make: *** [build] Error 255 [ 408s] dpkg-buildpackage: error: debian/rules build gave error exit status 2 [ 408s] [ 408s] cloud116 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 20:00:47 UTC 2017. [ 408s] [ 408s] ### VM INTERACTION START ### [ 411s] [ 364.791340] reboot: Power down [ 412s] ### VM INTERACTION END ### [ 412s] [ 412s] cloud116 failed "build osmo-trx_0.1.9.20170117.dsc" at Tue Jan 17 20:00:52 UTC 2017. [ 412s]
Dear all,
On Tue, Jan 17, 2017 at 08:01:06PM +0000, OBS Notification wrote:
Package network:osmocom:nightly/osmo-trx failed to build in xUbuntu_16.04/x86_64
should we keep the build notifications here on this list (which probably would mean more build failures right now than human discussion), or should I send them to the redmine or other list? Even a new list?
I am somewhat undecided. Having the posts here means that the social pressure increases to fix those issues *fast*. However, if that's not possible for some reason, we get continued mails...What do you think?
Regards, Harald
There is no social pressure if no one is reading the list, because it's spammed by a bot..
I believe it's too many emails at the email rate the build system is currently sending.
I'd vote to either send those mail somewhere else or to find a way to send a single email for all projects and only when a breakage starts (i.e. not for every commit)
Please excuse typos. Written with a touchscreen keyboard.
-- Regards, Alexander Chemeris CEO Fairwaves, Inc. https://fairwaves.co
On Jan 18, 2017 10:15 AM, "Harald Welte" laforge@gnumonks.org wrote:
Dear all,
On Tue, Jan 17, 2017 at 08:01:06PM +0000, OBS Notification wrote:
Package network:osmocom:nightly/osmo-trx failed to build in
xUbuntu_16.04/x86_64
should we keep the build notifications here on this list (which probably would mean more build failures right now than human discussion), or should I send them to the redmine or other list? Even a new list?
I am somewhat undecided. Having the posts here means that the social pressure increases to fix those issues *fast*. However, if that's not possible for some reason, we get continued mails...What do you think?
Regards, Harald
--
- Harald Welte laforge@gnumonks.org
http://laforge.gnumonks.org/
================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
Hi.
One of the options would be to disable builds for packages which are known to be problematic. Also, huge chunk of the failures comes from 14.04 repo - are we really interesting in supporting this?
Other than that: - build failures for osmo-stp should be fixed once gerrit #1616 is merged - build failures for osmo-bts should be fixed once gerrit #1621 is merged - OpenBSC build failure for 16.04 i586 seems to be related to libdbi issue (will be fixed once vlr work is merged, shall we disable it until than?) - libosmo-netif build failure for 16.10 x86_64 puzzles me as this is unreproducible locally or in jenkins: is there any way to extract build artifacts from OBS to look into testsuite.log?
On Wed, Jan 18, 2017 at 11:02:02AM +0100, Max wrote:
One of the options would be to disable builds for packages which are known to be problematic.
They still need to be resolved.
Also, huge chunk of the failures comes from 14.04 repo - are we really interesting in supporting this?
no, simply remove it.
On 18 Jan 2017, at 07:59, Harald Welte laforge@gnumonks.org wrote:
Dear all,
On Tue, Jan 17, 2017 at 08:01:06PM +0000, OBS Notification wrote:
Package network:osmocom:nightly/osmo-trx failed to build in xUbuntu_16.04/x86_64
should we keep the build notifications here on this list (which probably would mean more build failures right now than human discussion), or should I send them to the redmine or other list? Even a new list?
I am somewhat undecided. Having the posts here means that the social pressure increases to fix those issues *fast*. However, if that's not possible for some reason, we get continued mails...What do you think?
Probably not to this mailinglist. I was looking into using osc pr -c and creating a jenkins job that will execute/check it. Then we would be edge triggered but "race" a bit with when will the build complete.
Roughly...run once every couple of hours * Use osc pr -c and check CSV file if everything is complete * Check failed or unresolvable
Configure job to send mail on first failure (and when fixed)?
what do you think?
holger
I would put it either on our high-noise gerrit-log@ list, or if that's too cross-topic create a new one. I personally would subscribe. With a separate list, filtering is easy.
Social pressure could be exerted by me or someone else subscribed posting to openbsc@ that it's still not fixed or something like that.
~N
On Wed, Jan 18, 2017 at 07:59:40AM +0100, Harald Welte wrote:
Dear all,
On Tue, Jan 17, 2017 at 08:01:06PM +0000, OBS Notification wrote:
Package network:osmocom:nightly/osmo-trx failed to build in xUbuntu_16.04/x86_64
should we keep the build notifications here on this list (which probably would mean more build failures right now than human discussion), or should I send them to the redmine or other list? Even a new list?
I am somewhat undecided. Having the posts here means that the social pressure increases to fix those issues *fast*. However, if that's not possible for some reason, we get continued mails...What do you think?
Regards, Harald
--
- Harald Welte laforge@gnumonks.org http://laforge.gnumonks.org/
============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)
On Wed, Jan 18, 2017 at 07:59:40AM +0100, Harald Welte wrote:
should we keep the build notifications here on this list (which probably would mean more build failures right now than human discussion), or should I send them to the redmine or other list? Even a new list?
I've now re-configured the build failures to go to gerrit-log@lists.osmocom.org instead.
BTW, my reply to this email resulted in a ticket being created automatically at opensuse.org alerting the admins there, without my intention. That's because the mail recipients included the address
OBS Notification admin@opensuse.org
Keep an eye out in the future to exclude this mail address if you come across it, or all of us will create OBS tickets to their admins' annoyance...
~N
Hi.
That's odd: - according to https://projects.osmocom.org/projects/cellular-infrastructure/wiki/Nightly_B... source packages made once a day by jenkins - according to https://build.opensuse.org/project/show/network:osmocom:nightly packages have not been updated in 3 days
Because of that latest fixes for packaging have already landed in master but have not affected the OBS yet.
Is there something wrong with jenkins? Or, contrary to what wiki says, some manual steps required?
On Mon, Jan 23, 2017 at 01:28:32PM +0100, Max wrote:
Is there something wrong with jenkins?
https://jenkins.osmocom.org/jenkins/job/Osmocom_nightly_packages/
As you could have seen youself, the job has been red for the past 3 runs.
[[[ + gbp buildpackage -S -uc -us --git-export-dir=/home/osmocom-build/jenkins/workspace/Osmocom_nightly_packages/osmo-bts/../data gbp:error: Can't determine upstream version from changelog Build step 'Execute shell' marked build as failure Finished: FAILURE ]]]
It comes from your commit 70b71507c27f8967b0aa31cad0b3070c6780f3b4 deb: use gsm_data_shared.* from openbsc-dev
because you changed the debian/source/format to "quilt". I saw that change and thought you knew what you were doing, because I certainly don't know what that does :)
https://gerrit.osmocom.org/#/c/1636/1/debian/source/format
If I change it back to 'native', gbp can again figure out the version number on my machine. Do you need that quilt thing for something else??
Next time maybe try to run gbp buildpackage on your machine before submitting a debian/ patch?
...should we add that to the gerrit build?
~N
Yes, it's necessary for Debian-specific patches to be applied automatically. I'll have a look into how to make gbp behave in this case. I've used dpkg-buildpackage locally and it worked well.
On 23.01.2017 21:14, Neels Hofmeyr wrote:
If I change it back to 'native', gbp can again figure out the version number on my machine. Do you need that quilt thing for something else??
-
Alexander Chemeris -
Harald Welte -
Holger Freyther -
Max -
Neels Hofmeyr -
OBS Notification