Skip to content

Add scheduled quarantine runs #19352

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Feb 26, 2020
Merged

Add scheduled quarantine runs #19352

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
3911257
Run quarantined tests every 4 hours
BrennanConroy Feb 25, 2020
99d606b
now?
BrennanConroy Feb 25, 2020
beba271
both
BrennanConroy Feb 25, 2020
2fa32a1
internal
BrennanConroy Feb 25, 2020
e7cd951
no pr
BrennanConroy Feb 26, 2020
c86277d
whoops
BrennanConroy Feb 26, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions .azure/pipelines/quarantined-tests.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,17 +5,20 @@ trigger:
include:
- master

# Run PR validation on all branches
pr:
schedules:
- cron: "0 */4 * * *"
displayName: Every 4 hours test run
branches:
include:
- '*'
- master
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Pilchie @mkArtakMSFT do we have enough Blazor tests running in Helix to make including schedule runs for the 'blazor-wasm' branch worthwhile?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we have any running #18636

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BrennanConroy you're probably right but I wasn't positive on the current status

always: true

variables:
- ${{ if ne(variables['System.TeamProject'], 'internal') }}:
- name: _UseHelixOpenQueues
value: 'true'
- ${{ if eq(variables['System.TeamProject'], 'internal') }}:
- group: DotNet-HelixApi-Access
- name: _UseHelixOpenQueues
value: 'false'

Expand All @@ -32,6 +35,7 @@ jobs:
- script: .\build.cmd -ci -NoRestore -test -projects eng\helix\helix.proj /p:RunQuarantinedTests=true /p:IsRequiredCheck=true /p:IsHelixJob=true /p:BuildAllProjects=true /p:BuildNative=true /p:ASPNETCORE_TEST_LOG_DIR=artifacts/log -bl
displayName: Run build.cmd helix target
env:
HelixApiAccessToken: $(HelixApiAccessToken) # Needed for internal queues
SYSTEM_ACCESSTOKEN: $(System.AccessToken) # We need to set this env var to publish helix results to Azure Dev Ops
artifacts:
- name: Helix_logs
Expand Down