[Xen-devel] [xen-unstable-smoke test] 141063: regressions - FAIL

[Xen-devel] [xen-unstable-smoke test] 141063: regressions - FAIL

[osstest service owner]

flight 141063 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/141063/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64                   6 xen-build                fail REGR. vs. 141049

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt      1 build-check(1)               blocked  n/a
 test-amd64-amd64-xl-qemuu-debianhvm-amd64  1 build-check(1)        blocked n/a
 build-amd64-libvirt           1 build-check(1)               blocked  n/a
 test-armhf-armhf-xl          13 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          14 saverestore-support-check    fail   never pass
 test-arm64-arm64-xl-xsm      13 migrate-support-check        fail   never pass
 test-arm64-arm64-xl-xsm      14 saverestore-support-check    fail   never pass

version targeted for testing:
 xen                  d2a95f1c3ef96f47840ab172278293e55c4fc430
baseline version:
 xen                  9676360b7ae3dc59ce0e0080769fbd6a1121d1be

Last test of basis   141049  2019-09-05 13:02:28 Z    0 days
Testing same since   141063  2019-09-05 19:03:42 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@citrix.com>
  Jan Beulich <jbeulich@suse.com>

jobs:
 build-arm64-xsm                                              pass    
 build-amd64                                                  fail    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          blocked 
 test-armhf-armhf-xl                                          pass    
 test-arm64-arm64-xl-xsm                                      pass    
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    blocked 
 test-amd64-amd64-libvirt                                     blocked 


------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit d2a95f1c3ef96f47840ab172278293e55c4fc430
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date:   Thu Dec 27 15:14:01 2018 +0000

    x86/AMD: Fix handling of x87 exception pointers on Fam17h hardware
    
    AMD Pre-Fam17h CPUs "optimise" {F,}X{SAVE,RSTOR} by not saving/restoring
    FOP/FIP/FDP if an x87 exception isn't pending.  This causes an information
    leak, CVE-2006-1056, and worked around by several OSes, including Xen.  AMD
    Fam17h CPUs no longer have this leak, and advertise so in a CPUID bit.
    
    Introduce the RSTR_FP_ERR_PTRS feature, as specified by AMD, and expose to all
    guests by default.  While adjusting libxl's cpuid table, add CLZERO which
    looks to have been omitted previously.
    
    Also introduce an X86_BUG bit to trigger the (F)XRSTOR workaround, and set it
    on AMD hardware where RSTR_FP_ERR_PTRS is not advertised.  Optimise the
    conditions for the workaround paths.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Reviewed-by: Jan Beulich <jbeulich@suse.com>

commit 6408ae3f80287e194cd66218f28edcec939b6fca
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date:   Thu Dec 27 15:13:55 2018 +0000

    x86/feature: Generalise synth and introduce a bug word
    
    Future changes are going to want to use cpu_bug_* in a mannor similar to
    Linux.  Introduce one bug word, and generalise the calculation of
    NCAPINTS.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Acked-by: Jan Beulich <jbeulich@suse.com>
(qemu changes not included)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [xen-unstable-smoke test] 141063: regressions - FAIL

[Jan Beulich]

On 06.09.2019 00:04, osstest service owner wrote:
> flight 141063 xen-unstable-smoke real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/141063/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  build-amd64                   6 xen-build                fail REGR. vs. 141049

Looks like this currently fails about every other time, and

/home/osstest/build.141063.build-amd64/xen/tools/firmware/../../tools/cross-install -m0644 -p xen-dir/xen-shim /home/osstest/build.141063.build-amd64/xen/dist/install/usr/local/lib/xen/boot/xen-shim
install: cannot stat 'xen-dir/xen-shim': No such file or directory
Makefile:48: recipe for target 'install' failed
make[4]: Leaving directory '/home/osstest/build.141063.build-amd64/xen/tools/firmware'
make[4]: *** [install] Error 1

suggests to me that the further amount of duct tape put in
place by a342900d48 still wasn't enough.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [xen-unstable-smoke test] 141063: regressions - FAIL

[Andrew Cooper]

On 06/09/2019 08:29, Jan Beulich wrote:
> On 06.09.2019 00:04, osstest service owner wrote:
>> flight 141063 xen-unstable-smoke real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/141063/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>>  build-amd64                   6 xen-build                fail REGR. vs. 141049
> Looks like this currently fails about every other time, and
>
> /home/osstest/build.141063.build-amd64/xen/tools/firmware/../../tools/cross-install -m0644 -p xen-dir/xen-shim /home/osstest/build.141063.build-amd64/xen/dist/install/usr/local/lib/xen/boot/xen-shim
> install: cannot stat 'xen-dir/xen-shim': No such file or directory
> Makefile:48: recipe for target 'install' failed
> make[4]: Leaving directory '/home/osstest/build.141063.build-amd64/xen/tools/firmware'
> make[4]: *** [install] Error 1
>
> suggests to me that the further amount of duct tape put in
> place by a342900d48 still wasn't enough.

Right.  I don't have time to investigate further.  I'll revert the
original patches which caused this, as doing so will most likely resolve
the intermittent pv-shim test issues.

We can revisit this at some point in the future.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [xen-unstable-smoke test] 141063: regressions - FAIL

[Jan Beulich]

On 06.09.2019 14:28, Andrew Cooper wrote:
> On 06/09/2019 08:29, Jan Beulich wrote:
>> On 06.09.2019 00:04, osstest service owner wrote:
>>> flight 141063 xen-unstable-smoke real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/141063/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>>  build-amd64                   6 xen-build                fail REGR. vs. 141049
>> Looks like this currently fails about every other time, and
>>
>> /home/osstest/build.141063.build-amd64/xen/tools/firmware/../../tools/cross-install -m0644 -p xen-dir/xen-shim /home/osstest/build.141063.build-amd64/xen/dist/install/usr/local/lib/xen/boot/xen-shim
>> install: cannot stat 'xen-dir/xen-shim': No such file or directory
>> Makefile:48: recipe for target 'install' failed
>> make[4]: Leaving directory '/home/osstest/build.141063.build-amd64/xen/tools/firmware'
>> make[4]: *** [install] Error 1
>>
>> suggests to me that the further amount of duct tape put in
>> place by a342900d48 still wasn't enough.
> 
> Right.  I don't have time to investigate further.  I'll revert the
> original patches which caused this, as doing so will most likely resolve
> the intermittent pv-shim test issues.

Hmm, why did you also revert the follow-on Makefile adjustment?
That was right, wasn't it?

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [xen-unstable-smoke test] 141063: regressions - FAIL

[Andrew Cooper]

On 06/09/2019 14:12, Jan Beulich wrote:
> On 06.09.2019 14:28, Andrew Cooper wrote:
>> On 06/09/2019 08:29, Jan Beulich wrote:
>>> On 06.09.2019 00:04, osstest service owner wrote:
>>>> flight 141063 xen-unstable-smoke real [real]
>>>> http://logs.test-lab.xenproject.org/osstest/logs/141063/
>>>>
>>>> Regressions :-(
>>>>
>>>> Tests which did not succeed and are blocking,
>>>> including tests which could not be run:
>>>>  build-amd64                   6 xen-build                fail REGR. vs. 141049
>>> Looks like this currently fails about every other time, and
>>>
>>> /home/osstest/build.141063.build-amd64/xen/tools/firmware/../../tools/cross-install -m0644 -p xen-dir/xen-shim /home/osstest/build.141063.build-amd64/xen/dist/install/usr/local/lib/xen/boot/xen-shim
>>> install: cannot stat 'xen-dir/xen-shim': No such file or directory
>>> Makefile:48: recipe for target 'install' failed
>>> make[4]: Leaving directory '/home/osstest/build.141063.build-amd64/xen/tools/firmware'
>>> make[4]: *** [install] Error 1
>>>
>>> suggests to me that the further amount of duct tape put in
>>> place by a342900d48 still wasn't enough.
>> Right.  I don't have time to investigate further.  I'll revert the
>> original patches which caused this, as doing so will most likely resolve
>> the intermittent pv-shim test issues.
> Hmm, why did you also revert the follow-on Makefile adjustment?
> That was right, wasn't it?

c/s 32b1d62887 alone completely broke a parallel build, and was fixed by
c/s 060f4eee0f

To revert 32b1d62887, I needed to take both out.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel