* Fix pinned dependencies in dev.in
* Revert "Fix pinned dependencies in dev.in"
This reverts commit 5dca034baf.
* Fix pinned dependencies in dev.in
* Revert "Fix pinned dependencies in dev.in"
This reverts commit 5dca034baf.
* Fix pinned dependencies in dev.in
* Revert "Fix pinned dependencies in dev.in"
This reverts commit 5dca034baf.
* Fix pinned dependencies in dev.in
* Revert "Fix pinned dependencies in dev.in"
This reverts commit 5dca034baf.
* Add Android 13 / Pixel 5 to Treeherder known platforms.
* put 'Shippable' at the end of the pretty platform name
Co-authored-by: Sebastian Hengst <aryx.github@gmx-topmail.de>
* Add the profile urls to performance alerts only if the profile artifacts are available
* Add a test to make sure we don't output the profile links when there is no profile artifact
It looks like inside the `getData` function we are getting the
`contentType` from the header. But while doing it, we have a weird
`''.startsWith('text/html');` after an OR operator. I think this might
be a forgotten artifact while refactoring that code.
`''.startsWith('text/html');` always returns false, which was confusing
to me while I was looking at this function. And below that line, we have
a check for `contentType` to see if it's "application/json".
See:
eccd74e32e/ui/helpers/http.js (L24)
* Add Firefox Profiler profile urls to browsertime regression template
* Rename FilterAlertsWithVideos class to BrowsertimeAlertsExtraData
* Add the browsertime alert extra data to 'Copy Summary' button as well
* Add tests for the new browsertime profiler url feature
* fix IFV graphs to use utc dates consistently to prevent never ending spinner
* IFV: only use UTC when looping over days
* also switch this to moment.utc
* fix graph x axis display date, increment day via moment, and use moment date as index for counter
Co-authored-by: Sebastian Hengst <aryx.github@gmx-topmail.de>
* Bug 1770903 - move time-to-triage logic to backend
* Bug 1770903 - Update UI countdown
* Bug 1770903 - Show alert created date under push date
* Address errors and reviews
Co-authored-by: Alex Ionescu <aionescu@mozilla.com>
Bug 1757222 removed the error message from failure lines if they are supposed to
get classified with bugs which track all failures for a test (single tracking
bug). The error message contains valuable information (e.g. it can indicate if
the issue is a permanent failure) and should be shown.
* Update to webpack 5
* Update style-loader to ^3.3.0
* Update copy-webpack-plugin to 11.0.0
* Update css-loader & html-webpack-plugin
* Replace file-loader by a webpack asset
* Replace url-loader by a webpack asset
* Update code imports
* Update webpack config
* Drop process.env.NODE_ENV in eslintrc
* Move webpack related deps to devDependencies
* Suggestion: serve dev server via the webpack module
* Bug 1757222 - hack suggestion list to only be simplified bug view
* Bump url-parse from 1.5.7 to 1.5.10 (#7399)
Bumps [url-parse](https://github.com/unshiftio/url-parse) from 1.5.7 to 1.5.10.
- [Release notes](https://github.com/unshiftio/url-parse/releases)
- [Commits](https://github.com/unshiftio/url-parse/compare/1.5.7...1.5.10)
---
updated-dependencies:
- dependency-name: url-parse
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Bug 1757222 - hack suggestion list to only be simplified bug view
* Bug 1757222 - hack suggestion list to only be simplified bug view
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The bug page opened after a bug got created with treeherder's bugfiler should
use the host specified by the BUGZILLA_API_URL environment variable. Until now,
the bug got created on httpst://bugzilla-dev.allizom.org but an unrelated bug
with same id on https://bugzilla.mozilla.org/ got opened on success.
The button to transfer selected text from the log viewer into the bug filer in a
different tab got added in bug bug 1745936 but didn't trigger React's `onChange`
event.
* Bug 1755301 - Add new tests
* Bug 1755301 - Changed display due date countdown logic
* Bug 1755301 - change get number of weekends day function
* Bug 1755301 - fix tests typo
* Bug 1748832 - Alerts View - Add time to triage countdown
* changed days counting logic, it now includes the day the alert was created
* work in progress, needs clarification
* new version, needs tests
* handle countdown render when duedate its a weekend day
* fixed secenario when there is a weekend between created date and due date
* Address PR changes
* added tests
* remove logs
* added new tests
* Address PR changes
This improves the response time for tasks with many failure lines locally by a
factor of 5. In production these requests often timed out because they were
too slow to get a response.
The `untriaged` label was displayed in green with a checkmark before it, which doesn't really convey
the state of the alert (someone might think the work is done here).
This patch updates the element so it uses yellow instead (from the `text-warning` class).
Bug was filed in bugzilla: for https://bugzilla.mozilla.org/show_bug.cgi?id=1741449
* Add [All] button next to the expanded group name, to select/deselect all jobs in this group, in "Add new jobs" view.
* Check jobInstance.props property value before accessing its property
* Removing the bug-job associations prevents wrong updates to bugs about the
issue still being observed in CI or about its frequency.
* Deletion of the classification type instead of appending 'not classified'
makes the data more robust for analysis.
* This feature is only enabled for employees and members of the 'sheriff' LDAP
group to prevent broad undesired changes by random users.
The failure classification type ("intermittent", "infra", ...) is stored
independently from the bug used for classification (bug 1169720), hence no model
based view set gets used.
* Bug 1743523 - Always show 5 pages in pagination.
* Bug 1743520 - Part 1: Always show pagination arrows
* Bug 1743520 - Part 2: Make the pagination button size consistent.
* Bug 1720105 - drop 'os' column from 'bugscache' table because it's unused
* For Bug 1731631 - only ingest data about intermittent bugs changed since the last update of the bugscache
store for duplicate bugs against which non-duplicate bug they got set as duplicate
* Simplify pinnedJobBugs by switching from Object to Set
* use open bug for classification if duplicate one matches failure line
Switching between different failed tasks and clicking "Show more bug
suggestions" for a failure line shows the additional bugs and still "Hide more
bug suggestions" after one switched directly to another failed task with bug
suggestions for a failure line at the same index (e.g. the first one).
This doesn't apply if one e.g. selected a failed task with no suggestions at the
same failure line index or one selected a task without failure lines inbetween.
React didn't update the element because the key was static (onyl index used).
* Bug 1735489 - Fetch other alerts from backend based on framework id
* Bug 1735489 - Add highlight other alerts toggle, add vertical lines to mark other alerts
* Bug 1735489 - Add unit test, clean code
* Bug 1735489 - Address pr requests
* Bug 1735489 - Fix failing test
* Refactor the artifacts tab in the details panel and add the pernosco link to that tab only for try and autoland for linux 64 builds; this link will show in jobs view and push health.
Support for filing issues as security bugs got added in bug 1369067. Having the
security group hardcoded and not matching the default one for the component
causes bugs to get missed during triage.
Bug 1429030 added automatic suggestions of the Bugzilla product and component
combination to use for new bugs created from the bug filer. Unrelated
product::component suggestions got suggested under certain conditions.
* Add model for file-to-bugzilla-component relation and its ingestion process
* add API endpoint to get Bugzilla product and component for source file path/search term
* bug filer: identify bugzilla product and component to use based on file path
* Bug 1723963 - Eliminate duplicated name for suite and test
* Bug 1723963 - Add unit tests
* Bug 1723963 - Fix unit tests
* Bug 1723963 - Move TextualSummary class, fix duplication test name for bugzilla
* Bug 1723963 - Reset testAlert signature's values
* Bug 1723963 - Rename Suite & Test column to Test for bug description
Bug 1450045 removed the machine_name data from the frontend cache and the
ability to filter by 'machine name' has been broken since.
Checking the results of tasks which have been run a specific machine should be
done with Taskcluster. Treeherder would also only show the runs for the
currently shown tree, to which machines are not bound.
The object holding the mapping of job IDs to the jobs themselves got iteratively
regenerated - the script walked over all jobs currently shown (with
Array.prototype.reduce) and for each job of the push which shall be shown, a new
object got generated based on the old one + the new job id and data. Based on
testing with mozilla-central and the default 10 pushes shown, this translates
into ~90k jobs and slow page warnings (execution up to 46s measured). The new
code takes one object and sets the id and data pairs iteratively in 100-200ms.
* Enable pagination in Compare View
* Moved implementation to CompareTableControls
* WIP updating the url parameters
* Keep filtered text in the input box when refreshing page
* Compact data in AlertTable
* Add sort to Magnitude of Change
* Abbreviate next/previous value, fix spacing tags&options
* Add unit tests for new/previous value
* Rename AlertTableMagnitude to Magnitude
Joel Maher
Nazım Can Altınova
alexandru-io
beatrice-acasandrei
Sebastian Hengst
renovate[bot]
arai-a
Valentin Rigal
esanuandra
aeyk
eng-esther
Alexandru Irimovici
Sorin Toma
Ben Hearsum (he/him)
Sarah Clements
Nicolas Chevobbe
Sarah Clements
Joel Maher
Michelle