Run automated tests on buildbot #69541
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#69541
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated tests were enabled on buildbot.
Added subscriber: @brecht
Currently tests are only working on Linux. The issue is that the buildbot installs Blender to a directory separate from the build directory. However the tests run Blender from the build directory, and then will miss the Python executable on Windows and OpenMP library on macOS.
We need to either make the tests run from the install directory, or install Blender to the build directory.
This issue was referenced by
2028302f44
Tests are now passing on al platforms after
2028302f44
and some additional fixes.It seems builds are still being uploaded if tests fail.
Added subscriber: @Calra
From the discussion on blender chat, the notifications for failed build can be sent to
#blender-coders
. Help code snippet which will/can be used:Hey @brecht I am kind of getting stuck, could you give some insight?
StatusBot
class and extracting the build information from there? as that is the base class being used by the [IRC]] and [ https:*github.com/buildbot/buildbot/blob/e882d79d71161e471fb63355048f93d4e8c65f96/master/buildbot/reporters/telegram.py | Telegram botI also had a few design questions.
Using it on IRC was simple
The functionality I would expect is just a message whenever a build fails. And then perhaps that could be made a bit smarter to group together results from different platforms, filter out reports from the custom branch builder, not report consecutive build failures if it's too noisy, etc. Whatever we find out is a good signal to noise ratio in practice. Maybe just showing every failed build for every platform is fine.
I don't think the bot has to be interactive. It doesn't really solve a problem we have as far as I know, and would mean more maintenance and things that can break. If we do, then
StatusBot
would make sense since it provides that kind of functionality.But for our purposes, just subclassing
HttpStatusPush
seems enough, as is done for the Hipchat bot for example?Hey @brecht I looked into
HttpStatusPush
, it seems apt for our use case.I made one
BlenderChatStatusPush
subclassingHttpStatusPush
. Here is what all I tried:Directly trying to use
HttpStatusPush
to send some message to Blender Chat, from the documentation, it says it returns JSON object.For the
generator
parameter, I created an object ofBuildStatusGenerator
class, withmode="all"
For
user
andpassword
I used my Blender Chat user ID and authorization token.Subclassing
HttpStatusPush
and trying to make some changes to thesendMessage
,configService
andreconfigService
methodExplicitly calling
sendMessage
method but then it requires other parameters likebuild
Here is my understanding, correct me if I am wrong
All build information is passed internally, we don't need to provide the builder name explicitly (as the IRC bot already had all this info)
I didn't have much success with sending the status to blender.chat or rather any message using the reporter.
HttpClientService
is not receiving proper parameters to make a post request?I couldn't use Hipchat api to test it, Hipchat has been shutdown, also Hipchat used
HttpStatusPushBase
which had been deprecated, I mostly toyed around withHttpStatusPush
. Could you look into this?Thanks
The authorization token is not an HTTP password and can't be used as such. The user and token need to be put in the header as in the code snippet.
Subclassing just
HttpStatusPushBase
may be enough. You don't even have to usehttpclientservice
, usingrequests
as in the code snippet instead is probably fine.You need to implement the
send
method (notsendMessage
), and convert thebuild
object it receives into a human-readable text message.Yes, I passed the authorization token and user id in the headers as well.
Yes, this was my first approach, I tried directly using
post
method ofrequests
and attempted to send a message to myself on blender.chat inside bothsend/sendMessage
method (separately).I realized this after already commenting, I was implementing it in the wrong method. I will try it again.
Added subscriber: @ponderz
Moved to infrastructure/blender-projects-platform#47 and infrastructure/blender-projects-platform#46.
It's unfortunate the rocket chat integration was implemented but never deployed. However it seems less necessary now with the direct integration of CI status on projects.blender.org.