Closed
Bug 1394054
Opened 5 years ago
Closed 5 years ago
try push from |./mach try fuzzy| didn't generate any jobs
Categories
(Taskcluster :: General, defect)
Taskcluster
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla57
People
(Reporter: bholley, Assigned: dustin)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Assignee | ||
Comment 1•5 years ago
|
||
The request is for +{ + "tasks":[ + "build-android-checkstyle/opt", + "static-analysis-linux64-st-an/opt", + "test-linux32-stylo/debug-cppunit", + "test-linux32-stylo/debug-crashtest-e10s", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-1", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-10", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-11", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-12", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-13", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-14", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-15", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-16", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-2", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-3", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-4", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-5", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-6", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-7", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-8", + "test-linux32-stylo/debug-mochitest-browser-chrome-e10s-9", ... and I see such mochitest-bc tasks in https://public-artifacts.taskcluster.net/HRjJS-v-SSmRtmpvzy0ssg/0/public/full-task-graph.json but not in https://public-artifacts.taskcluster.net/HRjJS-v-SSmRtmpvzy0ssg/0/public/target-tasks.json So these were removed in the target task phase: [task 2017-08-25T21:02:58.925784Z] Filter filter_target_tasks pruned 7618 tasks (31 remain) Looking at parameters, https://queue.taskcluster.net/v1/task/HRjJS-v-SSmRtmpvzy0ssg/runs/0/artifacts/public/parameters.yml target_task_labels: [] The logic for try falls back to try syntax if there are no labels specified, and blank try syntax just runs the jobs you saw. That logic's changing in bug 1383880. But the question is, why's that value empty.
Assignee | ||
Comment 2•5 years ago
|
||
Ah, it's sparse checkouts -- it didn't check out try_task_config.json.
Assignee | ||
Updated•5 years ago
|
Assignee: nobody → dustin
Comment hidden (mozreview-request) |
Comment 4•5 years ago
|
||
mozreview-review |
Comment on attachment 8901395 [details] Bug 1394054: include try_task_config.json in sparse checkout; https://reviewboard.mozilla.org/r/172858/#review178236
Attachment #8901395 -
Flags: review?(gps) → review+
Pushed by gszorc@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/911140c13de3 include try_task_config.json in sparse checkout; r=gps
Comment 6•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/911140c13de3
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
You need to log in
before you can comment on or make changes to this bug.
Description
•