Age | Commit message (Collapse) | Author | Files | Lines |
|
Archive the obj directory for arm builds
|
|
This will allow us to correctly populate the core_root for eventual
arm linux testing.
|
|
Fix timeouts. Up timeouts for non-default (Pri-1) builds.
|
|
|
|
This will reduce our ARM64 hardware load.
|
|
Enable arm/armlb/arm64 periodic GCStress=C jobs
|
|
These tests can time out when run with the default job timeout.
So, disable them in normal runs.
|
|
|
|
Don't add triggers for arm/armlb/arm64 non-flow jobs
|
|
Need to unset AltJit environment variables (and possibly others)
before running powershell.
|
|
|
|
|
|
This improves stress test coverage and creates consistency with
other platforms.
The jobs:
```
tieredcompilation
forcerelocs
jitnosimd (will soon be interesting for ARM64)
heapverify1
gcstress0xc_zapdisable
gcstress0xc_zapdisable_jitstress2
gcstress0xc_zapdisable_heapverify1
gcstress0xc_minopts_heapverify1
```
|
|
Run the command to ZIP the output directory in the same
"Execute Batch File" step as the smarty. Otherwise, a failure
of smarty will cause Jenkins to not run the subsequent batch file
steps, including the ZIP step.
Also, preserve the smarty error code to use that as the batch
file step exit code.
|
|
|
|
* [x86/Linux] Preparing pri2 unittest
- Copy test binary from x86 Windows build
- Copy CoreFX managed from arm CoreFX managed build
- Add archival
* Fix to merge test job generation
Change approach by expanding existing x64 & arm64 linux infrastructure
* [CI][Linux/x86] Fix configuration and architecture in netci.groovy
Fix to use configuration instead of lowerConfiguration
USe architecture and osGroup
* [CI][Linux/x86] Save test native builds in build job
Fix to save test native build in build job
Saved native builds are used on test job
|
|
Put the powershell command to create the archive in a separate
batch file step, so the smarty command error code will be recognized
separately.
|
|
Currently, a PR (from someone on the ARM64 whitelist) will automatically
trigger Windows ARM64 Debug builds. Due to an issue with test definitions,
this also triggers a Debug test run. This is unnecessary; Checked test
runs (and builds) should be sufficient. Save time and machine resources
by not doing Debug builds and tests by default.
|
|
Archive smarty directory for arm/armlb/arm64 runs
|
|
-NoProfile (#15164)
Code execution in several scripts and tests can be affected by powershell profile
execution at startup. Adding -NoProfile option to all powershell invocations which
may be affected by execution of profile startup code.
|
|
Currently, we only archive the *.smrt files, which is not enough to
see why a test failed, only that it did. Instead, ZIP the entire
Smarty.run.0 directory, and upload that (it's about 26MB for a
Pri-1 test run). This allows us to see the actual output of
each test, as generated by smarty.
|
|
A fix like #15075 will replace this soon.
|
|
|
|
|
|
* Clean up netci.groovy
1. Don't repeat entire list of JIT stress and R2R scenarios over and over;
use functions to check for scenario groups.
2. Merge handling of R2R baseline and stress scenarios.
3. Add function to determine if a scenario is a JIT stress scenario.
4. Fix JIT stress mode display name generator to handle CoreFx tests
as well, preserving the way they are currently displayed.
5. Fix R2R display name generator to handle baseline R2R scenario.
6. Fix bug where x86 R2R baseline job wasn't created.
7. Fix bugs where triggering some jobs, such as R2R jobs, would trigger lots
of other jobs with insufficient trigger strings. Thus, more trigger strings
now have architecture + scenario in them. E.g., "Innerloop" jobs now much
be triggered using a phrase containing "Innerloop".
8. Simplify code that creates builds, and test run commands.
9. Fix mis-casing of COMPlus_JITMinOpts in R2R stress list.
10. Expand list of valid ARM Windows scenarios to match total list of
scenarios, but with some scenarios commented out. Add the
jitstress2 + jitstressregs to the acceptable list. Add note about the
many scenarios in this list that are not in the full scenario list. Add
function to determine if a scenario is in this list.
11. Support crossgen of frameworks using altjit
12. Don't support 'r2r' scenario on arm/armlb/arm64 Windows.
|
|
* Re-enable Standalone GC job, running daily
* osGroup is already defined
* Fix failed assertion
|
|
Add jitstress arm64 jobs again
|
|
|
|
Better smarty archiving
|
|
|
|
Currently, an ARM build and CI test run uses the legacy backend
arm32 JIT. This change enables a build of RyuJIT/arm32 as a
cross-targeting protojit.dll (altjit) in the cross tools (placed
next to the x86 hosted crossgen.exe in the build), and uses that
RyuJIT/arm32 cross-compiler to build System.Private.CoreLib.dll.
The CI system when testing RyuJIT/arm32 will use this to test
the crossgen'ed System.Private.CoreLib.dll built by RyuJIT/arm32
for all "arm" architecture jobs.
|
|
|
|
Rework Arm64 Windows jobs to flow jobs
|
|
This drops our dependency on the internal Arm64CI
|
|
|
|
Rework Arm64 Windows jobs to flow jobs
|
|
This drops our dependency on the internal Arm64CI
|
|
|
|
|
|
For altjit, we can't run managed code from .NET installs that
are not under test. The XSLT Compiler tests invoke an XSLT
Compiler from the machine installed desktop framework. When it
sees the AltJit variables, but no altjit compiler dll, it dies.
So, don't run those tests. They have been annotated with a new
attribute to allow this exclusion.
|
|
These jobs are getting clean enough where having them regularly run
will be valuable.
|
|
|
|
|
|
Fix CoreFx testing
|
|
Currently, build.cmd will pass through all arguments starting with
an argument it doesn't recognize. Since it doesn't process/recognize
'-priority', make sure this is the last argument passed.
|
|
[ARM] Re-enable armel CI
|
|
The windows release builds are broken because they call build with
enforcepgo instead of -enforcepgo. This change fixes the parameter.
|
|
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
|
|
Because armel uses different implementation compared to armlb,
let's reenable armel CI.
Signed-off-by: Hyung-Kyu Choi <hk0110.choi@samsung.com>
|
|
Pri0 and pri1 rework
|