Re: One test suite failure left on static build (after $HOME has been fixed)

[Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>]

On Dec 2,  6:20pm, Axel Beckert wrote:
}
} Leaves this test suite error:
} 
} ../../Test/C02cond.ztst: starting.
} Test ../../Test/C02cond.ztst failed: bad status 1, expected 0 from:
}   if (( EUID == 0 )); then
}     print -u$ZTST_fd 'Warning: Not testing [[ ! -r file ]] (root reads anything)'
}     [[ -r zerolength && -r unmodish ]]
}   elif [[ $OSTYPE = cygwin ]]; then
}     print -u$ZTST_fd 'Warning: Not testing [[ ! -r file ]]
}    (all files created by user may be readable)'
}    [[ -r zerolength ]]
}   else
}     [[ -r zerolength && ! -r unmodish ]]
}   fi
} Was testing: -r cond

This could be a umask issue, there's an implicit assumption that

    umask 077
    touch zerolength
    chgrp $EGID zerolength

will create a readable file, and that

    touch unmodish
    chmod 000 unmodish

will create an UNreadable file.  Unfortunately it's not possible to
tell from the test which one of (-r zerolength) or (! -r unmodish)
failed.  I have no idea why running this in the package build would
affect this, though.