From 2329e4d738475826095ae8d91c1e871199a58fb6 Mon Sep 17 00:00:00 2001 From: Alan Peixinho Date: Fri, 26 Jun 2026 13:15:21 -0300 Subject: [PATCH 1/7] chore: add coverage config Signed-off-by: Alan Peixinho --- .coveragerc | 7 +++++++ .gitignore | 1 + requirements-dev.txt | 1 + 3 files changed, 9 insertions(+) create mode 100644 .coveragerc diff --git a/.coveragerc b/.coveragerc new file mode 100644 index 0000000..2a05b8f --- /dev/null +++ b/.coveragerc @@ -0,0 +1,7 @@ +[run] +source = regzbot +omit = regzbot/testing*.py + +[report] +fail_under = 60 +show_missing = true diff --git a/.gitignore b/.gitignore index 45d7529..d86e6a9 100644 --- a/.gitignore +++ b/.gitignore @@ -3,3 +3,4 @@ __pycache__ *.pyc *.pyo *.swp +.coverage diff --git a/requirements-dev.txt b/requirements-dev.txt index 60ff385..c3c628f 100644 --- a/requirements-dev.txt +++ b/requirements-dev.txt @@ -1,2 +1,3 @@ ruff==0.11.9 pre-commit==4.2.0 +coverage From 6f608ffe431db950b5f9f81c4fc917bbe83059ae Mon Sep 17 00:00:00 2001 From: Alan Peixinho Date: Tue, 14 Jul 2026 11:05:55 -0300 Subject: [PATCH 2/7] refactor: extract db_ensure_cursor helper Replace repeated dbcursor None-checks with a shared helper. Signed-off-by: Alan Peixinho --- regzbot/__init__.py | 56 ++++++++++++++++++--------------------------- 1 file changed, 22 insertions(+), 34 deletions(-) diff --git a/regzbot/__init__.py b/regzbot/__init__.py index 3bdfb3c..31452a6 100644 --- a/regzbot/__init__.py +++ b/regzbot/__init__.py @@ -94,16 +94,14 @@ def init(databasedir): @staticmethod def update(dbcursor=None): - if dbcursor is None: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) if not RegzbotDbMeta.table_exists("RegzbotState", dbcursor): RegzbotState.db_create(1, dbcursor) @staticmethod def table_exists(tablename, dbcursor=None): - if dbcursor is None: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbresult = dbcursor.execute( "SELECT name FROM sqlite_master WHERE type='table' AND name=(?)", (tablename,) ).fetchone() @@ -113,8 +111,7 @@ def table_exists(tablename, dbcursor=None): @staticmethod def set_tableversion(tablename, version, dbcursor=None): - if dbcursor is None: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbcursor.execute( """ INSERT INTO RegzbotMeta @@ -135,8 +132,7 @@ def db_create(version, dbcursor): @staticmethod def get(attribute, dbcursor=None): - if dbcursor is None: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbresult = dbcursor.execute( "SELECT value FROM RegzbotState WHERE attribute=(?)", (attribute,) ).fetchone() @@ -146,8 +142,7 @@ def get(attribute, dbcursor=None): @staticmethod def set(attribute, value, dbcursor=None): - if dbcursor is None: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbcursor.execute( """ INSERT OR REPLACE INTO RegzbotState @@ -173,8 +168,7 @@ def db_create(version, dbcursor): @staticmethod def add(msgid, gmtime, dbcursor=None): - if dbcursor is None: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbcursor.execute( """INSERT INTO msgidrecord @@ -186,8 +180,7 @@ def add(msgid, gmtime, dbcursor=None): @staticmethod def check_presence(msgid, gmtime=None, dbcursor=None): - if dbcursor is None: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbresult = dbcursor.execute( "SELECT * FROM msgidrecord WHERE msgid=(?)", (msgid,) @@ -931,8 +924,7 @@ def add(regid, repsrcid, entry, gmtime, subject, authorname, authormail): return dbcursor.lastrowid def delete(self, dbcursor=None): - if not dbcursor: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) # delete related activities for activity in RegActivityEvent.getall_by_actimonid(self.actimonid): @@ -1157,8 +1149,7 @@ def db_create(version, dbcursor): )""") def delete(self, dbcursor=None): - if not dbcursor: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) # delete related activities if self.repsrcid and ReportSource.get_by_id(self.repsrcid, dbcursor).ismail(): @@ -1453,8 +1444,7 @@ def get_by_regid(cls, regid): @staticmethod def remove(regid, dbcursor=None): - if dbcursor is None: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbresult = dbcursor.execute( "SELECT subject FROM regbackburner WHERE regid=(?)", (regid,) ).fetchone() @@ -1502,8 +1492,7 @@ def db_create(version, dbcursor): )""") def delete(self, dbcursor=None): - if not dbcursor: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) if self.repsrcid and ReportSource.get_by_id(self.repsrcid, dbcursor).ismail(): RecordProcessedMsgids.delete(self.entry) @@ -1757,8 +1746,7 @@ def get_by_reg_n_reptrd(cls, regression, reptrd): yield cls(*dbresult) def delete(self, dbcursor=None): - if not dbcursor: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbcursor.execute( """DELETE FROM reglinks @@ -2092,8 +2080,7 @@ def _db_update_solved(self): ) def delete(self, dbcursor=None): - if not dbcursor: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) for activity in RegActivityEvent.get_all(self.regid, onlyonce=False): activity.delete(dbcursor=dbcursor) @@ -2151,8 +2138,7 @@ def get_all(cls, order="regid", only_unsolved=False): @classmethod def get_by_regid(cls, regid, dbcursor=None): - if not dbcursor: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbresult = dbcursor.execute( "SELECT %s FROM regressions WHERE regid=?" % RegressionBasic.DBCOLS, (regid,) ).fetchone() @@ -2162,8 +2148,7 @@ def get_by_regid(cls, regid, dbcursor=None): @classmethod def get_by_entry(cls, entry, dbcursor=None): - if not dbcursor: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbresult = dbcursor.execute( "SELECT %s FROM regressions INNER JOIN actmonitor ON actmonitor.regid = regressions.regid WHERE actmonitor.entry=?" @@ -3225,8 +3210,7 @@ def modify( ) def delete(self, dbcursor=None): - if not dbcursor: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbresult = dbcursor.execute( """DELETE FROM reportsources WHERE repsrcid=(?)""", @@ -3255,8 +3239,7 @@ def islore(cls, repsrcid): @classmethod def get_by_id(cls, repsrcid, dbcursor=None): - if not dbcursor: - dbcursor = DBCON.cursor() + dbcursor = db_ensure_cursor(dbcursor) dbresult = dbcursor.execute( "SELECT * FROM reportsources WHERE repsrcid=(?)", (repsrcid,) @@ -3525,6 +3508,11 @@ class RepDownloadError(Exception): pass + +def db_ensure_cursor(dbcursor=None): + return DBCON.cursor() if dbcursor is None else dbcursor + + def db_close(): global DBCON DBCON.close() From 9e1c2635663499924e6dfb2bcf673927d75195d2 Mon Sep 17 00:00:00 2001 From: Alan Peixinho Date: Tue, 14 Jul 2026 11:06:08 -0300 Subject: [PATCH 3/7] chore: remove unused regression and URL helpers Drop dead get_by_link/dupof/update_author/parse_link paths that no callers use anymore. Signed-off-by: Alan Peixinho --- regzbot/__init__.py | 174 -------------------------------------------- 1 file changed, 174 deletions(-) diff --git a/regzbot/__init__.py b/regzbot/__init__.py index 31452a6..47b7ec3 100644 --- a/regzbot/__init__.py +++ b/regzbot/__init__.py @@ -2248,23 +2248,6 @@ def get_expected_by_subject(cls, subject): if dbresult: yield cls(*dbresult) - @classmethod - def get_by_link(cls, link): - tmpstring = link - if tmpstring.startswith("https://"): - tmpstring = tmpstring.removeprefix("https://") - elif tmpstring.startswith("http://"): - tmpstring = tmpstring.removeprefix("http://") - - if tmpstring.startswith("lore.kernel.org/"): - _, _, tmpstring = tmpstring.split("/", maxsplit=2) - msgid, _, _ = tmpstring.partition("/") - for regression in cls.get_by_entry(urldecode(msgid)): - return regression - else: - logger.warning("RegressionBasic.get_by_link(%s): unsupported domain ", link) - return None - @classmethod def get_by_url(cls, url): try: @@ -2387,93 +2370,6 @@ def introduced_update(self, tagload): self.introduced, ) - def __create_dup(self, url, gmtime): - subject = self.subject - repsrc, entry = ReportSource.get_by_url(url) - - # defaults that normally will be overridden - authorname = "Unknown" - authormail = None - - # create regression - return self.__create_obsolete( - self.introduced, - self.gitbranchid, - repsrc.repsrcid, - entry, - gmtime, - subject, - authorname, - authormail, - ) - - def _dupof_direct( - self, regression_other, gmtime, msgid, msgsubject, authorname, repsrcid, *, history=True - ): - if self.regid == regression_other.regid: - logger.warning( - 'regression[%s, "%s"]: request to mark this a as duplicate of ourselves; aborting', - self.regid, - self.subject, - ) - # FIXME properly - sys.exit(1) - - if self.solved_subject is None: - self.solved_subject = regression_other.subject - - self.solved_gmtime = gmtime - self.solved_duplicateof = regression_other.regid - - self._db_update_solved() - - logger.info( - 'regression[%s, "%s"]: marked as duplicate of regression Regression[%s, "%s"])', - self.regid, - self.subject, - regression_other.regid, - regression_other.subject, - ) - if history: - # make sure this is mentioned in the other regression, too - RegHistory.event( - regression_other.regid, - gmtime, - msgid, - self.solved_subject, - authorname, - repsrcid=repsrcid, - regzbotcmd='dup: the regression "%s" was marked as duplicate of this' - % (self.subject), - ) - - def dupof(self, tagload, gmtime, msgid, msgsubject, authorname, repsrcid): - def parse(tagload): - tagload = tagload.split(maxsplit=1) - url = tagload[0] - if len(tagload) > 1: - subject = tagload[1] - else: - subject = None - return url, subject - - urldup, self.solved_subject = parse(tagload) - - regression_other = self.get_by_link(urldup) - if not regression_other: - regression_other = self.__create_dup(urldup, gmtime) - RegHistory.event( - regression_other.regid, - gmtime, - msgid, - msgsubject, - authorname, - repsrcid=repsrcid, - regzbotcmd="introduced: %s [implicit, due to usage of 'dup-of']" % self.introduced, - ) - - self._dupof_direct(regression_other, gmtime, msgid, msgsubject, authorname, repsrcid) - def fixed(self, gmtime, commit_hexsha, commit_subject, gitbranchid): if self.solved_reason == "fixed": logger.info( @@ -2652,36 +2548,6 @@ def _solve_reason(self, reason, tagload, gmtime, msgid, repsrcid): self.solved_repentry = msgid self._db_update_solved() - def update_author(self, entry, tagload): - from email.utils import parseaddr - - author, authormail = parseaddr(tagload) - - dbcursor = DBCON.cursor() - dbcursor.execute( - """UPDATE actmonitor - SET authorname = (?), authormail = (?) - WHERE regid=(?) and entry=(?)""", - (author, authormail, self.regid, entry), - ) - logger.debug( - '[db regressions] author is now %s, authormail now %s (regid:%s; subject:"%s")', - author, - authormail, - self.regid, - self.subject, - ) - logger.info( - 'regression[%s, "%s"]: author is now %s, authormail now %s', - self.regid, - self.subject, - author, - authormail, - ) - - self.author = author - self.author = authormail - def title(self, tagload): dbcursor = DBCON.cursor() dbcursor.execute( @@ -3508,7 +3374,6 @@ class RepDownloadError(Exception): pass - def db_ensure_cursor(dbcursor=None): return DBCON.cursor() if dbcursor is None else dbcursor @@ -3629,45 +3494,6 @@ def timendate_gmtime_to_dt(gmtime): return datetime.datetime.fromtimestamp(gmtime, tz=datetime.timezone.utc) -def parse_link(url): - tmpstring = url - - if tmpstring.startswith("https://"): - tmpstring = tmpstring.removeprefix("https://") - elif tmpstring.startswith("http://"): - tmpstring = tmpstring.removeprefix("http://") - - domain = mlist = msgid = None - if tmpstring.startswith("lore.kernel.org") or tmpstring.startswith("lkml.kernel.org"): - domain = "lore.kernel.org" - tmplist = tmpstring.split("/", maxsplit=2) - if len(tmplist) <= 2: - logger.debug("Ignoring %s, failed to parse", url) - return None, None, None - - mlist = tmplist[1] - tmpstring = tmplist[2] - - msgid, _, _ = tmpstring.partition("/") - - if mlist == "r": - if tmpstring.startswith("lkml.kernel.org"): - mlist = "lkml" - else: - # FIXMELATER: this is the lore redirector; for now just assume it redirecting to LKML, which likely needs fixing later - mlist = "lkml" - elif tmpstring.startswith("bugzilla.kernel.org"): - bugid = tmpstring.removeprefix("bugzilla.kernel.org/show_bug.cgi?id=") - if bugid.isnumeric(): - msgid = bugid - domain = "bugzilla.kernel.org" - else: - logger.debug("Tried to get bugid from %s, but failed", url) - else: - logger.debug("Tried to get msgid from %s, but don't known how to handle that domain", url) - return domain, mlist, msgid - - def basicressource_checkdir_exists(directory, create=False): try: if os.path.exists(directory): From 7aefe7febdaf6994505d36c238b6884e8fdb7a76 Mon Sep 17 00:00:00 2001 From: Alan Peixinho Date: Tue, 14 Jul 2026 11:06:09 -0300 Subject: [PATCH 4/7] refactor: add _web_days_delta for deterministic web dates Use injectable _web_now so offline tests can freeze web page timestamps. Signed-off-by: Alan Peixinho --- regzbot/export_web.py | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/regzbot/export_web.py b/regzbot/export_web.py index 1542808..d3de14e 100644 --- a/regzbot/export_web.py +++ b/regzbot/export_web.py @@ -17,6 +17,18 @@ logger = regzbot.logger + +def _web_now(): + mail_now = regzbot._TESTING.get("mail_now") + if mail_now is not None: + return mail_now + return regzbot.timendate_now() + + +def _web_days_delta(past): + return (_web_now() - datetime.datetime.fromtimestamp(past, datetime.timezone.utc)).days + + class RegLinkWeb(regzbot.RegLink): def __init__(self, *args): super().__init__(*args) @@ -718,7 +730,7 @@ def outpage_footer(yattagdoc, count): yattagdoc.text("[compiled by ") with yattagdoc.tag("a", href="https://linux-regtracking.leemhuis.info"): yattagdoc.text("regzbot") - currenttime = datetime.datetime.now(datetime.timezone.utc) + currenttime = _web_now() yattagdoc.text(" on %s (UTC). " % currenttime.strftime("%Y-%m-%d %H:%M:%S")) yattagdoc.text("Wanna know more about regzbot? Then check out its ") @@ -999,7 +1011,7 @@ def categorize(cls, regressionlist): } for regression in regressionlist: - last_activity_days = regzbot.days_delta(regression.gmtime_activity) + last_activity_days = _web_days_delta(regression.gmtime_activity) if regression.solved_reason == "inconclusive": categories["inconclusive"]["default"]["entries"].append(regression) elif regression.gmtime_solved: @@ -1110,7 +1122,7 @@ def compile(cls): regressionslist = list() eventslist = list() events_gmtime_offset = ( - int(datetime.datetime.now(datetime.timezone.utc).timestamp()) - 604800 + int(_web_now().timestamp()) - 604800 ) if regzbot.is_running_citesting("offline"): events_gmtime_offset = 604800 * 52 * 10 @@ -1187,10 +1199,7 @@ def compile(cls): for regression in regressionslist: if regression.gmtime_solved: continue - filed_days = ( - datetime.datetime.now(datetime.timezone.utc) - - datetime.datetime.fromtimestamp(regression.gmtime_filed, datetime.timezone.utc) - ).days + filed_days = _web_days_delta(regression.gmtime_filed) if filed_days < 7: categories[regression.treename]["entries"].append(regression) else: From b07cdb9cbadce94a70e573a703647f4f9ba362bb Mon Sep 17 00:00:00 2001 From: Alan Peixinho Date: Tue, 14 Jul 2026 11:06:21 -0300 Subject: [PATCH 5/7] refactor: split mail exporter for offline testing Extract prepare/publish helpers, injectable mail clock, and non-interactive compile path used by offline tests. Signed-off-by: Alan Peixinho --- regzbot/export_mail.py | 189 ++++++++++++++++++++++++++--------------- 1 file changed, 121 insertions(+), 68 deletions(-) diff --git a/regzbot/export_mail.py b/regzbot/export_mail.py index 4ba605e..30ee7b7 100644 --- a/regzbot/export_mail.py +++ b/regzbot/export_mail.py @@ -6,6 +6,7 @@ from collections import Counter import datetime +from email import generator as email_generator from email.message import EmailMessage import email.utils import tempfile @@ -17,6 +18,17 @@ logger = regzbot.logger +def _mail_now(): + mail_now = regzbot._TESTING.get("mail_now") + if mail_now is not None: + return mail_now + return regzbot.timendate_now() + + +def _mail_days_delta(past): + return (_mail_now() - datetime.datetime.fromtimestamp(past, datetime.timezone.utc)).days + + class RegLinkMailReport(regzbot.RegLink): def __init__(self, *args): super().__init__(*args) @@ -31,7 +43,7 @@ def mailreport(self): ): monitored = "; thread monitored." authored = "\n %s days ago, by %s%s" % ( - regzbot.days_delta(self.gmtime), + _mail_days_delta(self.gmtime), self.author, monitored, ) @@ -95,17 +107,17 @@ def compile(self, lastreport_gmtime): statusline.append(", ") statusline.append("; ") - statusline.append(str(regzbot.days_delta(self.gmtime))) + statusline.append(str(_mail_days_delta(self.gmtime))) statusline.append(" days ago; ") statusline.append(str(len(self._actievents))) statusline.append(" activities") if len(self._actievents) > 0: statusline.append(", latest ") - statusline.append(str(regzbot.days_delta(self._actievents[-1].gmtime))) + statusline.append(str(_mail_days_delta(self._actievents[-1].gmtime))) statusline.append(" days ago") if self.poked: - statusline.append("; poked %s days ago" % regzbot.days_delta(self.poked.gmtime)) + statusline.append("; poked %s days ago" % _mail_days_delta(self.poked.gmtime)) statusline.append(".") report.append("".join(statusline)) @@ -166,7 +178,7 @@ def add_latestpatch(self, report): report.append("* %s" % actievent.subject) report.append(" %s" % actievent.url()) report.append( - " %s days ago, by %s" % (regzbot.days_delta(actievent.gmtime), actievent.author) + " %s days ago, by %s" % (_mail_days_delta(actievent.gmtime), actievent.author) ) break @@ -235,7 +247,33 @@ def __init__( self.reporttext = reporttext @classmethod - def __create_mail(cls, content, treename): + def listed(cls, lastreport_gmtime): + regressionslist = list() + for regression in RegressionMailReport.get_all(only_unsolved=True): + # ignore some + if regression._actievents: + last_activity = regression._actievents[-1].gmtime + else: + last_activity = regression._histevents[-1].gmtime + regressionslist.append( + cls( + regression._actim_report.entry, + regression.gmtime, + regression.gmtime_filed, + last_activity, + regression.treename, + regression.versionline, + regression.backburner, + regression.identified, + regression.mailreport(lastreport_gmtime), + ) + ) + + regressionslist.sort(key=lambda x: x.gmtime_activity, reverse=True) + return regressionslist + + @classmethod + def __create_mail(cls, content, treename, *, fixed_message_id=False): msg = EmailMessage() msg["To"] = ( "LKML , Linus Torvalds , Linux regressions mailing list " @@ -243,25 +281,29 @@ def __create_mail(cls, content, treename): msg["Subject"] = "%s for %s [%s]" % ( regzbot.REPORT_SUBJECT_PREFIX, treename, - datetime.date.today(), + _mail_now().date(), ) - msg["Date"] = email.utils.localtime() - msg["Message-ID"] = email.utils.make_msgid(domain="leemhuis.info") + msg["Date"] = email.utils.formatdate(timeval=_mail_now().timestamp(), localtime=True) + if fixed_message_id: + msg["Message-ID"] = "" + else: + msg["Message-ID"] = email.utils.make_msgid(domain="leemhuis.info") msg.set_content(content, cte="quoted-printable") return msg @classmethod - def pagecreate(cls, categories, treename, lastreport_msgid): + def pagecreate(cls, categories, treename, lastreport_msgid, *, interactive=True): def repintro(report, number_issues, treename): intro = list() - print("Enter/Paste your intro for %s and hit Ctrl-D to save it." % treename) - while True: - try: - line = input() - except EOFError: - break - intro.append(line) + if interactive: + print("Enter/Paste your intro for %s and hit Ctrl-D to save it." % treename) + while True: + try: + line = input() + except EOFError: + break + intro.append(line) if report: intro.append("\n---\n") @@ -450,11 +492,7 @@ def categorize(cls, regressionlist, lastreport_gmtime): } for regression in regressionlist: - filed_days = ( - datetime.datetime.now(datetime.timezone.utc) - - datetime.datetime.fromtimestamp(regression.gmtime_filed, datetime.timezone.utc) - ).days - last_activity_days = regzbot.days_delta(regression.gmtime_activity) + last_activity_days = _mail_days_delta(regression.gmtime_activity) if regression.backburner: if lastreport_gmtime > regression.gmtime_activity: @@ -512,71 +550,71 @@ def categorize(cls, regressionlist, lastreport_gmtime): return categories @classmethod - def compile(cls): - logger.debug("[reportmail] generating") + def prepare_reports(cls, categories, lastreport_msgid, *, interactive=True): + reports = dict() + for treename in categories.keys(): + reports[treename] = cls.pagecreate( + categories[treename], treename, lastreport_msgid, interactive=interactive + ) + return reports + + @classmethod + def lastreport(cls): + if regzbot.is_running_citesting("offline"): + lastreport_gmtime = regzbot._TESTING["mail_lastreport_gmtime"] + lastreport_msgid = regzbot._TESTING.get("mail_lastreport_msgid") + else: + lastreport_msgid = regzbot.RegzbotState.get("lastreport_mainline_msgid") + lastreport_gmtime = regzbot.RegzbotState.get("lastreport_mainline_gmtime") - lastreport_msgid = regzbot.RegzbotState.get("lastreport_mainline_msgid") - lastreport_gmtime = regzbot.RegzbotState.get("lastreport_mainline_gmtime") if lastreport_gmtime: lastreport_gmtime = int(lastreport_gmtime) else: - lastreport_gmtime = int(datetime.datetime.now(datetime.timezone.utc).timestamp()) + lastreport_gmtime = int(_mail_now().timestamp()) + return lastreport_gmtime, lastreport_msgid + + @classmethod + def prepare(cls, *, interactive=True): + lastreport_gmtime, lastreport_msgid = cls.lastreport() logger.debug("[reportmail] lastreport was %s" % lastreport_gmtime) # gather everything we need - regressionslist = list() + categories = cls.categorize(cls.listed(lastreport_gmtime), lastreport_gmtime) + reports = cls.prepare_reports(categories, lastreport_msgid, interactive=interactive) + return reports, categories - for regression in RegressionMailReport.get_all(only_unsolved=True): - # ignore some - if regression._actievents: - last_activity = regression._actievents[-1].gmtime - else: - last_activity = regression._histevents[-1].gmtime - last_activity_days = regzbot.days_delta(last_activity) - if regression._actievents: - last_activity = regression._actievents[-1].gmtime - else: - last_activity = regression._histevents[-1].gmtime - regressionslist.append( - cls( - regression._actim_report.entry, - regression.gmtime, - regression.gmtime_filed, - last_activity, - regression.treename, - regression.versionline, - regression.backburner, - regression.identified, - regression.mailreport(lastreport_gmtime), - ) - ) - - regressionslist.sort(key=lambda x: x.gmtime_activity, reverse=True) - categories = cls.categorize(regressionslist, lastreport_gmtime) - - report_gmtime = int(datetime.datetime.now(datetime.timezone.utc).timestamp()) + @classmethod + def publish(cls, reports, *, interactive=True): + report_gmtime = int(_mail_now().timestamp()) + lastreport_msgid = None with tempfile.TemporaryDirectory() as tmpdirname: - for counter, treename in enumerate(categories.keys()): - report = cls.pagecreate(categories[treename], treename, lastreport_msgid) - + counter = 0 + for treename, report in reports.items(): if not report: logger.info("Nothing to report for %s" % treename) continue filename = os.path.join(tmpdirname, "%s-regzbotreport-%s" % (counter, treename)) - msg = cls.__create_mail(report, treename) + msg = cls.__create_mail(report, treename, fixed_message_id=not interactive) lastreport_msgid = msg["Message-ID"].strip("<>") - print("#" * 120) - print("\n%s\n" % filename) - print("#" * 120) - print(report) + if interactive: + print("#" * 120) + print("\n%s\n" % filename) + print("#" * 120) + print(report) with open(filename, "w") as out: - gen = email.generator.Generator(out) + gen = email_generator.Generator(out) gen.flatten(msg) + counter += 1 - print("#" * 120) + if counter == 0: + return + + if not interactive: + return + print("#" * 120) print( "Review the reports in %s and sent them using \"git send-email --from='Regzbot (on behalf of Thorsten Leemhuis) ' --suppress-cc=self --to '' %s/*\"" % (tmpdirname, tmpdirname) @@ -584,8 +622,23 @@ def compile(cls): answer = input("Enter c to confirm you sent the report, anything else to abort: ") if answer.lower() != "c": return + regzbot.RegzbotState.set("lastreport_mainline_gmtime", report_gmtime) regzbot.RegzbotState.set("lastreport_mainline_msgid", lastreport_msgid) - lastreport_msgid = regzbot.RegzbotState.get("lastreport_mainline_msgid") logger.debug("[report] generated") + + @classmethod + def compile(cls, *, interactive=True): + logger.debug("[reportmail] generating") + reports, _categories = cls.prepare(interactive=interactive) + cls.publish(reports, interactive=interactive) + + +def dumpall_mail(): + reports, categories = RegExportMailReport.prepare(interactive=False) + if not any(category["entries"] for category in categories.get("mainline", {}).values()): + return + + yield reports.get("mainline", "") + yield "\n" From 4d1334d07ee32635fb28dee1b88bebbbb6df754b Mon Sep 17 00:00:00 2001 From: Alan Peixinho Date: Tue, 14 Jul 2026 11:06:22 -0300 Subject: [PATCH 6/7] refactor: split web exporter for offline testing Extract prepare/publish/build_compilation and dumpall_web so offline tests can assert web output without writing pages alone. Signed-off-by: Alan Peixinho --- regzbot/export_web.py | 71 ++++++++++++++++++++++++++++++++----------- 1 file changed, 54 insertions(+), 17 deletions(-) diff --git a/regzbot/export_web.py b/regzbot/export_web.py index d3de14e..a5748fb 100644 --- a/regzbot/export_web.py +++ b/regzbot/export_web.py @@ -17,7 +17,6 @@ logger = regzbot.logger - def _web_now(): mail_now = regzbot._TESTING.get("mail_now") if mail_now is not None: @@ -799,7 +798,7 @@ def create_individual_page(cls, htmlpages, unhandled_count, regression): ) @classmethod - def createpage_compilation(cls, htmlpages, unhandled_count, categories, pagename): + def build_compilation(cls, htmlpages, unhandled_count, categories, pagename): tablecolumns = 3 yattagdoc = yattag.Doc() cls.outpage_head(yattagdoc) @@ -830,8 +829,12 @@ def createpage_compilation(cls, htmlpages, unhandled_count, categories, pagename with yattagdoc.tag("td", style="width: 100px;"): yattagdoc.text(regressionweb.treename) cls.outpage_footer(yattagdoc, unhandled_count) + return yattagdoc - cls.outpage_write(pagename, yattagdoc) + @classmethod + def createpage_compilation(cls, htmlpages, unhandled_count, categories, pagename): + yattagdoc = cls.build_compilation(htmlpages, unhandled_count, categories, pagename) + cls.outpage_write(pagename, yattagdoc) @classmethod def create_events(cls, directory, unhandled_count, htmlpages, eventslist): @@ -1109,24 +1112,22 @@ def regression_to_json(cls, regression): } @classmethod - def compile(cls): - logger.debug("[webpages] generating") + def _events_gmtime_offset(cls): + events_gmtime_offset = int(_web_now().timestamp()) - 604800 + if regzbot.is_running_citesting("offline"): + events_gmtime_offset = int(_web_now().timestamp()) - 604800 * 52 * 10 + return events_gmtime_offset + @classmethod + def prepare(cls): # these are the pages we are going to create htmlpages = ("next", "mainline", "stable", "new", "all", "resolved", "inconclusive") - - # handle this page first, as we need something from it anyway - unhandled_count = cls.create_unhandled(regzbot.WEBPAGEDIR, htmlpages) + unhandled_count = len(list(UnhandledEventWeb.get_all())) + events_gmtime_offset = cls._events_gmtime_offset() # gather everything we need regressionslist = list() eventslist = list() - events_gmtime_offset = ( - int(_web_now().timestamp()) - 604800 - ) - if regzbot.is_running_citesting("offline"): - events_gmtime_offset = 604800 * 52 * 10 - json_data = list() for regression in RegressionWeb.get_all(): json_data.append(cls.regression_to_json(regression)) @@ -1164,12 +1165,28 @@ def compile(cls): ) ) - cls.create_scriptfile_reldate() - eventslist.sort(key=lambda x: x["gmtime"], reverse=True) + return { + "htmlpages": htmlpages, + "unhandled_count": unhandled_count, + "regressionslist": regressionslist, + "json_data": json_data, + "eventslist": eventslist, + } + + @classmethod + def publish(cls, prepared): + htmlpages = prepared["htmlpages"] + unhandled_count = prepared["unhandled_count"] + regressionslist = prepared["regressionslist"] + json_data = prepared["json_data"] + eventslist = prepared["eventslist"] + + # handle this page first, as we need something from it anyway + cls.create_unhandled(regzbot.WEBPAGEDIR, htmlpages) + cls.create_scriptfile_reldate() cls.create_events(regzbot.WEBPAGEDIR, unhandled_count, htmlpages, eventslist) # we don't need this anymore now that we iterated over all regressions - eventslist = events_gmtime_offset = None # create the page listing all regressions, sorted by date regressionslist.sort(key=lambda x: x.gmtime_report, reverse=True) @@ -1230,4 +1247,24 @@ def compile(cls): with open(os.path.join(regzbot.WEBPAGEDIR, "regressions.json"), "w") as jsonfile: jsonfile.write(json.dumps(json_data)) + @classmethod + def compile(cls): + logger.debug("[webpages] generating") + cls.publish(cls.prepare()) logger.debug("[webpages] generated") + + +def dumpall_web(): + prepared = RegExportWeb.prepare() + regressionslist = prepared["regressionslist"] + regressionslist.sort(key=lambda x: x.gmtime_activity, reverse=True) + categories = RegExportWeb.categorize(regressionslist) + mainline = categories.get("mainline", {}) + if not any(section["entries"] for section in mainline.values()): + return + + doc = RegExportWeb.build_compilation( + prepared["htmlpages"], prepared["unhandled_count"], mainline, "mainline" + ) + yield yattag.indent(doc.getvalue()) + yield "\n" From b693997e381e00a696805131c237a850c9211f54 Mon Sep 17 00:00:00 2001 From: Alan Peixinho Date: Tue, 14 Jul 2026 11:06:23 -0300 Subject: [PATCH 7/7] test: cover mail/web export and deletion offline Record mail and web exporter dumps in results-offline.csv and add a delete regression exercise. Signed-off-by: Alan Peixinho --- regzbot/testing_offline.py | 58 +- testdata/expected/results-offline.csv | 9200 +++++++++++++++++++++++++ 2 files changed, 9257 insertions(+), 1 deletion(-) diff --git a/regzbot/testing_offline.py b/regzbot/testing_offline.py index 82c2c7c..489d9d3 100644 --- a/regzbot/testing_offline.py +++ b/regzbot/testing_offline.py @@ -22,6 +22,7 @@ import git import regzbot import regzbot.export_csv +import regzbot.export_mail import regzbot.export_web import regzbot._repsources._lore @@ -448,6 +449,12 @@ def init_mailsdir(path_tmpmail): def init(tmpdir, testdatadir): regzbot.set_citesting("offline") + regzbot._TESTING["mail_now"] = datetime.datetime.fromtimestamp( + Emaildir._startdate + 30 * 86400, datetime.timezone.utc + ) + regzbot._TESTING["mail_lastreport_gmtime"] = Emaildir._startdate - 86400 + regzbot._TESTING["mail_lastreport_msgid"] = "testing-lastreport@example.com" + _, databasedir, gittreesdir, _ = regzbot.basicressources_get_dirs( tmpdir=tmpdir, databasedir=os.path.join(tmpdir, "db-offlinetsts") ) @@ -475,6 +482,9 @@ def run(resultfilename, tmpdir, testdatadir): testfuncprefix = "offltest" this = sys.modules[__name__] + mail_results = [] + web_results = [] + outercount = 0 while "%s_%s_0" % (testfuncprefix, outercount) in dir(this): # reset git @@ -505,12 +515,21 @@ def run(resultfilename, tmpdir, testdatadir): update_gittrees() # write results - resultfile.write("[%s_%s_%s]\n" % (testfuncprefix, outercount, innercount)) + name = "%s_%s_%s" % (testfuncprefix, outercount, innercount) + resultfile.write("[%s]\n" % name) for data in regzbot.export_csv.dumpall_csv(): resultfile.write(data) resultfile.write("\n") + mail_results.append("-----BEGIN MAIL %s-----\n" % name) + mail_results.extend(regzbot.export_mail.dumpall_mail()) + mail_results.append("-----END MAIL %s-----\n\n" % name) + web_results.append("-----BEGIN WEB %s-----\n" % name) + web_results.extend(regzbot.export_web.dumpall_web()) + web_results.append("-----END WEB %s-----\n\n" % name) + regzbot.export_web.RegExportWeb.compile() + regzbot.export_mail.RegExportMailReport.compile(interactive=False) if instructions and "wait" in instructions: # regzbot.db_commit() @@ -521,6 +540,15 @@ def run(resultfilename, tmpdir, testdatadir): # remove generated mails emaildirs_clear() outercount += 1 + + separator = "=" * 80 + "\n" + resultfile.write(separator + "= MAIL REPORTS\n" + separator) + for data in mail_results: + resultfile.write(data) + resultfile.write(separator + "= WEB REPORTS\n" + separator) + for data in web_results: + resultfile.write(data) + resultfile.close() regzbot.db_commit() regzbot.db_close() @@ -1845,3 +1873,31 @@ def offltest_5_2(funcname): ) return ["mailchk"] + + +def offltest_6_0(funcname): + logger.info("%s: create a regression with link, note, and reply for delete test" % funcname) + + emaildirs["primary"].create_email(funcname, "#regzbot introduced: v1.8..v1.9-rc1") + + subcounter = 1 + emaildirs["primary"].create_email( + "%s_%s" % (funcname, subcounter), + "#regzbot relatebrief: https://www.kernel.org/releases.html Some link\n" + "#regzbot note: note before delete", + replyto=funcname, + ) + + subcounter += 2 + emaildirs["primary"].create_email( + "%s_%s" % (funcname, subcounter), "a reply to generate activity", replyto=funcname + ) + + return ["mailchk"] + + +def offltest_6_1(funcname): + logger.info("%s: delete the regression created in 6_0" % funcname) + for regression in regzbot.RegressionBasic.get_all(): + regression.delete() + return [] diff --git a/testdata/expected/results-offline.csv b/testdata/expected/results-offline.csv index b0422a1..1c4085e 100644 --- a/testdata/expected/results-offline.csv +++ b/testdata/expected/results-offline.csv @@ -3184,3 +3184,9203 @@ UNHANDLED: 5, https://lore.kernel.org/regressions/regzbot-testing-test_5_2_2@exa UNHANDLED: 6, https://lore.kernel.org/regressions/regzbot-testing-test_5_2_3@example.com/, unable to unrelate thread http://lore.kernel.org/somelist/somemsgid/, not related yet, 1546822800, None, test_5_2_3: Lorem ipsum dolor sit amet, None, None, None UNHANDLED: 7, https://lore.kernel.org/regressions/regzbot-testing-test_5_2_4@example.com/, unable to unrelate thread http://lore.kernel.org/regressions/some_fake_msgid/, not related yet, 1546909200, None, test_5_2_4: Lorem ipsum dolor sit amet, None, None, None +[offltest_6_0] +REGRESSION: test_6_0: Lorem ipsum dolor sit amet, v1.8..v1.9-rc1 (None), None, mainline, master, previous: no flags +INITIAL_REPORT: 1546304400, test_6_0: Lorem ipsum dolor sit amet, Regzbot testingmail, nobody@example.com, https://lore.kernel.org/regressions/regzbot-testing-test_6_0@example.com/ +LINK: Some link, https://www.kernel.org/releases.html, Regzbot testingmail, 1546390800 +ACTIVITY: test_6_0: Lorem ipsum dolor sit amet, Regzbot testingmail, https://lore.kernel.org/regressions/regzbot-testing-test_6_0@example.com/, 1546304400, PatchKind(None) +ACTIVITY: test_6_0_1: Lorem ipsum dolor sit amet, Regzbot testingmail, https://lore.kernel.org/regressions/regzbot-testing-test_6_0_1@example.com/, 1546390800, PatchKind(None) +ACTIVITY: test_6_0_3: Lorem ipsum dolor sit amet, Regzbot testingmail, https://lore.kernel.org/regressions/regzbot-testing-test_6_0_3@example.com/, 1546477200, PatchKind(None) +HISTORY: test_6_0: Lorem ipsum dolor sit amet, 1546304400, Regzbot testingmail, https://lore.kernel.org/regressions/regzbot-testing-test_6_0@example.com/, introduced: v1.8..v1.9-rc1 +HISTORY: test_6_0_1: Lorem ipsum dolor sit amet, 1546390800, Regzbot testingmail, https://lore.kernel.org/regressions/regzbot-testing-test_6_0_1@example.com/, relatebrief: https://www.kernel.org/releases.html Some link +HISTORY: test_6_0_1: Lorem ipsum dolor sit amet, 1546390800, Regzbot testingmail, https://lore.kernel.org/regressions/regzbot-testing-test_6_0_1@example.com/, note: note before delete +LATEST: test_6_0_3: Lorem ipsum dolor sit amet, Regzbot testingmail, https://lore.kernel.org/regressions/regzbot-testing-test_6_0_3@example.com/, 1546477200, PatchKind(None) + +[offltest_6_1] + +================================================================================ += MAIL REPORTS +================================================================================ +-----BEGIN MAIL offltest_0_0----- +-----END MAIL offltest_0_0----- + +-----BEGIN MAIL offltest_0_1----- +-----END MAIL offltest_0_1----- + +-----BEGIN MAIL offltest_0_2----- +-----END MAIL offltest_0_2----- + +-----BEGIN MAIL offltest_0_3----- +-----END MAIL offltest_0_3----- + +-----BEGIN MAIL offltest_0_4----- +-----END MAIL offltest_0_4----- + +-----BEGIN MAIL offltest_0_5----- +-----END MAIL offltest_0_5----- + +-----BEGIN MAIL offltest_0_6----- +-----END MAIL offltest_0_6----- + +-----BEGIN MAIL offltest_0_7----- +-----END MAIL offltest_0_7----- + +-----BEGIN MAIL offltest_0_8----- +-----END MAIL offltest_0_8----- + +-----BEGIN MAIL offltest_0_9----- +-----END MAIL offltest_0_9----- + +-----BEGIN MAIL offltest_0_10----- +-----END MAIL offltest_0_10----- + +-----BEGIN MAIL offltest_0_11----- +-----END MAIL offltest_0_11----- + +-----BEGIN MAIL offltest_0_12----- +-----END MAIL offltest_0_12----- + +-----BEGIN MAIL offltest_0_13----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================= +on back burner, but with activity since the last report +======================================================= + + +[ *NEW* ] updated title, set by test_0_10_0 +------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_0_9_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_0_9_0@example.com/ + +By Regzbot testingmail; 19 days ago; 4 activities, latest 13 days ago. +Introduced in v1.8..v1.9-rc1 + +Recent activities from: Regzbot testingmail (4) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_0_13----- + +-----BEGIN MAIL offltest_0_14----- +-----END MAIL offltest_0_14----- + +-----BEGIN MAIL offltest_0_15----- +-----END MAIL offltest_0_15----- + +-----BEGIN MAIL offltest_0_16----- +-----END MAIL offltest_0_16----- + +-----BEGIN MAIL offltest_0_17----- +-----END MAIL offltest_0_17----- + +-----BEGIN MAIL offltest_0_18----- +-----END MAIL offltest_0_18----- + +-----BEGIN MAIL offltest_0_19----- +-----END MAIL offltest_0_19----- + +-----BEGIN MAIL offltest_0_20----- +-----END MAIL offltest_0_20----- + +-----BEGIN MAIL offltest_0_21----- +-----END MAIL offltest_0_21----- + +-----BEGIN MAIL offltest_0_22----- +-----END MAIL offltest_0_22----- + +-----BEGIN MAIL offltest_0_23----- +-----END MAIL offltest_0_23----- + +-----BEGIN MAIL offltest_1_0----- +-----END MAIL offltest_1_0----- + +-----BEGIN MAIL offltest_1_1----- +-----END MAIL offltest_1_1----- + +-----BEGIN MAIL offltest_1_2----- +-----END MAIL offltest_1_2----- + +-----BEGIN MAIL offltest_1_3----- +-----END MAIL offltest_1_3----- + +-----BEGIN MAIL offltest_1_4----- +-----END MAIL offltest_1_4----- + +-----BEGIN MAIL offltest_1_5----- +-----END MAIL offltest_1_5----- + +-----BEGIN MAIL offltest_1_6----- +-----END MAIL offltest_1_6----- + +-----BEGIN MAIL offltest_1_7----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_1_7: Lorem ipsum dolor sit amet +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_1_7@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_1_7@example.com/ + +By Regzbot testingmail; 25 days ago; 1 activities, latest 25 days ago. +Introduced in 74cdebb9321b + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_1_7----- + +-----BEGIN MAIL offltest_1_8----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_1_7: Lorem ipsum dolor sit amet +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_1_7@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_1_7@example.com/ + +By Regzbot testingmail; 25 days ago; 1 activities, latest 25 days ago. +Introduced in 74cdebb9321b + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_1_8----- + +-----BEGIN MAIL offltest_1_9----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_1_7: Lorem ipsum dolor sit amet +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_1_7@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_1_7@example.com/ + +By Regzbot testingmail; 25 days ago; 1 activities, latest 25 days ago. +Introduced in 74cdebb9321b + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_1_9----- + +-----BEGIN MAIL offltest_1_10----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_1_7: Lorem ipsum dolor sit amet +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_1_7@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_1_7@example.com/ + +By Regzbot testingmail; 25 days ago; 1 activities, latest 25 days ago. +Introduced in 74cdebb9321b + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_1_10----- + +-----BEGIN MAIL offltest_1_11----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_1_7: Lorem ipsum dolor sit amet +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_1_7@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_1_7@example.com/ + +By Regzbot testingmail; 25 days ago; 1 activities, latest 25 days ago. +Introduced in 74cdebb9321b + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_1_11----- + +-----BEGIN MAIL offltest_1_12----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_1_7: Lorem ipsum dolor sit amet +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_1_7@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_1_7@example.com/ + +By Regzbot testingmail; 25 days ago; 1 activities, latest 25 days ago. +Introduced in 74cdebb9321b + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_1_12----- + +-----BEGIN MAIL offltest_2_0----- +-----END MAIL offltest_2_0----- + +-----BEGIN MAIL offltest_2_1----- +-----END MAIL offltest_2_1----- + +-----BEGIN MAIL offltest_2_2----- +-----END MAIL offltest_2_2----- + +-----BEGIN MAIL offltest_2_3----- +-----END MAIL offltest_2_3----- + +-----BEGIN MAIL offltest_2_4----- +-----END MAIL offltest_2_4----- + +-----BEGIN MAIL offltest_2_5----- +-----END MAIL offltest_2_5----- + +-----BEGIN MAIL offltest_2_6----- +-----END MAIL offltest_2_6----- + +-----BEGIN MAIL offltest_2_7----- +-----END MAIL offltest_2_7----- + +-----BEGIN MAIL offltest_2_8----- +-----END MAIL offltest_2_8----- + +-----BEGIN MAIL offltest_2_9----- +-----END MAIL offltest_2_9----- + +-----BEGIN MAIL offltest_2_10----- +-----END MAIL offltest_2_10----- + +-----BEGIN MAIL offltest_2_11----- +-----END MAIL offltest_2_11----- + +-----BEGIN MAIL offltest_2_12----- +-----END MAIL offltest_2_12----- + +-----BEGIN MAIL offltest_2_13----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] new title set via a monitored thread +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_2_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_2_0@example.com/ + +By Regzbot testingmail; 30 days ago; 11 activities, latest 13 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (11) + +3 patch postings are associated with this regression, the latest is this: +* test_2_12_3: add a mail with a simple patch + https://lore.kernel.org/regressions/regzbot-testing-test_2_12_3@example.com/ + 14 days ago, by Regzbot testingmail + +Noteworthy links: +* test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag] + https://lore.kernel.org/lkml/regzbot-testing-test_2_9@example.com/ + 20 days ago, by Regzbot testingmail; thread monitored. + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_2_13----- + +-----BEGIN MAIL offltest_2_14----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] new title set via a monitored thread +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_2_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_2_0@example.com/ + +By Regzbot testingmail; 30 days ago; 11 activities, latest 13 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (11) + +3 patch postings are associated with this regression, the latest is this: +* test_2_12_3: add a mail with a simple patch + https://lore.kernel.org/regressions/regzbot-testing-test_2_12_3@example.com/ + 14 days ago, by Regzbot testingmail + +Noteworthy links: +* test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag] + https://lore.kernel.org/lkml/regzbot-testing-test_2_9@example.com/ + 20 days ago, by Regzbot testingmail; thread monitored. + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_2_14----- + +-----BEGIN MAIL offltest_2_15----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] new title set via a monitored thread +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_2_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_2_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_2_14_0@example.com/ + +By Regzbot testingmail and Regzbot testingmail; 30 days ago; 12 activities, latest 8 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (12) + +3 patch postings are associated with this regression, the latest is this: +* test_2_12_3: add a mail with a simple patch + https://lore.kernel.org/regressions/regzbot-testing-test_2_12_3@example.com/ + 14 days ago, by Regzbot testingmail + +Noteworthy links: +* test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag] + https://lore.kernel.org/lkml/regzbot-testing-test_2_9@example.com/ + 20 days ago, by Regzbot testingmail; thread monitored. + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_2_15----- + +-----BEGIN MAIL offltest_2_16----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] new title set via a monitored thread +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_2_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_2_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_2_14_0@example.com/ + +By Regzbot testingmail and Regzbot testingmail; 30 days ago; 12 activities, latest 8 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (12) + +3 patch postings are associated with this regression, the latest is this: +* test_2_12_3: add a mail with a simple patch + https://lore.kernel.org/regressions/regzbot-testing-test_2_12_3@example.com/ + 14 days ago, by Regzbot testingmail + +Noteworthy links: +* test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag] + https://lore.kernel.org/lkml/regzbot-testing-test_2_9@example.com/ + 20 days ago, by Regzbot testingmail; thread monitored. + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_2_16----- + +-----BEGIN MAIL offltest_3_0----- +-----END MAIL offltest_3_0----- + +-----BEGIN MAIL offltest_3_1----- +-----END MAIL offltest_3_1----- + +-----BEGIN MAIL offltest_3_2----- +-----END MAIL offltest_3_2----- + +-----BEGIN MAIL offltest_3_3----- +-----END MAIL offltest_3_3----- + +-----BEGIN MAIL offltest_3_4----- +-----END MAIL offltest_3_4----- + +-----BEGIN MAIL offltest_3_5----- +-----END MAIL offltest_3_5----- + +-----BEGIN MAIL offltest_4_0----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 2 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_4_0_1: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_1@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_1@example.com/ + +By Regzbot testingmail; 29 days ago; 1 activities, latest 29 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (1) + + +===================================================== +current cycle (v1.10.. aka v1.11-rc), unknown culprit +===================================================== + + +[ *NEW* ] test_4_0_0: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_0@example.com/ + +By Regzbot testingmail; 30 days ago; 1 activities, latest 30 days ago. +Introduced in v1.10..v1.11-rc1 + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_4_0----- + +-----BEGIN MAIL offltest_4_1----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 2 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_4_0_1: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_1@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_1@example.com/ + +By Regzbot testingmail; 29 days ago; 1 activities, latest 29 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (1) + + +===================================================== +current cycle (v1.10.. aka v1.11-rc), unknown culprit +===================================================== + + +[ *NEW* ] test_4_0_0: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_0@example.com/ + +By Regzbot testingmail; 30 days ago; 1 activities, latest 30 days ago. +Introduced in v1.10..v1.11-rc1 + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_4_1----- + +-----BEGIN MAIL offltest_4_2----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 2 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_4_0_1: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_1@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_1@example.com/ + +By Regzbot testingmail; 29 days ago; 1 activities, latest 29 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (1) + + +===================================================== +current cycle (v1.10.. aka v1.11-rc), unknown culprit +===================================================== + + +[ *NEW* ] test_4_0_0: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_0@example.com/ + +By Regzbot testingmail; 30 days ago; 1 activities, latest 30 days ago. +Introduced in v1.10..v1.11-rc1 + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_4_2----- + +-----BEGIN MAIL offltest_4_3----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 2 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_4_0_1: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_1@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_1@example.com/ + +By Regzbot testingmail; 29 days ago; 1 activities, latest 29 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (1) + + +===================================================== +current cycle (v1.10.. aka v1.11-rc), unknown culprit +===================================================== + + +[ *NEW* ] test_4_0_0: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_0@example.com/ + +By Regzbot testingmail; 30 days ago; 1 activities, latest 30 days ago. +Introduced in v1.10..v1.11-rc1 + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_4_3----- + +-----BEGIN MAIL offltest_4_4----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 5 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +======================================================== +current cycle (v1.10.. aka v1.11-rc), culprit identified +======================================================== + + +[ *NEW* ] test_4_4_0: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_4_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_4_0@example.com/ + +By Regzbot testingmail; 12 days ago; 2 activities, latest 11 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (2) + +Noteworthy links: +* Link somewhere + https://www.kernel.org/releases.html + 11 days ago, by Regzbot testingmail + + +[ *NEW* ] test_4_0_1: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_1@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_1@example.com/ + +By Regzbot testingmail; 29 days ago; 1 activities, latest 29 days ago. +Introduced in 23bde5c338c7 + +Recent activities from: Regzbot testingmail (1) + + +===================================================== +current cycle (v1.10.. aka v1.11-rc), unknown culprit +===================================================== + + +[ *NEW* ] test_4_4_10: Lorem ipsum dolor sit amet +------------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_4_10@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_4_10@example.com/ + +By Regzbot testingmail; 2 days ago; 2 activities, latest -335 days ago. +Introduced in v1.10..v1.11-rc1 + +Fix incoming: +* Testcommit test_4_4 + https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=master&id=62f89ca29d354a42662bc61fc2e63ee6af41b3fd + + +[ *NEW* ] test_4_4_4: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_4_4@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_4_4@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_4_6@example.com/ + +By Regzbot testingmail and Regzbot testingmail; 8 days ago; 2 activities, latest 7 days ago. +Introduced in v1.10..v1.11-rc1 + +Fix incoming: +* https://lore.kernel.org/regressions/regzbot-testing-test_4_4_5@example.com/ + + +[ *NEW* ] test_4_0_0: Lorem ipsum dolor sit amet +------------------------------------------------ +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_4_0_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_4_0_0@example.com/ + +By Regzbot testingmail; 30 days ago; 1 activities, latest 30 days ago. +Introduced in v1.10..v1.11-rc1 + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_4_4----- + +-----BEGIN MAIL offltest_5_0----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +===================================================== +current cycle (v1.10.. aka v1.11-rc), unknown culprit +===================================================== + + +[ *NEW* ] test_5_0: Lorem ipsum dolor sit amet +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_5_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_5_0@example.com/ + +By Regzbot testingmail; 30 days ago; 1 activities, latest 30 days ago. +Introduced in v1.10..v1.11-rc1 + +Recent activities from: Regzbot testingmail (1) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_5_0----- + +-----BEGIN MAIL offltest_5_1----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +===================================================== +current cycle (v1.10.. aka v1.11-rc), unknown culprit +===================================================== + + +[ *NEW* ] test_5_0: Lorem ipsum dolor sit amet +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_5_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_5_0@example.com/ + +By Regzbot testingmail; 30 days ago; 2 activities, latest 29 days ago. +Introduced in v1.10..v1.11-rc1 + +Recent activities from: Regzbot testingmail (2) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_5_1----- + +-----BEGIN MAIL offltest_5_2----- + +--- + +Hi, this is regzbot, the Linux kernel regression tracking bot. + +Currently I'm aware of 1 regressions in linux-mainline. Find the +current status below and the latest on the web: + +https://linux-regtracking.leemhuis.info/regzbot/mainline/ + +Bye bye, hope to see you soon for the next report. + Regzbot (on behalf of Thorsten Leemhuis) + + +===================================================== +current cycle (v1.10.. aka v1.11-rc), unknown culprit +===================================================== + + +[ *NEW* ] test_5_0: Lorem ipsum dolor sit amet +---------------------------------------------- +https://linux-regtracking.leemhuis.info/regzbot/regression/lore/regzbot-testing-test_5_0@example.com/ +https://lore.kernel.org/regressions/regzbot-testing-test_5_0@example.com/ + +By Regzbot testingmail; 30 days ago; 7 activities, latest 23 days ago. +Introduced in v1.10..v1.11-rc1 + +Recent activities from: Regzbot testingmail (7) + + +============= +End of report +============= + +All regressions marked '[ *NEW* ]' were added since the previous report, +which can be found here: +https://lore.kernel.org/r/testing-lastreport@example.com + +Thanks for your attention, have a nice day! + + Regzbot, your hard working Linux kernel regression tracking robot + + +P.S.: Wanna know more about regzbot or how to use it to track regressions +for your subsystem? Then check out the getting started guide or the +reference documentation: + +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md +https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md + +The short version: if you see a regression report you want to see +tracked, just send a reply to the report where you Cc +regressions@lists.linux.dev with a line like this: + +#regzbot introduced: v5.13..v5.14-rc1 + +If you want to fix a tracked regression, just do what is expected +anyway: add a 'Link:' tag with the url to the report, e.g.: + +Link: https://lore.kernel.org/all/30th.anniversary.repost@klaava.Helsinki.FI/ +-----END MAIL offltest_5_2----- + +-----BEGIN MAIL offltest_6_0----- +-----END MAIL offltest_6_0----- + +-----BEGIN MAIL offltest_6_1----- +-----END MAIL offltest_6_1----- + +================================================================================ += WEB REPORTS +================================================================================ +-----BEGIN WEB offltest_0_0----- + + + + + + + +

Linux kernel regression status

+

[next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ current cycle (v1.10.. aka v1.11-rc), culprit identified +
none known by regzbot
+
+ current cycle (v1.10.. aka v1.11-rc), unknown culprit +
none known by regzbot
+
+ previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
none known by regzbot
+
+ older cycles (..v1.9), culprit identified, with activity in the past three months +
none known by regzbot
+
+ previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
none known by regzbot
+
+ older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
none known by regzbot
+
+ all others with unknown culprit and activity in the past three months +
+
+
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_0: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_0----- + +-----BEGIN WEB offltest_0_1----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    +
    +
  • + 4ddd01e474b9 +
    (v1.10-rc1^0)
    +
    • +
    +     		+
    + test_0_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_1----- + +-----BEGIN WEB offltest_0_2----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    +
    +
  • + 4ddd01e474b9 +
    (v1.10-rc1^0)
    +
    • +
    +     		+
    + test_0_0: updated title (set by test_0_2) by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_2----- + +-----BEGIN WEB offltest_0_3----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    +
    +
  • + 4ddd01e474b9 +
    (v1.10-rc1^0)
    +
    • +
    +     		+
    + test_0_0: updated title (set by test_0_2) by Regzbot testingmail and Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_3----- + +-----BEGIN WEB offltest_0_4----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    +
    +
  • + 4ddd01e474b9 +
    (v1.10-rc1^0)
    +
    • +
    +     		+
    + test_0_0: updated title (set by test_0_2) by Regzbot testingmail and Regzbot testingmail +
    + Fix incoming: + + 4169881b9e07 ("Testcomment to fixed-by") + +
    + +
    +
    +

    Latest five known activities:

    +

    Regzbot command history:

    +
    +
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_4----- + +-----BEGIN WEB offltest_0_5----- +-----END WEB offltest_0_5----- + +-----BEGIN WEB offltest_0_6----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + all others with unknown culprit and activity in the past three months +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_6: Lorem ipsum dolor sit amet by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_6----- + +-----BEGIN WEB offltest_0_7----- +-----END WEB offltest_0_7----- + +-----BEGIN WEB offltest_0_8----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_8----- + +-----BEGIN WEB offltest_0_9----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_9_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_9----- + +-----BEGIN WEB offltest_0_10----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + updated title, set by test_0_10_0 by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_10----- + +-----BEGIN WEB offltest_0_11----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + updated title, set by test_0_10_0 by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_11----- + +-----BEGIN WEB offltest_0_12----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + updated title, set by test_0_10_0 by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_12----- + +-----BEGIN WEB offltest_0_13----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + updated title, set by test_0_10_0 by Regzbot testingmail +
    On back burner: Some reason
    , by Regzbot testingmail
    +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_13----- + +-----BEGIN WEB offltest_0_14----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + updated title, set by test_0_10_0 by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_14----- + +-----BEGIN WEB offltest_0_15----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + updated title, set by test_0_10_0 by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_15----- + +-----BEGIN WEB offltest_0_16----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + updated title, set by test_0_10_0 by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_16----- + +-----BEGIN WEB offltest_0_17----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_17_0: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + updated title, set by test_0_10_0 by Regzbot testingmail +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    All known activities:

    +

    Regzbot command history:

    +

    When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

    +
    +
    +
    + all others with unknown culprit and activity in the past three months +
    none known by regzbot
    +
    + on back burner with activity in the past six months +
    none known by regzbot
    +
    +

    [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

    + +-----END WEB offltest_0_17----- + +-----BEGIN WEB offltest_0_18----- + + + + + + + +

    Linux kernel regression status

    +

    [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

    + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    +
    + current cycle (v1.10.. aka v1.11-rc), culprit identified +
    none known by regzbot
    +
    + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + older cycles (..v1.9), culprit identified, with activity in the past three months +
    none known by regzbot
    +
    + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
    none known by regzbot
    +
    + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
    +
    +
  • v1.8..v1.9-rc1
    • +
    +     		+
    + test_0_18: Lorem ipsum dolor sit amet by Regzbot testingmail
    Earliest & latest activity: .
     +

    +

      +

      +

      Regzbot command history:

      +

      When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

      +
      +
      +
      +
    • v1.8..v1.9-rc1
      • +
      +       		+
      + test_0_17_0: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail +

      All known activities:

      +

      Regzbot command history:

      +

      When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

      +
      +
      +
      +
    • v1.8..v1.9-rc1
      • +
      +       		+
      + updated title, set by test_0_10_0 by Regzbot testingmail +

      All known activities:

      +

      Regzbot command history:

      +

      When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

      +
      +
      +
      +
    • v1.8..v1.9-rc1
      • +
      +       		+
      + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
      Earliest & latest activity: .
       +

      All known activities:

      +

      Regzbot command history:

      +

      When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

      +
      +
      +
      + all others with unknown culprit and activity in the past three months +
      none known by regzbot
      +
      + on back burner with activity in the past six months +
      none known by regzbot
      +
      +

      [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

      + +-----END WEB offltest_0_18----- + +-----BEGIN WEB offltest_0_19----- + + + + + + + +

      Linux kernel regression status

      +

      [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
      +
      + current cycle (v1.10.. aka v1.11-rc), culprit identified +
      none known by regzbot
      +
      + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
      none known by regzbot
      +
      + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
      none known by regzbot
      +
      + older cycles (..v1.9), culprit identified, with activity in the past three months +
      none known by regzbot
      +
      + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
      none known by regzbot
      +
      + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
      +
      +
    • v1.8..v1.9-rc1
      • +
      +       		+
      + test_0_19_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

      All known activities:

      +

      Regzbot command history:

      +

      When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

      +
      +
      +
      +
    • v1.8..v1.9-rc1
      • +
      +       		+
      + test_0_18: Lorem ipsum dolor sit amet by Regzbot testingmail
      Earliest & latest activity: .
       +

      +

        +

        +

        Regzbot command history:

        +

        When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

        +
        +
        +
        +
      • v1.8..v1.9-rc1
        • +
        +         		+
        + test_0_17_0: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail +

        All known activities:

        +

        Regzbot command history:

        +

        When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

        +
        +
        +
        +
      • v1.8..v1.9-rc1
        • +
        +         		+
        + updated title, set by test_0_10_0 by Regzbot testingmail +

        All known activities:

        +

        Regzbot command history:

        +

        When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

        +
        +
        +
        +
      • v1.8..v1.9-rc1
        • +
        +         		+
        + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
        Earliest & latest activity: .
         +

        All known activities:

        +

        Regzbot command history:

        +

        When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

        +
        +
        +
        + all others with unknown culprit and activity in the past three months +
        none known by regzbot
        +
        + on back burner with activity in the past six months +
        none known by regzbot
        +
        +

        [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

        + +-----END WEB offltest_0_19----- + +-----BEGIN WEB offltest_0_20----- + + + + + + + +

        Linux kernel regression status

        +

        [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

        + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        +
        + current cycle (v1.10.. aka v1.11-rc), culprit identified +
        none known by regzbot
        +
        + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
        none known by regzbot
        +
        + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
        none known by regzbot
        +
        + older cycles (..v1.9), culprit identified, with activity in the past three months +
        none known by regzbot
        +
        + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
        none known by regzbot
        +
        + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
        +
        +
      • v1.8..v1.9-rc1
        • +
        +         		+
        + test_0_19_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

        All known activities:

        +

        Regzbot command history:

        +

        When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

        +
        +
        +
        +
      • v1.8..v1.9-rc1
        • +
        +         		+
        + test_0_18: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail
        Earliest & latest activity: .
         +

        +

          +

          +

          Regzbot command history:

          +

          When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

          +
          +
          +
          +
        • v1.8..v1.9-rc1
          • +
          +           		+
          + test_0_17_0: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail +

          All known activities:

          +

          Regzbot command history:

          +

          When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

          +
          +
          +
          +
        • v1.8..v1.9-rc1
          • +
          +           		+
          + updated title, set by test_0_10_0 by Regzbot testingmail +

          All known activities:

          +

          Regzbot command history:

          +

          When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

          +
          +
          +
          +
        • v1.8..v1.9-rc1
          • +
          +           		+
          + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
          Earliest & latest activity: .
           +

          All known activities:

          +

          Regzbot command history:

          +

          When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

          +
          +
          +
          + all others with unknown culprit and activity in the past three months +
          none known by regzbot
          +
          + on back burner with activity in the past six months +
          none known by regzbot
          +
          +

          [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

          + +-----END WEB offltest_0_20----- + +-----BEGIN WEB offltest_0_21----- + + + + + + + +

          Linux kernel regression status

          +

          [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

          + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
          +
          + current cycle (v1.10.. aka v1.11-rc), culprit identified +
          none known by regzbot
          +
          + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
          none known by regzbot
          +
          + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
          none known by regzbot
          +
          + older cycles (..v1.9), culprit identified, with activity in the past three months +
          none known by regzbot
          +
          + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
          none known by regzbot
          +
          + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
          +
          +
        • v1.8..v1.9-rc1
          • +
          +           		+
          + test_0_19_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

          All known activities:

          +

          Regzbot command history:

          +

          When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

          +
          +
          +
          +
        • v1.8..v1.9-rc1
          • +
          +           		+
          + test_0_18: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail
          Earliest & latest activity: .
           +

          +

            +

            +

            Regzbot command history:

            +

            When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

            +
            +
            +
            +
          • v1.8..v1.9-rc1
            • +
            +             		+
            + test_0_17_0: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail +

            All known activities:

            +

            Regzbot command history:

            +

            When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

            +
            +
            +
            +
          • v1.8..v1.9-rc1
            • +
            +             		+
            + updated title, set by test_0_10_0 by Regzbot testingmail +

            All known activities:

            +

            Regzbot command history:

            +

            When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

            +
            +
            +
            +
          • v1.8..v1.9-rc1
            • +
            +             		+
            + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
            Earliest & latest activity: .
             +

            All known activities:

            +

            Regzbot command history:

            +

            When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

            +
            +
            +
            + all others with unknown culprit and activity in the past three months +
            none known by regzbot
            +
            + on back burner with activity in the past six months +
            none known by regzbot
            +
            +

            [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

            + +-----END WEB offltest_0_21----- + +-----BEGIN WEB offltest_0_22----- + + + + + + + +

            Linux kernel regression status

            +

            [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

            + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
            +
            + current cycle (v1.10.. aka v1.11-rc), culprit identified +
            none known by regzbot
            +
            + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
            none known by regzbot
            +
            + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
            none known by regzbot
            +
            + older cycles (..v1.9), culprit identified, with activity in the past three months +
            none known by regzbot
            +
            + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
            none known by regzbot
            +
            + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
            +
            +
          • v1.8..v1.9-rc1
            • +
            +             		+
            + test_0_22_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

            All known activities:

            +

            Regzbot command history:

            +

            When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

            +
            +
            +
            +
          • v1.8..v1.9-rc1
            • +
            +             		+
            + test_0_19_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

            All known activities:

            +

            Regzbot command history:

            +

            When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

            +
            +
            +
            +
          • v1.8..v1.9-rc1
            • +
            +             		+
            + test_0_18: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail
            Earliest & latest activity: .
             +

            +

              +

              +

              Regzbot command history:

              +

              When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

              +
              +
              +
              +
            • v1.8..v1.9-rc1
              • +
              +               		+
              + test_0_17_0: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail +

              All known activities:

              +

              Regzbot command history:

              +

              When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

              +
              +
              +
              +
            • v1.8..v1.9-rc1
              • +
              +               		+
              + updated title, set by test_0_10_0 by Regzbot testingmail +

              All known activities:

              +

              Regzbot command history:

              +

              When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

              +
              +
              +
              +
            • v1.8..v1.9-rc1
              • +
              +               		+
              + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
              Earliest & latest activity: .
               +

              All known activities:

              +

              Regzbot command history:

              +

              When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

              +
              +
              +
              + all others with unknown culprit and activity in the past three months +
              none known by regzbot
              +
              + on back burner with activity in the past six months +
              none known by regzbot
              +
              +

              [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

              + +-----END WEB offltest_0_22----- + +-----BEGIN WEB offltest_0_23----- + + + + + + + +

              Linux kernel regression status

              +

              [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

              + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
              +
              + current cycle (v1.10.. aka v1.11-rc), culprit identified +
              none known by regzbot
              +
              + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
              none known by regzbot
              +
              + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
              none known by regzbot
              +
              + older cycles (..v1.9), culprit identified, with activity in the past three months +
              none known by regzbot
              +
              + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
              none known by regzbot
              +
              + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
              +
              +
            • v1.8..v1.9-rc1
              • +
              +               		+
              + test_0_23_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

              All known activities:

              +

              Regzbot command history:

              +

              When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

              +
              +
              +
              +
            • v1.8..v1.9-rc1
              • +
              +               		+
              + test_0_22_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

              All known activities:

              +

              Regzbot command history:

              +

              When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

              +
              +
              +
              +
            • v1.8..v1.9-rc1
              • +
              +               		+
              + test_0_19_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

              All known activities:

              +

              Regzbot command history:

              +

              When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

              +
              +
              +
              +
            • v1.8..v1.9-rc1
              • +
              +               		+
              + test_0_18: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail
              Earliest & latest activity: .
               +

              +

                +

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_0_17_0: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + updated title, set by test_0_10_0 by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_0_8: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_0_23----- + +-----BEGIN WEB offltest_1_0----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_0----- + +-----BEGIN WEB offltest_1_1----- +-----END WEB offltest_1_1----- + +-----BEGIN WEB offltest_1_2----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_2_0: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + 74cdebb9321b + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_2----- + +-----BEGIN WEB offltest_1_3----- +-----END WEB offltest_1_3----- + +-----BEGIN WEB offltest_1_4----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_4: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + f524db9faf55 ("Testcommit test_1_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_4----- + +-----BEGIN WEB offltest_1_5----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_5: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_4: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + f524db9faf55 ("Testcommit test_1_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_5----- + +-----BEGIN WEB offltest_1_6----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_5: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_4: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + f524db9faf55 ("Testcommit test_1_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_6----- + +-----BEGIN WEB offltest_1_7----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 74cdebb9321b +
                • +
                +                 		+
                + test_1_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_5: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_4: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + f524db9faf55 ("Testcommit test_1_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_7----- + +-----BEGIN WEB offltest_1_8----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 74cdebb9321b +
                • +
                +                 		+
                + test_1_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_5: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_4: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + f524db9faf55 ("Testcommit test_1_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_8----- + +-----BEGIN WEB offltest_1_9----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 74cdebb9321b +
                • +
                +                 		+
                + test_1_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_5: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_4: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + f524db9faf55 ("Testcommit test_1_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_9----- + +-----BEGIN WEB offltest_1_10----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 74cdebb9321b +
                • +
                +                 		+
                + test_1_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_5: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_4: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + f524db9faf55 ("Testcommit test_1_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_10----- + +-----BEGIN WEB offltest_1_11----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 74cdebb9321b +
                • +
                +                 		+
                + test_1_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_5: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_4: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + f524db9faf55 ("Testcommit test_1_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_11----- + +-----BEGIN WEB offltest_1_12----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 74cdebb9321b +
                • +
                +                 		+
                + test_1_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_5: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_1_4: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + f524db9faf55 ("Testcommit test_1_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_1_12----- + +-----BEGIN WEB offltest_2_0----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: Linktitle
                , by Regzbot testingmail
                +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_0----- + +-----BEGIN WEB offltest_2_1----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: Updated linktitle
                , by Regzbot testingmail
                +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_1----- + +-----BEGIN WEB offltest_2_2----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_2----- + +-----BEGIN WEB offltest_2_3----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_3----- + +-----BEGIN WEB offltest_2_4----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_3: refer to this regression on another mainling list
                , by Regzbot testingmail (monitored)
                +

                Latest five known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_4----- + +-----BEGIN WEB offltest_2_5----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_3: refer to this regression on another mainling list
                , by Regzbot testingmail (monitored)
                +

                Latest five known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_5----- + +-----BEGIN WEB offltest_2_6----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + new title set via a monitored thread by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_3: refer to this regression on another mainling list
                , by Regzbot testingmail (monitored)
                +

                Latest five known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_6----- + +-----BEGIN WEB offltest_2_7----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + new title set via a monitored thread by Regzbot testingmail +

                Latest five known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_7----- + +-----BEGIN WEB offltest_2_8----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + new title set via a monitored thread by Regzbot testingmail +

                Latest five known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_8----- + +-----BEGIN WEB offltest_2_9----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + new title set via a monitored thread by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                +

                Latest five known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_9----- + +-----BEGIN WEB offltest_2_10----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + new title set via a monitored thread by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                +

                Latest five known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_10----- + +-----BEGIN WEB offltest_2_11----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + new title set via a monitored thread by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                +

                Latest five known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_11----- + +-----BEGIN WEB offltest_2_12----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                new title set via a monitored thread by Regzbot testingmail
                [1]: test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                Latest patch: test_2_12_3: add a mail with a simple patch
                , by Regzbot testingmail; signed-off-by present
                Earlier patches: 1, 2

                Latest five known activities:

                Regzbot command history:

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_12----- + +-----BEGIN WEB offltest_2_13----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                new title set via a monitored thread by Regzbot testingmail
                [1]: test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                Latest patch: test_2_12_3: add a mail with a simple patch
                , by Regzbot testingmail; signed-off-by present
                Earlier patches: 1, 2

                Latest five known activities:

                Regzbot command history:

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_13----- + +-----BEGIN WEB offltest_2_14----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                new title set via a monitored thread by Regzbot testingmail
                [1]: test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                Latest patch: test_2_12_3: add a mail with a simple patch
                , by Regzbot testingmail; signed-off-by present
                Earlier patches: 1, 2

                Latest five known activities:

                Regzbot command history:

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_14_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_14_2: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_14_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_14_2: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_14----- + +-----BEGIN WEB offltest_2_15----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                new title set via a monitored thread by Regzbot testingmail and Regzbot testingmail
                [1]: test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                Latest patch: test_2_12_3: add a mail with a simple patch
                , by Regzbot testingmail; signed-off-by present
                Earlier patches: 1, 2

                Latest five known activities:

                Regzbot command history:

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_14_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_14_2: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_15----- + +-----BEGIN WEB offltest_2_16----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                new title set via a monitored thread by Regzbot testingmail and Regzbot testingmail
                [1]: test_2_9: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                Latest patch: test_2_12_3: add a mail with a simple patch
                , by Regzbot testingmail; signed-off-by present
                Earlier patches: 1, 2

                Latest five known activities:

                Regzbot command history:

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_16_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 + +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_2_14_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: test_2_14_2: refer to this regression on another mainling list [implicit due to Link/Closes tag]
                , by Regzbot testingmail (monitored)
                +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_2_16----- + +-----BEGIN WEB offltest_3_0----- +-----END WEB offltest_3_0----- + +-----BEGIN WEB offltest_3_1----- +-----END WEB offltest_3_1----- + +-----BEGIN WEB offltest_3_2----- +-----END WEB offltest_3_2----- + +-----BEGIN WEB offltest_3_3----- +-----END WEB offltest_3_3----- + +-----BEGIN WEB offltest_3_4----- +-----END WEB offltest_3_4----- + +-----BEGIN WEB offltest_3_5----- +-----END WEB offltest_3_5----- + +-----BEGIN WEB offltest_4_0----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                + test_4_0_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_4_0_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                +
                +
              • + bff114a4835d +
                (v1.10^0)
                +
                • +
                +                 		+
                + test_4_0_3: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                +
                +
              • + 2c5fa4b5edeb +
                (v1.9-rc2^0)
                +
                • +
                +                 		+
                + test_4_0_5: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.10..23bde5c338c7
                • +
                +                 		+
                + test_4_0_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.11-rc1
                • +
                +                 		+
                + test_4_0_6: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_4_0_4: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.10-rc2
                • +
                +                 		+
                + test_4_0_2: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_4_0----- + +-----BEGIN WEB offltest_4_1----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                + test_4_0_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_4_0_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                +
                +
              • + bff114a4835d +
                (v1.10^0)
                +
                • +
                +                 		+
                + test_4_0_3: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                +
                +
              • + 2c5fa4b5edeb +
                (v1.9-rc2^0)
                +
                • +
                +                 		+
                + test_4_0_5: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.10..23bde5c338c7
                • +
                +                 		+
                + test_4_0_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.11-rc1
                • +
                +                 		+
                + test_4_0_6: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_4_0_4: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.10-rc2
                • +
                +                 		+
                + test_4_0_2: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_4_1----- + +-----BEGIN WEB offltest_4_2----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                + test_4_0_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_4_0_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                +
                +
              • + bff114a4835d +
                (v1.10^0)
                +
                • +
                +                 		+
                + test_4_0_3: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                +
                +
              • + 2c5fa4b5edeb +
                (v1.9-rc2^0)
                +
                • +
                +                 		+
                + test_4_0_5: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • v1.9.2..v1.10
                • +
                +                 		+
                + test_4_2_4: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.10.2..v1.11-rc1
                • +
                +                 		+
                + test_4_2_3: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.8.1
                • +
                +                 		+
                + test_4_2_2: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.10..23bde5c338c7
                • +
                +                 		+
                + test_4_0_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.11-rc1
                • +
                +                 		+
                + test_4_0_6: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_4_0_4: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.10-rc2
                • +
                +                 		+
                + test_4_0_2: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_4_2----- + +-----BEGIN WEB offltest_4_3----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                + test_4_0_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_4_0_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                +
                +
              • + bff114a4835d +
                (v1.10^0)
                +
                • +
                +                 		+
                + test_4_0_3: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                +
                +
              • + 2c5fa4b5edeb +
                (v1.9-rc2^0)
                +
                • +
                +                 		+
                + test_4_0_5: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • 123456789012
                • +
                +                 		+
                + test_4_3_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v0.10..v0.11
                • +
                +                 		+
                + test_4_3_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9.2..v1.10
                • +
                +                 		+
                + test_4_2_4: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.10.2..v1.11-rc1
                • +
                +                 		+
                + test_4_2_3: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.8.1
                • +
                +                 		+
                + test_4_2_2: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.10..23bde5c338c7
                • +
                +                 		+
                + test_4_0_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.11-rc1
                • +
                +                 		+
                + test_4_0_6: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_4_0_4: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.10-rc2
                • +
                +                 		+
                + test_4_0_2: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_4_3----- + +-----BEGIN WEB offltest_4_4----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                + test_4_4_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: Link somewhere
                , by Regzbot testingmail
                +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • + 23bde5c338c7 +
                • +
                +                 		+
                + test_4_0_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_4_4_10: Lorem ipsum dolor sit amet by Regzbot testingmail +
                + Fix incoming: + + 62f89ca29d35 ("Testcommit test_4_4") + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_4_4_4: Lorem ipsum dolor sit amet by Regzbot testingmail and Regzbot testingmail +
                + Fix incoming: + + 1234567890ab + +
                + +
                +
                +

                All known activities:

                +

                Regzbot command history:

                +
                +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_4_0_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                +
                +
              • + bff114a4835d +
                (v1.10^0)
                +
                • +
                +                 		+
                + test_4_0_3: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                +
                +
              • + 2c5fa4b5edeb +
                (v1.9-rc2^0)
                +
                • +
                +                 		+
                + test_4_0_5: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                +
                +
              • 123456789012
                • +
                +                 		+
                + test_4_3_1: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v0.10..v0.11
                • +
                +                 		+
                + test_4_3_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9.2..v1.10
                • +
                +                 		+
                + test_4_2_4: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.10.2..v1.11-rc1
                • +
                +                 		+
                + test_4_2_3: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.8.1
                • +
                +                 		+
                + test_4_2_2: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.10..23bde5c338c7
                • +
                +                 		+
                + test_4_0_7: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.11-rc1
                • +
                +                 		+
                + test_4_0_6: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_4_0_4: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                +
              • v1.9..v1.10-rc2
                • +
                +                 		+
                + test_4_0_2: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_4_4----- + +-----BEGIN WEB offltest_5_0----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_5_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity: .
                 +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_5_0----- + +-----BEGIN WEB offltest_5_1----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_5_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                +

                [recently 2 events occurred that regzbot was unable to handle]

                + +-----END WEB offltest_5_1----- + +-----BEGIN WEB offltest_5_2----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                +
                +
              • v1.10..v1.11-rc1
                • +
                +                 		+
                + test_5_0: Lorem ipsum dolor sit amet by Regzbot testingmail +

                Latest five known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                none known by regzbot
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                +

                [recently 7 events occurred that regzbot was unable to handle]

                + +-----END WEB offltest_5_2----- + +-----BEGIN WEB offltest_6_0----- + + + + + + + +

                Linux kernel regression status

                +

                [next] [mainline] [stable/longterm] • [new] • [all] • [resolved] [inconclusive] 

                + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                +
                + current cycle (v1.10.. aka v1.11-rc), culprit identified +
                none known by regzbot
                +
                + current cycle (v1.10.. aka v1.11-rc), unknown culprit +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + older cycles (..v1.9), culprit identified, with activity in the past three months +
                none known by regzbot
                +
                + previous cycle (v1.9..v1.10), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + older cycles (..v1.9), unknown culprit, with activity in the past three weeks +
                none known by regzbot
                +
                + all others with unknown culprit and activity in the past three months +
                +
                +
              • v1.8..v1.9-rc1
                • +
                +                 		+
                + test_6_0: Lorem ipsum dolor sit amet by Regzbot testingmail
                Earliest & latest activity:  & . Noteworthy: [1].
                 +
                [1]: Some link
                , by Regzbot testingmail
                +

                All known activities:

                +

                Regzbot command history:

                +

                When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

                +
                +
                +
                + on back burner with activity in the past six months +
                none known by regzbot
                +
                +

                [compiled by regzbot on 2019-01-31 01:00:00 (UTC). Wanna know more about regzbot? Then check out its getting started guide or its reference documentation.]

                + +-----END WEB offltest_6_0----- + +-----BEGIN WEB offltest_6_1----- +-----END WEB offltest_6_1----- +