While investigating https://bugzilla.yoctoproject.org/show_bug.cgi?id=13977 (which is no longer failing), we noted that the mechanism uses the headless browser PhantomJS for image capture purposes. PhantomJS is no longer being actively worked on (see https://github.com/ariya/phantomjs/issues/15344) and the latest stable version is from 2016. While it still works and there is some activity on the GitHub repository, it is worth considering some more active alternatives: Playwright: https://github.com/microsoft/playwright Puppeteer: https://github.com/puppeteer/puppeteer
Might be easier to just replace that code with dynamically generated charts instead, chartjs or so on can draw a chart on the client in HTML. This will give us interactive charts too.
Ross: The issue isn't the website which already uses dynamically generated charts, its sharing images in the performance machine emails. If we do away with the charts in the emails, we can drop this. I suspect the issue is that client code execution from html emails is problematic. The right answer could well be just to drop the functionality and concentrate on the web browsable stuff.
I'd be entirely fine with the mail notifications being a high level summary of the report, and a link to a web page.
I'm leaning quite heavily to simplifying the email to just the text reports and a link...
Given how quickly JavaScript projects tend to change, that sounds like a good idea to me too. I still have this on my shortlist of things to do if we still want the screenshots, though.
Did we ever come to a conclusion on whether or not to simplify emails?
Bulk move of 64 bugs to 4.3 M3 after a quick review. If a bug is actually fixed, please add a commit link and resolve it. -- Randy for YP bug team.
Moved to 5.0 M1.
Bulk move of 52 5.0-M1 bugs to M2.
Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3.
We removed phantomjs usage: https://git.openembedded.org/openembedded-core/commit/?id=b5c131006e3fad0a15e6cdf81f71dc1e96647028