| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
See https://docs.taskcluster.net/docs/reference/integrations/taskcluster-github/docs/taskcluster-yml-v1#result
|
|
|
|
|
|
|
|
| |
These tasks should be untrusted, since they run before review.
The `repo:github.com/servo/servo:pull-request` role determines what scopes
(permissions) those tasks have.
https://tools.taskcluster.net/auth/roles/repo%3Agithub.com%2Fservo%2Fservo%3Apull-request
|
| |
|
|
|
|
| |
https://bugzilla.mozilla.org/show_bug.cgi?id=1509027
|
|
|
|
| |
I forgot to include this in https://github.com/servo/servo/pull/22381
|
| |
|
|
|
|
|
| |
This is an alternative fix for https://github.com/servo/saltfs/issues/903,
and anticipates adding trychooser support to Taskcluster
|
|
|
|
| |
See for example https://treeherder.allizom.org/#/jobs?repo=servo-try-taskcluster
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is where are kept files whose downloads sometimes fail, so downloading less often will reduce the impact of those failures.
```
> Could not get resource 'https://jcenter.bintray.com/com/android/tools/build/gradle/3.1.3/gradle-3.1.3.pom'.
> Could not GET 'https://jcenter.bintray.com/com/android/tools/build/gradle/3.1.3/gradle-3.1.3.pom'.
> Read timed out
```
https://tools.taskcluster.net/groups/PGuIkH5QQmqghZozhVtmoQ/tasks/CBa6IbLmQJqYgoswRn-hiw/runs/0/logs/public%2Flogs%2Flive.log#L3411
|
| |
|
| |
|
| |
|
|
|
|
| |
https://tools.taskcluster.net/hooks/project-servo/daily
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on the Taskcluster log for
(https://taskcluster-artifacts.net/HkxDh1oKQceXH1fL9RSGow/0/public/logs/live_backing.log),
it looks like the job is running successfully but hitting the max time limit.
Our builds + tests shouldn't take this long to run normally,
but we'll need to set up sccache with cache uploading/downloading
in order to improve most build times.
For now, bump the max run time to 2 hours;
since we complete one build + som tests within an hour,
2 hours should be enough for the second build to finish as well.
|
| |
|
|
|
|
|
| |
We have not yet pushed a :latest tag,
so use the (old) named tag that we have for now.
|
|
|
|
|
|
|
|
|
|
| |
Spawn TC jobs on the following events:
- Pull request opened or reopened
- New commit made in pull request
Spawn TC jobs for pull requests started by anybody,
not just trusted collaborators.
This is safe for now as we do not provide any scopes to spawned jobs.
|
|
Template mostly from https://tools.taskcluster.net/quickstart/. Steps from the
linux-dev builder in etc/ci/buildbot_steps.yml are in taskcluster-test.sh.
|