| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Fix tests to work with FIPS enabled
|
| |
| |
| |
| |
| | |
the mocks have all attrs by default, had to remove the nonexistent ones.
The test was missing the correct name and wasn't running.
|
| |
| |
| |
| | |
These lines setup the sconsign program to use the correct filename for the test.
|
| |
| |
| |
| |
| | |
Accidentally added two unused format strings.
Also referenced a variable from a copy-paste error.
|
| |
| |
| |
| |
| | |
is none vs == None.
this check is to ensure that the default None passthrough works correctly
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
defaulted to md5.
Dir search now excludes all types of sconsfiles that are now created.
Environment now defaults to the current scons filename instead of .sconsfile
Sconsign now has a function used by a lot of code that gets the default sconsign filename
Any tests referring to .sconsfile have now been changed, including one old legacy test.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The linter identified that warnings was unused in hash-format.py
The linter found that the skip_test function call was using 2 space indentation (not sure how I managed to do that).
Warning was originally added as hash-format gave a warning on ALLOWED_HASH_FORMATS != default
That was changed to instead test the different cases directly.
option--config.py skips the test if the default algorithm is not MD5 as the hashes used are OS-specific,
and supporting it in FIPS mode would be difficult. It's better to just skip this testcase in FIPS mode instead as
this specific test is different in that regard to the other FIPS-enabled tests.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Modified failing tests to use the new defaulted .sconsign database based on the hash algorithm
For MD5, default database will be .sconsign.dblite
For other algorithms the default will be .sconsign_<hashname>.dblite.
For all cases where the user changes the hash algorithm used, the database will be .sconsign_<hashname>.dblite (including md5)
For sub-scons directories it remains as .sconsign
Also added unit-tests for Util.py for the new hash default changes.
It's difficult to setup a fips-compliant platform using containers, and instead we mock that.
option--config uses multiple types of hash algorithms so was skipped.
Removed one f-string (python 3.5 doesn't support those)
Corrupt.py is using an explicit .sconsign so that was left as-is, and only the parent default .sconsign was changed for work test 1.
A fetch-database name option was added to the testing framework.
The unlink_sconsignfile was not updated as no usages of it were found.
|
| |
| |
| |
| |
| |
| | |
The original check was causing issues where 3.8 in Windows was throwing an unexpected error.
This should hopefully fix 3.8 in Windows while maintaining the same support in Linux.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Refactored code to match PR requirements
Changed result ==... result== to result in(...)
Updated the man page to reference the defaulting behavior for FIPS machines.
Updated a typo and design of change in the CHANGES.txt file
Made an ugly bit of code in Util.py that fixes it so python3.9 has MD5 support enabled in FIPS mode.
The code is much more ugly than before, with the tradeoff being it's testable and usable.
In python >= 3.9, SCons will now always default to MD5.
Next commit will work on getting the tests to auto-skip the md5-required steps on versions <= python 3.8.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Still failing on:
SCons/UtilTests.py
test/Configure/ConfigureDryRunError.py
test/Configure/implicit-cache.py
test/Configure/option--config.py
test/option/hash-format.py
test/option/option-n.py
test/question/Configure.py
These tests all have hardcoded md5 sums or use md5 directly
Next commit should fix it so the md5-specific tests are skipped if fips mode detected.
Also will figure out a way around the hardcoded m5sums.
|
| |
| |
| |
| | |
Test suite currently failing with FIPS enabled due to hard-coded MD5 tests.
|
|\ \
| | |
| | | |
Deprecate qt tool and rearrange docs
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Back out changes to runtest.py, those are now tracked in
separate PR #4055 with some others.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Updates tests to disable the warning that this change enables.
Fix runtest.py to make sure -o logging option captures all the output.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add markup.
Move description of qt tool into entry for qt tool, itself,
previously it was in the entry for the QTDIR variable.
Add QTDIR environment variable to the manpage, since
scons will read this one if set.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\ \
| | |
| | | |
Update Java support for more versions
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Listed the wrong option in the workaround suggestion.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
Also add more linux locations for Java headers (old saved patch)
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* on Windows, detect more possible JDK locations.
* On all platforms, more Java versions (up to 17.0 now).
* Add some docu on version selection and on JavaH tool in light of javah
command dropped since 10.0.
* Try to be better about preserving user's passed-in JAVA* consvars.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\ \ \
| | | |
| | | | |
Ensure build.ninja is always in a clean state
|
| |\ \ \
| |/ / /
|/| | | |
|
|\ \ \ \
| | | | |
| | | | | |
Some adjustments to runtest.py
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Close a hole where if logging (-o) *and* multi-job (-j),
the feedback from the tests was not logged. (-j)
* Clear list of failed tests if no tests failed.
* add a flush method to the Tee class, there are error conditions
where the lack of a flush threw an exception.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Switch Windows CI builds to VS2022 and Py3.10
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Replacing the build with 3.5 and VS2015
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Skip two scons-time tests on Windows
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The scons-time tests trying to test the "run" subcommand of
scons-time substitute a dummy script named my_python.py for Python.
In order for this to work on Windows, the file association chain for
.py files has to lead back to an Python interpreter, but we cannot
control this - for example, systems with VS Code installed often
steals this association in ways that are aren't easy to pre-detect.
Note that scons-time itself carfully uses the Python interpreter
to launch things so it's not affected by this, it's just the test
that tries to mock part of this scheme that has problems.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
|\ \ \ \
| | | | |
| | | | | |
Fix gcc-version test for Windows
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A constructed string containing the Python path wasn't listed
as a raw string, which led to a unicode error, because the
path string contained a \Users which was misinterpreted as a
Unicode escape.
Also had left a debug print in a script.
Signed-off-by: Mats Wichmann <mats@linux.com>
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
Remove -prerelease for MSVC 2022
|
|/ / / |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
doesn't match other platforms, but it should be sufficient to verify that build.ninja file still exists
|