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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 xen                  24470b99c1671dca531c2cf5747eda2f8892ecbc
baseline version:
 xen                  3f491d6873be9caa77f02ad8d98f174f0152b819

Last test of basis   119171  2018-02-14 09:35:07 Z    4 days
Testing same since   119558  2018-02-18 09:47:32 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Acked-by: Razvan Cojocaru <rcojoc...@bitdefender.com>
  Alexandru Isaila <aisa...@bitdefender.com>
  Andrew Cooper <andrew.coop...@citrix.com>
  Jan Beulich <jbeul...@suse.com>
  Julien Grall <julien.gr...@arm.com>
  Razvan Cojocaru <rcojoc...@bitdefender.com>
  Roger Pau Monne <roger....@citrix.com>
  Roger Pau Monné <roger....@citrix.com>
  Ross Lagerwall <ross.lagerw...@citrix.com>
  Stefano Stabellini <sstabell...@kernel.org>
  Tamas K Lengyel <ta...@tklengyel.com>
  Uwe Dannowski <u...@amazon.de>

jobs:
 coverity-amd64                                               pass    


------------------------------------------------------------
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


Pushing revision :

To xenbits.xen.org:/home/xen/git/xen.git
   3f491d6873..24470b99c1  24470b99c1671dca531c2cf5747eda2f8892ecbc -> 
coverity-tested/smoke

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

Reply via email to