From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 18 Jun 2019 09:45:23 +0200 Subject: [Buildroot] [PATCH v5 1/4] autobuild-run: move creation of result directory to run_instance() In-Reply-To: <7971482d-2efd-4bb0-d105-56746c5039d4@mind.be> References: <20190617093456.6110-1-itsatharva@gmail.com> <20190617200609.4276a61a@windsurf> <20190618091403.582cd799@windsurf> <7971482d-2efd-4bb0-d105-56746c5039d4@mind.be> Message-ID: <20190618094523.391e02c2@windsurf> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Tue, 18 Jun 2019 09:34:54 +0200 Arnout Vandecappelle wrote: > > - The output in build-end.log does not show any indication that the > > overall build failure is caused by the build being non-reproducible. > > What build-end.log shows is just a "make legal-info" that ends up > > successfully, which is very confusing since the build status is > > "failure", but the log doesn't show any sort of failure. > > > > I think the check_reproducibility() function should at least show > > something in the build log. > > You can see it through the existence of the "reproducible_results" file. Yes, I know, I have read the autobuild-run patches before applying them :-) Still the immediate thing you click on when you see a failure is the build log, and when there's no apparent failure it's confusing. > But it would indeed be a good idea to use that file as the build log instead of > the normal log. Correct. > > - The reason of the failures, visible at > > http://autobuild.buildroot.net/?submitter=Thomas+Petazzoni+(Bootlin+server)&status=NOK > > are just "unknown". We really want to have a better "reason". I > > guess the easiest here would be to move the calculation of the > > "reason" into autobuild-run instead of having it server-side, as > > Arnout has suggested in a separate discussion yesterday. > > Ack, that was the plan. The "unkown" is exactly what we expected. I think it's > OK for a few weeks. Yes, it is OK for now, but it would be good to work on fixing this. Best regards, Thomas -- Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com