Le jeu. 7 mars 2019 à 21:19, Michael <aixto...@felt.demon.nl> a écrit : > I think "ouch" - as I have been working hard to get all the tests to > pass for AIX. I feel "defeated".
Congrats :-) But that only for 3.x branch: 2.7 and 3.7 branches are still red. Can we simply remove AIX jobs on 2.7 and 3.7 branches? Or does anyone see the point of keeping them? Tests pass on PPC64 3.x, but all jobs POWER6 AIX are job (including POWER6 AIX 3.x). > -- Short comment on the "platforms.html" - sys.platform (re aix3 and > aix4) is dated. Is this something I can assist with via an issue and a PR? http://pythondev.readthedocs.io/platforms.html is my website. https://github.com/vstinner/pythondev is the source. I have no idea of what is the current value of sys.platform on recent AIX. > -- oh yes, I thought "unstable" already meant no messages were sent. > Corrected. Oh wait, I wasn't aware of that. Is it something new? I confirm that I saw this code in master.cfg: if stability == STABLE: mail_status_builders.append(buildername) github_status_builders.append(buildername) I started this email thread because I get emails from custom jobs. It seems like this test should be updated to explicitly exclude notifications from custom jobs. > -- p.s. I do not see you holding up a release of Python because a test > regresses on AIX (and no explanation can be found) - but I would hop > that AIX will be seen as stable enough to warrant being permitted to > send a message during development to signal a portability issue. The release process is unrelated to my thread. My use case is that I'm keeping an eye on buildbots as part of the Night's Watch team: I'm reading most emails sent to buildbot-status and I'm trying to analyze all failures. I didn't know that unstable buildbots don't send emails. When an unstable buildbot switch from green to red, I would like to be notified as well. It can be a regression in Python, not specific to the buildbot. I can handle regresions caused by a change on a buildbot, like an update of the system. > -- p.p.s. When I get an idea and/or assistance with understanding how to > debug the *multiprocessing* test failures the bot faces (but I > (generally) do not get when running manually) I'll dig further. Oh. Multiprocessing is complex. There are still many know issues reported to the bug tracker, *but* multiprocessing tests should be way more stable on buildbots now, than they were 1 or 2 years ago. You should be more specific if you want to help you, but maybe start a new thread instead. Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Buildbots mailing list Python-Buildbots@python.org https://mail.python.org/mailman/listinfo/python-buildbots
