[freebsd-master test] 124732: trouble: pass/running

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

flight 124732 freebsd-master running [real]
http://logs.test-lab.xenproject.org/osstest/logs/124732/

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-freebsd-again     4 syslog-server                running
 build-amd64-freebsd-again     7 freebsd-build                running

version targeted for testing:
 freebsd              cc43f1dd4feb9a46ac52d130db311feedbc2b299
baseline version:
 freebsd              120832ac318f335dedfba859043b74375bba5e51

Last test of basis   124724  2018-06-26 07:42:35 Z    0 days
Testing same since                          (not found)         0 attempts

------------------------------------------------------------
People who touched revisions under test:
  delphij <delphij@xxxxxxxxxxx>
  kevans <kevans@xxxxxxxxxxx>
  markj <markj@xxxxxxxxxxx>

jobs:
 build-amd64-freebsd-again                                    running 
 build-amd64-freebsd                                          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


Not pushing.

------------------------------------------------------------
commit cc43f1dd4feb9a46ac52d130db311feedbc2b299
Author: markj <markj@xxxxxxxxxxx>
Date:   Tue Jun 26 09:30:14 2018 +0000

    Add missing MLINK.
    
    MFC after:      3 days

commit 67f26b0663100e19ab25466d9404466ef2501b99
Author: delphij <delphij@xxxxxxxxxxx>
Date:   Tue Jun 26 06:18:59 2018 +0000

    Fix division by zero when reading boot block by postponing division
    until it is necessary and after we validated bytes per sector is non-
    zero.
    
    Obtained from:  Android 
https://android-review.googlesource.com/c/platform/external/fsck_msdos/+/36362
    MFC after:      2 weeks

commit f6dc513a0546b302a2d05b8089ea94c34671e950
Author: kevans <kevans@xxxxxxxxxxx>
Date:   Tue Jun 26 04:06:49 2018 +0000

    config(8): part of patch disappeared, don't close ifp at the end

commit 0d906f9fa4ceeb8a9b266d9ae3b387b25900a5f2
Author: kevans <kevans@xxxxxxxxxxx>
Date:   Tue Jun 26 04:02:25 2018 +0000

    config(8): Flip the order of concatenation for `hints` and `env`
    
    As previously noted, kernel's processing of these means that the first
    appearance of a hint/variable wins. Flipping the order of concatenation
    means that later variables override earlier variables, as expected when one
    does:
    
    hints x
    hints y
    
    Where perhaps x is:
    
    hint.aw_sid.0.disable=1
    
    and y is:
    
    hint.aw_sid.0.disable=0
    
    The expectation would be that a later appearing variable would override an
    earlier appearing variable, such as with `device`/`nodevice`, device.hints,
    and other similarly structured data files.

commit b77bd81b376dd4e8dda43a3f092846e256e44b98
Author: kevans <kevans@xxxxxxxxxxx>
Date:   Tue Jun 26 03:56:10 2018 +0000

    config(8): Make 'env' files consistent with other file-accepting options
    
    Previously, only one 'env' file could be specified. Later 'env' directives
    would overwrite earlier 'env' directives. This is inconsistent with every
    other file-accepting directives which process files in order, including
    hints.
    
    A caveat applies to both hints and env that isn't mentioned: they're
    concatenated in the order of appearance, so they're not actually applied in
    the way one might think by supplying:
    
    hints x
    hints y
    
    Hints in x will take precedence over same-name hints in y due to how
    the kernel processes them, stopping at the first line that matches the hint
    we're searching for. Future work will flip the order of concatenation so
    that later files may still properly override earlier files.
    
    In practice, this likely doesn't matter at all due to the nature of the
    beast.

_______________________________________________
osstest-output mailing list
osstest-output@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/osstest-output