When the user has the setgid bit is set on the parent directory of
the build directory, the setgid bit will be propagated throughout the
build tree. Most tests do not care about permissions as long as they
can read and write the files the need. The CPack tests, however, validate
that permissions match an expected set, and fail with the setgid bit set.
Explicitly set permissions on directories created in the CPackTestHelpers
to clear the setgid bit.
Signed-off-by: william.r.dieter <william.r.dieter@intel.com>
ac6a4d4884 ExternalProject: Improve robustness of update step
17c4c8b92b Tests: Prevent the noisy CMP0114 warnings in ExternalProjectUpdate test
1cb65e680d ExternalProject: Prevent the noisy detached head messages on checkout
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5389
9b5fd04905 Tests: Disable MFC test for IntelLLVM due to #18311ccdf7c0005 Tests: Skip VSGNUFortran test for ifx.
ddaf412dd0 Tests: Skip per file PDBs in PDBDirectoryAndName for IntelLLVM
a619b32768 Tests: Update RunCMake.GenerateExportHeader for IntelLLVM
661b04d6a6 Tests: Skip old PrecompiledHeader test on IntelLLVM
01b1e9c40d Tests: Update CompileFeatures test for IntelLLVM
f26f10184f Tests: Update Module.WriteCompilerDetectionHeader for IntelLLVM
3ceb364b1c Tests: Update RunCMake.FileAPI for IntelLLVM
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5594
Refactor the update logic to make it easier to follow. The following
fixes/improvements are some consequences of this change:
* Absorb a confusing git checkout failure message when the failure
is allowed and we act on that failure appropriately.
* Fix an unnecessary fetch in some scenarios when checking out a
git hash we already have locally.
* Stash and restore any local changes even when not rebasing.
* Avoid unsafe rebasing where we are not on a branch that is
already tracking the requested branch.
* When fetching, use --tags --force to ensure we get all the tags
and commits leading up to them regardless of whether the tags
are on branches or not. Also update our local tags if they move
on the remote.
Fixes: #20677
When checking out a specific commit by its git hash, git will output
a very noisy message about checking out a detached HEAD. This
is not particularly helpful for us here and makes the output overall
quite verbose. Add a git config setting to prevent it.
clang-cl cannot deal with implicit dependencies in UTF16 files
(see #18311). IntelLLVM inherits this behavior from Clang. The
MFC test uses `rc` in the way described in #18311 and gets the same
error described in #18311. Disable the test until #18311 is fixed.
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
The IntelLLVM C compiler do not yet support PDBs per file with the /Fd
option. Disable the parts of PDBDirectoryAndName that tries to generate
them so that the test will pass.
Work around an icx bug in command line handling of preprocessor macros.
A `\\\"` string in a macro passed to icx on the command line is not
properly parsed in compiler versions 2021.1.0 and earlier. This problem
is expected to be fixed, though a target release has no been set yet.
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
By default icx and icpx do not add build IDs when linking, so enable
the build ID to make the test pass.
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
This compiler makes stack frames large enough (at least in Debug
builds) that CMake language recursion to depth 1000 overflows the
stack. Reduce the limit for this compiler.
Using a single ID 'IntelLLVM' for the suite of Intel compilers based on
the LLVM backend. The 'IntelLLVM' ID are used for C, C++, and Fortran.
Data Parallel C++ will be handled in a separate commit.
The C and C++ definitions are based on the Clang definitions. The Intel
LLVM-based C and C++ compilers are based on the Clang front end, so
existing Clang options are more likely to be a good match than options
for the older Intel compilers.
Fortran is based on the older Fortran front end with the LLVM backend.
It has a similar interface to the older versions, though many options
are shared with the C and C++ compilers.
Fixes: #21561
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
Previously, when looking for exactly one file and the number of files
was not one, the test printed out an error message saying that too many
files were found, then printing the list of files. However, 0 is not
1 and also not too many files.
To reduce confusion, this commit adds a different message when 0 files
are found and 1 is expected.
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
A symbolic link in the path was causing false path mismatches.
Resolving the symlinks makes both paths identical.
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
Symbolic links in the path to the cmake build directory caused some
paths to have '..' directories in the path, which are equivalent, but
not a string match for the expected path. As a result, some tests fail.
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
Several extern functions were declared without return type, which results
in warnings. The functions are for calling Fortran subroutines, so
there should not be a return value.
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
Windows absolute paths start with a drive letter, followed by the path.
Without an explicit access method specification, CVS treats the drive
letter as a host name. This changes explicitly adds `:local:` to local
directory repository paths used in tests to avoid this confusion.
See the CVS Manual [1] for more information.
[1] https://www.gnu.org/software/trans-coord/manual/cvs/cvs.html#Repository
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
4de28ba4e6 Tests: Update tests for NVHPC compiler
90502d76b7 FindOpenMP: Add support for NVHPC compiler
76dee5831b FindOpenACC: Add support for NVHPC compiler
ff7bab83c2 GenerateExportHeader: Add support for NVHPC compiler
83ea49818f NVHPC: Add support for NVIDIA HPC SDK compilers based on PGI
Acked-by: Kitware Robot <kwrobot@kitware.com>
Merge-request: !5475
Use `linux_release` in names associated with building or testing
release-style binaries. Add a `.linux_package` helper to adjust
the release binary build behavior for package-specific jobs.
