Closed
Bug 1577278
Opened 5 years ago
Closed 3 years ago
migrate windows tests from AWS to Azure
Categories
(Testing :: General, task, P3)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jmaher, Unassigned)
References
Details
this bug will be the main tracking bug for migration of unittests running on AWS -> GCP. Currently these are the tests that run on windows 1803.
Validation will include:
- overall runtime comparison (does xpcshell-1 run the same on aws vs gcp)
** 10x on aws vs 10x on gcp- compare total runtime - overall failure comparison
** same number of perma fails (should be zero)
** relative number of intermittent failures the same
** don't care about which tests fail intermittently
This could include:
- fixing some tests that fail frequently or perma fail as a result of moving (I expect really low numbers)
- experimenting with runtime on various available machine types at GCP
I assume this includes:
- windows10-64 opt/shippable/debug/asan/ccov
- windows7-32 shippable/opt/debug
Updated•5 years ago
|
Priority: -- → P3
Comment 1•4 years ago
|
||
These are moving to Azure now instead of GCP.
No longer blocks: tc-gcp
No longer depends on: tc-gcp-tests
Summary: migrate windows tests from AWS to GCP → migrate windows tests from AWS to Azure
Comment 2•3 years ago
|
||
With the other bugs and meta bugs for this move to Azure, is this bug still needed?
Flags: needinfo?(jmaher)
Reporter | ||
Comment 3•3 years ago
|
||
we can close this, thanks for checking
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(jmaher)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•