Mozregression should stop looking for builds when it realises that there are none due to TaskCluster only keeping builds for one year
Categories
(Testing :: mozregression, defect)
Tracking
(Not tracked)
People
(Reporter: felix.bau, Unassigned, NeedInfo)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:137.0) Gecko/20100101 Firefox/137.0
Steps to reproduce:
Test is run on up-to-date Windows 11 x64.
Start mozregression GUI 6.3.0 on app "Firefox"
Choose arch x86_64 and type debug
Choose 2016-04-06 to 2016-04-09 as regression range
Actual results:
It prints
2025-04-18T14:07:07.202000: INFO : TaskCluster only keeps builds for one year. Using 2024-04-18 14:07:07.202918 instead of 2016-04-06.
2025-04-18T14:07:07.202000: INFO : TaskCluster only keeps builds for one year. Using 2024-04-18 14:07:07.202918 instead of 2016-04-09.
and then keeps scrolling a lot (due to debug output and certain builds not being available - i.a. skipped)
but it doesn't stop the bisection even though no data is available.
It settles on loading 127.0a1 (2024-04-18) (today - 1year) which is not in the chosen range.
The log scrolled so fast, that most users will miss above's Info Message, while on pgo output is less, leading to the info message still being visible
Expected results:
Mozregression should have stopped looking for builds when it realised that there are none. Instead of presenting builds outside of the regression range.
|
||
Comment 1•17 days ago
|
||
The severity field is not set for this bug.
:zeid, could you have a look please?
For more information, please visit BugBot documentation.
Description
•