[opensuse-buildservice] osc bl downloads wrong log file
Hi, This gives me a logfile from yesterday: $ cd rudi_m:ul-all/ul-plain $ osc bl openSUSE_13.1_ports ppc But it was rebuilt today a few times already. I ve got the right log when I was watching the log before the build was finished. But after it has been finished I get an old one. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Ruediger Meier <sweet_f_a@gmx.de> writes:
This gives me a logfile from yesterday: $ cd rudi_m:ul-all/ul-plain $ osc bl openSUSE_13.1_ports ppc
But it was rebuilt today a few times already.
This is by design. $ osc jobhist -l1 home:rudi_m:ul-all/ul-plain openSUSE_13.1_ports ppc time package reason code build time worker 2015-04-15 08:09:57 CET ul-plain meta change unchanged 3m 28s build91:6 ^^^^^^^^^ $ osc rblt home:rudi_m:ul-all/ul-plain openSUSE_13.1_ports ppc | tail -10 Retried build at Tue Apr 14 18:09:24 2015 returned same result, skipped Retried build at Tue Apr 14 18:25:32 2015 returned same result, skipped Retried build at Tue Apr 14 18:51:56 2015 returned same result, skipped Retried build at Tue Apr 14 21:19:48 2015 returned same result, skipped Retried build at Tue Apr 14 22:36:25 2015 returned same result, skipped Retried build at Wed Apr 15 09:05:40 2015 returned same result, skipped Retried build at Wed Apr 15 09:24:23 2015 returned same result, skipped Retried build at Wed Apr 15 09:29:13 2015 returned same result, skipped Retried build at Wed Apr 15 10:09:57 2015 returned same result, skipped Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wednesday 15 April 2015, Andreas Schwab wrote:
Ruediger Meier <sweet_f_a@gmx.de> writes:
This gives me a logfile from yesterday: $ cd rudi_m:ul-all/ul-plain $ osc bl openSUSE_13.1_ports ppc
But it was rebuilt today a few times already.
This is by design.
I see, but this is very confusing when you just want to watch the log to see whether the expected BuildRequires were installed or whether the tests were running or whatever. Yesterday I have updated certain "BuildRequires" and there is no way to check whether the right version was actually used for build.
$ osc rblt home:rudi_m:ul-all/ul-plain openSUSE_13.1_ports ppc | tail -10
Retried build at Tue Apr 14 18:09:24 2015 returned same result, skipped:
I would say the last log should be kept rather than the first one. Then the only confusing thing would be that the package is older than the log. BTW there is a bug with these "skipped" lines. https://bugzilla.suse.com/show_bug.cgi?id=927225 cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 15. April 2015, 12:12:32 wrote Ruediger Meier:
On Wednesday 15 April 2015, Andreas Schwab wrote:
Ruediger Meier <sweet_f_a@gmx.de> writes:
This gives me a logfile from yesterday: $ cd rudi_m:ul-all/ul-plain $ osc bl openSUSE_13.1_ports ppc
But it was rebuilt today a few times already.
This is by design.
I see, but this is very confusing when you just want to watch the log to see whether the expected BuildRequires were installed or whether the tests were running or whatever.
Yesterday I have updated certain "BuildRequires" and there is no way to check whether the right version was actually used for build.
use "osc buildinfo .... | grep $your_package" to find out which one gets used.
$ osc rblt home:rudi_m:ul-all/ul-plain openSUSE_13.1_ports ppc | tail -10
Retried build at Tue Apr 14 18:09:24 2015 returned same result, skipped:
I would say the last log should be kept rather than the first one. Then the only confusing thing would be that the package is older than the log.
no, the log file which belongs to the build rpms must be kept IMHO -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wednesday 15 April 2015, Adrian Schröter wrote:
On Mittwoch, 15. April 2015, 12:12:32 wrote Ruediger Meier:
On Wednesday 15 April 2015, Andreas Schwab wrote:
Ruediger Meier <sweet_f_a@gmx.de> writes:
This gives me a logfile from yesterday: $ cd rudi_m:ul-all/ul-plain $ osc bl openSUSE_13.1_ports ppc
But it was rebuilt today a few times already.
This is by design.
I see, but this is very confusing when you just want to watch the log to see whether the expected BuildRequires were installed or whether the tests were running or whatever.
Yesterday I have updated certain "BuildRequires" and there is no way to check whether the right version was actually used for build.
use "osc buildinfo .... | grep $your_package" to find out which one gets used.
Hm, this is the buildinfo which would be used for the next build. I still can't proove that my package has already survived a build with this config.
$ osc rblt home:rudi_m:ul-all/ul-plain openSUSE_13.1_ports ppc | tail -10
Retried build at Tue Apr 14 18:09:24 2015 returned same result, skipped:
I would say the last log should be kept rather than the first one. Then the only confusing thing would be that the package is older than the log.
no, the log file which belongs to the build rpms must be kept IMHO
This depends on the point of view. For me as developer the last one is the wanted one in 99% of all cases. Actually I find that ALL logs should be kept. OBS is wasting so many time to rebuild packages ... and then we even throw away all these nice logs. It's a pity. For me it would have much value to have full buildlog history. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 15. April 2015, 12:34:49 wrote Ruediger Meier:
On Wednesday 15 April 2015, Adrian Schröter wrote:
On Mittwoch, 15. April 2015, 12:12:32 wrote Ruediger Meier:
On Wednesday 15 April 2015, Andreas Schwab wrote:
Ruediger Meier <sweet_f_a@gmx.de> writes:
This gives me a logfile from yesterday: $ cd rudi_m:ul-all/ul-plain $ osc bl openSUSE_13.1_ports ppc
But it was rebuilt today a few times already.
This is by design.
I see, but this is very confusing when you just want to watch the log to see whether the expected BuildRequires were installed or whether the tests were running or whatever.
Yesterday I have updated certain "BuildRequires" and there is no way to check whether the right version was actually used for build.
use "osc buildinfo .... | grep $your_package" to find out which one gets used.
Hm, this is the buildinfo which would be used for the next build. I still can't proove that my package has already survived a build with this config.
then download the _buildenv file which is stored along with the builds. It is used to reproduce the exact same build environment (if binaries are still available)
$ osc rblt home:rudi_m:ul-all/ul-plain openSUSE_13.1_ports ppc | tail -10
Retried build at Tue Apr 14 18:09:24 2015 returned same result, skipped:
I would say the last log should be kept rather than the first one. Then the only confusing thing would be that the package is older than the log.
no, the log file which belongs to the build rpms must be kept IMHO
This depends on the point of view. For me as developer the last one is the wanted one in 99% of all cases.
Actually I find that ALL logs should be kept. OBS is wasting so many time to rebuild packages ... and then we even throw away all these nice logs. It's a pity. For me it would have much value to have full buildlog history.
why do you think that the build log would differ much when the result is actually the same? -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wednesday 15 April 2015, Adrian Schröter wrote:
On Mittwoch, 15. April 2015, 12:34:49 wrote Ruediger Meier:
On Wednesday 15 April 2015, Adrian Schröter wrote:
On Mittwoch, 15. April 2015, 12:12:32 wrote Ruediger Meier:
On Wednesday 15 April 2015, Andreas Schwab wrote:
Ruediger Meier <sweet_f_a@gmx.de> writes:
This gives me a logfile from yesterday: $ cd rudi_m:ul-all/ul-plain $ osc bl openSUSE_13.1_ports ppc
But it was rebuilt today a few times already.
This is by design.
I see, but this is very confusing when you just want to watch the log to see whether the expected BuildRequires were installed or whether the tests were running or whatever.
Yesterday I have updated certain "BuildRequires" and there is no way to check whether the right version was actually used for build.
use "osc buildinfo .... | grep $your_package" to find out which one gets used.
Hm, this is the buildinfo which would be used for the next build. I still can't proove that my package has already survived a build with this config.
then download the _buildenv file which is stored along with the builds.
And this is really from the last build?
It is used to reproduce the exact same build environment (if binaries are still available)
$ osc rblt home:rudi_m:ul-all/ul-plain openSUSE_13.1_ports ppc | tail -10
Retried build at Tue Apr 14 18:09:24 2015 returned same result, skipped:
I would say the last log should be kept rather than the first one. Then the only confusing thing would be that the package is older than the log.
no, the log file which belongs to the build rpms must be kept IMHO
This depends on the point of view. For me as developer the last one is the wanted one in 99% of all cases.
Actually I find that ALL logs should be kept. OBS is wasting so many time to rebuild packages ... and then we even throw away all these nice logs. It's a pity. For me it would have much value to have full buildlog history.
why do you think that the build log would differ much when the result is actually the same?
For example because I have an advanced %check section which runs different tests dependent on what the build host supports. It always run different tests on xen, kvm or whatever machines. Sometimes loading kernel modules is supported, somethimes not, etc. Once a check fails I always have the same questions: Was this a random/racy fail? Was this check ever successful on a similar build host. What is the difference between the last failed and the last successful build(s). I don't understand how could you find the benefit of full buildlog history questionable. Look how nice this looks for other build machineries which I'm using: https://travis-ci.org/rudimeier/util-linux/builds https://drone.io/github.com/rudimeier/util-linux cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 15. April 2015, 13:13:32 wrote Ruediger Meier:
On Wednesday 15 April 2015, Adrian Schröter wrote:
On Mittwoch, 15. April 2015, 12:34:49 wrote Ruediger Meier:
On Wednesday 15 April 2015, Adrian Schröter wrote:
On Mittwoch, 15. April 2015, 12:12:32 wrote Ruediger Meier:
On Wednesday 15 April 2015, Andreas Schwab wrote:
Ruediger Meier <sweet_f_a@gmx.de> writes: > This gives me a logfile from yesterday: > $ cd rudi_m:ul-all/ul-plain > $ osc bl openSUSE_13.1_ports ppc > > But it was rebuilt today a few times already.
This is by design.
I see, but this is very confusing when you just want to watch the log to see whether the expected BuildRequires were installed or whether the tests were running or whatever.
Yesterday I have updated certain "BuildRequires" and there is no way to check whether the right version was actually used for build.
use "osc buildinfo .... | grep $your_package" to find out which one gets used.
Hm, this is the buildinfo which would be used for the next build. I still can't proove that my package has already survived a build with this config.
then download the _buildenv file which is stored along with the builds.
And this is really from the last build?
no, but what do you want here? Either the description of the available build which matches to binary and logfile? or what would happen with current config? Storing any random in-between situations do not make any sense to me. ...
why do you think that the build log would differ much when the result is actually the same?
For example because I have an advanced %check section which runs different tests dependent on what the build host supports. It always run different tests on xen, kvm or whatever machines. Sometimes loading kernel modules is supported, somethimes not, etc.
Once a check fails I always have the same questions:
Was this a random/racy fail? Was this check ever successful on a similar build host. What is the difference between the last failed and the last successful build(s).
okay, I see.
I don't understand how could you find the benefit of full buildlog history questionable.
well, I find it questionable to have a different build log not matching to the build result. If you want to introduce an entire history for build results, that would be fine. But that would be a new OBS feature.
Look how nice this looks for other build machineries which I'm using: https://travis-ci.org/rudimeier/util-linux/builds
has different problems, the build environment is permanently changing there and you can not reproduce it.... we use it also :)
https://drone.io/github.com/rudimeier/util-linux
cu, Rudi
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wednesday 15 April 2015, Adrian Schröter wrote:
On Mittwoch, 15. April 2015, 13:13:32 wrote Ruediger Meier:
why do you think that the build log would differ much when the result is actually the same?
For example because I have an advanced %check section which runs different tests dependent on what the build host supports. It always run different tests on xen, kvm or whatever machines. Sometimes loading kernel modules is supported, somethimes not, etc.
Once a check fails I always have the same questions:
Was this a random/racy fail? Was this check ever successful on a similar build host. What is the difference between the last failed and the last successful build(s).
okay, I see.
I don't understand how could you find the benefit of full buildlog history questionable.
well, I find it questionable to have a different build log not matching to the build result.
The current log is a log which gave us the same result, so what? The current one would be more easily to reproduce because the chance that similar build hosts and the used packages still exist is much higher. "osc bl --last" is made to compare the last success with the current failure. Why bothering the packager with an outdated unreproducible buildlog? BTW really confusing is that you get different logfiles in "follow mode" and "download mode". This mode is automatically switched!
If you want to introduce an entire history for build results, that would be fine. But that would be a new OBS feature.
I will see if I could add that.
Look how nice this looks for other build machineries which I'm using: https://travis-ci.org/rudimeier/util-linux/builds
has different problems, the build environment is permanently changing there and you can not reproduce it.... we use it also :)
I know that that there are pro and cons about any existing ci systems that's why I'm using many of them incl. OBS. Regarding build env I find travis much more stable than OBS. For example the running kernel, CPU etc. stays the same for long periods. For example on OBS you may get a RHEL_4 with kernel 3.16! nowadays. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 15. April 2015, 15:22:15 wrote Ruediger Meier:
On Wednesday 15 April 2015, Adrian Schröter wrote:
On Mittwoch, 15. April 2015, 13:13:32 wrote Ruediger Meier: ..
why do you think that the build log would differ much when the result is actually the same?
For example because I have an advanced %check section which runs different tests dependent on what the build host supports. It always run different tests on xen, kvm or whatever machines. Sometimes loading kernel modules is supported, somethimes not, etc.
Once a check fails I always have the same questions:
Was this a random/racy fail? Was this check ever successful on a similar build host. What is the difference between the last failed and the last successful build(s).
okay, I see.
I don't understand how could you find the benefit of full buildlog history questionable.
well, I find it questionable to have a different build log not matching to the build result.
The current log is a log which gave us the same result, so what? The current one would be more easily to reproduce because the chance that similar build hosts and the used packages still exist is much higher.
"osc bl --last" is made to compare the last success with the current failure. Why bothering the packager with an outdated unreproducible buildlog?
this is actually the only reproducable build log. You can use the _buildenv data stored along with the rpms. Okay, this is only true when the used repos do not remove the build binaries, so this works only reliable against openSUSE:*:Update projects.
BTW really confusing is that you get different logfiles in "follow mode" and "download mode". This mode is automatically switched!
feel free to make a github issue for that.
If you want to introduce an entire history for build results, that would be fine. But that would be a new OBS feature.
I will see if I could add that.
Any concept how to organise files on disk and how to access via api should be prepared first. Just to avoid that you write code which will not be merged ....
Look how nice this looks for other build machineries which I'm using: https://travis-ci.org/rudimeier/util-linux/builds
has different problems, the build environment is permanently changing there and you can not reproduce it.... we use it also :)
I know that that there are pro and cons about any existing ci systems that's why I'm using many of them incl. OBS.
Regarding build env I find travis much more stable than OBS. For example the running kernel, CPU etc. stays the same for long periods.
and then it changes to another OS and you can do anything against it;)
For example on OBS you may get a RHEL_4 with kernel 3.16! nowadays.
right, this is why we introduce the support for own kernels in *SUSE distributions meanwhile. If someone takes care to build the kernel-obs-build package pendant for Fedora/RHEL/... I can import and activate them there as well. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wednesday 2015-04-15 12:13, Adrian Schröter wrote:
$ osc rblt home:rudi_m:ul-all/ul-plain openSUSE_13.1_ports ppc | tail -10
Retried build at Tue Apr 14 18:09:24 2015 returned same result, skipped:
I would say the last log should be kept rather than the first one. Then the only confusing thing would be that the package is older than the log.
no, the log file which belongs to the build rpms must be kept IMHO
no, both logs should be kept :) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Adrian Schröter -
Andreas Schwab -
Jan Engelhardt -
Ruediger Meier