Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
CoreFX is going to be merging changes soon that will break how we
consume them to do our testing. To give us time to react, we'll fix
the version of the repository we build to a commit before the
changes. We'll also download artifacts from a saved build (produced
before the change took place) so the layout is as we expect.
The issue tracking cleaning this up is #8937
|
|
Fix some problems with the ubuntu dasm output
|
|
Add x86 Release PR Trigger
|
|
|
|
Currently, only checked runs can be triggered for x86. This adds a trigger
for release runs as well.
|
|
- Re-enable the default build archiving in jitdiff scenarios so that the
windows _bld job will publish correct build artifacts for the
ubuntu_jitdiff_tst job to consume.
- Use relative paths in the generated scripts to avoid drive letters in
bash scripts.
- Fix exit code reporting in bash wrapper scripts.
- Upgrade jit-dasm version to use version with improved error handling
- Upgrade jit-analyze version to use same dependencies as jit-dasm
|
|
These archival and testResult groovy calls were using absolute paths, which is
apparently incorrect. Change then to use relative paths and make things
consistent between Windodws and Ubuntu runs.
|
|
Users are able to supply an fx_root that does not yet exist and
run-corefx-tests.py will create that directory. However,
run-corefx-tests.py checks to confirm that fx_root already exists when
we validate. This causes the script to exit with an error when fx_root
does not yet exist. This change modifies run-corefx-tests.py so that we
do not validate the fx_root path.
This change also fixes the path to WORKSPACE for ubuntu corefx testing
in netci.groovy.
|
|
|
|
Move the increasingly complex logic required for the CI to run CoreFx
tests from the CoreCLR repo into a separate script.
Also enable automated CoreFx jitstress testing for x86.
|
|
These jobs are failing and shouldn't be triggered on PRs
|
|
Make RyuJIT/x86 the default x86 JIT
|
|
JIT32 becomes compatjit.dll and RyuJIT LEGACY_BACKEND becomes legacyjit.dll
(and is an altjit).
If JIT32 is not being built, then RyuJIT LEGACY_BACKEND becomes compatjit.dll
and is a normal jit (not an altjit).
Both clrjit.dll and compatjit.dll are added to the JIT NuGet package.
|
|
The dasm archiving was enabled for all jitdiff scenarios, including the
build set up for the ubuntu/osx flow jobs. The dasm artifacts don't
exist in build-only scenarios, and this was preventing archiving of
the build.
|
|
This change adds a section to the generated bash/cmd scripts for each
test that will run jit-dasm on the test dll when runtests is invoked
with the jitdasm flag.
Also begin updating netci.groovy to support jit-diff scenario.
Other minor fixes:
- Add corefxlab feed for System.CommandLine test dependency
Without this, restoring the test dependencies retrieved an obsolete
package of the same name from nuget.org.
- Skip jit-diff job generation for arm
This fixes an assert that was checking that we are in the default
scenario on arm.
- Fix an assert in netci.groovy
- Add branch that skips non-checked configurations for jitdiff scenario.
- Fix some dasm failures and a typo in dasm job name
- Some jit-dasm runs were failing because the dependencies in the
current directory wasn't included in the arguments.
- Escape argument to jit-dasm
- increase timeout for jit-diff job
- Put PR job under a trigger, and some temporary changes for testing
- Make PR trigger look for comment
- Update Newtonsoft.Json version for compatibility with cijobs
- Update cijobs version for retrieving job by commit
- Temporarily run only one test
- Archive raw dasm output instead of zip
- Remove pr-specific logic, enable framework dasm
- Remove windows System.Private.CoreLib.ni.dll from test overlay
The new test runtime dependencies were placing
System.Private.CoreLib.ni.dll in the core_root directory, which resulted
in the native image for windows being placed in the coreoverlay
directory. We already had similar logic handling this case for
mscorlib.ni.dll.
This change also fixes the framework dasm output directory to match the
test dasm output directory, and fixes some typos in the generated .sh
files for running dasm on linux.
- Add dasm archiving on non-windows jobs
- Use core_root in bash scripts
|
|
* Add CI job and build.cmd command for building with FEATURE_STANDALONE_GC
* Add missed case
* Correct a condition
* Accidental fallthrough in switch
* Only run on x64
|
|
Change over from the old arm64 scripting.
|
|
This change moves away from hosting all of scripts on the Z:\ drive.
The share that used to be shared between the x64 machines and the
arm64 devices. It removes all the old scripting for one python script
arm64_post_build.py, which is responsible for setup of dotnet and
launching
the x64_client.
|
|
|
|
Create patches in formatting job
|
|
In the formatting job, if there are formatting errors, we will run the
formatter in --fix mode and generate a patch which will be uploaded to
azure storage.
|
|
The new server's email plugin version has different syntax and the email publishing doesn't work currently anyway. Will be re-enabled at a future time
|
|
Make dotnet/coreclr reference corresponding dotnet/corefx branch
|
|
We run CoreFx tests under JitStress modes in CoreCLR. Previously, we were
always pulling down CoreFx master, which is bad for CoreCLR release
branches when things are out of synch.
|
|
|
|
|
|
|
|
|
|
This also changes the x86/RyuJIT CI job to pass this option to
build.cmd. This leg will now use RyuJIT when crossgen'ing S.P.CoreLib
and when running tests.
|
|
|
|
|
|
|
|
|
|
|
|
In format.py, we were downloading bootstrap.sh/cmd to the current working
directory, but assuming that it was in coreclr/bootstrap, which is
incorrect. This change downloads it directly to coreclr/bootstrap, so that
we download and run to the same location.
This change also modifies where we install the newer version of dotnetcli
needed for jitutils to the coreclr/dotnetcli-jitutils directory. This
change is necessary because build.cmd->run.cmd->init-tools.cmd removes the
Tools directory, including our dotnetcli directory, so we don't want our
version of the cli to be trashed.
We also clean up our work at the end of the script by removing the
created jitutils and dotnetcli directories, and the bootstrap script.
Finally, this change adds some comments to tell the user what it's doing.
|
|
Add Formatting job
|
|
We want to be able to run jitstress, gcstress, etc. jobs on ryujit to
monitor our progress. This change adds additional vars to be written to
the TestEnv script for jitstress jobs.
|
|
|
|
This change adds the Windows and Ubuntu formatting jobs to the lab, and
makes them requestable. This also enables them to be run on push. The
jobs do the following:
On Windows:
- Build the Checked/Debug/Release builds as usenmakemakefiles, which
is a configureonly option (so won't do a full build)
- Download the bootstrap script for jitutils
- Download the correct version of dotnet cli
- Run the bootstrap script
- Run jit-format for Windows_NT Checked/Debug/Release
dll/standalone/crossgen configurations
On Ubuntu:
- Build release, checked, debug builds of coreclr in configureonly mode.
This will only run cmake and generate the compile_commands.json
- Install the correct version of dotnet cli
- Install the bootstrap script for jitutils
- Run the bootstrap script
- Run jit format over all configurations for Ubuntu (release, checked,
debug x dll, standalone, crossgen)
|
|
|
|
up new platforms
|
|
|
|
|
|
Change how we pass parameters when building CoreFx
|
|
|
|
Strings requiring inline replacement need double quotes
|
|
|
|
Ubuntu testing is failing with a groovy scripting error.
Matt asked me to revert this change for now.
This reverts commit 7fc5cb7e52c5db53a5696d398e281c0f6f6a1588.
|
|
Pulls crash dump links from dumplings.txt in the workspace into the build report
|