Closed (fixed)
Project:
Test driven development infrastructure
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
25 Dec 2010 at 11:56 UTC
Updated:
5 Feb 2016 at 00:22 UTC
Jump to comment: Most recent
Comments
Comment #1
pillarsdotnet commentedSort-of fixed.
Right now all patches in issues marked 6.x are given a status of "Postponed".
I suspect that there aren't any D6 testbots right now.
Comment #2
klonosLike you said Bob: "sort-of fixed". Thanx for the update concerning the postponed status of 6.x patches. This at least will take care of the patches failing tests when people expect them to pass.
PS: ...corrected minor typo in issue's title.
Comment #3
klonos...if #66484: Allow issues to be filed against multiple versions/branches. gets ever implemented, then the 'run tests against the core version the issue is set to' part of the request should become 'run tests against the version each patch is set to'.
Comment #4
pillarsdotnet commentedLooks like the testbots are testing against the version the issue is set to. so marking this "fixed".
Comment #5
klonosYep. Now should I file a new issue about the test bot running against the core version each patch is set to and keep this issue's status fixed, or should we rename this one instead and keep it open?
Still relevant: #66484: Allow issues to be filed against multiple versions/branches.
Also related: #1050616: Figure out backport workflow from Drupal 8 to Drupal 7
Comment #6
pillarsdotnet commentedYou must do what you think is right, of course. But any further progress is going to block on #66484: Allow issues to be filed against multiple versions/branches.
Comment #7
klonosI hear you Bob. The thing is that some maintainers roll patches for both D6 & D7 in one go. They usually file the issue against 7.x and simply leave the 6.x patch be ignored by the bot. This needs to be addressed in a manner that tests both/all patches against their respective core version.
PS: ...issue title change to reflect what actually got fixed.
Comment #8
klonos#1171958: Allow files to be assigned to branch(es)/version(s) and thus tested against it
Comment #10
mile23A bit of a follow-up for the new era of drupalci: #2663018: Useful core branch defaults for contrib CI