We critically need a test bot to be able to proceed effectively with big refactors as WSCCI involves.

Who should I talk to? Initiative owner, Larry? Sam Boyer and the Git team? The infrastructure team?

Comments

tamasd’s picture

tamasd commented

subscribing

Crell’s picture

Crell commented

I will reiterate this need in the Initiative Owner scrum call this week. It would require work by the infra/git team to make it happen.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

The problem here is that PIFT is only able to test branches that have a release node associated.

As of now, the most simple proposal heard in IRC was to allow development snapshot releases for sandboxes, but don't allow them to be published.

Crell’s picture

Crell commented
Status: Active » Postponed (maintainer needs more info)

Marking postponed until the infra team figures out what to do here. :-/ For the time being, open a core issue, make a huge mega patch, and post it there. Then throw out the issue (eventually). That's the best we can do for now.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Project: WSCCI » Drupal core
Version: » 8.x-dev
Component: Code » wscci

Per catch, and blessed by Larry, moving this and all other WSCCI issues to the Drupal core queue.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: We need a test bot » Testbot for core sandboxes
Component: wscci » simpletest.module
Category: bug » feature
Priority: Critical » Major
Status: Postponed (maintainer needs more info) » Active
Issue tags: +Testing system

Re-classifying.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Project: Drupal core » Defunct Infrastructure.drupal.org site
Version: 8.0.x-dev » 7.x-1.x-dev
Component: simpletest.module » Miscellaneous
Issue summary: View changes

This doesn't seem like a core issue.

tvn’s picture

tvn commented
Project: Defunct Infrastructure.drupal.org site » Drupal.org Testbots
Version: 7.x-1.x-dev »

Not Infra.d.o issue either.

jthorson’s picture

jthorson commented
Project: Drupal.org Testbots » DrupalCI: Drupal.org Testing Infrastructure

Not compatible with the current PIFR architecture (based on release_id references, and sandboxes can't have release_ids).

We can look at working around this in the next generation product.

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
commented
Title: Testbot for core sandboxes » [Policy] Allow testing of sandboxes with drupalci
Component: Miscellaneous » Policy
andypost’s picture

andypost
he/him
Primary language Russian
commented

Working on core proposal https://www.drupal.org/sandbox/jhodgdon/2369943 it screams to allow testing patches within sandbox

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Yes please! In this sandbox, anydpost, some other people, and I are working on a Core proposal for a new experimental module #2920309: Add experimental module for Help Topics
It makes a lot of sense (for this project) to have a Sandbox with its own issue queue to work on this. But when we post patches to issues, they don't get tested, meaning we either have to update the Core patch on the master issue and see what happens, or run the tests manually ourselves. Neither is a huge deal, but it would be faster/easier for us if the Sandbox could have auto testing of patches.