>>> On 11.06.17 at 17:55, <osstest-ad...@xenproject.org> wrote: > branch xen-4.7-testing > xenbranch xen-4.7-testing > job build-amd64 > testid xen-build > > Tree: qemuu git://xenbits.xen.org/qemu-xen.git > Tree: xen git://xenbits.xen.org/xen.git > > *** Found and reproduced problem changeset *** > > Bug is in tree: xen git://xenbits.xen.org/xen.git > Bug introduced: 164c34dd23bc3ea8d5285752d9270627a93c91f5 > Bug not present: da743dc82adffd36ce2d71776f4ea5afbc186a15 > Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/110317/ > > > commit 164c34dd23bc3ea8d5285752d9270627a93c91f5 > Author: Jan Beulich <jbeul...@suse.com> > Date: Fri Jun 9 13:51:34 2017 +0200 > > hvmloader: avoid tests when they would clobber used memory
I appreciate the test pointing out an oversight of mine, but I wonder why debug builds are being done/run in osstest (as me having done only release builds was the reason for not spotting the issue earlier on) - this way osstest tests what likely only very few people are going to actually use in production. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
