Age | Commit message (Collapse) | Author | Files | Lines |
|
scenario
|
|
|
|
We have a problem with the xunit plug-in, where it is consistently
failing on Ubuntu arm32 test result uploading with this error:
```
The plugin hasn't been performed correctly
```
We haven't been able to identify the reason. So, do not add xunit parsing of the test data in this scenario.
This is tracked by: https://github.com/dotnet/coreclr/issues/19447.
|
|
|
|
|
|
1. Stop doing any OSX CoreFX jobs; they're too unreliable.
2. Stop running Debug jobs.
|
|
Also, create PR triggers for jobs that currently don't have them
(which is a bug), such as Debug and Release Windows x64 jobs.
|
|
Update vc-runtime package used by Windows ARM/ARM64 testing
|
|
|
|
|
|
These will be PR triggered for all users, not just those on the
arm64Users list. Since these are Build only, and do no testing,
with the change to use public VS2017 build tools, they can be run
by anyone.
Users on the arm64Users list will still get Checked Build and Test
jobs, which require using the private test machines.
|
|
Remove support for specifying the toolset directory for arm64,
which was used to point to an internal toolset.
Building for arm64 now works just like the other platforms, e.g.
invoke `build arm64`.
The requirements:
. Visual Studio 2017 Update 4 or later, with ARM64 toolset installed
. Windows SDK 10.0.17134.0 or later
. CMake 3.10 or later
|
|
|
|
We don't want these Debug jobs to run tests, because Debug testing is
slow, and we have few machine resources. It's a bit of a bug that we
are currently running tests, because the job is named with "Build", not
"Build and Test".
So make it do what the name says: Debug normal/innerloop arm32/arm64 jobs
will not run tests.
This is asymmetric, unfortunately. I might prefer that the Debug jobs get
generated as "Build and Test", but just not be triggered. (But be available
for triggering.) Or perhaps just not get generated. That might require a
separate set of just "Build" jobs that could be useful in some scenarios,
such as for what the current Debug "Build" only jobs are currently used for.
|
|
Enable the no tiered compilation innerloop PR legs
|
|
Also add a minimal fix that fixes a current problem, but isn't
expected to help fix the entire issue.
Failures tracked by https://github.com/dotnet/coreclr/issues/19003.
|
|
Enable Windows ARM64 corefx jobs in the CI
|
|
* Add no tiered compilation test jobs
With the upcoming switch to make tiered compilation on by default we want to preserve some JIT testing that will not enable tiered compilation.
1) Add 'no_tiered_compilation_pri0' jit stress job, logically the non-tiered variant of current 'Innerloop' jobs
- This job will run on all PRs for Checked x (Windows x86, Windows x64, Ubuntu arm) - but not scheduled that way for the moment so it can be tested post-checkin
2) Add 'no_tiered_compilation' jit stress job, logically the non-tiered variant of the current 'normal' job
- This job has the same periodic schedule as other jit stress jobs
3) Add 'r2r_no_tiered_compilation' r2r stress job, logically the non-tiered variant of the current 'r2r' job
- This job has the same periodic schedule as other r2r stress jobs
Misc adjustments - Added isPri0TestScenario because 'innerloop' is no longer the only scenario name which has this property + eliminated various comments that implied 'innerloop' IFF pri0
|
|
Fixes #18174
|
|
Disable various tests that currently fail, tagged with issues
describing the failures.
|
|
|
|
|
|
Make it explicit that most JIT testing does not use tiered compilation regardless of the runtime default
Clone jitstress1/2 and r2r_jitstress1/2 test modes both with and without tiering.
Move the existing tieredcompilation test modes to have the same periodic scheduling as other jit test runs.
|
|
* Modify netci.groovy
* Add script exit codes
* Ad PR Triggers for Ubuntu and OSX10.12
* Remove release PR triggers
* Rename arch
Remove IsJitStressTestScenario assert
* Add correct asserts
* Reformat conditions and add triggers for Release/Checked/Debug
* Change %WORKSPACE% to \${WORKSPACE}
|
|
Now that we have Ubuntu arm hardware in the lab, these are unnecessary.
The jobs have also been failing for months.
|
|
Remove build-only and TST jobs from the Jenkins views
|
|
We only want non-PR, "top-level" jobs in the views. Build-only
and TST jobs are always "child" jobs of other flow jobs, which
will be in the views.
|
|
|
|
* Update Tizen rootfs generation scripts for Tizen 5.0 M1
* Update Tizen CI docker image
* Update Tizen CI RID
|
|
|
|
|
|
CoreFX CI - Correct testResults path
|
|
|
|
|
|
|
|
* Netci
* Add fake test switch
* Add branch PR trigger
* Add Checked corefx_innerloop jobs
|
|
1. Remove armlb testing from netci.groovy
2. Remove legacy jit exclusions from tests.lst
3. Remove some unused `LEGACY_BACKEND` build definitions
4. Remove regpair.h
|
|
* Update Tizen CI docker image
* Revert "Remove Tizen armel automatic PR triggered jobs"
This reverts commit 462e2b59c67b0b6d25985a7284616539f348cbfc.
* Update Tizen CI docker image in netci
* Update links required for generation of Tizen rootfs
* Remove -rebuild from arm32 CI docker build
|
|
|
|
|
|
|
|
|
|
1. Enable using the test exclusion file for Ubuntu arm32.
2. Update the Ubuntu and Windows arm32 exclusion files based on
current GitHub issues.
|
|
Enable Ubuntu arm32 corefx testing
|
|
|
|
Add adityamandaleeka to arm64 users
|
|
|
|
Using "verbose" creates an extraordinary amount of output,
obscuring interesting output. I don't know of a compelling
reason to continue using "verbose", so stop doing so.
|
|
[Arm64/Linux] Enable crosscomponent build in CI
|
|
Disallow Ubuntu arm32 non-PR jobs in non-master branches
|