Age | Commit message (Collapse) | Author | Files | Lines |
|
This change adds an opt_level throughput option so that we can run
throughput jobs in minopts mode. This also adds jobs to the lab for min
opts runs
|
|
|
|
|
|
Note this will add a new lst file and leverage the old existing arm64
infrastructure.
|
|
Fixes #12171.
* bootstrap.py was printing an improperly-cased path to put PGO/IBC
training data, which breaks on case-sensitive file systems, i.e., on
Linux.
* On Linux, `skiprestoreoptdata` was improperly skipping PGO even if
optdata was already present due to some of the conditional checks in
build.sh. This cleans that up to better match the intent of the
switch, and to fix Linux behavior to better match Windows.
|
|
There are many assemblies in our throughput benchmark package that are
reference or forwarding assemblies. There is no jit work in these
assemblies, so we want to exclude them.
This change also adds an iterations parameter so users can specify a
specific number of iterations for testing.
|
|
* Replace ScriptGenerator project.json with csproj
* Update project.json occurrences in docs
Fix few typos.
* Remove project.json comments
|
|
On Windows, we download a set of assemblies that we have uploaded to
MyGet. On Linux, we were building corefx each run to get the benchmarks.
This change updates Linux to pull down the same benchmarks Windows uses,
using curl to grab the nuget package from MyGet.
Note: after this commit, we will have data for fewer assemblies on
Linux, but we will now have the same set for both Windows and Linux.
Some data in Benchview may be affected.
|
|
|
|
SPC and the jit/coreclr are tightly coupled. With the changes to
crossgen into the dll, rather than the ni.dll, the throughput jobs are
now using the non-crossgen'd version of SPC on TP runs, which led to a
regression in TP on Linux because our comparison was not the same. This
change updates testing to replace the System.Private.CoreLib in the
throughput directory with the System.Private.CoreLib built by the
coreclr build.
|
|
* Return 0 on success from GC Reliability Framework scripts
* Don't save standard out, Jenkins already does this
|
|
Fix optdata restore functionality (#11935)
Bring back optdata restore functionality following the move to 2.0
BuildTools and csproj-based CLI. Disable a harmless warning that broke
the Linux build when consuming PGO counts due to -Werr.
Fix #11796 for master
|
|
- This update contains a fix for this issue: https://github.com/Microsoft/xunit-performance/issues/230
- Consolidate the Api version in two places: `dependencies.prop` and `PerfHarness.csproj`
- Move performance log files to root directory where Jenkins can archive them
- Fixed the output to console, so it is easier to see on the Jenkins job the sccript steps live and get an exact repro step if needed
|
|
- Removing `[assembly: MeasureInstructionsRetired]` from performance tests.
- Due to this issue: https://github.com/Microsoft/xunit-performance/issues/231, we are blocked from running on performance tests on Linux.
The tag is not used by infrastructure and it is passed during runtime when profiling on Windows.
- Adding the option to execute CoreRun with the stability prefix.
- Moving file to be archived by Jenkins and updating groovy file.
- Setting the maximum number of iterations.
|
|
|
|
Tizen basically requires GDBJIT enabled libraries.
Enable GDBJIT feature to prevent related build fail issues in advance.
|
|
|
|
1) Add LinkBench to the xunit-perf benchmark runs, as a scenario test
2) Some improvements to run-xunit-perf to
- Handle tests that perform size measurement
- Parametrization of test group
- Tests running multiple scenarios
CoreFX testing is currently disabled because it fails in the lab
due to a path length limitation.
|
|
Windows Arm64 - Build/Run tests in CI
|
|
Build tests with arm64 runs and upload/run them to the arm64 test
machines.
|
|
|
|
|
|
When I merged the PR that enabled the lean runs I added another call to
our run script. This run script had an assumption that it would only
ever be called once and as such would try and copy two files that had
the same name. This would cause it to prompt to overwrite or not and
fail the run. This change makes each copy unique based on the
collection flags that were used for collection.
|
|
* Add GC Reliability Framework CI job
* Three changes:
1) To address offline feedback, update the CI trigger phase document
and the GC testing instructions
2) Set the timeout for GC RF CI jobs to 24 hours, so they don't time
out (they will run for 15 hours by default)
3) Refactor "scenario == 'gc_reliability_framework' to its own method
so that new GC RF scenarios can easily and cleanly be added if
desired in the future
|
|
In the xunit performance harness we added support for a "lean" run which
only runs the stopwatch to collect duration and none of the ETW
providers are turned on. This adds support in the automation for doing
runs that use this lean feature.
|
|
This adds a run that will fire on the set of Azure VMs and will only run
for one interation. This along with the changes to fail a performance
run if a test fails will allow us to start gating checkins on the
performance tests still running.
|
|
* [ARM] Update cross rootfs for armel Tizen
Update cross rootfs for armel Tizen
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
* [ARM] Update cmake file and CI for armel Tizen
Update CI and cmake file for armel Tizen, because rootfs for Tizen is updated.
And rootfs for Tizen is embedded in Docker image for CI as Ubuntu for arm does.
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
|
|
These changes remove support for the x86 compat JIT from the build, the
runtime, and the various perf/test scripts.
Fixes #10733, #10734.
|
|
* [ARM32] clang 3.9 as a default for ARM cross build
Use clang 3.9 as a default compiler for ARM cross build
* Both arm and armel will be built using clang 3.9 as a default
* ARM CI will use clang 3.9 as a default
* ARM pipieline build will use clang 3.9 as a default
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
* [ARM32] Update docs describing clang-3.9 and ARM cross build
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
* [ARM] Check minimum version requirement of clang for ARM cross build
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
|
|
* [x86/Linux] Change CI docker image
Change CI docker image to support clang-3.9
* Update x86_ci_script.sh
change docker tag name
* Update x86_ci_script.sh
environment set correctly: ROOTFS_DIR
* Update x86_ci_script.sh
change docker image name
|
|
|
|
|
|
|
|
- This is the case when running on the dev boxes (outside automation)
|
|
- Added error checking to the script and make it fail fast
- Updated the xUnit Performance API version (build0002 -> build0003)
|
|
The perf harness needs 1.0.3-alpha-experimental now.
|
|
Modified Xunit runner to run Scenario Benchmarks
Updating xunit-performance packages
|
|
* Fix ARM32/Linux release CI test failure
Fix ARM32/Linux release CI test failure by removing libcoreclrptprovider.so from CoreFX build results.
* Fix typo
Fix typo in netci.groovy
|
|
Fix run-xunit-perf.cmd for local use
|
|
* Build libcoreclrtraceptprovider.so for ARM32 and modify cmake
- Build libcoreclrtraceptprovider.so for ARM32
- Include libcoreclrtraceptprovider.so in nuget package
- Don't build libcoreclrtraceptprovider.so for
Tizen: lttng is not supported in Tizen
- Exclude packaging libcoreclrtraceptprovider.so based on os-name
excluded for tizen
* Remove libcoreclrtraceptprovider.so before test for ARM32/Linux
Remove libcoreclrtraceptprovider.so before test for ARM32/Linux in CI
CI test environment using docker with qemu has some problem to use lttng library
|
|
run-xunit-perf.cmd specifies the full path to the benchmark using
%WORKSPACE%, which a user may not set locally. This change modifies it to
use %CORECLR_ROOT%.
|
|
If we use clang3.9 version, we will use O3 option for optimization.
Otherwise, use O1 option as before.
|
|
Update ILLINK build commands to reflect current CoreBuild of ILLinker.
Also remove the line that sets DoNotEmbedDescriptors,
since it is no longer necessary.
|
|
* [x86/Linux] PAL test in CI build
Add PAL test in CI x86/Linux build
Change docker image: including rootfs
* Fix netci.groovy
Add PAL test's result
|
|
Add jobs to run CoreCLR tests on Ubuntu via ILLINK
|
|
Update the arm64 test drop - WIP
|
|
|
|
Made changes to the test infrastructure to
1) Generate <test>.sh with commands to invoke ILLINK and run the output
2) Add runtest.sh --link=<path-to-illink> to invoke the ILLINK testing
|
|
This updates the CoreCLR performance runs to use the new xunit
performance api. This will unblock several people who were wanting to
move tests forward from netstandard1.4 which is were we have been locked
because of using the old desktop runner.
|
|
[ARM/CI] ARM CI script for arm and armel
|