rocket-tools/riscv-gnu-toolchain/qemu/meson.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author	Files	Lines
12 days	run_single_test.py: Fix for symlink changes	Dylan Baker	1	-1/+4

2024-09-23	run_single_test: Ensure symlinks exist and are cleaned up	Andrew McNulty	1	-0/+3
	The common test case "268 install functions and follow symlinks" requires that certain symlinks exist in order to function. If one clones a fresh repo and executes run_single_test.py with the aforementioned test as the target it will fail as the required symlinks are not part of the repo. Normally these symlinks are created and cleaned up when the overall testsuite is run but this is not the case for run_single_test.py This commit calls the necessary creation and cleanup functions in the case of run_single_test.py.
2024-07-12	tests: rename poorly named function and add report argument	Dylan Baker	1	-3/+3
	The poorly named `print_tool_versions()` doesn't just print the tools versions, it finds them and populates a global table, without which some tests will fail. Rename the function and add a `report` argument so that calls can decide whether they want to have the printed message, because the single runner doesn't in quick mode.
2023-12-13	Use SPDX-License-Identifier consistently	Dylan Baker	1	-2/+2
	This replaces all of the Apache blurbs at the start of each file with an `# SPDX-License-Identifier: Apache-2.0` string. It also fixes existing uses to be consistent in capitalization, and to be placed above any copyright notices. This removes nearly 3000 lines of boilerplate from the project (only python files), which no developer cares to look at. SPDX is in common use, particularly in the Linux kernel, and is the recommended format for Meson's own `project(license: )` field
2023-08-17	tests: consolidate MESON_SKIP_TEST reporting and use it in unittests	Eli Schwartz	1	-10/+3
	Previously, we only reported the skip reason when running project tests.
2023-05-25	run_single_test: add a --quick option to skip compiler/tool checking	Dylan Baker	1	-2/+5
	This can be the longest part of the entire test process, often with no benefit because we already know the environment is sane. So, let's have an option save some time.
2022-07-11	run_single_test: Allow passing extra args like run_project_test	Dylan Baker	1	-1/+4
	So you can do things like `run_single_test.py <path> -- -Ddefault_library=both`
2022-04-03	project tests: log the reason why a test is skipped	Eli Schwartz	1	-2/+18
	We expose a reason after the string 'MESON_SKIP_TEST', but it is actually ignored when running the test, so it is only useful as documentation and really might as well be a comment. Make it even more useful by actually printing that string after the '[SKIPPED]' message. Also, sometimes a test can be skipped for multiple reasons, and it would be useful to know which one occurred.
2021-11-22	run_single_test: honor the --use-tmpdir flag	Dylan Baker	1	-1/+1

2021-11-22	run_single_test: fix running failing tests	Dylan Baker	1	-1/+10

2021-07-07	Drop checking skippable() in run_single_test	Jon Turney	1	-2/+2
	Drop checking skippable() in run_single_test. It always returns True unless we are under CI, so checking it here is pointless.
2021-06-18	tests: Always enable the traceback in run_project_tests.py	Daniel Mensinger	1	-1/+1

2021-06-09	tests: Reduce complexity of the run_tests signature	Daniel Mensinger	1	-24/+12

2021-06-09	typing: Fully annotate run_project_tests.py	Daniel Mensinger	1	-1/+1

2021-03-23	run_single_test: Handle MESON_SKIP_TEST correctly	Dylan Baker	1	-3/+3

2021-02-23	add a script to run a single test	Dylan Baker	1	-0/+89
	As a Meson developer it's often frustrating to have a single functional test with a regression. These tests can be awkward to reproduce, especially when they make use of a test.json file. This script provides a simmple interface to call functional tests 1 at a time, regardless of whether they use a test.json or not. If they do use a test.json, and have a matrix, then the `--subtest` option can be used to select spcific combinations, for example: ```sh ./run_single_test.py "test cases/frameworks/15 llvm" --subtest 1 ``` will run only the second (zero indexed of course) subtest from the llvm test cases. This is not a super elegent script, but this is super useful.