Versions Compared

Old Version 4

changes.mady.by.user Jesper Wilhelmsson

Saved on

compared with

New Version 5

changes.mady.by.user Jesper Wilhelmsson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleHow to get an exception from the no failure policy

Any rule, any process has exceptions. And in some cases it is better to live with a potential failure and integrate anyway. It should of course be used in rare cases only, for example when it is more important to continue to run the test, and thus at the same time accept the failure. A typical example is an intermittent failure like an intermittent crash (say once a month) in a large system test, or if more info is needed, possibly diagnostics are added to the test, and the risk of not running it is high.

Note
An exception like this requires that someone is actively working on the issue.

Label the bug with hs-nightly-quarantine-exception.

 

Expand
titleHow to know if a bug has escaped

There are a few ways to figure out if a problem has already escaped a repository:

  • The easiest way is of course if you know which change that caused the problem. Just have a look at the hg log of the upstream repository to see if the change is in there.
  • Searching JBS can give information as well. See if there is more than one bug filed for the issue. If it escaped it is likely that someone else has found it and maybe filed a new bug.

...