ai: Add Sentry attachment for JSON parse failure (#1920) #11073
backspaceci.yaml
on: push
AI bot Tests
49s
Boxel UI Tests
3m 18s
Realm Server Tests
15m 55s
Check which packages changed
4s
Matrix: Matrix Client Tests
Boxel Motion Tests
1m 15s
Boxel UI ensure raw icon changes only
43s
Boxel Icons ensure raw icon changes only
1m 14s
Boxel Tools VS Code Extension package
2m 8s
Deploy boxel to staging
/
...
/
Build
2m 1s
Deploy boxel to staging
/
...
/
Build
2m 8s
Deploy boxel to staging
/
...
/
Build
2m 2s
Deploy boxel to staging
/
...
/
Deploy
1m 24s
Deploy boxel to staging
/
...
/
Deploy
3m 30s
Merge Matrix reports and publish
56s
Deploy boxel to staging
/
...
/
Deploy
4m 40s
Deploy boxel to staging
/
...
/
Deploy
4m 1s
Deploy boxel to staging
/
...
/
Deploy
4m 17s
Annotations
53 warnings
|
Check which packages changed
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Boxel UI ensure raw icon changes only
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
AI bot Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Boxel Icons ensure raw icon changes only
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Boxel Motion Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Boxel Tools VS Code Extension package
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Boxel UI Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (9, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (11, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (7, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (12, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (8, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (4, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (6, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (10, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (5, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (2, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (1, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Matrix Client Tests (3, 12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Merge Matrix reports and publish
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Realm Server Tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Deploy boxel-motion / Deploy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Build realm-server Docker image / Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Build pg-migration Docker image / Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Build ai-bot Docker image / Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Deploy boxel-ui / Deploy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Build host / Build
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Deploy host / Deploy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Deploy and run DB migrations / Deploy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Deploy and run DB migrations / Deploy
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy and run DB migrations / Deploy
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy and run DB migrations / Deploy
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy and run DB migrations / Deploy
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy and run DB migrations / Deploy
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy and run DB migrations / Deploy
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy and run DB migrations / Deploy
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy realm server / Deploy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Deploy realm server / Deploy
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy realm server / Deploy
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy realm server / Deploy
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy realm server / Deploy
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy realm server / Deploy
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy realm server / Deploy
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy realm server / Deploy
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy ai-bot to AWS ECS / Deploy
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
Deploy boxel to staging / Deploy ai-bot to AWS ECS / Deploy
Ignoring property 'compatibilities' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy ai-bot to AWS ECS / Deploy
Ignoring property 'taskDefinitionArn' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy ai-bot to AWS ECS / Deploy
Ignoring property 'requiresAttributes' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy ai-bot to AWS ECS / Deploy
Ignoring property 'revision' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy ai-bot to AWS ECS / Deploy
Ignoring property 'status' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy ai-bot to AWS ECS / Deploy
Ignoring property 'registeredAt' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deploy boxel to staging / Deploy ai-bot to AWS ECS / Deploy
Ignoring property 'registeredBy' in the task definition file. This property is returned by the Amazon ECS DescribeTaskDefinition API and may be shown in the ECS console, but it is not a valid field when registering a new task definition. This field can be safely removed from your task definition file.
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "host-dist".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
blob-report-1
Expired
|
3.38 MB |
|
|
blob-report-10
Expired
|
9.26 MB |
|
|
blob-report-11
Expired
|
46.7 KB |
|
|
blob-report-12
Expired
|
55.4 KB |
|
|
blob-report-2
Expired
|
58.4 KB |
|
|
blob-report-3
Expired
|
10.9 MB |
|
|
blob-report-4
Expired
|
58.7 KB |
|
|
blob-report-5
Expired
|
65.6 KB |
|
|
blob-report-6
Expired
|
53.1 KB |
|
|
blob-report-7
Expired
|
51 KB |
|
|
blob-report-8
Expired
|
54.9 KB |
|
|
blob-report-9
Expired
|
49.7 KB |
|
|
host-dist
|
131 MB |
|
|
html-report--attempt-1
|
24.2 MB |
|
|
playwright-traces-1
|
3.32 MB |
|
|
playwright-traces-10
|
9.21 MB |
|
|
playwright-traces-3
|
10.9 MB |
|
|
realm-server-log
|
29.7 KB |
|
|
realm-server-log-1
|
8.55 KB |
|
|
realm-server-log-10
|
6.98 KB |
|
|
realm-server-log-11
|
6.84 KB |
|
|
realm-server-log-12
|
7.51 KB |
|
|
realm-server-log-2
|
7.05 KB |
|
|
realm-server-log-3
|
7.33 KB |
|
|
realm-server-log-4
|
7.28 KB |
|
|
realm-server-log-5
|
7.72 KB |
|
|
realm-server-log-6
|
6.88 KB |
|
|
realm-server-log-7
|
6.9 KB |
|
|
realm-server-log-8
|
6.57 KB |
|
|
realm-server-log-9
|
6.67 KB |
|
|
vscode-boxel-tools
|
3.85 MB |
|