Page Comparison

Updated: CI_Weekly_Master_failures.xlsx

CI Status_WW39.pptx

Various test runs (e.g. the weekly test run, or master test runs after a merge) are not directly associated with user activity and therefore and no clear responsible party when something goes wrong.  With no

...

Rotation begins WW30'20.  The rotation term is 2 weeks.  Owners are responsible for finding or exchanging with an alternate if their rotation falls during a vacation or other OOO situation.

For latest update on ticket status, full list of intermittent failures and details on failures, please refer to ticket in JIRA using filter "Intermittent Test Issues"

Use the template below for creating a new ticket for tests failing in CI.

...

Labels: Intermittent Test Issues (for PR/master failures) or weekly_failures (for failures on weekly-testing branch)

Fill in Bug Exposure, Bug Quality, Bug Type accordingly.

Summary: Provide a summary of the issue (if it is an issue on weekly, precede with "Weekly Test - <summary>"

Description: Please include the following in the description.

...

Include stack trace, error message

Attach debug logs.

Intermittent CI failures

Here is a quick summary of recent CI failures.

For latest update on ticket status, full list of intermittent failures and details on failures, please refer to ticket in JIRA using filter "Intermittent Test Issues"

...

...

Test died without reporting the status. Runner error occurred: Timeout reached
Test should have produced a coredump.

...

...

Test died without reporting the status. Runner error occurred: Timeout reached
Test should have produced a coredump

...

...

Test was expected to pass but it failed. 
Test should have produced a coredump

...

Test died without reporting the status. Runner error occurred: Timeout reached

Stderr:

...