add problematic pkgs

This commit is contained in:
Patrick Schratz 2024-11-25 10:05:23 +01:00
commit 1da194471d
Signed by: pat-s
GPG key ID: 3C6318841EF78925

View file

@ -100,8 +100,8 @@ The build metadata is stored in a PostgreSQL database.
The database has a public endpoint at `r-binaries.devxy.io` and port `15432`. The database has a public endpoint at `r-binaries.devxy.io` and port `15432`.
The database contains one table named `single_builds`, which holds the build metadata for each package: The database contains one table named `single_builds`, which holds the build metadata for each package:
| package_name | tag | platform | error_occurred | build_timestamp | build_duration | error | size | | package_name | tag | platform | error_occurred | build_timestamp | build_duration | error | size | removed |
| ------------ | --- | -------- | -------------- | --------------- | -------------- | ----- | ---- | | ------------ | --- | -------- | -------------- | --------------- | -------------- | ----- | ---- | ------- |
Column types: Column types:
@ -113,6 +113,7 @@ Column types:
- `build_duration`: numeric(1000,2) - `build_duration`: numeric(1000,2)
- `error`: text - `error`: text
- `size`: numeric(1000,2) - `size`: numeric(1000,2)
- `removed`: boolean
Alternatively, use `\d+ single_builds`. Alternatively, use `\d+ single_builds`.
@ -186,6 +187,7 @@ These scripts can assist in various situations, such as manually processing pack
## Common Errors ## Common Errors
Below is a collection of raw errors observed during the build process: Below is a collection of raw errors observed during the build process:
<details> <details>
``` ```
@ -229,6 +231,20 @@ Some packages have been intentionally skipped after multiple build attempts.
The reasons for this vary, and ideally, solutions can be found over the long term. The reasons for this vary, and ideally, solutions can be found over the long term.
Contributions to help resolve these issues are highly welcome! Contributions to help resolve these issues are highly welcome!
| Name | Platform | Arch | Reason | Solved via | Date Created | Date Solved |
| ------------- | -------------- | ------- | ------------- | ---------- | ------------ | ----------- |
| Apollonius | redhat-8 | | gmp missing | 2024-11-15 | |
| doBy | alpine-320 | amd | hangs | 2024-11-23 | |
| later | ubuntu 22 & 24 | amd | hangs - xfvb? | 2024-11-23 | |
| CoTiMA | ubuntu 22 & 24 | amd | OOM? | 2024-11-23 | |
| FrF2 | alpine | arm | hangs | 2024-11-23 | |
| FrF2.catlg128 | alpine | arm | hangs | 2024-11-23 | |
| DoE.base | alpine | arm/amd | hangs | 2024-11-23 | |
| eha | alpine | amd | hangs | 2024-11-23 | |
| gRain | alpine | amd | hangs | 2024-11-23 | |
| gRbase | alpine | amd | hangs | 2024-11-24 | |
| IDPmisc | alpine | amd | hangs | 2024-11-24 | |
## CDN Settings ## CDN Settings
A CDN is used in front of the S3 bucket to efficiently distribute the binaries globally. A CDN is used in front of the S3 bucket to efficiently distribute the binaries globally.
@ -236,6 +252,6 @@ A CDN is used in front of the S3 bucket to efficiently distribute the binaries g
A "Perma-Cache" is enabled for three different regions around the world (DE, US, Asia). A "Perma-Cache" is enabled for three different regions around the world (DE, US, Asia).
Once a binary is requested for the first time from a specific location, the asset is copied to the perma-cache and served from there for subsequent requests. Once a binary is requested for the first time from a specific location, the asset is copied to the perma-cache and served from there for subsequent requests.
The `CacheControl = "no-cache"` header is set for all PACKAGES* files to ensure users always receive the latest version, as these files change daily. The `CacheControl = "no-cache"` header is set for all PACKAGES\* files to ensure users always receive the latest version, as these files change daily.
A monthly traffic limit of 50 TB is set on cran.devxy.io to prevent abuse and manage costs. A monthly traffic limit of 50 TB is set on cran.devxy.io to prevent abuse and manage costs.