Closed Bug 1372210 Opened 7 years ago Closed 7 years ago

CoT on generic worker for windows uploads to 'public/logs/' when it should upload to 'public/'

Categories

(Taskcluster :: Workers, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: pmoore)

References

Details

Attachments

(1 file)

Over the weekend I tried to run a windows nightly on `date`.

It failed, with CoT issues (in the signingscriptworker task)...  https://public-artifacts.taskcluster.net/OX49DUwNRveJOSwtIljKdQ/0/public/logs/chain_of_trust.log


If we compare a Linux Build, we see: https://tools.taskcluster.net/task-inspector/#AkjIRRCeSYmYeS7k0_ZOXA/0  has `public/chainOfTrust.json.asc` while a windows (generic-worker) instance [ https://tools.taskcluster.net/task-inspector/#VCQLsQPeTUWSxhkCtCQxaQ/0 ] has `public/logs/chainOfTrust.json.asc`
Nice spot Callek - indeed, this was a different location to docker-worker, and of the two, I think public/chainOfTrust.json.asc is the better artifact name, so adjusting in generic worker.
Assignee: nobody → pmoore
Status: NEW → ASSIGNED
Attachment #8876754 - Flags: review?(dustin)
Attachment #8876754 - Flags: feedback?(aki)
Attachment #8876754 - Flags: feedback?(aki) → feedback+
Attachment #8876754 - Flags: review?(dustin) → review+
Commit pushed to master at https://github.com/taskcluster/generic-worker

https://github.com/taskcluster/generic-worker/commit/fb423538809096208570991a7c03bb5396971eef
Merge pull request #56 from taskcluster/bug1372210

public/logs/chainOfTrust.json.asc => public/chainOfTrust.json.asc
The generic-worker 10.0.5 release is currently deploying on the following worker types:

  * gecko-1-b-win2012-beta
  * gecko-1-b-win2012
  * gecko-2-b-win2012
  * gecko-3-b-win2012
  * gecko-t-win10-64-beta
  * gecko-t-win10-64-cu
  * gecko-t-win10-64-gpu-b
  * gecko-t-win10-64-gpu
  * gecko-t-win7-32-beta
  * gecko-t-win7-32-cu
  * gecko-t-win7-32-gpu-b

The deployment can be monitored in this task group:

  * https://tools.taskcluster.net/task-group-inspector/#/CX99WKPVSiac1-ZFIVVH1Q

Note, the deployments to gecko-t-win10-64, gecko-t-win7-32, gecko-t-win7-32-gpu in this task group were *intentionally* cancelled as we still have some issues to troubleshoot there with the new worker.

Note:

  * All task runs that are claimed before the worker type deployment task complete obviously run with the old worker
  * Task runs that are claimed within 30 minutes of the deployment task completing may run with either an old worker or a new worker
  * All task runs that are claimed 30 minutes after a worker type deployment task completes or later, will be claimed by a newly deployed worker
https://public-artifacts.taskcluster.net/BHQSfBhCQPqsaot94WpRgQ/0/public/chainOfTrust.json.asc
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: Generic-Worker → Workers
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: